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

 

 

APPENDIX C

Purpose

The objective of the elicitation procedure is to discover and capture candidate software requirements (both functional and non-functional) by communicating with the customer and/or end users and others who have stake in the system development. There are several techniques to elicit requirements, which include brainstorming, interviews, questionnaires and focus groups.

Definitions

No

Term

Definition

1

Functional Requirements

Functional requirements define the internal workings of the software. That is, the calculations, technical details, data manipulation, data processing, and other specific functionality that show how the required behavior is to be satisfied. They are supported by non-functional requirements, which impose constraints on the design or implementation (such as performance requirements, quality standards, or design constraints).

2

Non-Functional Requirements

Non-functional requirements are requirements which specify criteria that can be used to judge the operation of a system, rather than specific behaviors. This should be contrasted with functional requirements that specify specific behavior or functions. Typical non-functional requirements are reliability, scalability, and cost. Other terms for non-functional requirements are ‘quality attributes’ and ‘quality of service requirements’.

Entry Criteria

No

Criteria

Exit Criteria Of

1

Requirements Elicitation Plan Approval

RITS_PD_Requirements_Planning_Procedure

Inputs

No

Input

Coming from/Output Of

1

Approved Requirements Elicitation Plan

RITS_PD_Requirements_Planning_Procedure

Activities

No

Activity

Responsible

Input

Output

Temp/Form

1

Acquire the application domain knowledge, knowledge about the target organization and specific problem knowledge.

AN

Requirements Elicitation Plan

Acquired knowledge

 

2

Identify candidate functional requirements. Each requirement is captured along with its rationale (if possible). The requirements may be arbitrary broken down into sub-groups to facilitate collection.

AN

Requirements Elicitation Plan

Identified functional Requirements

 

3

Record functional requirements in the requirements database and procedures to establish traceability are activated at this point.

AN

Requirements Elicitation Plan

Documented Requirements

RITS_PD_ Requirements_ Management_ Form

4

Identify candidate non-functional requirements. Each requirement is captured along with its rationale (if possible). The requirements may be arbitrary broken down into sub-groups to facilitate collection.

AN

Requirements Elicitation Plan

Identified Non-functional Requirements

 

5

Record non-functional requirements in the requirements database and procedures to establish traceability are activated at this point.

AN

Requirements Elicitation Plan

Documented Requirements

RITS_PD_ Requirements_ Management_ Form

6

Repeat the previous two steps for any other types of requirements.

AN

Requirements Elicitation Plan

Documented Requirements

RITS_PD_ Requirements_ Management_ Form

7

Review the documented requirements.

PM

Documented Requirements

Updated Documented Requirements

 

8

Add outputs to the CM repository.

AN

Updated Documented Requirements

Stored Documented Requirements

 

9

Collect measurements as per the identified metrics below.

PM

Stored Requirements Elicitation Plan

Measurements

 

10

Monitor the progress.

PM

Measurements

Deviations

 

11

Approve the outputs of the procedure

PM

Documented Candidate Requirements

Approved Candidate Requirements

 

Outputs

No

Output

Going To/Input Of

1

Approved Candidate Requirements

RITS_PD_Requirements_Analysis_Procedure

RITS_PD_Requirements_Administration_Procedure

RITS_PD_Development_Planning_Procedure

RITS_PR_Planning_Procedure

RITS_QA_Planning_Procedure

RITS_CM_Planning_Procedure

RITS_PM_Estimatation_Procedure

Exit Criteria (OR)

No

Criteria

Entry Criteria Of

1

Candidate Requirements Approval

RITS_PD_Planning_Procedure

RITS_PR_Planning_Procedure

RITS_QA_Planning_Procedure

RITS_CM_Planning_Procedure

RITS_PM_Estimatation_Procedure

2

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

·         Size of requirements, which can be measured in one of the following:

o   Number of use cases

o   Number of functional requirements

o   Number of non-functional requirements

Subjects for Review

·         Candidate Requirements

Records

·         MOM

·         Approvals (such as e-mails)

Configurable Items

·         Requirements Database

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Quality Management System (QMS)