0% found this document useful (0 votes)
5 views

sys2

The document outlines the complexities and challenges of systems engineering, emphasizing the need for inter-disciplinary collaboration and the application of model-based systems engineering. It discusses foundational questions linking systems engineering to other fields, the increasing complexity of man-made systems, and the importance of human factors in system design. The document concludes that while systems engineering is challenging, cooperation among disciplines is essential for effective system development.

Uploaded by

adil.rizki
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
5 views

sys2

The document outlines the complexities and challenges of systems engineering, emphasizing the need for inter-disciplinary collaboration and the application of model-based systems engineering. It discusses foundational questions linking systems engineering to other fields, the increasing complexity of man-made systems, and the importance of human factors in system design. The document concludes that while systems engineering is challenging, cooperation among disciplines is essential for effective system development.

Uploaded by

adil.rizki
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 26

Next lecture : The System

Basic Introduction
System Engineering

System Engineering
System Engineering II
Inter-disciplinary involvement

Software Electronic Mechanical


engineering engineering engineering

Structural ATC systems User interface


engineering engineering design

Civil Electrical
Architecture
engineering engineering
Foundational questions

• What are the foundational ideas that link Systems


Engineering to other fields in the Arts and Sciences?
• How is systems engineering related to the broader area of systems
sciences, complexity, and language?
• If we aim to utilize systems engineering in diverse areas
not traditional to SE origins, how must these be
conceptually mapped, and with what impact?
Foundational questions

• What conceptual road maps of simplified foundational


ideas can be used to more easily or effectively
understand, perform, manage, or conform to current,
complex, or specific SE methodologies, standards, and
processes?
• What principles are needed to apply systems
engineering to more complex problems than the design
of traditional systems; e.g.,
• As in the engineering of globally optimized families of
configurable systems (product lines)?
• Or the engineering of high intelligence systems?
Model-based systems engineering
• Model-based systems engineering is an emerging approach to
systems engineering:
– See www.incose.org
• Uses explicit models where previously informal, intuitive,
natural language prose (e.g., English) of documents was used

M odel M odeled Thing

M odel Interpreter

P rocessor Farm
The Systems Challenge
The Man-Made World Is Increasingly Populated by Systems

• Transportation, Energy & Power


Systems
• Manufacturing, Construction
Systems
• Telecommunication Networks
• Man-Made Biological & Health
Care Systems
• Facility, Properties
• Business Processes
• Other Man-Made and Natural
Systems
The Systems Challenge
These Systems Are Becoming More Complex

• Under pressure of demand & competition


• Enabled by progress in technology
• Becoming more complex at exponentially
growing rates
The Systems Challenge
The Growth Of Systems Complexity Eventually Can Outpace
Human Ability To:

• Describe • Understand • Communicate About


• Predict • Install • Design and Implement
• Manage • Operate • Manufacture
• Monitor • Repair • Diagnose
• Configure • Maintain • Control
• Evolve • Account For • Maintain Security Of

Those Systems . . .
The Systems Challenge

. . . At Least Within Reasonable:


• Time
• Cost
• Effort
• Sense of Security from Risk

Incose : Faster, Better and Cheaper


For a meal : must NOT result in MacDonald Hamburger !!
Systems may be any technology

• Mechanical
• Electronic
• Software
• Chemical
• Thermodynamic
• Human organizations
• Biological
Not everything that has parts is a system

• For components to “interact”, there must be an


idea of “state” and relationship between states of
components:
– Two components interact if the state of at least one is
impacted by the interaction having occurred
– A book, a piece of music, or a photograph have their
own components, but not direct interactions between
them
• This view distinguishes the engineering view of
systems from “systems” in some other fields.
Example system

• System: Semi-trailer truck hauling freight


• Components: engine, power train, suspension,
lubrication system, fuel system, braking system,
electrical system, cab, trailer, navigation system,
communication system, software modules
• Relationships: physical containment, power
dependency, control interaction, mechanical
connection, thermal interaction
Physical and Logical Systems
• A Logical System is equivalent to a functional role.
• Physical Systems may be assigned responsibilities to perform
roles that are Logical Systems.
• What plays the role of Engine System in a gas-fired generator?
• What plays the role of Engine System in a hybrid automobile?

• Example of Logical System: • Examples of Physical Systems:


– Engine System: An Engine System – Toyota Camry Model XLE
converts atmospheric air and Automobile
chemical fuel into rotating – Caterpillar Model 3406 Diesel
mechanical power for use by other Engine
machine subsystems. – Program Module 1750
Services

• A Service is:
– a feature of a system
– what system users consume
– something that can be measured and be subject to a
service level agreement
The system engineering process

Requirements System
definition decommissioning

System System
design evolution

Sub-system System
development installation

System
integration
An example of SE process
(Procurement)
Delivery
note

Equipment Checked Delivery


spec. spec. note
Specify Validate Accept Check
Get cost
equipment specification delivery of delivered
estimates
requir ed equipment items
Spec. +
supplier + Installation
estima te Order
Equipment notification instructions
spec. Supplier list
Place
Supplier Find Choose equipment Install
database suppliers supplier equipment
Order order
details +
Blank order Installation
form acceptance

Accept
delivered
Checked and equipment
signed order form

Equipment
details

Equipment
database
Software and systems engineering
• Proportion of software in systems is increasing.
Software-driven general purpose electronics is
replacing special-purpose systems
• Problems of systems engineering are similar to
problems of software engineering
• Software is (unfortunately) seen as a problem
in systems engineering. Many large system
projects have been delayed because of software
problems
Systems and their environment
• Systems are not independent but exist in an
environment
• System 뭩 function may be to change its
environment
• Environment affects the functioning of the
system e.g. system may require electrical
supply from its environment
• Organizational as well as physical environment
may be important
System hierarchies
Town

Street

Building
Heating Power Water
system system system
Security Lighting Waste
system system system
Contractor/Sub-contractor model
System
customer

Principal
contractor

Sub-contractor 1 Sub-contractor 2 Sub-contr actor 3


System architecture modelling

• An architectural model presents an abstract


view of the sub-systems making up a
system
• May include major information flows
between sub-systems
• Usually presented as a block diagram
• May identify different types of functional
component in the model
Radar Transponder Da ta comms. Aircraft Telephone
system system system comms. system

Position Backup Comms. Backup comms.


processor position processor processor
processor

Aircraft Flight plan


simulation database
system

Weather map
system

Controller Controller
Accounting info. system consoles
system

Activity logging
system
Human factors

• All systems have human users and are used


in a social and organisational context
• An appropriate user interface is essential for
effective system operation
• Human factors are often the most important
factor in determining the success or
otherwise of a system
Other human factors
• Changes to work processes in the system
environment
– May be resisted by users if jobs are lost
• De-skilling of users
– May be resented by professionals
• Changes to organisation power structure
– Managers don 뭪 like to lose control
• Work changes
– Some changes to work practice may be
unacceptable
Conclusion
• Systems engineering is hard!
• There will never be an easy answer to the
problems of complex system development
• Software engineers do not have all the answers
but are often better at taking a systems
viewpoint
• Disciplines need to recognise each others
strengths and actively rather than reluctantly
cooperate in the systems engineering process
Next lecture : SE Standards

Basic Introduction
System Engineering

System EIA 632


Engineering

You might also like