notes-SRE Lec - 1
notes-SRE Lec - 1
ENGINEERING
INTRODUCTI
ON
Requirement
Something required, something wanted or needed
Webster’s dictionary
Response of
Software requirements may be: software against
🗸 Abstract statements of services the input
🗸 Detailed mathematical functions
🗸 Part of the bid of contract
🗸 The contract itself
🗸 Part of the technical document, which describes a
product
Requirement
Can be
functionali
constraint
ty
A condition or capability that must be met or possessed by a
system...to satisfy a contract, standard, specification, or other
formally imposed document
🞑 IEEE Std 729
Sources of Requirement
Stakeholders
🗸People affected in some way
by the system
Documents
Sources of Requirement
12
Existing
system
Application
Domain
The Goal of Software
Development
The goal of software development is to
develop quality software—on time and on
budget—that meets customers' real needs.
🗸 Re-specification.
🗸 Redesign.
🗸 Recoding.
🗸 Retesting.
🗸 Change orders
🗸 Corrective action
Requirements Engineering
Process
Elicitation: work with the customer on
gathering requirements
Information systems and other applications developed for use within a company
(such as the payroll system being used to calculate the take-home pay for our
next paycheck). This category is the basis for the information system/information
technology industry, or IS/IT.
Types of Software Applications
Commercial Software Applications
Types Explanation
Product specify that the delivered product must behave in
requirements: a
particular way e.g. execution speed, reliability, etc.
are a consequence of organizational policies and
Organizational
procedures e.g. process standards used, implementation
requirements:
requirements, etc.
arise from factors which are external to the system and its
External
development process e.g. interoperability requirements,
requirements:
legislative requirements, etc.
Non-Functional Requirements
Non-functional
requirements
Example:
Most successful requirements journeys begin with a trip to the land of problem.
This problem domain is the home of real users and other stakeholders, people
whose needs must be addressed in order for us to build the perfect system.
This is the home of the people who need the rock or a new sales order entry
system or a configuration management system good enough to blow the
competition away.
In all probability, these people are not like us. Their technical and economic
backgrounds are different from ours.
On rare occasions, they are just like us. They are programmers looking for a
new tool or system developers who have asked you to develop a portion of the
system.
Problem Domain
These users have business or technical
problems that they need our help to solve.
Needs
Moving towards the solution domain
We move to Solution domain from the problem domain in order to provide a
solution to the problem at hand.