Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Resource Guide How to use this workbook and links to key resources on the NPI wiki
Lite Job Jar Efforts ONLY Describe the project overview, business case, and process details
Business Requirements Document, prioritize, and track both high-level and detailed business requirements
Issues & Questions Track issues and questions related to the solution requirements
Reference View and/or edit category, sub-category, and source look-up values
Glossary Define terms and applications specific to your project in this worksheet
Page 1 of 10
ND
General
Priority
1,2,3,4
Sub-Category
General
CTA-B001.01.01
CTA-B001.02
ND
ND
General
General
H
H
1
1
CTA-B001.03
ND
General
CTA-B001.04
ND
General
CTA-B001.05
ND
General
New for
ITAM
Factory
(Y/N)
Requirement Description
Supporting Information
N
Croatia will be set up with 2 samples for weighting. One
sample contains all homes, including test homes. The
other sample only includes the homes for reporting.
Ops Console
CTA-B002.02
FE
Ops Console
CTA-B002.03
FE
Ops Console
CTA-B002.04
FE
Monitoring
CTA-B002.05
FE
Monitoring
Input
CTA-B003.02
Output
Produce 1 set of SV, Family Intab, and Control Files for the For environments with multiple samples, the set to be
production environment.
provided should correspond to the main sample for that
environment.
Output
CTA-B003.04
FE
Output
CTA-B003.05
FE
Output
CTA-B003.06
Output
Ingestion Section
CTA-B004.01
ND
Ingestion Rules
FE
Ingestion Rules
CTA-B004.01.01a FE
Ingestion Rules
CTA-B004.01.01
4/10/2013
X Proposed
4/10/2013
X
X
X Proposed
X Proposed
4/10/2013
9/3/2013
X Proposed
4/10/2013
X Proposed
4/10/2013
X Proposed
4/10/2013
X Proposed
9/3/2013
X Proposed
9/3/2013
X Proposed
9/3/2013
X Proposed
9/3/2013
Proposed
9/3/2013
X Proposed
9/3/2013
Proposed
9/3/2013
Proposed
9/3/2013
Proposed
9/3/2013
Proposed
9/3/2013
Proposed
9/3/2013
Proposed
9/3/2013
Proposed
9/3/2013
Proposed
9/3/2013
Proposed
4/10/2013
Status
Status Notes
N
N
N
FE
X Proposed
N
N
Reprocessing
CTA-B003.03
X
N
CTA-B001.06
ND
Ops Console & Monitoring
CTA-B002.01
ND
FE
Source
Ops Console
CTA-B001.01
ND
Ingestion
CTA-B001
Level
Business Requirement
ID
Type
N
N
N
N
N
N
N
N
To be confirmed.
To be confirmed. Note: Raw data files provided to
clients.
Y
N
N
N
N
Page 2 of 10
Ingestion Rules
CTA-B004.01.01c A
Ingestion Rules
CTA-B004.01.01d A
Ingestion Rules
CTA-B004.01.02
FE
Ingestion Rules
CTA-B004.01.03
FE
Ingestion Rules
CTA-B004.01.04
FE
Ingestion Rules
CTA-B004.01.05
FE
Ingestion Rules
CTA-B004.01.06
FE
Ingestion Rules
CTA-B004.01.07
Ingestion Rules
CTA-B004.01.08
FE
Ingestion Rules
CTA-B004.01.09
FE
Ingestion Rules
CTA-B004.01.10
FE
Ingestion Rules
To be confirmed.
To be confirmed.
No new Event Codes will be provided than what is
already defined within ITAM Factory.
N
N
N
N
N
N
Example: LongTVOn
N
Prevelance of a Minute Rule
Recrediting
Weighting
CTA-B006.01
FE
Weighting
Non-Functional Requirements
CTA-B007.01
FE Non-Functional
CTA-B007.02
9/3/2013
Proposed
9/3/2013
Proposed
9/3/2013
Proposed
9/3/2013
Proposed
9/3/2013
Proposed
9/3/2013
Proposed
9/3/2013
Proposed
9/3/2013
Proposed
4/10/2013
Proposed
9/3/2013
Proposed
9/3/2013
Proposed
9/3/2013
Proposed
9/3/2013
Proposed
9/3/2013
X Proposed
9/3/2013
FE
Non-Functional
Proposed
Recrediting
CTA-B005.01
FE
N
Kelli Frazier
Proposed
4/10/2013
Page 3 of 10
ID Type
1
2
3
Description
Date Assigned
Assigned to
Target
Resolution Date
Status
Resolution
Resolved By
Page 4 of 10
BR Category
BR Sub-Category
BR Sources
Input
Output
Gap Rules
Family Rejection Rules
Individual Rejection Rules
Guest Rejection Rules
Statement Rejection Rules
Source 1
Source 2
Source 3
Source 4
Source 5
Source 6
Source 7
Source 8
Source 9
Source 10
Source 11
Source 12
Source 13
Source 14
Source 15
Source 16
Source 17
FE/ND - Accuracy
FE/ND - Business Process
FE/ND - Data Requirements
FE/ND - Entities
FE/ND - Hierarchy
FE/ND - Performance
FE/ND - Ranking
FE/ND - Reporting
FE/ND - Roll-ups
FE/ND - Trade-off
Category 1
Category 2
Category 3
Category 4
Category 5
Category 6
Category 7
Category 8
Category 9
Category 10
Category 11
Category 12
Category 13
Category 14
Category 15
Category 16
Category 17
Category 18
Category 19
Category 20
Category 21
Category 22
Category 23
Non-Functional
Close
Reprocessing
General
Ingestion Rules
Monitoring
Sub-Catgory 24
Sub-Catgory 25
Sub-Catgory 26
Sub-Catgory 27
Sub-Catgory 28
Sub-Catgory 29
Sub-Catgory 30
Sub-Catgory 31
Sub-Catgory 32
Sub-Catgory 33
Sub-Catgory 34
Sub-Catgory 35
Sub-Catgory 36
Sub-Catgory 37
Sub-Catgory 38
Sub-Catgory 39
Sub-Catgory 40
Sub-Catgory 41
Sub-Catgory 42
Sub-Catgory 43
Sub-Catgory 44
Sub-Catgory 45
Sub-Catgory 46
Sub-Catgory 47
Sub-Catgory 48
Sub-Catgory 49
Sub-Catgory 50
Source 18
Source 19
Source 20
Source 21
Source 22
Source 23
Source 24
Source 25
Source 26
Source 27
Source 28
Source 29
Source 30
Source 31
Source 32
Source 33
Source 34
Source 35
Source 36
Source 37
Source 38
Source 39
Source 40
Source 41
Source 42
Source 43
Source 44
Source 45
Source 46
Source 47
Source 48
Source 49
Source 50
Notes
5 of 10
Sub-Catgory 51
Sub-Catgory 52
Sub-Catgory 53
Sub-Catgory 54
Sub-Catgory 55
Sub-Catgory 56
Sub-Catgory 57
Sub-Catgory 58
Sub-Catgory 59
Sub-Catgory 60
Sub-Catgory 61
Sub-Catgory 62
Sub-Catgory 63
Sub-Catgory 64
Sub-Catgory 65
Sub-Catgory 66
Sub-Catgory 67
Sub-Catgory 68
Sub-Catgory 69
Sub-Catgory 70
Sub-Catgory 71
Sub-Catgory 72
Sub-Catgory 73
Sub-Catgory 74
Sub-Catgory 75
Sub-Catgory 76
Sub-Catgory 77
Sub-Catgory 78
Sub-Catgory 79
Sub-Catgory 80
Sub-Catgory 81
Sub-Catgory 82
Sub-Catgory 83
Sub-Catgory 84
Sub-Catgory 85
Sub-Catgory 86
Sub-Catgory 87
Sub-Catgory 88
Sub-Catgory 89
Sub-Catgory 90
Sub-Catgory 91
Sub-Catgory 92
Sub-Catgory 93
Sub-Catgory 94
Sub-Catgory 95
Sub-Catgory 96
Sub-Catgory 97
Sub-Catgory 98
Sub-Catgory 99
Sub-Catgory 100
6 of 10
Glossary of Terms
Term
Maintain
Process
Pluggable
SLA
Definition
For the purposes of this document 'maintain' means provide the ability to create, read, update and delete data elements.
For the purposes of this document 'process' means extract, translate and use data.
Algorithms should be "pluggable". For example: If a better distance calculation is discovered, we want to use it without code changes.
Service Level Agreement - Contract signed with the client to provide a specified level of service.
Impacted Apps
ISM
Integrated Sample Management
NOL
Nielsen Online
MSM
Metered Sample Management
E&T
Engineering & Technology
Page 7 of 10
Project Overview
<<enter description here . . . row height can be adjusted to accommodate your entry>>
Business Case
Provide the details supporting the business case for the project (include information pertaining to clients and customers).
<<enter description here . . . row height can be adjusted to accommodate your entry>>
Process Details
Describe and/or map the process(es), identifying problems, possible ways to overcome the problems, and impacted functional areas (include current/as is process and to be process as appropriate.
TIP: Value Stream Mapping (VSM) may be used to document the detailed as-is process flow for each of the business functionalities. See the BPI Toolkit for more details.
<<enter description here . . . row height can be adjusted to accommodate your entry>>
<<paste flows, pictures, and other diagrams to this or any new worksheet>>
Resource Guide
Definitions
This wiki page provides a set of definitions for they different types of business requirements.
Elicitation Questions
This wiki page provides a list of common questions that can be used to elicit business requirements from customers to help drive them to completion.
Assessing Requirements
This wiki page provides a list of traits that can be used to assess the quality and completeness of Business Requirements Spreadsheet (BRS).
Best Practices
This wiki page provides methods or techniques that have consistently shown results superior to those achieved with other means, and that are used as
benchmarks for requirements management.
Use this worksheet to document process details such as current/as is process overviews & diagrams and to be process overviews & diagrams.
Business Requirement ID
Type
indicates if a requirements is an Assumption (A), Business Rule (BRL), Constraint (C), Feature (FE), or Need (ND); this is a
drop-down field with standardized values to be used
Category
indicates the area within the type of requirement being addressed; this is a drop-down field with pre-set values and values
that can be customized (see Reference worksheet instructions below)
Sub-Category
indicates the sub-area within the type of requirement being addressed; this is a drop-down field with pre-set values and
values that can be customized (see Reference worksheet instructions below)
Level
Priority
indicates the importance of including/fulfilling the requirement; this is a drop-down field with standardardized values to be
used
Requirement Description
Supporting Information
to provide rationale, comments, or examples; be sure to document any dependencies in this field
Acceptance Criteria
Source
Area 1 - 10
functional areas and products the requirement applies to; replace the placeholder labels with the actual functional area or
product; add more columns if needed
Status
indicates where a requirement is in the requirements management process; this is a drop-down field with standardized
values to be used
Status Notes
Approval Date
Last Updated
Use this worksheet to document and track issues and questions related to the business requirements. The type and status fields are drop-down fields with
standardized values to be used. Type can be either I (Issue) or Q (Question).
Reference
Use this worksheet to update the drop-down list values for the Category & Sub-category and to document the Sources; to add a Category or Sub-Category
value, just type over one of the placeholder values (Category 1, 2, 3, . . . ).
Glossary
Use this worksheet to outline standard operational definitions to be used in the requirements documentation for this project.
Approvals