Software Requirement Engineering

Week 02
Types of Requirements
The Requirement Dilemma:
What Vs How
 Requirements tell the developers what their system must do.
 They should avoid specifying any unnecessary design or
implementation details, or testing and information associated
with project management.

 This is "what versus how" paradigm

The Requirements Dilemma
 Excluding Project Information
 Project-related information
schedules, configuration management plans etc
 Budget
 test procedures or acceptance procedures
The Requirements Dilemma
 Excluding Design Information

 Exclude information about the system design

 "Trending information will be provided in a

histogram report written in Visual Basic, showing
major contributing causes on the x-axis and the
number of defects found on the y-axis" (Figure 2).

Figure 2:: Pareto Chart

Requirements versus Design
 Requirements (mostly) precede design
 Requirements decisions.

 Design decisions
Iterating Requirements and
Design
 In reality, the requirements versus design activities must be
iterative.
 Requirements discovery, definition, and design decisions are
circular. The process is a continual give and take, in that
Kinds of Software Requirements
 Business Requirements
 Functional requirements
 Non-functional requirements
 Domain requirements
 Inverse requirements
 Design and implementation constraints
The Requirements Engineering Process
RE activities and documents
(Wiegers): Levels of Requirements
Quiz 01: SE-5A

 How can you measure reliability of the

system?
 Relate 2nd layer of RE with 3rd Layer
 How business rules influence Quality
attributes. Justify with example?
Quiz 01: SE-5B

 Suppose you are going for an interview to

gather requirements from the stakeholders.
The product is a new concept for the
developing organization. Which type of
requWhich type of requirement would you be
targeting in this case and why?
 Are business and functional requirements
relatable? If yes, how?
Relationships among features, user
requirements, and functional requirements.
 Feature tree, an analysis model that shows how a feature can be hierarchically
decomposed into a set of smaller features, which relate to specific user
requirements and lead to specifying sets of functional requirements (Beatty and
Chen 2012).
Working with three levels
Page 45

 Figure 1-3 illustrates how various stakeholders

might participate in eliciting the three levels of
requirements. Different organizations use a
variety of names for the roles involved in these
activities; think about who performs these
activities in your organization. The role names
often differ depending on whether the
developing organization is an internal corporate
entity or a company building software for
commercial use.
Requirements Development and
Management
The Software Team
Software Team
 Individual team members have different skills, that's what
makes a team a team.

 In the software team, we hope that

 Some work with the customers effectively

 Some have software programming abilities

 others have testing abilities.

 Still other team players will need design and architecture

abilities.
 Many more skills are required as well.
 Requisite Team Skills for Effective
Requirements Management
 Six team Skills
 Team Skill 1, Analyzing the Problem
 Team Skill 2, Understanding User and Stakeholder Needs
 Team Skill 3, Defining the System
 Team Skill 4, Managing Scope
 Team Skill 5, Refining the System Definition
 Team Skill 6, Building the Right System
Requirements Analyst/ Functional Architect/
Business Systems Analyst

Employee Management System

Add, Delete, Modify
Tasks of Requirements Engineer /Analyst

 Define Business Needs.

 Identify Project Stakeholders
and user classes
 Elicit Requirements
 Analyze Requirements

 Write Specifications
Tasks of Requirements Engineer /Analyst

 Model the Requirements

 Lead Validation

 Facilitate
Prioritization
 Manage Requirements
References

 Software Requirements, Wiegers K. &Beatty

J., 3rd Edition (2013), Microsoft Press.

 Managing Software Requirements, Addison

W. ,Leffingwell & Widrig