Download Free Templates http://bigtheme.net/ Websites Templates

 

 

APPENDIX C

Purpose

The objective of the requirements development procedure is to transform identified requirements into a formal software requirement specification document. The result of the formalization procedure is a document, Software Requirements Specifications (SRS), which is used to communicate requirements among all stakeholders.  

Definitions

No

Term

Definition

1

Software Requirement Specification

A Software Requirements Specification (SRS) is a complete description of the behavior of the system to be developed. It includes a set of user cases that describe all of the interactions that the users will have with the software. In addition to user cases, SRS contains functional requirements and nonfunctional requirements.

Entry Criteria (OR)

No

Criteria

Exit Criteria Of

1

Clear Traceable Requirements Approval

RITS_PD_Requirements_Analysis_Procedure

2

Rework From Requirements Validation

RITS_PD_Requirements_Validation_Procedure

3

Calling From Requirements Administration

RITS_PD_Requirements_Administration_Procedure

Inputs

No

Input

Coming from/Output Of

1

Approved Clear Traceable Requirements

RITS_PD_Requirements_Analysis_Procedure

Activities

No

Activity

Responsible

Input

Output

Temp/Form

1

Review the available traceable requirements to gain understanding of the requirements  

AN

Approved Clear Traceable Requirements

Understood Requirements

RITS_PD_

Software_ Requirements_ Specification_ Template

2

Develop and document precise functional requirements  

AN

Approved Clear Traceable Requirements

Developed Functional Requirements

RITS_PD_

Software_ Requirements_ Specification_ Template

3

Develop and document precise non-functional requirements  

AN

Approved Clear Traceable Requirements

Developed Non- functional Requirements

RITS_PD_

Software_ Requirements_ Specification_ Template

4

Develop and document any further related customer specifications

AN

Approved Clear Traceable Requirements

Developed Customer Specifications

RITS_PD_

Software_ Requirements_ Specification_ Template

5

Develop and document precise user interface

AN

Approved Clear Traceable Requirements

Developed User Interface

RITS_PD_

Software_ Requirements_ Specification_ Template

6

Develop and document precise software interface

AN

Approved Clear Traceable Requirements

Developed Software Interface

RITS_PD_

Software_ Requirements_ Specification_ Template

7

Develop and document precise hardware interface

AN

Approved Clear Traceable Requirements

Developed Hardware Interface

RITS_PD_

Software_ Requirements_ Specification_ Template

8

Develop and document precise list of associated product documentation and training material 

AN

Approved Clear Traceable Requirements

Developed Product Documentation and Training material

RITS_PD_

Software_ Requirements_ Specification_ Template

9

Develop and document precise remaining customer requirements such as delivery dates and evolution support

AN

Approved Clear Traceable Requirements

Developed Remaining Customer Requirements 

RITS_PD_

Software_ Requirements_ Specification_ Template

10

Develop and document precise acceptance criteria

AN

Approved Clear Traceable Requirements

Developed Acceptance Criteria

RITS_PD_

Software_ Requirements_ Specification_ Template

11

Develop and document precise methods for validation and verifications

AN

Approved Clear Traceable Requirements

Developed Methods for V & V

RITS_PD_

Software_ Requirements_ Specification_ Template

12

Develop and document precise (if needed) all organizational requirements such as business and cost requirements 

AN

Approved Clear Traceable Requirements

Developed Organizational Requirements

RITS_PD_

Software_ Requirements_ Specification_ Template

13

Develop and document any other required information

AN

Approved Clear Traceable Requirements

Documented Remaining Information

RITS_PD_

Software_ Requirements_ Specification_ Template

14

Update the traceability matrix  and document the traceability and dependency between all requirements.

AN

Clear Traceable Requirements

Updated Clear Traceable Requirements

RITS_PD_ Requirements_ Management_ Form

15

Conduct peer review as per the peer review process and plan.

PR

As per the process

As per the process

As per the process

16

Conduct QA audit as per the QA process and plan.

QAR

As per the process

As per the process

As per the process

17

Conduct CM activities as per the CM process and plan.

CC

As per the process

As per the process

As per the process

18

Collect measurements as per the measurement plan.

MC

As per the process

As per the process

As per the process

19

Monitor the progress as per the PM process and plan.

PM

As per the process

As per the process

As per the process

20

Approve the outputs of the procedure.

PM

Updated Clear Traceable Requirements

Approved Clear Traceable Requirements

 

 

Outputs

No

Output

Going To/Input Of

1

Updated RTM

RITS_PD_Requirements_Validation_Procedure

2

Approved SRS

RITS_PD_Requirements_Validation_Procedure

Exit Criteria (OR)

No

Criteria

Entry Criteria Of

1

SRS Approval

RITS_PD_Requirements_Validation_Procedure

2

Requirements Analysis Rework

RITS_PD_Requirements_Analysis_Procedure

3

Requirements Elicitation Rework

RITS_PD_Requirements_Elicitation_Procedure

4

Requirements Planning Rework

RITS_PD_Requirements_Planning_Procedure

Metrics

These measures can be useful to support the process enactment, or future enactments:

·         Actual versus planned time and effort

Subjects for Review

·         Requirements Traceability Matrix (RTM)

·         Software Requirements Specifications (SRS)

Records

·         None

Configurable Items

·         Requirements Traceability Matrix (RTM)

·         Software Requirements Specifications (SRS)

 

 

 

 

Quality Management System (QMS)