Requirements Development and Management

Requirements Engineering Processes

Requirements Engineering

Elicitation Analysis Specification Validation

Requirements Development Requirements Management

Requirements Engineering Process

04/07/55

Requirements Engineering Processes

y Processes used to discover, analyse

Requirements engineering processes

y The processes used for RE vary widely depending on the

and validate system requirements

application domain, the people involved and the organisation developing the requirements y However, there are a number of generic activities common to all processes
y Requirements elicitation y Requirements analysis y Requirement specification y Requirements validation y Requirements management

Requirements Engineering Process

7/4/2012

Requirements Engineering Process

7/4/2012

The requirements engineering process

Feasibility studies
y For each new system RE starts with this study y A feasibility study decides whether or not the proposed

system is worthwhile y A short focused study that checks

y If the system contributes to organisational objectives y If the system can be engineered using current technology and

within budget y If the system can be integrated with other systems that are used

Requirements Engineering Process

7/4/2012

Requirements Engineering Process

7/4/2012

Feasibility study implementation

y Based on information assessment (what is required),

Requirements Elicitation
y Sometimes called requirements elicitation or requirements

information collection and report writing y Questions for people in the organisation
y What if the system wasnt implemented? y What are current process problems? y How will the proposed system help? y What will be the integration problems? y Is new technology needed? What skills? y What facilities must be supported by the proposed system?

discovery y Involves technical staff working with customers to find out about the application domain, the services that the system should provide and the systems operational constraints y May involve end-users, managers, engineers involved in maintenance, domain experts, trade unions, etc. These are called stakeholders

Requirements Engineering Process

7/4/2012

Requirements Engineering Process

7/4/2012

Requirements Elicitation Process

y Define requirement development process. y Write a vision and scope document. y Identify user class and their characteristics. y Select product champions for each user class. y Establish focus groups of typical users. y Work with user representatives to identify use cases. y Identify system events and responses. y Hold facilitated elicitation workshop. y Observe users performing their jobs. y Examine problem reports of current systems for

Requirements Analysis
y Involves refining the requirements to ensure that all

requirement ideas. y Reuse requirements across projects. Requirements Engineering Process

stakeholders understand them and scrutinizing them for error. y Analysis includes decomposing high-level requirements into details, building prototype, evaluating feasibility, and negotiating priorities. y The goal is to develop requirements of sufficient quality and detail that manager can construct realistic project estimates and technical staff can proceed with design, construction, and testing.
7/4/2012 10 Requirements Engineering Process 7/4/2012

Problems of requirements analysis

y Stakeholders dont know what they really want y Stakeholders express requirements in their own terms y Different stakeholders may have conflicting requirements y Organisational and political factors may influence the system

Requirements Analysis Process

y Draw a context diagram. y Create user interface and technical prototype. y Analyze requirements feasibility. y Prioritize the requirements. y Model the requirements. y Create a data dictionary. y Allocate requirements to subsystems. y Apply quality function deployment.

requirements y The requirements change during the analysis process. New stakeholders may emerge and the business environment changes

11

Requirements Engineering Process

7/4/2012

12

Requirements Engineering Process

7/4/2012

Requirements Specification
y Requirements specification is to document the user

Requirements Specification Process

y Adopt and SRS template. y Identify sources of requirements. y Uniquely label each requirement. y Record business rules. y Specify quality attributes.

requirements in some consistent, accessible, and reviewable way. y The document is called Software Requirements Specification (SRS). y It contains the detailed software functional and nonfunctional requirements

13

Requirements Engineering Process

7/4/2012

14

Requirements Engineering Process

7/4/2012

Requirements Validation
y Validation ensures that the requirement statements are

Requirements Validation Process

y Inspect requirements documents. y Test the requirements. y Define acceptance criteria.

correct, demonstrate the desired quality characteristics, and will satisfy customer needs. y Writing test cases from the requirements often reveals ambiguities and vagueness.

15

Requirements Engineering Process

7/4/2012

16

Requirements Engineering Process

7/4/2012

Requirements Management
y Once you have the initial requirements for a body of work in

Requirements evolution

hand, you must cope with the inevitable changes that customer, managers, marketing, the development team, and other request during development. y A change control board (CCB), compose of key stakeholders, decides which purposed changes to incorporate. y Tracking the status of each requirements as it moves through development and system testing provide insight into overall project status.

17

Requirements Engineering Process

7/4/2012

18

Requirements Engineering Process

7/4/2012

Requirements Management Process

y Define a requirements change-control process. y Establish a change control board. y Perform requirements-change impact analysis. y Establish a baseline and control versions of requirements y y y y y
19

Requirements change management

documents. Maintain a history of requirements changes. Track a status of each requirement. Measure requirements volatility. Use a requirements management tool. Create a requirements traceability matrix.
7/4/2012 20 Requirements Engineering Process 7/4/2012

Requirements Engineering Process