Sample of a Requirements Traceability Matrix

Document Sample
Sample of a Requirements Traceability Matrix Powered By Docstoc
					                                                Revision History
    Date           Version             Author                       Description of Change
  5/15/2009        DRAFT        Jane Doe            Initial draft
                   1.0
  6/20/2009        Final        Jane Doe            Baselined
                   1.0




Requirements Traceability Matrix Template
V 1.0
3/10/2011
                                            Review and Outcome History
    Date           Version          Reviewed by                                    Outcome
  5/20/2009        DRAFT        WAFR Customer Team,   minor editorial modification, needs 001 and 002 were removed
                   1.0          OTIS internal         from consideration. Will be addressed in future system
                                                      releases
  6/15/2009        Final        WAFR Customer Team,   Draft v 1.0 finalized, baselined as Final 1.0
                   1.0          OTIS internal




Requirements Traceability Matrix Template
V 1.0
3/10/2011
                                                                        DEP DIVISION OF WATER RESOURCE MANAGEMENT — WAFR
                                                                           WAFR ENHANCEMENTS — Needs Assessment — v2.30
                                                                           This Worksheet is Provided as an Example Only & is not meant to illustrate a complete set of business needs
                                                                                   Business          Source of Need                Business
  Need ID      Statement of Need                                                   Area              Statement                     Priority        Status               Subject Area         Notes
  001          The user needs to track collection system capacity.                 Wastewater        Needs Assessment              Low             Rejected             Collection Systems
                                                                                                     Interview 3
  002          The user needs to track collection system certifications of         Wastewater        WAFR Functionality            High            Rejected             Collection Systems
               completion.                                                                           Review
  003          The user needs to view the collection system permits                Wastewater        IMS WAFR Status               High            Accepted             Collection Systems
               associated with a wastewater treatment facility.                                      Meeting 2004-06-10

  004          The user needs a link between WAFR facility data and                Wastewater        Needs Assessment              High            Accepted             Compliance and
               COMET projects and activities related to the facility.                                Interview 1                                                        Enforcement

  004.01       The user needs the link between COMET projects and                  Wastewater        WAFR Functionality            High            Accepted             Compliance and
               wastewater facilities to be automated.                                                Review                                                             Enforcement
  005          The user needs to retain the current functionality of the           Wastewater        WAFR Functionality            High            Accepted             Compliance and
               COMET wastewater data reports.                                                        Review                                                             Enforcement
  006          The user needs to retain the existing functionality in the          Wastewater        WAFR Functionality            High            Accepted             Compliance and
               WAFR-DMR web application.                                                             Review                                                             Enforcement
  007          The user needs to retain the existing functionality in the          Wastewater        WAFR Functionality            High            Rejected             Compliance and
               WAFR-DMRLOG web application.                                                          Review                                                             Enforcement
  008          The user needs to view cross-program information about              Wastewater        Needs Assessment              High            Accepted             Compliance and
               permitting and compliance activities                                                  Interview 3                                                        Enforcement
  009          The user needs to retain the current functionality for              Wastewater        WAFR Functionality            High            Accepted             Data Transfer
               transferring E2 monitoring results into WAFR-DMR.                                     Review
  010          The user needs to retain the current functionality of the eIP       Wastewater        WAFR Functionality            High            Accepted             Data Transfer
               process in WAFR and COMET.                                                            Review
  011          The user needs to retain the current functionality for              Wastewater        WAFR ME Types                 High            Accepted             Data Transfer
               uploading NPDES Stormwater data to EPA's PCS database.                                Decision Meeting
                                                                                                     4/26/04
  012          The user needs to retain the current functionality for              Wastewater        WAFR Functionality            High            Accepted             Data Transfer
               transferring WAFR facility information into E2.                                       Review
  013          The user needs to retain the current functionality for              Wastewater        WAFR Functionality            High            Accepted             Data Transfer
               transferring WAFR permit requirements to the EDMR data                                Review
               transfer tables.
  014          The user needs to retain the current Permit Builder                 Wastewater        WAFR Functionality            High            Accepted             Data Transfer
               Transfer Process for loading data from Permit Builder into                            Review
               WAFR.
  015                                                                              Wastewater        WAFR Functionality            High            Accepted             Related Party
             The user needs to be able to enter different mailing addresses
                                                                                                     Review
             for the same individual with different roles.
  016        The user needs the ability to limit each individual or                Wastewater        WAFR Functionality            High            Accepted             Related Party
             organization to only one mailing address per role.                                      Review
  017        The user needs the city field in a mailing address verified           Wastewater        WAFR Functionality            High            Accepted             General
             against county and zip code.                                                            Review
  018                                                                              Wastewater                                      High            Accepted             Facility Inventory
             The user needs the following Managed Entity types in the                              WAFR ME Types Decision
             core database: 'Wastewater Facility' , 'NPDES Stormwater                              Meeting 4/26/04; WAFR
             Facility', 'Wastewater Residuals Application Site', and                              Integration Status Meeting
             'Wastewater Collection System'.                                                             on 07/08/04.


WAFR ENHANCEMENTS
NEEDS V 2.30                                                                                                               Page 3 of 12                                                              febfa74f-013f-4fd5-8d64-507b0ffb0156.xlsx
                                                                                                   DEP DIVISION OF WATER RESOURCE MANAGEMENT — WAFR
                                                                                                        WAFR ENHANCEMENTS — Requirements — v2.30
                                                                                         This Worksheet is Provided as an Example Only & is not meant to illustrate a complete set of requirements

                                                                   Requirement                                                                                   Implementa-                         Use
    Requirement                                                        No.         Need(s)            Requirement Type              Addressed by                  tion Priority       Timeframe      Case(s)   Testability   Notes
    The system shall provide a link between a wastewater             REQ-001       004                External Interface            DEP                                 2             2010 - Q1      N/A       Test Plan
    managed entity and the associated COMET projects and
    activities.
                                                                    REQ-002        004, 004.01        Functional Requirement        Vendor                              1             2009 - Q4      N/A       Test Plan
    The system shall allow the user to establish a link between
    a wastewater managed entity and environmental interest
    and the associated COMET project.
    The DMRENTRY system shall function with data from the           REQ-003        005                External Interface            Both                                1             2009 - Q4      N/A       Test Plan
    FDM and integrated WAFR databases.
    The DMRLOG system shall function with data from the FDM         REQ-004        006                External Interface            TBD                                 1             2009 - Q4      UC-001    Test Plan
    and integrated WAFR databases.
    The system shall allow the user to insert only one mailing      REQ-005      015, 016             Data Definition               DEP                                 1             2009 - Q4      UC-002    Test Plan
    address for an individual.
    The system shall verify City values in addresses located in     REQ-006        017                Data Definition               DEP                                 1             2009 - Q4      UC-002    Test Plan
    Florida against County and Zip Code.
    The system shall include the Managed Entity Type Code           REQ-007        018                Data Definition               DEP                                 1             2009 - Q4      N/A       Inspection
    values defined in the FIESTA WAFR Integration Code Values
    document.
    The display of date fields on forms shall conform to the IMS    REQ-008        N/A                Design Constraint             Both                                1             2009 - Q4      N/A       Inspection
    Oracle Forms Guidance document.
    ….                                                                 ….          ….




Requirements Traceability Matrix Template
V 1.0
3/10/2011                                                                                                                                 Page 4 of 12                                                                       febfa74f-013f-4fd5-8d64-507b0ffb0156.xlsx
                                            Requirement                                                  Implementa-                  Use
    Requirement                                 No.       Need(s)   Requirement Type   Addressed by       tion Priority   Timeframe   Case(s)   Testability   Notes




Requirements Traceability Matrix Template
V 1.0
3/10/2011                                                                                 Page 5 of 12                                                        febfa74f-013f-4fd5-8d64-507b0ffb0156.xlsx
                                            Requirement                                                  Implementa-                  Use
    Requirement                                 No.       Need(s)   Requirement Type   Addressed by       tion Priority   Timeframe   Case(s)   Testability   Notes




Requirements Traceability Matrix Template
V 1.0
3/10/2011                                                                                 Page 6 of 12                                                        febfa74f-013f-4fd5-8d64-507b0ffb0156.xlsx
                                            Requirement                                                  Implementa-                  Use
    Requirement                                 No.       Need(s)   Requirement Type   Addressed by       tion Priority   Timeframe   Case(s)   Testability   Notes




Requirements Traceability Matrix Template
V 1.0
3/10/2011                                                                                 Page 7 of 12                                                        febfa74f-013f-4fd5-8d64-507b0ffb0156.xlsx
                 Business                                                                                                                                                                                                                                                        Implementation   Testability
Business Areas   Priorities   Statuses          Subject Areas                        Use Cases                                                                    Requirement Types                                                                               Addressed by   Priorities       Methods
   Name             Name         Name              Name             ID       Name          Primary Actor               Name                         Notes                                                                                                           Name           Name              Name
   Wastewater       High         Proposed          Collection       N/A      N/A           N/A                         Business Requirement         A business requirement states a high-level business objective. It should answer the question: “Why are we       DEP            1                 Test Plan
                                                   Systems                                                                                          devoting resources to this requirement?”

                                                                                                                                                    Categories:
                                                                                                                                                    • Financial benefits such as reduced costs, increased revenue, enhanced market share
                                                                                                                                                    • Improvements in business operations
                                                                                                                                                    • Strategic positioning or brand enhancement
                                                                                                                                                    • Regulatory compliance
                    Medium       Under Review      Compliance       UC-001   UC-001 NAME   Public User or Admin User   Business Rule                A business rule is an organization policy, industry standard, or law or government regulation that defines,     Vendor         2                 Demonstration
                                                   and                                                                                              constrains, or governs some aspect of the business. Most business rules exist independently from a
                                                   Enforcement                                                                                      specific software system (that is, they are not software requirements), should be treated as an enterprise-
                                                                                                                                                    level asset, and should be documented separately from system-specific requirements. A business rule can
                                                                                                                                                    lead to various sets of functional requirements.

                                                                                                                                                    Business rule sub-types include:
                                                                                                                                                    • Action Enabler: describes an action to be taken when a condition is true, usually written as an “if-then”
                                                                                                                                                    or “when-then” statement (for example, “If the customer has an active membership, then display
                                                                                                                                                    membership rates”)
                                                                                                                                                    • Business Constraint: a policy (whether determined by management or an external regulatory agency)
                                                                                                                                                    that limits what the system or an actor within the system can do.
                                                                                                                                                    • Computation, Calculation, or Formula: self-explanatory (for example, “The total price shall be
                                                                                                                                                    calculated as …”).
                                                                                                                                                    • Fact: a simple factual statement, often associated with data attributes (for example, “Each customer has
                                                                                                                                                    a unique customer number”).
                                                                                                                                                    • Inference: describes a change to the status of data, usually written as an “if-then” statement (for
                                                                                                                                                    example, “If the customer does not pay for the reservation by the payment due date, then change the
                                                                                                                                                    reservation status to canceled” ).

                    Low          Accepted          Data Transfer    UC-002   UC-002 NAME   Public User                 Data Definition              Information that the system will Create, Read, Update, and/or Delete (CRUD). Typically this includes the        Both           3                 Simulation
                                                                                                                                                    name of a business object, its attributes, rules, and CRUD functions.
                                 Rejected          Facility         UC-003   UC-003 NAME   Admin User                  Design Constraint            A limitation of the solution or of its implementation. Examples:                                                TBD            99                Inspection
                                                   Inventory                                                                                        • “Funding for this project is only $5,000.”
                                                                                                                                                    • “The UI has to be compatible with the following web browsers: …”
                                                                                                                                                    • “Coding must be in Java.”
                                                   Financial        UC-004   UC-004 NAME   Public User or Admin User   External Interface           An interface between the system and the outside world. There are four types of external interfaces:             N/A                              Analysis

                                                                                                                                                    • User interface
                                                                                                                                                    • Hardware
                                                                                                                                                    • Software
                                                                                                                                                    • Communication

                                                   General          UC-005   UC-005 NAME   Public User                 Functional Requirement       A single statement of one individual function. Sometimes referred to as TSS statements: “The system
                                                                                                                                                    shall …” Functional requirements and other types of requirements information typically are embedded in
                                                                                                                                                    the software requirements specification (SRS) document.
                                                   Navigation       UC-006   UC-006 NAME   Admin User                  Quality Attribute            A quality characteristic that the system should possess. Sometimes referred to as quality factors or
                                                                                                                                                    quality of service requirements. Examples:

                                                                                                                                                    • Performance
                                                                                                                                                    • Reliability
                                                                                                                                                    • Scalability
                                                                                                                                                    • Security
                                                                                                                                                    • Redundancy
                                                                                                                                                    • Backup requirements
                                                                                                                                                    • Usability
                                                                                                                                                    • Availability
                                                   Permitting       UC-007   UC-007 NAME   Public User or Admin User   Solution Idea                A solution and/or statement of design. Usually stated by a business stakeholder, development or
                                                                                                                                                    implementaton team member, or even by the BA during project initiation or analysis. Examples:

                                                                                                                                                    • “We’ll need a new server for this application refresh.”
                                                                                                                                                    • “The public will have to book reservations only through the online system.”

                                                                                                                                                    It’s usually best to work backwards from a solution idea to identify the underlying business requirement:
                                                                                                                                                    “What problem are we trying to solve?”

                                                   Queries          UC-008   UC-008 NAME   Public User                 Use Case or Usage Scenario   Describes a process (collection of individual steps). Examples (possible use case name is underlined):

                                                                                                                                                    • “Users will be able to post payments to customer accounts.”
                                                                                                                                                    • “Users will be able to run accounts receivable agings reports.”

                                                                                                                                                    If starting from a use case or usage scenario requirement, it can be used as a way to identify functional
                                                                                                                                                    requirements. Its name should always start with an action verb.

                                                   Related Party    UC-009   UC-009 NAME   Admin User
                                                   Reports          UC-010   UC-010 NAME   Public User or Admin User
                                                   Site Inventory

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:487
posted:11/15/2011
language:English
pages:12