Software Engineering and Design Pattern
Requirements
D r. R u d r a P r a t a p D e b N a t h
Associate Professor
Department of Computer Science and Engineering
University of Chittagong
Email:rudra@cu.ac.bd
5th Semester 2022
Requirements
A system development project usually starts
by defining the requirements of the system
The requirements form the basis for
development
A requirement is a condition or a capability
needed by a user to solve a problem or
achieve an objective
A stakeholder of a system is a person or an
organization that has an (direct or indirect)
influences on the requirements of the system:
End users, system managers, system owners,
external stakeholders
Types of Requirements
Requirements specification
translates the information
collected into a set of
requirements.
User requirements are abstract
statements of the system
requirements for the customer
and end-user of the system
System requirements are a
more detailed description of the
functionality to be provided.
Types of Requirements
Functional requirements
Statements of services the system should provide, how the system should react
to particular inputs and how the system should behave in particular situations
Non-functional requirements
Constraints on the services or functions offered by the system such as timing
constraints, constraints on the development process, standards, etc.
Often apply to the system as a whole rather than individual features or services
Non-functional requirements may be more critical than functional requirements.
If these are not met, the system may be useless.
Requirements Examples
FRs for a healthcare system
A user shall be able to search the appointments lists for all clinics
The system shall generate each day, for each clinic, a list of patients who are
expected to attend appointments that day
Each staff member using the system shall be uniquely identified by his or her 8digit employee number
and how the system should behave in particular situations
Non-functional requirements
These define system properties and constraints e.g. reliability, response time
and storage requirements. Constraints are I/O device capability, system
representations, etc
Non-functional Requirements
Requirement Discovery Processes
The process of gathering information about the required and existing
systems and distilling the user and system requirements from this
information
Different processes:
Interviewing: closed and open interviews
Ethnography: A social scientist spends a considerable time observing
and analysing how people actually work
Stories and scenarios: are real life examples of how a system can be
used
Requirement Discovery Processes
Different processes:
Document Analysis
Requirement workshops
Prototyping
Storyboards/ Rich pictures
Interfaces analysis
Use cases
Self-study:
Recommended Requirements Gathering Practices, Dr. Ralph R. Young
4th Chapter of Sommerville.
Unclear Requirements
Stakeholders don’t know what they really want
Stakeholders express requirements in their own terms
Different stakeholders may have conflicting requirements
Organisational and political factors may influence the system
requirements
The requirements change during the analysis process. New
stakeholders may emerge and the business environment may change
Unclear Requirements
There are many examples of problems with requirements
Unclear requirements have been denoted as the main source of problems in
system development projects
Example: Amanda
The IT system for Arbejdsformidlingen (the national center for unemployed)
ended up costing 650 million kroner (original budget 214 million kroner)
It did not fit with the work of the employees; for example, they had to go through
40-50 screens to register a single person as unemployed
Many problems could be avoided by careful specification of requirements and
review of them
The aim of the System Choice activity is to accomplish that