Systems Engineering in Practice

1
Systems Engineeringin Practice

• Presentation to Rosatom, Moscow
• September 2009
• Dr. Asmus Pandikow
• Business Unit Manager, Systems Management
  Services, Syntell AB
• Managing Director, Syntell Deutschland GmbH

2
Does this look familiar?
3
Overview

• Systems Engineering Why and What?
• A Systems Engineers usual day
• Implementing SE
• and typical implementation areas
• Who is doing what within SE?
• including overview on INCOSE

4
SYSTEMS ENGINEERING WHY and What?
5
Why do we need Systems Engineers?
As proposed by the project sponsor
As specified in the project request
As designed by the analyst
required Coordination
As produced by the bean counters
As installed at the users site
What the user wanted
Based on John Oakland, Total Quality Management,
1989
6
SE as Discipline
7
Structure Evolution vs. Creativity Revolution
Structure Processes, methods and
tools Engineering knowledge and skills Documented
and explicit
SE
Creativity Skilled individuals and
teams Craftsmanship and art Undocumented and
implicit
8
SE Process in Context
SYSTEMS (ACQUISITION) PROCESS
Stakeholder Requirements Definition
Transition System Validation
Integrated system
Proposed characteristics
Stakeholder requirements
System reqts
Integration Verification
Architectural Design
System Requirements Analysis
SYSTEMS ENGINEERING PROCESS
Integrated system
Proposed characteristics
Design requirements (specifications)
Delivered components
COMPONENT DEVELOPMENT PROCESS
9
Generic SE Activities
Planned Change Deficiency Technology
Development Discovery etc.
Stakeholders
System Concept
Operational View
System Architecture
Detailed Design
Integration
Verification
Validation
10
What is so difficult with SE?

• System of systems
• Project of projects
• Life-cycle of life-cycles

...and dont forgetthe enabling systems!
11
A Systems engineers USUAL DAY
12
A Systems Engineers Usual Day
Management
understand
explain
Stakeholders
support
support
Systems Engineer
Program/Project Management
Engineers
13
The Twelve SE Roles(Sheard, 1996)

• Requirements Owner
• System Designer
• System Analyst
• Validation/Verification Engineer
• Logistics/Operations Engineer
• Glue Among Subsystems
• Customer Interface
• Technical Manager
• Information Manager
• Process Engineer
• Coordinator
• (Specialist Engineer)

and many more
14
ImplementinG SE
15
SE Implementation Aspects
SE Roadmap
16
SE Implementation Dimensions (Scope)
Pilot Project 1
Requirements Engineering
Configuration Management

17
SE Implementation Life-CycleApplied to all
implementation aspects
A
B
D
E
F
C
18
SE Capability Assessment Model
19
International Standards as Guidelines CMMI-DEV
as Example

• Others
• ISO/IEC 15288
• ISO 9001 / 14001

20
Typical Implementation Areas
21
Typical Low Hanging Fruitsin large-scale
OrganizationsOr Where to start first

• Cross-organizational competence development
  program
• Cross-organizational requirements management
• Cross-organizational configuration management
• Cross-organizational process system
• International assignments including international
  customers and suppliers

22
Example Requirements Management

• Requirements Strategy
• How shall the organization work with requirements
• Objectives Requirements prioritization
  balancing,traceability between need /
  requirement / product / test / service
• Guidelines for requirements
• Requirements Development What are good
  requirements?
• Requirements Management How to save / trace /
  change requirements?
• Shall be applied across the organization
• Requirements Baselines
• Freezing of requirements
• Formal decision process for changes (CCB)

23
Example Process System

• Process Framework
• Common, homogeneous way of describing processes
• Well-defined roles and resources
• Guidelines for development and maintenance of
  processes
• Process Definitions
• Common, homogeneous structure
• Integrated processes, via input / output
• Priorities for step-wise introduction
• Requirements
• Embedded Systems process
• RD process

24
Example Organization / New Roles

• Requirements Configuration Control Board
• Decision forum for changing agreed requirements
  baselines
• Requirements Manager
• Coordination of requirements changes and
  requirements CCB meetings
• Process Owner and Process Groups
• Resources for development and maintenance of
  processes
• Process Coordinator
• Responsible for maintaining process framework
• The new roles are common roles in the
  organization, they cannot be implemented at lower
  levels!

25
SE APPLICATION EXAMPLES
26
Examples of applied SEDomain-independent

• System Development (NPP)
• Product Development (Heavy trucks buses)
• Technology Development (Packaging)

• Competition Analysis (Defense)
• Proposal Development (NPP Security)

• Process Development(Defense, Ship Building)
• Support Concept Development(NPP Support, Defense)

27
(Industrial) Proposal Process
iterative
multi-level
28
Development Process
Management
SRR
PDR
CDR
TRR
SAT
User Requirements System Concept Validation Plan
Validate System to User Requirements
Development Test Integration
Validation
System Specification Verification Plan
Integrate System verify to Spec.
Verification
Integration and Verification
Decomposition and Definition
Configuration Items Design-To Spec.
Verification Plan
Assemble CIs verify to Spec.
Verification
Inspect / Testto Build-To
Build-To Spec. Verification Procedures
Verif.
Fabrication Assembly
Hard-ware
Soft-ware
Manu-factu-ring
Pur-chasing
29
System of Processes
30
Experiences Where does SE help and where not?

• Helpful
• Break-down and structuring of complexity
• Create and maintain traceability and consistency
• Support multi-stakeholder environments
• Support multi-national (-cultural) co-operations
• Complex product and service development
• Less helpful
• No systems thinking required
• Straight-forward product and technology
  development
• No re-use
• Lessons learned
• SE is domain-independent
• SE is process-independent (i.e. usable outside
  engineering)

31
WHO is Doing What?
32
SE Who is doing what?

• Governmental bodies / authorities
• Interested in SE education, standards and best
  practices (quality)
• Industry
• Interested in direct SE benefits (profit margin)
• Consultants
• Interested in SE application and education
• Tool Suppliers
• Interested in applied SE
• INCOSE
• Supporting all of them

33
About INCOSE
34
The INCOSE Mission

• Advance the state of the artand practice of
  systems engineeringin industry, academia, and
  government
• by promotinginterdisciplinary, scalable
  approaches to produce technologically appropriate
  solutions that meet societal needs.

35
INCOSE Background and Structure

• History
• Started in 1990 by 35 senior technical managers
• Incorporated as not-for-profit technical society
  in 1992
• International status 1995
• Structure
• Board of Directors
• Corporate Advisory Board
• Member Board (6 regions)
• Technical Operations
• Administrative Committees
• Central Office (Administrative Management)

36
INCOSE Regions
37
INCOSE Members
Today Over 7000 Region III Over 2600
38
INCOSE Chapters
39
Technical Operations

• Helps achieve the INCOSE mission by providing
  information that anticipates and responds to the
  technical needs of all INCOSE stakeholders via
• Technical events symposia, workshops, other
• Technical products SE Handbook, Working Group
  products
• Technical interactions among stakeholders
• Working Group meetings
• CAB Needs responses
• Standards bodies participation
• Initiatives for SE Vision 2020
• Technical information repositories

40
INCOSE Working Groups
41
Publications and Products

• INSIGHT (quarterly)
• Systems Engineering The Journal of the INCOSE
• Symposia Proceedings (and i-pub, papers online)
• Products from Working Groups
• Free to the public on the Web (www.incose.org)
• Tools Database
• Technical resource center
• From the Members Area of the Web
• Measurement Primer
• Systems Engineering Handbook
• Systems Engineering Technical Vision 2020

42
INCOSE Events

• Annual International Symposium ( July)
• Annual International Workshop ( January)
• Conference of Systems Engineering Research (CSER)
• Regional conferences
• Region III EuSEC 2010, May 23-26, Stockholm,
  Sweden!
• Local Chapters meet regularly
• Virtual meetings via monthly Webinars
• Extensive professional networking
• PhD network - SEANET

43
INCOSE Certification

• Certified Systems Engineering Professional
• Targeted towards Systems Engineers with five or
  more years work experience
• CSEPs are certified against experience,
  education, and knowledge requirements
• Applications must be substantiated by 3-5
  references
• Available since 2004
• Associate Systems Engineering Professional
• Targeted towards Systems Engineers with limited
  work experience
• Ideal for junior/emerging Systems Engineers and
  recent college graduates
• ASEPs are certified against education and
  knowledge requirements
• Available since July 2008

• CSEP Acquisition Extension
• Targeted towards Systems Engineers who support or
  work in a US Department of the Defense
  acquisition environment
• Same core CSEPs experience, education, and
  knowledge requirements
• Additional acquisition knowledge items tested
• Available since July 2008
• Expert Systems Engineering Professional
• Targeted towards Systems Engineers with
  significant work experience and demonstrated
  systems accomplishments
• ESEPs are certified against accomplishment,
  experience, and education requirements
• Interviews used to validate significant systems
  accomplishments
• Available in 2009

44
What Can INCOSE Do for You?

• Advance Your Knowledge of the Discipline and
  Practice of Systems Engineering
• State of the Art Resources
• Participation in Working Groups
• Participation in Symposia and Workshops
• Participation in Local Chapter Events
• Enable Career Growth and Advancement
• Knowledge is Power
• Certification

45
What Can You Do for Systems Engineering?

• Help Fulfill the Mission Advance the state of
  the art and practice of Systems Engineering
• Via Participation
• Local Chapters
• Symposia and Workshops
• Publication
• Working Groups
• Via Practice in industry, academia, and government