For detail regarding the practice of Requirements Management,

please refer to the Requirements Management Practices Guide

Instructions For Completing This Document

1.) Complete the Project Name, C/I/O, Project Manager Name, and Project
Description fields
2.) For each issue identified, complete the following:
ID: A unique ID number used to identify the traceability item in the
requirements traceability matrix.
Associated ID(s): This column should contain the ID of any
associated utilities used for requirements tracking such as a
repository, pipeline document, etc.
Technical Assumption(s) or Customer Need(s): This column
should be populated with a description of the technical assumption
or customer need linked to the functional requirement.

Functional Requirement: This column should be populated with a

description of the functional requirement.
Status: This column should be populated with the current status of
the functional requirement.
Architectural/Design Document: This column should be
populated with a description of the architectural/design document
linked to the functional requirement.
Technical Specification: This column should be populated with a
description of the technical specification linked to the functional
requirement.
System Component(s): This column should be populated with a
description of the system component(s) linked to the functional
requirement.
Software Module(s): This column should be populated with a
description of the software module(s) linked to the functional
requirement.
Test Case Number: This column should be populated with the test
case number linked to the functional requirement.
Tested In: This column should be populated with the module that
the functional requirement has been tested in.
Implemented In: This column should be populated with the module
that the functional requirement has been implemented in.

Verification: This column should be populated with a description of

the verification document linked to the functional requirement.

Additional Comments: This column should be populated with any

additional comments
REQUIREMENTS TRACEABILITY MATRIX
Project Name:
Project Manager Name:
Project Description:
Linked to Other
Assoc Functional Architectural/Design Technical
ID Requirements (Provide Use Case
ID Requirement Document Specification
Reqt ID #)
001 1.1 Ability to auto synch with gas meter 1.2 IDENTIFY and DOCUMENT From the functional requirements, the elements
002 Synch Meter 4,7,9,11 required in the API is identified (commands,
1. MAIN FUNCTIONS (Synch functions, protocols, objects)
003 Meter), Sub-systems (e.g.
004 Read Meter; Measure Flow Mobile APIs, such as the iOS API, provide
Detection), and commands for detecting touchscreen input, such
005 1.2 Ability to read every 24 hrs at 12:01 a.m. Synch Meter as tapping, swinping and rotating. It also includes
common user interface elements, such as a pop-
006 Read Measure up keyboard, a search bar, and a tab bar, which
007 Meter Flow provides navigation buttons the bottom of the
2. Architectural Impact : screen. The iOS API also includes predefined
008 functions for interacting with an iOS device's
009 APPLICATION ARCHITECTURE Interface hardware, such as the camera, microphone, or
Impact speakers.
010 (e.g. Is there a Move or Add or Change
required by the project of any one of
011
the following : application interface, Pseudo code can be provided
012 web interface, data interface? net new
function?
013
014 INEGRATION ARCHITECTURE
Is there a Move or Add or CHange of
015 software on a gateway; SOA;
016
messaging; API; EAI; connector
component?
017
DATA ARCHITECTURE
018 Net new object? Net new data? I
019 s there a Move or Add of a data source
required by the project, OR, is there a
020 change to an interface in a system other
021
than the source of truth?

022 SECURITY ARCHITECTURE

Is there a Move or Add of
023 Authentication or Authorization
024 interfaces or servers required by the
project?
025
026 i.e. Is there an impact to Security
Architecture? The softwa
027 structure o
028 comprise s
visible prop
029
relationship
030
031
032
033
034

UP Template Version: 11/30/06 Page 2 of 4

 <optional>
<required>
<required>

System Test Case

Tested In Vadlidation
Component(s) Number

Decompose sub-systems 6.1.4. User accesses subscriber This column should be populated with This column should be populated
into components. gas reading and autopopulates the module that the functional with a description of the
Read billing requirement has been tested in. validation document linked to
Meter the functional requirement.

Link requirements with specific hardware or

software components in the system which are
used to implement the requirement

Component
Decomposition (Syntax and Semantics)
(participating classes; method invocation;message
queue
event notification
process (threaded object) )

The software architecture of a system is the

structure or structures of the system, which
comprise software elements, the externally
visible properties of those elements, and the
relationships among them (this is tracing)

UP Template Version: 11/30/06 Page 3 of 4

 Additional
Comments

lated
to

UP Template Version: 11/30/06 Page 4 of 4