Introduction to Systems Engineering

1
Lesson 1

• Introduction to Systems Engineering

2
Course Outline Day 1

• Introduction to Systems Engineering
• Systems Engineering and Procurement
• Concept of Operations
• Requirements Engineering
• System Design Practices

3
Learning Objectives

• Describe the purpose of systems engineering
• List the activities of a systems engineer
• Name participants and their roles in the systems
  engineering processes

4
What Is a System?
An aggregation of end products and enabling
products to achieve a given purpose
A collection of hardware, software, data,
processes, and people that work together to
achieve a common goal Electronic Industries
Association (EIA) 632
5
Class Vote - Is This a System ?
10a
6
What is a System?(Stereo Example)
System
Stereo
User
CD Player
Amplifier
Speakers
Subsystems
CDs, remote controls, cabling, etc.
Components
7
What is a System?(ITS Example)
System
Electronic Toll Collection
Tag Reader
Photo Enforcement
Clearinghouse Processing
Subsystems
Toll Tag
Chips, camera lens, antenna, etc.
Components
8
Is a dynamic message sign (DMS) a system?
9
To a sign manufacturer it is
System
Dynamic Message Sign
LCD Matrices
Sign Bridge
Sign Processor
Subsystems
LCDs, wiring, chips, connectors, struts, etc.
Components
10
But not to a Transit System Dispatcher
System
Dispatch System
DMS Signs
Bus AVL
Central Computer
Subsystems
LCD matrices, sign bridge, sign processor, etc.
Components
11
Class Vote - Is This a System ?
10a
12
Class Problem

• Define the system, subsystem and component
  hierarchy for a simple freeway traffic management
  system.
• Assume the system includes
• Traffic monitoring
• Inputs and outputs for system operators
• Roadside devices for displaying information to
  motorists

13
What Is Systems Engineering?

• Processes
• Ways of doing things
• Tools and techniques
• Things that you do or use
• A structured way of thinking

14
Systems Engineering is a Combination of Skills
Project Management
Engineering
Systems Engineering
Domain knowledge, legal societal, etc.
15
V Representation of the Systems Engineering
Life Cycle
Concept of Operations
Operations Maintenance
Assessment
High Level Requirements
System Verification
Detailed Requirements
High Level Design
Subsystem Verification
Detailed Design
Integration Test
Implementation
Time
Ref Forsberg, et al, Visualizing Project
Management, Wiley, 2000
16
Systems Engineering Life Cycle
Concept of Operations
Operations Maintenance
High Level Requirements
System Verification
Detailed Requirements
Integration Verification and Validation
High Level Design
Subsystem Verification
Definition and Decomposition
Detailed Design
Integration Test
Implementation
Time
17
Systems Engineering Life Cycle Peer to Peer
Verification/Validation
Validate
Concept of Operations
Operations Maintenance
High Level Requirements
System Verification
Verify
Detailed Requirements
Verify
High Level Design
Subsystem Verification
Verify
Detailed Design
Integration Test
Implementation
Time
18
Systems Engineering Life Cycle Tracking
Requirements
Traceability
Concept of Operations
System Validation
System Level Requirements
System Verification
Through And Across
Subsystem Integration Verification
High Level Design
Component Integration Verification
Detailed Design
Implementation
7
19
Systems Engineering Life Cycle Crosscutting
Activities
Tech. Mngmnt Risk Mngmnt. Configuration
Mngmnt. Validation Verification
Concept of Operations
Operations Maintenance
High Level Requirements
System Verification
Detailed Requirements
High Level Design
Subsystem Verification
Detailed Design
Integration Test
Implementation
Time
20
Another View Waterfall Model
Concept of Operations
Requirements Engineering
Design
Development Deployment
Acceptance Test
Plan
Design
Implement
21
This can be Shown as a Timeline for a Single
Project
Assessment - Identifies need for a new system
Concept of Operations
Develop Deploy
Acceptance Test
Requirements
Design
Time
Operations Maintenance
22
The V and the Evolutionary Development Model
Final System
Initial Vision
Deployment Version 1
Deployment Version 2
Added Requirements
Added Requirements
Time
Design (Decomposition) Develop (Recomposition)
23
Evolutionary Model Timeline
Concept of Operations
Develop Deploy
Acceptance Test
Requirements
Design
Vision
Phase I
V
C
R
D
D2
A
Phase II
C
R
D
D2
A
Phase III
C
R
D
D2
A
Time
24
Comparison of Techniques

• Waterfall Model
• Traditional approach
• Matches highway design practice
• Consistent with organizational responsibilities
• Should only be used when project is very well
  defined

• Evolutionary Model
• Recognizes uncertainty
• Permits learning by doing
• Minimizes risk
• Recommended for complex ITS systems

25
Evolutionary Model

• Features iterative development
• Development pieces should be completed within 6
  to 9 months
• Minimizes requirements changes. They can be
  deferred for the next iteration

26
Why is Systems Engineering Important?

• Theres never enough time to do it right, but
  theres always enough time to do it over
• Anonymous

27
The Benefits of Systems Engineering

• It ensures the development of a system that
  reflects the needs of the user (customer)
• It leads to improved system reliability and
  stability
• It improves the chances of a system development
  on-time and within budget

28
Systems Engineering Helps Avoid Problems of the
Past
Ref http//www.standishgroup.com/visitor/chaos.ht
m
29
What is the Purpose of System Engineering?

• Reduce risk
• Control costs and schedule
• Satisfy users needs
• Improved system quality
• Meet the requirements of the Federal Rule

30
Systems Engineering Impact One example
1.6
1.4
Ratio of actual to planned program cost
1.2
1.0
5
10
15
20
Systems engineering effort as of project cost
Ref. Honour, et al, Value of Systems
Engineering, Honourcode, Inc., Pensacola, FL
31
The Key to SuccessPlan for Change

• Recognize that change is inevitable
• Change must be controlled
• Only accept essential changes
• Fully understand the impacts of change
• Change must be documented
• Configuration
• Documentation

32
The Key to SuccessExpectation Management

• Dont oversell the system
• Dont oversell the schedule
• Recognize that setbacks are inevitable
• Expectations will go unrealized without
  operations planning

33
The Key to SuccessEvolutionary Development

• Divide the design and implementation into
  bite-sized pieces
• Minimizes schedule slippage
• Minimizes risk
• Requirements changes can be deferred
• Produces near-term results

34
New Federal Rule (Part 940)

• Applies to
• Projects funded by the Highway Trust Fund
• Any project incorporating an ITS User Service
• Does not apply to
• Research projects
• Projects in existence before TEA-21
• OM on projects existing before 6/9/98
• Defines accepted planning level practices

35
The Rule Identifies System Engineering Practices

• Identify the portion of the regional architecture
  being implemented
• Identification of participating agencies
• Definition of requirements
• Analysis of alternatives
• Procurement options
• Standards and testing procedures
• Resources for operations and maintenance

36
Relationship Between the Rule and the System
Engineering Life Cycle
Regional Architecture Mapping
Concept of Operations
Participating agencies Requirements
definition Alternatives analysis Procurement
options Standards and testing Operations and
maintenance
High Level Requirements
Detailed Requirements
High Level Design
Detailed Design
Integ
Implementation
Initial planning for these activities occurs
during Concept of Operations
37
What Does a Systems Engineer Do?

• System planning
• Alternatives analysis
• Risk management
• Project controls (planning and execution)
• Requirements engineering
• Problem mitigation
• Quality assurance

38
Who Does Systems Engineering?

• Both client and developer
• Participants include
• Stakeholders
• Contracts and legal
• Management and technical personnel

39
Agency Involvement Tracks the Process
Concept of Operations
Operations Maintenance
Participates
Participates
High Level Requirements
System Verification
Detailed Requirements
Supports
Supports
High Level Design
Subsystem Verification
Detailed Design
Integration Test
Observes
Observes
Implementation
Observes
40
Relative Roles
41
Can the developer provide SE services for me?

• No!
• But they can do it with you

42
The Process Begins with a Plan

• Project Description
• Statement of work
• Preliminary system description
• Project Management Plan
• Organization and staffing
• Schedules and budgets
• Systems Engineering Plan
• Activities performed
• Models
• See Appendix A for detailed outline

43
Learning Objectives

• Describe the purpose of systems engineering
• List the activities of a systems engineer
• Name participants and their roles in the systems
  engineering processes