cse3 march2009cwd35with crane

Introduction to Complex System Engineering

3 march 2009

Emmanuel FUCHS

Slides available soon at www.elfuchs.fr

Content

• Complex System Example

• System Definition

• System Engineering

• Design The Right System

• Process

• Requirements

• Design and Architecture

• Physical Decomposition

• Integration

• IVVQCA

Content





• Process

• Requirements


• Functional and Physical Allocation

• Integration

• IVVQCA

Information Systems

ComplexSystem

Examples

System ProblemsExamples

System Problems Examples

Content





• Process

• Requirements



• Integration

• IVVQCA

System definition (Eberhardt Rechtin 1926-2006)

• A system is a construct or collection of different elements that together produce results not obtainable by the elements alone.

• The elements, or parts, can include people, hardware, software, facilities, policies, and documents; that is, all things required to produce systems-level results.

• The results include system level qualities, properties, characteristics, functions, behavior and performance.

• The value added by the system as a whole, beyond that contributed independently by the parts, is primarily created by the relationship among the parts; that is, how they are interconnected.

Systemic

The whole is greater than the sum of the parts;

The part is greater than a fraction of the whole.Aristotle

System: another definition

• A system is any set (group) of interdependent or temporally interacting parts.

• Parts are generally systems themselves and are composed of other parts, just as systems are generally parts of other systems.

http://en.wikipedia.org/wiki/Temporal

System Definition

SubSystem

SubSystem

SubSystem

SystemUsers

Mission

EnvironmentStakeholders

Border

System

Components

Context

operates In

Purpose

built from

Life Cycle

Functions

performs

ExternalSystem

operates In

performs

Items

receive, transform, sends

Interfaces

performs

EnergyPhysical

EntityInformation

Entity

Interacts with via item

has

carries

has a

has a

performs

System Meta Model

From INCOSE

SE Bodies

• http://www.afis.fr/– Association Française d'Ingénierie Système

• http://www.incose.org/– International Council on Systems Engineering

(INCOSE)

http://www.afis.fr/

http://www.incose.org/

Content





• Process

• Requirements



• Integration

• IVVQCA

System Engineering Definition

“an interdisciplinary approach encompassing the entire technical effort to evolve and verify an integrated and balanced set of system, people, product, and process solutions that satisfy customer needs…..”

System Engineering (SE)

• SE focuses on defining customer needs and required functionality early in the development cycle, documenting requirements, then proceeding with design synthesis and system validation while considering the complete problem

• Systems engineers deal with abstract systems, and rely on other engineering disciplines to design and deliver the tangible products that are the realization of those systems.

• Systems engineering effort spans the whole system lifecycle.

http://en.wikipedia.org/wiki/System_lifecycle

Systemic Approach

• One + One > two

• Aristotle : The whole is more than the sum of its parts.– Parts (Components)– Connections

System Engineering Meta Model

SystemEngineering

EnablingProducts

focus on

EndProduct

OperationalEnvironment

Stackholdersexpectations

CostsSchedule

Performances

StructuredDiscoverProcess

Team

must be on

define in term of

operates in

focus onfocus on

balance in

maintains vision on

required for

is a performed by

From INCOSE

System engineer/architect

• Works with system abstraction.– It is impossible to master everything

• Requirements Management

• System Model

Content





• Process

• Requirements



• Integration

• IVVQCA

Design the right system

As proposed bythe project sponsor

As proposed by the programmers

As specified in the project request

As designed bythe project analyst

As installed at the users’ site

What the customer really want

Content





• Process

• Requirements



• Integration

• IVVQCA

Process Definition

• Set of interrelated of interacting activities which transforms inputs to outputs

P

Inputs Outputs

A Process

UserRequirement

Analysis

SystemRequirement

Analysis

SystemDesign

ComponentsDeveloppmentComponents

DeveloppmentComponents


Developpment

SystemIntegration

SystemValidation

SystemVerfication

Process: V cycle

UserRequirement

Analysis

SystemRequirement

Analysis

SystemDesign




Developpment

SystemIntegration

SystemValidation

SystemVerfication

Sequential V cycle drawbacks

DocumentationAnd mock-up

Phase

Iterative and Incremental

Incremental

Iterative

Barry W. Boehm

Iterative and Incremental

• The Systems Engineering Process is not sequential. It is parallel and iterative.

• The complex interrelationship between creating and improving models throughout the process of developing and selecting alternatives is a good example of the dynamic nature of the systems engineering process.

Process Standardization

• NASA• DOD (US Departement Of Defense):

– Documentation Model

• IEEE• ISO (International Organization for

Standardization) • IEC (International Electrotechnical Committee).

– ISO/IEC 15504 / SPICE (Software Process Improvement and Capability dEtermination)

• SEI (Software Engineering Institute)

Capability Maturity Model - Integration

• CMMI defines the essential elements of effective processes for engineering disciplines based on best industry experiences.

• CMMI models provide guidance when developing and evaluating processes.

• CMMI models are not actually processes or process descriptions.

http://www.sei.cmu.edu/cmmi/

CMMI Maturity Levels

Level Identified as Status

5 optimizing focus on process improvement

4quantitatively managed process measured and controlled

3 definedprocess characterized for the organization and is proactive

2 managedprocess characterized by projects and often reactive

1 initialprocess uncontrolled poorly managed and reactive

ITIL

• ITIL : Information Technology Infrastructure Library

• http://www.itil-officialsite.com

http://www.itil-officialsite.com/home/home.asp

http://www.itil-officialsite.com/home/home.asp

Process Documentation and Review

• SSS: System/Segment Specification • SSDD : System/Segment Design Document • IRS : Interface Requirement Specification• ICD : Interface Control Definition

• SRR : System Requirement Review• SDR : System Design Review• TRR : Test Readiness Review

Content





• Process

• Requirements



• Integration

• IVVQCA

Process Activities

UserRequirement

Analysis

SystemRequirement

Analysis

SystemDesign




Developpment

SystemIntegration

SystemValidation

SystemVerfication

What is a requirement ?

• A requirement is a condition to be satisfied in order to respond to:– A contract– A standard– A specification – Any other document and / or model imposed.

Requirements

• User’s Requirements– Statements in natural language of the system

services.– Described by the user

• System Requirements– Structured document setting out detailed

description of system services. – Part of the contract

User’s Requirements example

• A customer must be able to abort a transaction in progress by pressing the Cancel key instead of responding to a request from the machine.

• The washing machine will be used in the following countries: UK, USA, Europe, Eastern Europe

Process

UserRequirement

Analysis

SystemRequirement

Analysis

SystemDesign




Developpment

SystemIntegration

SystemValidation

SystemVerfication

System Requirements

• The System shall provide ........

• The System shall be capable of ........

• The System shall weigh ........

• The Subsystem #1 shall provide ........

• The Subsystem #2 shall interface with .....

Requirement Quality

• A good requirement states something that is necessary, verifiable, and attainable

• To be verifiable, the requirement must state something that can be verified by:– analysis, inspection, test, or demonstration

(AIDT)

Requirement analysis

• User Requirement– Minimum levels of noise and vibration

are desirable.

• System Requirement– Requirement 03320: The noise

generated shall not exceed 60 db

Requirement Types

• Functional requirements– Functional requirements capture the intended

behavior of the system. – This behavior may be expressed as services,

tasks or functions the system is required to perform

• Non-Functional requirements– All others

• Constraints

Content





• Process

• Requirements



• Integration

• IVVQCA

Process

UserRequirement

Analysis

SystemRequirement

Analysis

SystemDesign




Developpment

SystemIntegration

SystemValidation

SystemVerfication

System Architecture

• The System Architecture identifies all the products (including enabling products) that are necessary to support the system and, by implication, the processes necessary for development, production/construction, deployment, operations, support, disposal, training, and verification

Architecture Modeling

• System : Abstraction– Functional model– Dynamic model– Semantic Model– Object model– Physical Model– Interfaces Model

• Model Views

Architecture Meta Model

Mission

system

stakeHolder

ViewPoints

1..*has a

1..*

Is addressed by

a

concerns views

Conform to

Is important for

a1..*

*

1..*

Used to cover

fullfil1..*

Architecturedescription

identify

1..*i

1..*

identify

Environnementinfluence

Is part of

View PointsLibrary

0..1Has sources

model

1..*

Participate in1..*

consist off

Established method for

1..*

1..*

select

1..*Organised in

ArchitectureHas a

1Described by

rationalprovides

1..*

participatesin

1

aggregates

From IEEE

Architecture and Components Assembly

system

Architecture

connections component

define use

has

has

0..*

2 Is connected to

Example of Architecture Views

• The Functional Architecture – identifies and structures the allocated

functional and performance requirements.

• The Physical Architecture– depicts the system product by showing how it

is broken down into subsystems and components

Functional VS physical Model

• How to fly ?

• Look at birds: Physical Model

• So I need: Legs, Eyes, Brain, and Wings.

• But I can not fly !!!

• Why ?

• I have to find the flight functional model !

Example Birds physical for flying

• Physical decomposition: – physical components that birds used to fly:

Legs, Eyes, Brain, and Wings.

• But can not be applied to system directly

Flying functional model

• Functional decomposition of flying function:– Produce horizontal thrust,– Produce vertical lift. – Takeoff and land, – Sense position and velocity, – Navigate,

Allocations

• Represent general relationships that map one model element to another

• Different types of allocation are:– Behavioral (i.e., function to component)– Structural (i.e., logical to physical)– Software to Hardware– ….

Function Airplane Physical

Component Bird Physical

Component

Takeoff and land Wheels, Legs

Sense position and velocity

Vision or radar Eyes

Navigate Brain or computer Brain

Produce horizontal thrust

Propeller or jet Wings

Produce vertical lift Wings Wings

Bird and Airplane Functional to Physical architecture

mapping

Stove Pipe architecture

User

Functional

Organization

Physical

Multi-criteria decision

Trade Off

• Multi-criteria decision-aiding techniques are available to help discover the preferred alternatives.

• This analysis should be repeated, as better data becomes available.

Content





• Process

• Requirements



• Integration

• IVVQCA

Tower Crane example

Tower Crane example

x

French Tower Cranes

British Tower Cranes

Luffing jib tower crane

• When the jib is moved, the hoist gear is controlled in such a way as to ensure that the hook travels horizontally.

The two types of basic jib design

• Horizontal Jib – This jib takes the form of a simple structure

extending from the tower, along which a trolley can travel, carrying the hoist rope and hook assembly to vary radii.

• Luffing Jib – The luffing jib has no trolley, the variation of

hook radii is achieved by altering the jib angle, the same as with a mobile crane.

Horizontal Jib

Luffing Jib


• These cranes have been designed for work on particularly high buildings or in extremely restricted spaces.

• These cranes can solve all the problems that may appear in building sites settled in crowded places, in the town centres or in some areas full of obstacles like prefabricated buildings or towers.

Washing Machine example

Functional To Physical Model

• Functional : Discover the system functions

• Washing Machine– What it does ?

• Washes

– How it does ?• Agitates

– Physical Component : Agitator

Washing Machine Physical Model

agitator

tube

draining

hand-operated washer

plungers

http://sleekfreak.ath.cx:81/3wdev/VITAHTML/SUBLEV/EN1/WASHMACH.HTM


agitator

Outer tube

draining

top loading

US

http://www.repairclinic.com/0100_23.asp


agitator

Outer tube

draining

Inner tube = drum

front loading

Europe


Washing Machine Functional model

Context Diagram

Dirty Cloths

Washing

Machine

Cold H2O

Soap

Electricity

Operator Settings

Clean Dump Cloths

Dirty Hot H2O

Washing Machine Functional Breakdown

Washingmachine

rinsing wringing

Washing

agitating

draining

supply

Washing Machine Data Flows

heating agitating

holding

supplying draining

power

dirty clothes clean clothes

Dirty water

Clean water

Soap

Washing Machine allocation example


agitator

tube

draining

hand-operated washer

plungers

http://sleekfreak.ath.cx:81/3wdev/VITAHTML/SUBLEV/EN1/WASHMACH.HTM


agitator

Outer tube

draining

top loading

US



agitator

Outer tube

draining

Inner tube = drum

front loading

Europe


Washing Machine Physical ModelWashing Machine

ElectricalSubSystem

SequenceSubSystem

MechanicalSubSystem

Drive MotorHeatingResistor

LiquidSubSystem

Agitator

Inner tube pumpdrawervalve Outer tube

top loading


Washing Machine Physical ModelWashing Machine

ElectricalSubSystem

SequenceSubSystem

MechanicalSubSystem

Drive MotorHeatingResistor

LiquidSubSystem

Drum

tube pumpdrawervalve

front loading



drivingmotor

drum

drawer pump

power

dirty clothes clean clothes

Dirty water

Clean water

Soap

tube

front loading


UML

Diagram

BehaviourDiagram

StructureDiagram

ComponentDiagram

ObjectDiagram

ClassDiagram

Composite StructureDiagram

DeploymentDiagram

PackageDiagram

Use CaseDiagram

State MachineDiagram

ActivityDiagram

InteractionDiagram

InteractionOverviewDiagram

SequenceDiagram

TimingDiagram

CommunicationDiagram

SysML

SysML Diagram

StructureDiagram

BehaviorDiagram

Use CaseDiagram

ActivityDiagram

Internal Block Diagram

Block Definition Diagram

SequenceDiagram

State MachineDiagram

ParametricDiagram

RequirementDiagram

Modified from UML 2

New diagram type

Package Diagram

Same as UML 2

Block definition diagram of the Clothe Washing Domain

«system of interest»WashingMachine

«block»Clothe Washing

Domain

W

«block»Cloths

«block»Environment

«block»Water

«block»Electrivity

User

c

e

bdd Structure [Clothe Washing Domain]

Activity hierarchy in block diagram definition (Hierarchical Functional Model)

«activity»Washing

«activity»rinsing

«activity»agitating

«activity»draining

«activity»Wringing

bdd activityExample

Washing Machine Data Flows

Content





• Process

• Requirements



• Integration

• IVVQCA

Process

UserRequirement

Analysis

SystemRequirement

Analysis

SystemDesign




Developpment

SystemIntegration

SystemValidation

SystemVerfication

Process: V cycle

UserRequirement

Analysis

SystemRequirement

Analysis

SystemDesign




Developpment

SystemIntegration

SystemValidation

SystemVerfication

Integration

• Integration means bringing things together so they work as a whole.

Spaghetti Plate Syndrome

Spaghetti Plate

System Architect System Integrator

Encapsulation Analogy

Implementation Interface

A driver doesn't care of engine's internal working.He only knows the interface

Content





• Process

• Requirements



• Integration

• IVVQCA

UserRequirement

Analysis

SystemRequirement

Analysis

SystemDesign




Developpment

SystemIntegration

SystemValidation

SystemVerfication

Process

IVVQCA

• Integrate : – Build the system

• Verification : – Ensures that you built it right

• Validation : – Ensures that you built the right thing

• Certification : – Ensure that the system is safe

• Acceptance : – Ensures that the customer gets what he wants and

the company get paid.

Ensure that the system is safe

Conclusion

Thank You For Your Attention

Questions are welcome

Contacts :

[email protected]

Slides Available soon at www.elfuchs.fr

mailto:[email protected]

cse3 march2009cwd35with crane

Technology

system validation

system abstraction

system meta model

system engineering se

system problems examples

system engineering meta

system level qualities

systems engineering