CHAPTER

THREE
SYSTEM INTEGRATION
REQUIREMENTS

1
 Require
ments
•A system cannot be analyzed, designed,
implemented and evaluated unless the
problem is understood and requirements
are elicited.
•Requirements are fundamental basis of
all the system development processes.
•Besides as the system is designed and
there is need for integration,
requirement is the basis.
•Requirements are statements
2
 Characteristics of
1. Good
Describes Requirement
What, Not How
2. Atomic. i.e., it should have a single purpose
3. Unique
4. Documented and Accessible
5. Identifies its Owner
6. Approved: After a requirement has been
revised, reviewed, and rewritten, it must be
approved by its owner.
7. Necessary
8. Complete
9. Unambiguous 3
 Requirements
1. ElicitationLife Cycle
Phase: The starting point of the
requirements engineering process is an
elicitation process that involves a number of
people to ensure consideration of a broad
scope of potential ideas and candidate
problems
2. Organization Phase: In this step there is no
transformation of the requirements, but
simple classification and categorization. For
example, requirements may be grouped into
functional vs. nonfunctional requirements.
3. Analysis Phase: This represents a
transformation. 4
 Requirements
Life Cycle…

Ra Organ Analy Complete

Elici
Orga Anal Proto Transf
tati
nisat ysis type orm
on
ion to
Phas
Phase Pha Phas spec
e
se e

5
 Requirements
Elicitation
•Requirements elicitation addresses the
gathering and documenting of the true and
real requirements for the Information System
being developed.
•Requirements is the wants and /or needs of
the
Whouser within a problem
does domain.
What is
•Requirements
it? elicitation
done?questions includes:
Where is it  When is it
done? done
How is it  Why is it
done? done?
6
Fact – Finding
Methods
•Sampling (of existing
documentation, forms and DBs).

•Research and site visits.

•Observation of the work

•Questionnaires.

•Interviews. 7
 Types of
A. Requirement
User Requirements: these are statements
sin Natural language & diagrams of
services the system provides, together
with its constraints. These can be
categorised
⚫Functional requirements : Describe
what the system should do
⚫Non-functional requirements : Consists
8
Con
t…
B. System Requirements
⚫What we agree to
provide
⚫Describes system
services
⚫Contract between
Client and contractor
9
Functional
Requirements
•What inputs the system should accept
•What outputs the system should
produce
•What data the system should store
that other systems might use
•What computations the system should
perform
10
 Non-functional
Requirements
•Non-functional requirements are global
constraints on a computer system
•e.g. development costs,
operational costs,
performance, reliability,
•The challenge of Non-functional
requirements:
•Hard to model
•Usually stated informally, and so are:
•often contradictory,
•difficult to enforce during 11
 Non-functional
Requirements…
• Define system properties and
constraints e.g. reliability, response
time and storage requirements.
Constraints are I/O device capability,
system representations.
• Process requirements may also be
specified mandating a particular
programming language or development
method
• Non-functional requirements may be
more critical than functional
12
 Examples
of NFR
•Interface requirements
•how will the new system
interface with its environment?
•User interfaces and “user-
friendliness”
•Interfaces with other systems
•Performance requirements
•Time - response time
•Throughput - transactions per
second
•Security
•Survivability system will need to
–
•permissible information flows
survive fire natural
 Con
t…
•Operating requirements
•physical constraints (size, weight),
•personnel availability & skill level
•accessibility for maintenance
•environmental conditions
•Life-cycle requirements
•Maintainability, Enhanciability, Portability,
expected market or product lifespan
•Limits on developmentresource availability and
•E.g. development
time limitations, methodological
standards.
•Economic
requirements 14
 Requirements
•There Documentation
are basically two typesof
documents realized from the
requirements elicitation phase. These
include;
1. User Requirements Specification
Document
• It outlines precisely what the user is
expecting from this system.
• It incorporates the functional & non
functional requirements of the user
2. System Requirements Specification 15
 To
ols
•Tools that aid in developing &
understanding System Requirements
•Affinity diagrams
•Force-field analysis
•Ishikawa fishbone (cause-and-effect)
diagrams
•Pareto diagrams
•Pugh charts
16
Modeling
Requirements
•Tools for Modelling
Requirements
•Unified Modeling
Language (UML)
•Use case diagrams
•Class diagrams
•Sequential
diagrams
•State Diagrams
17
Reading
Assignment
•After reading about the following
tools which are use for modeling
Requirements, you might be
asked to present them in group
(if you have).
•Unified Modeling Language (UML)
•Use case diagrams
•Class diagrams
•Sequential diagrams
•State Diagrams and other
diagrams you know from your 18