Академический Документы
Профессиональный Документы
Культура Документы
Week 5
Software Requirement Engineering 2
Requirement
Something required, something wanted or needed
Webster’s dictionary
Software Requirements
Response of
Software requirements may be: software
against the input
Abstract statements of services
Requirement
Can be functionality
constraint
Importance of RE
• “Done well,
• requirements engineering presents an
opportunity to reduce costs and increase the
quality of software systems.
• Done poorly,
• it could lead to a software project failure.”
Software Engineering Institute (SEI)
Requirements engineering
• The process of finding out, analyzing, documenting and
checking the services that the customer requires and
constraints on its operation is called requirements
engineering (RE).
• 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.
Functional requirements
Specify the software functionality that the developers
must build into the product to enable users to accomplish
their tasks, thereby satisfying the business requirements.
• The user shall be able to search either all of the initial set
of databases or select a subset from it.
• The system shall provide appropriate viewers for the user
to read documents in the document store.
• Every order shall be allocated a unique identifier
(ORDER_ID) which the user shall be able to copy to the
account’s permanent storage area.
Examples of functional requirements for
MHC-PMS 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 eight-digit employee number.
Chapter 4 Requirements engineering 21
Requirements imprecision
• Problems arise when requirements are not precisely
stated.
• Ambiguous requirements may be interpreted in different
ways by developers and users.
• Consider the term ‘search’ in requirement 1
• User intention – search for a patient name across all appointments
in all clinics;
• Developer interpretation – search for a patient name in an
individual clinic. User chooses clinic then search.
Requirements completeness and consistency
Organizational requirement
Users of the MHC-PMS system shall authenticate themselves using their
health authority identity card.
External requirement
The system shall implement patient privacy provisions as set out in HStan-
03-2006-priv.
Functional vs. Non-functional requirements