INTEGRATED SYSTEM

DESIGN
 Outline
❖ Introduction to System Idea
❖ System Definition
❖ Common Features of the System
❖ Classification of Systems
❖ System Approach
❖ Systems Engineering
❖ Systems Engineering Processes
❖ Systems Design Methodologies
❖ Systems Development Life Cycle
❖ Alternative System Development Methodologies
 Introduction to System Idea
❖Starts with classification of the objects according
to the their mutual specifications (animal-plants
etc)
❖Objects are comprised of components and those
components are interrelated and interdependent
❖Groups formed by objects are also related and
dependent each other (relation between phases of
the moon and tides of oceans)-external focus
❖Cause effect relationship (deterministic or
probabilistic)
❖Synergy-The whole is greater than the sum of its
parts
What is a ‘System’?
 What is a system?

❖A group of components that work

together for a specified purpose e.g.
Aircraft
✓Purpose is achieved by implementing
many functions
 Common Features of the System
❖ Purpose: Main reason for system existence
❖ Component (elements, parts, etc.):
Components are the physical and conceptual
parts that make up the system. (E.g.wing)
❖ Attributes: Properties that characterize the
system (e.g. Lift generated)
❖ Relationships: Functional or logical dependency
between the components of a system.

6
 Common Features of the System

❖Qualification: It is the basic properties of

the components that affect the system
and define itself.
❖Actions: These are the activities that
occur as a result of relationships and are
carried out to achieve the goal.
❖Whole: It is the largest part formed by
the components and their relationships.
7
 Common Features of the System

❖Entropy and Negative Entropy: If

systems cannot get enough input from
their environment, they may face
dangers such as deterioration, disruption
and destruction. This condition is called
entropy.
❖For example, people not getting enough
nutrients, water and air from outside can
cause body balance to deteriorate,
systems not to work efficiently,
discomfort and even death of the
system. 8
 Common Features of the System
Borders of System

Components

INPUT OUTPUT

PROCESS Relations

Environment of
11
System
 Classification of Systems

SYSTEM

SUBSYSTEM 1 SUBSYSTEM 2 SUBSYSTEM 3

1A 1B 2A 2B 3A
3B

18
 Classification of Systems
❖ Open and Closed Systems: Systems that receive
input from its environment are called open
systems.
❖ Ex: Chemical equilibrium in closed vessel,
business organization
❖ Living and Inanimate Systems: Systems with
biological features such as birth, proliferation and
death are called living systems.
❖ Static and Dynamic Systems: Static systems are
static and immobile systems. Ex: Classification
systems in libraries. Dynamic systems, on the
other hand, have structural parts that are mobile
and show various activities.
❖ Ex: Aircraft
19
 Classification of Systems
❖ Real and Conceptual Systems: Real systems are
concrete systems that exist in the universe and
take up space in space. Conceptual systems are
abstract systems that consist of organized
stereotypes.
❖ Ex:Airline system, economic system

❖ Natural and Human-made Systems: Natural

systems are the systems that have been arised,
sustained and developed as a result of natural
processes.
❖ Ex: River system, Bridges

19
 System Approach

❖System approach;
✓ Understands and evaluates and manages
the systems that constitute the whole of a
system itself and the relationships between
these sub-systems,
✓ Uses and applies system analysis methods
in the decision making and resolution of
problems that may occur in the system.

❖System approach consists of seeing the whole,

evaluating different points of view and creating
a method from these points of view.
 System Approach
❖System approach separates the problems into
small pieces and reunite them by addressing
them within the framework of specified goals.

❖The system approach covers the stages of

analysis and design of a system.

❖The system approach is a way of thinking that

helps people associate the facts and activities
in their environment with each other, put these
relationships into a system framework by
organizing and classifying them in a
hierarchical order, and thus making sense of
the complex events in the environment.
 What is “Engineering”?

❖Knowledge of mathematical and natural

sciences applied to utilize limited
resources economically for the benefit of
people
❖ Scientific approach
❖ Optimize resources
❖ User/customer in focus

❖ Classical Engineering focused mainly on

product design
 Systems Engineering (SE)

❖SE is an interdisciplinary approach and means

to enable realization of successful systems
✓ It is very quantitative including tradeoff, optimization,
selection and integration of products from various
engineering disciplines
✓ It is more of an engineering discipline.
 Why “SE” is needed?

• High Complexity
• Multidisciplinary
• Cost & Time

“SE” is needed due to Technical complexity

 Why SE (cont..)

❖More systematic way of development

❖Better control of System Development incl.
management of risk, changes, configuration
❖Traceability at all levels
❖Operational & supportability aspects
✓ Effectiveness Analysis
✓ Risk management
✓ Operational - Maintainability, Availability, Safety
etc

❖ Ensures FINAL PRODUCT Fully Meets All

User Requirements
 Systems Engineering Emphasis
❖Top-down approach
✓Look at system from top
✓Decide inputs/outputs taking into account the
supersystem
✓Decide subsystems
✓… down to lower levels
❖Interdisciplinary approach
✓Analytical approach is inadequate
✓Capture the interactions between disciplines
✓Exploit the synergism of these interactions
 Systems Engineering Emphasis

❖Effort on more complete definition of system

requirements
✓Complete definition of needs facilitates verification
of system performance
✓Minimize surprises at later stages
❖Life cycle engineering approach
Systems Engineering Process

❖Planning

❖Analysis

❖Design

❖Implementation
Systems Design Methodologies
 System Design Life Cycle (SDLC)
Phases

❖Planning
❖Analysis
❖Design
❖Implementation
❖Maintenance

Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
23
 PD Life Cycle Models

❖Waterfall
❖Vee Diagrams
❖Incremental
❖Evolutionary
❖Spiral

24
 Systems Development Life Cycle (SDLC)
(Waterfall)
Need

Planning

Analysis

Design

Implementation

System

Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
25
 SDLC Phases

❖Planning
✓Project initiation involves a system request.
✓A feasibility study is conducted if needed.
✓If the project is approved, a project manager
is assigned, and he or she creates a work
plan, staffs the project, and adopts methods
for managing it.

Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
26
 Planning
Why Build the System?

Minor Step Deliverable

1. Identify business value System request

2. Analyze feasibility Feasibility study
3. Develop work plan Work plan
4. Staff project Staffing plan,
5. Control and direct project Project charter
Project management tools
CASE tool
Standards list
Project binders / files
Risk assessment

Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
27
 SDLC Phases
❖Analysis
✓Like a journalist's interview.
✓Important questions: who the users will
be, what the system will accomplish, and
where and when it will run.
✓Starts with an analysis strategy or a plan.
✓If there is an existing system, it is
analyzed, along with ways of moving to the
new system.
✓This leads to further information gathering,
leading up to the development of a process
model and a data model.
Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
28
 Analysis
Who, What, When, Where?

Minor Step Deliverable

6. Analyze problem Analysis plan

7. Gather information Information

8. Model process(es) Process model

9. Model data Data model

Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
29
 SDLC Phases
❖Design
✓It indicates how the system will work.
✓The specification of user interface, forms,
displays, reports and programs, databases,
and files.
✓In the design strategy, the amount of the
system to be purchased or contracted (vs.
built in-house) is decided on.
✓This leads to the architecture design.

Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
30
 Design
How Will the System Work?
Minor Step Deliverable

10. Design physical system Design plan

11. Design architecture Architecture design,

Infrastructure design

12. Design interface Interface design

13. Design database and files Data storage design

14. Design program(s) Program design

31
Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
 SDLC Phases
❖Implementation
✓Brings it all together.
✓The system is built or purchased.
✓Testing the system to verify that it works.
✓Better planning leads to systems with
fewer bugs.
✓Getting the system up and running.

Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
32
 Implementation
System Delivery

Minor Step Deliverable

15. Construction Test plan,

Programs,
Documentation

16. Installation Conversion plan,

Training plan

Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
33
Alternative System Development
Methodologies
❖Parallel development
❖Rapid application development (RAD)
methodologies
✓Phased development
✓Prototyping
✓Throwaway prototyping

Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
34
 Parallel Development

❖Multiple copies of design and implementation

phases
❖To develop separate subsystems
❖All come together in a single implementation
phase
❖Ex: DSS; the four components, database,
model base, user interface, and knowledge,
can essentially be developed in parallel.

Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
35
 Rapid Application Development
Methodologies

❖Phased development,

❖Prototyping,

❖Throwaway prototyping.

Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
36
 Phased Development

❖Break system up into versions developed

sequentially
❖Each version has more functionality
❖Evolves into a final system
❖Users gain functionality quickly
❖But initial systems are incomplete

Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
37
 Prototyping

❖Performing analysis, design, and

implementation phases concurrently, and
repeatedly
❖Users see system functionality quickly and
provide feedback
❖Decision maker learns about problem
❖But can lose gains in repetition
❖Changes are introduced quickly and there is no
attempt to correct design decisions early on.
They are repaired as the system evolves.

Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
38
 Prototyping
Need

Planning

Analysis

Design

Implementation

Prototype
Prototype Not OK
Prototype OK
System

Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
39
 Throwaway Prototyping

❖Like prototyping and SDLC

❖Analysis phase is thorough
❖Design prototypes assist in
understanding the system
❖Example: can use Excel, then Visual
Basic

Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
40
 Throwaway Prototyping
Need

Planning

Analysis Design

Design Implementation
Design Prototype
Not OK Implementation
System

Design
Prototype

Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
41
 References

❖ Decision Support Systems and Intelligent Systems,

Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall,
❖ Wikipedia “systems engineering”
https://en.wikipedia.org/wiki/Systems_engineering
❖ Systems Analysis and Design, by Wiley
❖ J. Lienig; H. Bruemmer (2017). Fundamentals of
Electronic Systems Design. Springer International
Publishing. pp. 6–7. doi:10.1007/978-3-319-55840-0.
ISBN 978-3-319-55839-4.

Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson, 6th edition
Copyright 2001, Prentice Hall, Upper Saddle River, NJ
42