Lecturer : Nguyen Hong Quang, PhD.

SOFTWARE ENGINEERING • Oct. 16, 2019

REQUIREMENTS
ENGINEERING
VO ANH TUAN MAMAIU16023
VU NGOC LINH MAMAIU16039
LE HONG ANH MAMAIU16025
NGUYEN THI HONG PHUC MAMAIU16047
 REQUIREMENTS ENGINEERING
May be the basis for a bid for a
contract - therefore must be open to
What is a
interpretation
re uirement ?
May be the basis for the contract itself
- therefore must be defined in detail
 USER REQUIREMENTS
Statements in natural language plus
diagrams of the services the system

Type of provides and its operational constraints.

Written for customers.
REQUIREMENTS ENGINEERING

re uirements SYSTEM REQUIREMENTS

A structured document setting out
detailed descriptions of the system’s
functions, services and operational
constraints.
Defines what should be implemented so
may be part of a contract between client
and contractor.
REQUIREMENTS ENGINEERING
 REQUIREMENTS ENGINEERING
Any person or organization who is affected
by the system in some way and so who has a
legitimate interest
System
STAKEHOLDER TYPES
stakeholders
End users
System managers
System owners
External stakeholders
 REQUIREMENTS ENGINEERING
Stakeholders in the Mentcare system

Patients whose information is recorded in the system.

Doctors who are responsible for assessing and treating patients.

Nurses who coordinate the consultations with doctors and administer some treatments.

Medical receptionists who manage patients’ appointments.

IT staff who are responsible for installing and maintaining the system.
 REQUIREMENTS ENGINEERING
Topic
Coverage
Functional & Non- Functional &
Non-functional
functional requirements
Requirements engineering
processes
Requirements elicitation
Requirements
re uirements
specification
Requirements validation
Requirements change
References
 Functional & Non-functional

REQUIREMENTS ENGINEERING
Topic re uirements
Coverage FUNCTIONAL REQUIREMENTS
Functional & Non- Statements of services the system should provide, how the system should react to
functional requirements particular inputs and how the system should behave in particular situations.
May state what the system should not do.
Requirements engineering
processes NON-FUNCTIONAL REQUIREMENTS
Requirements elicitation
Constraints on the services or functions offered by the system such as timing
Requirements constraints, constraints on the development process, standards, etc.
specification Often apply to the system as a whole rather than individual features or services.
Requirements validation
Requirements change DOMAIN REQUIREMENTS
References Constraints on the system from the domain of operation
 REQUIREMENTS ENGINEERING
Topic Functional re uirements
Coverage Describe functionality or system services.

Functional & Non- Depend on the type of software, expected users and the type of
functional requirements
system where the software is used.
Requirements engineering
processes Functional user requirements may be high-level statements of what
Requirements elicitation
the system should do.
Requirements
specification Functional system requirements should describe the system
Requirements validation
services in detail.
Requirements change
References
 Mentcare system :

REQUIREMENTS ENGINEERING
Topic Functional re uirements
Coverage
Functional & Non- A user shall be able to search the appointments lists for all clinics.
functional requirements
The system shall generate each day, for each clinic, a list of patients
Requirements engineering
processes who are expected to attend appointments that day.
Requirements elicitation
Each staff member using the system shall be uniquely identified by
Requirements
specification his or her 8-digit employee number.
Requirements validation
Requirements change
References
 Completeness

REQUIREMENTS ENGINEERING
Topic Imprecision
& Consistency
Coverage Problems arise when functional
requirements are not precisely stated.
In principle, requirements should be
both complete and consistent.
Ambiguous requirements may be
Functional & Non- Complete : They should include
interpreted in different ways by
functional requirements descriptions of all facilities required.
developers and users.
Requirements engineering Consider the term ‘search’ in Consistent : There should be no
processes requirement conflicts or contradictions in the
Requirements elicitation User intention - search for a patient descriptions of the system facilities.
Requirements name across all appointments in all
specification clinics;
In practice, because of system and
Developer interpretation – search for
Requirements validation environmental complexity, it is
a patient name in an individual
Requirements change clinic. User chooses clinic then impossible to produce a complete and
References search. consistent requirements document.
 REQUIREMENTS ENGINEERING
Topic Non-functional re uirements
Coverage These define system properties and constraints
e.g. reliability, response time and storage requirements.
Functional & Non-
functional requirements Constraints are I/O device capability, system representations, etc.
Requirements engineering Process requirements may also be specified mandating a particular
processes
Requirements elicitation IDE, programming language or development method.
Requirements Non-functional requirements may be more critical than functional
specification
Requirements validation requirements. If these are not met, the system may be useless.
Requirements change
References
 Type of Non-functional

REQUIREMENTS ENGINEERING
Topic re uirements
Coverage
Functional & Non-
functional requirements
Requirements engineering
processes
Requirements elicitation
Requirements
specification
Requirements validation
Requirements change
References
 REQUIREMENTS ENGINEERING
Topic Non-functional classi ications
Coverage Product requirements
Requirements which specify that the delivered product must
Functional & Non- behave in a particular way e.g. execution speed, reliability, etc.
functional requirements Organisational requirements
Requirements engineering Requirements which are a consequence of organisational
processes policies and procedures e.g. process standards used,
Requirements elicitation
implementation requirements, etc.
Requirements
External requirements
specification
Requirements validation Requirements which arise from factors which are external to the
Requirements change system and its development process e.g. interoperability
References requirements, legislative requirements, etc.
 Mentcare system :

REQUIREMENTS ENGINEERING
Topic Non-functional re uirements
Coverage Product requirement
Functional & Non- The Mentcare system shall be available to all clinics during
functional requirements normal working hours (Mon–Fri, 0830–17.30).
Requirements engineering Downtime within normal working hours shall not exceed five
processes seconds in any one day.
Requirements elicitation
Organizational requirement
Requirements
specification
Users of the Mentcare system shall authenticate themselves
Requirements validation using their health authority identity card.
Requirements change External requirement
References The system shall implement patient privacy provisions
 Metrics for specifying

REQUIREMENTS ENGINEERING
Topic nonfunctional re uirements
Coverage Property Measure
Speed Processed transactions/sec
Functional & Non- User/event response time
Screen refresh time
functional requirements Size Mbytes
Requirements engineering Number of ROM chips
processes Ease of use Training time
Number of help frames
Requirements elicitation
Reliability Mean time to failure
Requirements Probability of unavailability
specification Rate of failure occurence
Availability
Requirements validation
Robustness Time to restart after failure
Requirements change Percentage of events causing failure
References Probability of data corruption on failure
Portability Percentage of target dependent statements
Number of target systems
 REQUIREMENTS ENGINEERING
Topic
Coverage
Functional & Non- Re uirements
engineering
functional requirements
Requirements engineering
processes
Requirements elicitation
Requirements
processes
specification
Requirements validation
Requirements change
References
 Re uirements engineering

REQUIREMENTS ENGINEERING
Topic processes
Coverage The processes used for RE vary widely depending on the
application domain, the people involved and the organisation
Functional & Non-
developing the requirements.
functional requirements
Requirements engineering However, there are a number of generic activities common to all
processes processes
Requirements elicitation Requirements elicitation;
Requirements
Requirements analysis;
specification
Requirements validation Requirements validation;
Requirements change Requirements management.
References In practice, RE is an iterative activity in which these processes are
interleaved
 Spiral view of the re uirements

REQUIREMENTS ENGINEERING
Topic engineering process
Coverage
Functional & Non-
functional requirements
Requirements engineering
processes
Requirements elicitation
Requirements
specification
Requirements validation
Requirements change
References
 REQUIREMENTS ENGINEERING
Topic
Coverage
Functional & Non-
functional requirements
Requirements engineering
Re uirements
processes
Requirements elicitation
elicitation
Requirements
specification
Requirements validation
Requirements change
References
 REQUIREMENTS ENGINEERING
Topic
Coverage
Functional & Non-
functional requirements
Requirements engineering
Re uirements
processes
Requirements elicitation
speci ication
Requirements
specification
Requirements validation
Requirements change
References
 REQUIREMENTS ENGINEERING
Topic
Coverage
Functional & Non-
functional requirements
Requirements engineering
Re uirements
processes
Requirements elicitation
validation
Requirements
specification
Requirements validation
Requirements change
References
 Re uirements validation

REQUIREMENTS ENGINEERING
Topic
Coverage Concerned with demonstrating that the requirements define the
Functional & Non- system that the customer really wants
functional requirements
Requirements engineering
Requirements error costs are high so validation is very important
processes
Requirements elicitation
Fixing a requirements error after delivery may cost up to 100
Requirements times the cost of fixing an implementation error.
specification
Requirements validation
Requirements change
References
 Re uirements checking

REQUIREMENTS ENGINEERING
Topic
Coverage Validity Does the system provide the functions
which best support the customer’s
Functional & Non- needs?
functional requirements Consistency Are there any requirements conflicts?
Requirements engineering Completeness Are all functions required by the
processes
customer included?
Requirements elicitation
Requirements Realism Can the requirements be implemented
specification given available budget and technology
Requirements validation Verifiability Can the requirements be checked?
Requirements change
References
 Re uirements validation

REQUIREMENTS ENGINEERING
Topic techni ues
Coverage Requirements reviews
Functional & Non- Systematic manual analysis of the requirements.
functional requirements Prototyping
Requirements engineering
Using an executable model of the system to check requirements
processes
Requirements elicitation
Test-case generation
Requirements Developing tests for requirements to check testability.
specification
Requirements validation
Requirements change
References
 REQUIREMENTS ENGINEERING
Topic
Coverage
Functional & Non-
functional requirements
Requirements engineering
Re uirements
processes
Requirements elicitation
change
Requirements
specification
Requirements validation
Requirements change
References
 REQUIREMENTS ENGINEERING
Topic
Coverage
Functional & Non-

References
functional requirements
Requirements engineering
processes
Requirements elicitation
Requirements
specification
Requirements validation
Requirements change
References