Didactic Recommendations for Education in SystemsEngineering
by Gerrit Muller University of South-Eastern Norway-NISEe-mail: [email protected]
www.gaudisite.nl
Abstract
Teaching systems engineering differs from teaching a mono-disciplinary course,because the focus is much more on skills and less on transferable facts. Theteacher must trigger a learning process in the students that stimulates the studentto become active with the subject in a perceptive, reflective, and explorative way.This paper provides a number of recommendations for interaction, illustration, softskill development, the use of media and student feedback.
Distribution
This article or presentation is written as part of the Gaudí project. The Gaudí projectphilosophy is to improve by obtaining frequent feedback. Frequent feedback is pursued by anopen creation process. This document is published as intermediate or nearly mature versionto get feedback. Further distribution is allowed as long as the document remains completeand unchanged.
September 9, 2018status: conceptversion: 0
counter-intuitive examples
platform approaches reduce lead-time,
cost, ... platform developments in practice increase lead-time,
cost, ...
student teacher
"What do patient or insurance company need or expect?"
sudden changes of viewpoint
Introduction
INCOSE 2004 Academic Forum
Systems Engineering Education:
graduate and postgraduate,
but often an extension of regular engineering education.
Experience in SE education
"effective transfer of know-how requires an active attitude from the audience" Experiences of Teaching Systems Architecting, Gerrit Muller at INCOSE 2004
didactic recommendations
Didactic Recommendations for Education in Systems Engineering2 Gerrit Muller
version: 0September 9, 2018
DRSEintroduction
Example Postgraduate Programs Systems Engineering
Stevens Institute Systems Engineering and Engineering Managementhttp://www.soe.stevens.edu/seem/
MIT System Design and Managementhttp://lfmsdm.mit.edu/sdm/index.html
University of South Australiahttp://www.unisa.edu.au/seec/
Didactic Recommendations for Education in Systems Engineering3 Gerrit Muller
version: 0September 9, 2018
BA Graduate SE Programs in USA
BS program at:
University of Arizona
University of Arkansas at Little Rock
University of Pennsylvania
University of Virginia
U.S. Naval Academy
Washington University
credit hours
128
130
120
128
143
120
+ Credit hours for BS programs varies between 120 – 143 + All BS programs build on basic engineering and science courses. + Programs differ in their emphasis areas from university to university although the
systems engineering fundamental courses remain the same. + Some universities offer considerable amount of flexibility in their BS programs by
creating emphasis areas. source: Professor Cihan H Dagli, PhD at INCOSE 2004, Toulouse
Undergraduate Education in Systems Engineering in USA
less than 5% of complete curriculum!
Didactic Recommendations for Education in Systems Engineering4 Gerrit Muller
version: 0September 9, 2018
DRSEprogramsUSA
Systems Architecting Curriculum
maturity
Architectural Reasoning
ESA SW
EXARCH Execution architecture
SARCH
ESA stake- holders
root technical designer
technical generalist
business, application insight
process insight
psycho-social interests
apply theory in practice
become all-round
experience the non-technical aspects
see every human as an individual
System design methods
Bredemeyer SW architecture
CAFCR Multi-Objective System design
ESA s ystem
ESA silicon
ESA mechatronics
marketing, process and many more
Bredemeyer - Role of the architect
Thomas Gilb - EVO, requirements eng
mathematics physics chemistry mechanical engineering computer science electronical engineering
advanced SARCH
reliability engineering QFD and more
available missing external conventional curriculums
legend ESA : Embedded Systems Architecting EVO : Evolutionary Project Management QFD : Quality Function Deployment
Didactic Recommendations for Education in Systems Engineering5 Gerrit Muller
version: 0September 9, 2018
SXcurriculumSA
Active vs Passive
active
passive Theorydull
Practical Illustrationvivid
Interactionvivid
Spin-off:
cross-fertilization
Insight
Exercise
Abstraction
Didactic Recommendations for Education in Systems Engineering6 Gerrit Muller
version: 0September 9, 2018
DRSEpassiveVsActive
Finding the Balance Active-Passive
insufficient digestion of know how
insufficient know how transfer
time
% a
ctiv
e
10
20
30
40
50
60
70
80
1999 2000 2004 2003 2002 2001 2005
SARCH
Didactic Recommendations for Education in Systems Engineering7 Gerrit Muller
version: 0September 9, 2018
DRSEbalance
Interaction
+ Pose questions to the students
+ Keep the communication open in all directions
+ Keep the students alert
+ Maintain a consistent mindset
Didactic Recommendations for Education in Systems Engineering8 Gerrit Muller
version: 0September 9, 2018
DRSEinteraction
Example questions
Provocative:
"What is the most important process in your company?"
differentiate between important or core processes and less important supporting processes.
Explorative:
"What are the deliverables of an architect?"
followed by f.i. "What are deliverables?"
Inviting experiences:
"Who has seen a roadmap?"
followed by the question "What was the contents of this roadmap?"
or "What is the value of this roadmap for the organization?"
Didactic Recommendations for Education in Systems Engineering9 Gerrit Muller
version: 0September 9, 2018
DRSEquestions
Keep the Communication Open
+ Allow or even stimulate discussion
+ Managing two-way communication, the parking flip
+ Creating an open and safe learning environment, rules:
· Argue in a constructive way, no heat seeking missiles allowed!
· Stupid questions don't exist
P what
is how to ..
Didactic Recommendations for Education in Systems Engineering10 Gerrit Muller
version: 0September 9, 2018
DRSEopenCommunication
Keep the students alert
counter-intuitive examples
platform approaches reduce lead-time,
cost, ... platform developments in practice increase lead-time,
cost, ...
student teacher
"What do patient or insurance company need or expect?"
sudden changes of viewpoint
Didactic Recommendations for Education in Systems Engineering11 Gerrit Muller
version: 0September 9, 2018
DRSEalert
Maintain a consistent mindset
· Be customer, market, and result oriented
· Use common sense
· Use multiple viewpoints
· Be constructively critical
· Maintain your integrity and credibility as an architect
· Use facts, be specific
· Communicate clearly and to the point, provide overview
Didactic Recommendations for Education in Systems Engineering12 Gerrit Muller
version: 0September 9, 2018
DRSEmindset
Example maintain mindset by keeping alert
"Why do we need this amount of software?"
"How much work is required with this amount of software?"
"If the customer really needs this, how can we serve the customer anyhow?"
student teacher
We cannot do this, because the amount of
software is way too large
Didactic Recommendations for Education in Systems Engineering13 Gerrit Muller
version: 0September 9, 2018DRSEmindsetAlert
Soft Skill Development
+ presenting
+ teamwork
+ self-reflection
+ providing balanced feedback
Didactic Recommendations for Education in Systems Engineering14 Gerrit Muller
version: 0September 9, 2018
DRSEsoftSkills
The Use of Media
l o w-tech support + flips + yellow notes
course material + slides + reader
Didactic Recommendations for Education in Systems Engineering15 Gerrit Muller
version: 0September 9, 2018
DRSEmedia
Exercises
Exercise instruction:
short, asking for illustration and specifics
Team size:
4 is optimal; 3 or 5 members is acceptable
Duration
40 minutes
show the operational organization where you are operating, mention the names of the people involved explicitly
group dynamics: larger is better
active participation: smaller is better
3 4 5 2 6
Didactic Recommendations for Education in Systems Engineering16 Gerrit Muller
version: 0September 9, 2018
DRSEexercises