Systems EngineeringLecture Notes

Systems EngineeringLecture Notes

Maria-Iuliana Dascalu, PhDmariaiuliana.dascalu@gmail.com

Agenda• Course Schedule and Logistics

• Why are we here?– What are Systems?– What is Systems Engineering?– Why do we study Systems Engineering?

• Introduction to SE– Principles– Approaches– Activities and documents– Fields

• Course Schedule and Logistics

• Why are we here?– What are Systems?– What is Systems Engineering?– Why do we study Systems Engineering?

• Introduction to SE– Principles– Approaches– Activities and documents– Fields

Course Schedule and Logistics (1)

• 5 ECTS => a lot• 2 hours of lectures per week• 1 hour of application per week• 1 hour of project per week

• Grading:– 30% team- project– 20% individual assignments– 10% class participation (simple presences don’t count)– 40% the final exam: 20% open questions + 20% multiple-

choice questions

• 5 ECTS => a lot• 2 hours of lectures per week• 1 hour of application per week• 1 hour of project per week

• Grading:– 30% team- project– 20% individual assignments– 10% class participation (simple presences don’t count)– 40% the final exam: 20% open questions + 20% multiple-

choice questions

Course Schedule and Logistics (2)• Team-project:

– The goal is to apply the SE methods and tools to a topic that fits your interest.– First, you will have to make a project proposal and then, if accepted, you will

have to implement it. Details will be offered in a few weeks.• Individual assignments:

– The assignments will be sent by e-mail till the deadline or brought to class: ifyou have to answer to a question, please type your answer (no hand-writing).

• Class participation:– Instructor will randomly pick student names for class discussion: each positive

interventions values 0,10 points.– You have to read the papers/chapters indicated at each lecture, in order to be

able to participate at future class discussions.– If you don’t answer correctly, your class participation grade might decrease.

• Conditions for participating at the final exam:– Minimum 5 out of 10 at the project– Minimum 5 out of 10 at the individual assignments

• Conditions for passing:– Minimum 4,5 out of 10

• Team-project:– The goal is to apply the SE methods and tools to a topic that fits your interest.– First, you will have to make a project proposal and then, if accepted, you will

have to implement it. Details will be offered in a few weeks.• Individual assignments:

– The assignments will be sent by e-mail till the deadline or brought to class: ifyou have to answer to a question, please type your answer (no hand-writing).

• Class participation:– Instructor will randomly pick student names for class discussion: each positive

interventions values 0,10 points.– You have to read the papers/chapters indicated at each lecture, in order to be

able to participate at future class discussions.– If you don’t answer correctly, your class participation grade might decrease.

• Conditions for participating at the final exam:– Minimum 5 out of 10 at the project– Minimum 5 out of 10 at the individual assignments

• Conditions for passing:– Minimum 4,5 out of 10

Course Schedule and Logistics (3)• Course Materials

– Lecture notes:http://mariaiulianadascalu.com/teaching/se/

– Reference book:• Systems Engineering Principles and Practice, 2nd edition – A.

Kossiakoff, W. N. Sweet, A. J. Seymour, S. M. Biemer– Others:

• https://www.incose.org/• SE for Dummies, IBM

• If problems, please send an e-mail to me, with thefollowing subject: [SE] [NAME] [PROBLEM]

• Course Materials– Lecture notes:

http://mariaiulianadascalu.com/teaching/se/– Reference book:

• Systems Engineering Principles and Practice, 2nd edition – A.Kossiakoff, W. N. Sweet, A. J. Seymour, S. M. Biemer

– Others:• https://www.incose.org/• SE for Dummies, IBM

• If problems, please send an e-mail to me, with thefollowing subject: [SE] [NAME] [PROBLEM]

What are Systems?• An integrated set of elements, subsystems, or

assemblies that accomplish a defined objective.These elements include products (hardware,software, firmware), processes, people,information, techniques, facilities, services, andother support elements. (INCOSE SE Handbook)

• A set of interrelated components workingtogether as an integrated whole to achieve somecommon objective. (SE Principles and Practice, A.Kossiakoff & all)

• An integrated set of elements, subsystems, orassemblies that accomplish a defined objective.These elements include products (hardware,software, firmware), processes, people,information, techniques, facilities, services, andother support elements. (INCOSE SE Handbook)

• A set of interrelated components workingtogether as an integrated whole to achieve somecommon objective. (SE Principles and Practice, A.Kossiakoff & all)

What is Systems Engineering?• An iterative process of top‐down synthesis,

development, and operation of a real‐world systemthat satisfies, in a near optimal manner, the full rangeof requirements for the system. (INCOSE SE Handbook)

• A discipline (1) focused on the system as a whole, (2)concerned with customer needs and operationalenvironment, (3) which leads system conceptual design(4) and bridges traditional engineering disciplines andgaps between specialities. (SE Principles and Practice,A. Kossiakoff & all)

• Do all the systems need SE?

• An iterative process of top‐down synthesis,development, and operation of a real‐world systemthat satisfies, in a near optimal manner, the full rangeof requirements for the system. (INCOSE SE Handbook)

• A discipline (1) focused on the system as a whole, (2)concerned with customer needs and operationalenvironment, (3) which leads system conceptual design(4) and bridges traditional engineering disciplines andgaps between specialities. (SE Principles and Practice,A. Kossiakoff & all)

• Do all the systems need SE?

A System Requiring SE is…

• an engineered product, which satisfies aspecific need

• a complex system: contains diversecomponents

• a system which uses advanced technology(involving development risks and a highproduction cost)

• an engineered product, which satisfies aspecific need

• a complex system: contains diversecomponents

• a system which uses advanced technology(involving development risks and a highproduction cost)

Examples of Systems Requiring SE (1)

• Weather satellite• Terminal air traffic control system• Track location system• Airline reservation system• Clinical information system• Electric power plant• Passenger aircraft• A modern car• ….

• Weather satellite• Terminal air traffic control system• Track location system• Airline reservation system• Clinical information system• Electric power plant• Passenger aircraft• A modern car• ….

Examples of Systems Requiring SE (2)

Source: SE for Dummies, IBM

Why do we study Systems Engineering?

• To make smart products(instrumented,interconnected,intelligent)

• To shift from a focus oncost or performance toa focus on innovationand change, cost andperformance — withsoftware as thefoundation fordifferentiation

• To make smart products(instrumented,interconnected,intelligent)

• To shift from a focus oncost or performance toa focus on innovationand change, cost andperformance — withsoftware as thefoundation fordifferentiation Source: SE Principles and Practice, A. Kossiakoff & all

Introduction to SE

• Origins: after World War II• SE is both a technical discipline and a

management discipline• SE is 3-dimmensional: great technical breadth,

moderate technical depth and managementexpertise

• The recognitions of SE as a profession has led tothe formation of a professional society, theInternational Council on Systems Engineering(INCOSE)

• Origins: after World War II• SE is both a technical discipline and a

management discipline• SE is 3-dimmensional: great technical breadth,

moderate technical depth and managementexpertise

• The recognitions of SE as a profession has led tothe formation of a professional society, theInternational Council on Systems Engineering(INCOSE)

History of SE

The Machine Age

The System Age

Machine Age vs. Systems Age

SE Principles

• Keep your eyes on the prize.• Involve key stakeholders.• Define the problem before assuming a solution.• Break down the problem into manageable

chunks.• Delay specific technology choices.• Connect the dots between requirements and

design.• Test early, test often.

• Keep your eyes on the prize.• Involve key stakeholders.• Define the problem before assuming a solution.• Break down the problem into manageable

chunks.• Delay specific technology choices.• Connect the dots between requirements and

design.• Test early, test often.

SE Approaches for Systems Development

The V-Model

• At each step on the left side of the“V”, you create the requirementsthat drive the next step, as well as aplan for verifying theimplementation of the current levelof decomposition.

• At each step on the right side of the“V”, you create documentation tosupport system training, usage,maintenance, installation, andtesting.

• At each step on the left side of the“V”, you create the requirementsthat drive the next step, as well as aplan for verifying theimplementation of the current levelof decomposition.

• At each step on the right side of the“V”, you create documentation tosupport system training, usage,maintenance, installation, andtesting.

SE Activities and Documents

SE Fields

• Management• Engineering• Operation analysis• Architectures• Modeling and simulation• …..

• Management• Engineering• Operation analysis• Architectures• Modeling and simulation• …..

Managing Complexity with Models• System models allow you to capture complexity at many

different levels.

• If you can develop relatively inexpensive ways of designing,testing, and verifying your system before you go and buildit, you can save a lot of time and money.

• Models capture both the structure (architecture) andbehaviour (functionality) of a system, illustratingrelationships and interactions between system elements.

• System models allow you to capture complexity at manydifferent levels.

• If you can develop relatively inexpensive ways of designing,testing, and verifying your system before you go and buildit, you can save a lot of time and money.

• Models capture both the structure (architecture) andbehaviour (functionality) of a system, illustratingrelationships and interactions between system elements.

• SysML (based on UML) isthe standard language formodelling systems andsystems-of-systems

Course Layout

• SE and the system development process• Concept development (with a special accent

on concept modeling and SysML): early stagesof the system lifecycle

• Engineering Development: later stages of thesystem lifecycle

• Post development• Real case studies

• SE and the system development process• Concept development (with a special accent

on concept modeling and SysML): early stagesof the system lifecycle

• Engineering Development: later stages of thesystem lifecycle

• Post development• Real case studies

Application

• Discussion of real case-studies

Homework

• Q1: Systems engineering efforts reduce costand schedule overrun. Why?

• Q2: Compare the presented SE approaches(waterfall, spiral, V-model…).

Useful reading:• www.incose.org/secoe/0103/ValueSE-

INCOSE04.pdf• Chapters 1, 2, 3 from Systems Engineering Principles and

Practice, 2nd edition – A. Kossiakoff, W. N. Sweet, A. J.Seymour, S. M. Biemer

• Q1: Systems engineering efforts reduce costand schedule overrun. Why?

• Q2: Compare the presented SE approaches(waterfall, spiral, V-model…).

Useful reading:• www.incose.org/secoe/0103/ValueSE-

INCOSE04.pdf• Chapters 1, 2, 3 from Systems Engineering Principles and

Practice, 2nd edition – A. Kossiakoff, W. N. Sweet, A. J.Seymour, S. M. Biemer