Requirements Traceability Matrix
From ZenWiki
Contents |
Point of Contact
The point of contact for this document during the Spring 2007 semester is Sajjad Mustehsan.
Purpose
This document attempts to bridge the gap between the Software Requirements Specification (SRS) and various parts of the Architecture document. Essentially, the goal of this document is to allow the Zen team members to trace where each requirement listed in the SRS is allocated within the architecture. Such traceability will bring many advantages to the development process. Some of these are as follows:
- Ensure that the architecture is complete i.e. it does not overlook certain software requirements.
- Allow individual owners/developers of components to know what particular functionalities they need to address in the component(s) they are developing.
- Ensure that there are no improper requirements to component mappings within the architecture, for example: to ensure that a single functionality is not accidentally allocated to two components when it can be handled by only one.
- Ensure that each component addresses only the relevant requirements.
Traceability Matrix
Key
Each mapping between a software requirement 'A' and an architectural component 'B' is indicated by a 'X' placed in the cell in row labeled 'A' and column labeled 'B' of the matrix shown below.
Matrix
| SRS Req. ID | Req. Description | Client: Templ. | Client: Auth. | Client: Comm. | Client: Int. Status | Client: Rept. | Client: Data Access Layer | Client: Inst. & Config. | Client: UI Layer | Server: Auth. | Server: SMIG Maint. | Server: Data Access Layer | Server: Comm. | Server: Consol. | Server: UI. | Server: Rept. |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1-1 | The ZEN tool (encompassing the server and the client) shall provide all functionality based upon requirements marked in the SRS as required. | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X |
| 2-1 | The ZEN client shall be able to support an engagement interview. | X | X | X | X | X | ||||||||||
| 2.2-13 | The ZEN client shall provide the user with an interface to perform the interview. | X | ||||||||||||||
| 2.2.1-1 | The ZEN client shall provide the user with a navigation window. (Refer to the usability experiment presented in December 2006) | X | ||||||||||||||
| 2.2.1-2 | The ZEN client shall provide the user with a recording window. (Refer to the usability experiment presented in December 2006) | X | ||||||||||||||
| 2.2.1-3 | The ZEN client shall provide the user with a browsing window. (Refer to the usability experiment presented in December 2006 | X | ||||||||||||||
| 2.2-14 | The ZEN client shall provide the user with the ability to navigate the SMIG. | X | X | |||||||||||||
| 2.2.2-1 | The ZEN client shall provide the user with the ability to switch between the navigation window and the recording window. | X | ||||||||||||||
| 2.2.2-2 | The ZEN client shall provide the user with the ability to search for a specific question. | X | X | |||||||||||||
| 2.2.2-3 | If there is a follow-up question to the current question, the ZEN client shall provide the user with the ability to switch directly to the follow-up question. | X | X | |||||||||||||
| 2.2.2-4 | The ZEN client shall provide the user with the ability to move to the focus area previous to the current. Focus area refers to a UI view. (Refer to the usability experiment presented in December 2006) | X | X | |||||||||||||
| 2.2.2-5 | The ZEN client shall provide the user with the ability to move directly to the top level of the SMIG. | X | X | |||||||||||||
| 2.2.2-6 | The ZEN client shall provide the user with the ability to cycle the recording window through the history of recorded answers. (Refer to the usability experiment presented in December 2006) | X | X | |||||||||||||
| 2.2.2-7 | The ZEN client shall provide the user with the ability to select a question. | X | ||||||||||||||
| 2.2-15 | The ZEN client shall provide the user with the ability to view questions from the SMIG. | X | X | |||||||||||||
| 2.2.3-1 | The ZEN client shall provide the user with the ability to browse a set of questions from the SMIG. | X | X | |||||||||||||
| 2.2.3-2 | The ZEN client shall provide the user with the ability to view a specific question from the SMIG. | X | X | |||||||||||||
| 2.2.3-3 | The ZEN client shall display to the user an overview of the SMIG tree structure. | X | X | |||||||||||||
| 2.2.3-4 | When the user selects a question, the ZEN client shall display the selected question. | X | X | |||||||||||||
| 2.2.3-5 | In the recording window, the ZEN client shall provide the user with the text and all possible answers for the current question. | X | X | |||||||||||||
| 2.2.3-6 | In the recording window, the ZEN client shall provide the user with the text for the risk/mitigation strategy associated with the user's answer (tags and comments not included). | X | X | |||||||||||||
| 2.2-11 | During an interview, the ZEN client shall provide the user with SMIG coverage status. | X | X | |||||||||||||
| 2.2.4-1 | The ZEN client shall calculate the current interview status when the user indicates they are finished with the current question. | X | X | |||||||||||||
| 2.2.4-2 | The ZEN client shall display the interview status to the user. | X | X | X | ||||||||||||
| 2.2-16 | The ZEN client shall provide the user with the ability to record information associated with a specific question. | X | ||||||||||||||
| 2.2.5-1 | In the recording window, if there are answers associated with the current question, the ZEN client shall provide the user with the ability to select an answer to the current question. | X | ||||||||||||||
| 2.2.5-2 | In the recording window, the ZEN client shall provide the user with the ability to enter comments associated to the current question. | X | ||||||||||||||
| 2.2.5-3 | In the recording window, the ZEN client shall provide the user with the ability to apply one or more tags to the current question. | X | ||||||||||||||
| 2.2.5.4 | The ZEN client shall save all data (answer, comments, tags) associated with the current answer when the user indicates they are finished with the current question. | X | X | |||||||||||||
| 3-1 | The ZEN client shall be able to support data transfer and data consolidation. | X | X | X | ||||||||||||
| 3.1-1 | The ZEN client shall be able to send and receive engagement information. | X | X | X | X | X | ||||||||||
| 3.2-1 | The ZEN client shall require authentication for access. | X | X | |||||||||||||
| 3.2-2 | The ZEN client shall allow back-door access in case of a client lockout | X | X | |||||||||||||
| 3.2-3 | The ZEN client shall make available to a user, only that functionality, which is associated with his/her role (e.g. administrator can do things which another user cannot etc.). | X | X | X | ||||||||||||
| 3.3-1 | A browser shall be able to send a request to a ZEN server to consolidate data. | X | X | X | ||||||||||||
| 3.3-2 | After receiving the consolidated data, the ZEN client shall allow a user to change his own data in the client. Once this is done, the next consolidated output from the server shall reflect these changes. | X | X | |||||||||||||
| 3.6-1 | The ZEN client shall be able to create a component template table. | X | X | |||||||||||||
| 3.6-2 | The ZEN client shall be able to create a services template table. | X | X | |||||||||||||
| 3.7-1 | The ZEN client shall be able to allow the user to delete engagement data. | X | X | |||||||||||||
| 3.8-1 | The installation binaries for the ZEN client shall be made available for installation on client machines. | X | X | X | X | X | X | X | ||||||||
| 4-1 | The ZEN client shall be able to generate reports based upon current engagement information residing upon the local client. | X | X | X | ||||||||||||
| 4-4 | The ZEN client shall display the generated report on the computer monitor. | X | ||||||||||||||
| 4-5 | The ZEN client shall allow the user to be able to print the generated report. | X | ||||||||||||||
| 4.1-1 | The ZEN client shall be able to generate the "Current SMIG" report. | X | X | X | ||||||||||||
| 8-1 | The ZEN tool shall support a standard (Internet Explorer-based) web browser interface. | X | ||||||||||||||
| 8.1-1 | A standard browser shall be able to generate reports based upon a single engagement. | X | X | X | ||||||||||||
| 8.1-2 | A standard browser shall be able to generate reports based upon multiple engagements. | X | X | X | ||||||||||||
| 8.1-3 | A standard browser shall allow the user to be able to select a desired report. | X | X | |||||||||||||
| 8.1.1-1 | A standard browser shall allow the user to select the engagements a multi-engagement report is based upon. | X | ||||||||||||||
| 8.1-4 | A standard browser shall generate the report selected by the user. | X | X | X | ||||||||||||
| 8.1-5 | A standard browser shall display the generated report to the web browser. | X | ||||||||||||||
| 8.1-6 | A standard browser shall allow the user to print the displayed report. | X | ||||||||||||||
| 8.1.2-1 | A standard browser shall be able to generate the "Current SMIG" report. | X | X | |||||||||||||
| 8.1.2-2 | A standard browser shall be able to generate the "Draft of Final Report" report. | X | X | |||||||||||||
| 8.1.2-3 | A standard browser shall be able to generate the "List of Questions Per Tag" report. | X | X | |||||||||||||
| 8.1.2-4 | A standard browser shall be able to generate the "Different Types of Risk Summaries Per Engagement" report. | X | X | |||||||||||||
| 8.1.2-5 | A standard browser shall be able to generate the "Different Types of Risk Summaries Across All Engagements" report. | X | X | X | ||||||||||||
| 8.2-1 | A standard browser shall require authentication for access. | X | X | |||||||||||||
| 8.2-2 | A standard browser shall make available to a user, only that functionality, which is associated with his/her role (e.g. administrator can do things which another user cannot etc.). | X | X | X | ||||||||||||
| 8.3-1 | A standard browser shall be able to support SMIG modification. | X | X | X | ||||||||||||
| 8.3.1-1 | A standard browser shall be able to support adding a question to the SMIG. | X | X | X | ||||||||||||
| 8.3.1-2 | A standard browser shall be able to support modifying an existing SMIG question. Modifying includes all SMIG modifications. | X | X | X | ||||||||||||
| 8.3.1-3 | A standard browser shall be able to support marking a SMIG question as no longer active. | X | X | X | ||||||||||||
| 8.4-1 | A standard browser shall allow the user to maintain a default list of tags. | X | ||||||||||||||
| 8.4-2 | A standard browser shall allow the user to generate custom tags per engagement. | X | X | |||||||||||||
| 8.4-3 | A standard browser shall allow the user to select a set of tags and associate them with a particular engagement. | X | X | |||||||||||||
| 8.5-1 | A user shall be able to use a standard web-browser to transfer engagement data (which includes SMIG data, tag data, setup data etc) from the Zen server to a Zen client. | X | X | X | ||||||||||||
| 8.6-1 | A user shall be able to use a standard web-browser to setup a new engagement | X | X | |||||||||||||
| 5-1 | The ZEN tool shall be able to run as a server and perform server activities. | X | X | X | X | X | X | |||||||||
| 5.1-1 | The ZEN server shall be able to receive requests for data transfer and data consolidation. | X | X | |||||||||||||
| 5.2-1 | The ZEN server shall be able to send and receive engagement and SMIG data. | X | X | X | ||||||||||||
| 5.3-1 | The ZEN server shall be able to consolidate engagement data in response to a request. | X | X | X | ||||||||||||
| 5.3-2 | The ZEN Server shall be able to track changes to consolidated data by maintaining different versions of the consolidated output as it happens | X | X | X | ||||||||||||
| 6-1 | The primary development environment for the ZEN tool shall be JAVA. | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X |
| 6-2 | The ZEN tool shall be able to run on a computer using the Windows XP OS. | X | X | X | X | X | X | X | X | |||||||
| 6-3 | The ZEN server shall run on an XP server. | X | X | X | X | X | X | X | ||||||||
| 6-4 | The ZEN server and ZEN client shall use MySQL for database storage. | X | X |
