Course Review and Closing - PowerPoint PPT Presentation

1 / 21
About This Presentation
Title:

Course Review and Closing

Description:

Walkthroughs catch 60% of the errors. Ref. Royce. 4. Closing ... Participate in walkthroughs. Review all documentation and training. Participate in all testing ... – PowerPoint PPT presentation

Number of Views:49
Avg rating:3.0/5.0
Slides: 22
Provided by: mitre4
Category:

less

Transcript and Presenter's Notes

Title: Course Review and Closing


1
  • Course Review and Closing

2
What Is Systems Engineering?
  • Processes
  • Ways of doing things
  • Tools and techniques
  • Things that you do or use
  • A structured way of thinking

3
Systems Engineering Reflects the following Axioms
  • Fixing a problem after delivery costs 100 times
    more than fixing it during design
  • About 15 of software development effort is
    devoted to programming
  • Walkthroughs catch 60 of the errors
  • Ref. Royce

4
Related Courses (The Systems Engineering Training
Series)
5
Contents of SE Series
  • Introduction to SE The SE process, procurement,
    and crosscutting analysis
  • Applied SE Comparative analysis, fundamentals
    of standards, interfacing
  • Project Management Responsibilities of the
    public sector ITS PM.
  • Management Operations What to do when the
    system is built

6
Comparison of Classroom with Internet-based
Training
7
Course Outline Day 1
  • Introduction to Systems Engineering
  • Systems Engineering and Procurement
  • Concept of Operations
  • Requirements Engineering
  • System Design Practices

8
Systems Engineering Life Cycle
Concept of Operations
Operations Maintenance
Assessment
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
9
Course Outline Day 2
  • Object Oriented Design
  • Risk Management
  • Configuration Management
  • Validation and Verification
  • Review and Closing

10
Systems Engineering Life Cycle Tracking
Requirements
Concept of Operations
Operations Maintenance
High Level Requirements
Traceability
System Verification
Detailed Requirements
High Level Design
Subsystem Verification
Detailed Design
Integration Test
Implementation
Time
11
Crosscutting Activities
Systems Engineering Life Cycle Many Activities
Occur Throughout the Project
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
12
The V and the Spiral Model Evolutionary
Development
Final System
Initial Vision
Deployment Version 1
Deployment Version 2
Added Requirements
Added Requirements
Time
Decomposition Recomposition
13
Task Order
Select Consultant
Issue Task Orders
Planning
Design
Implement
Test
Inspect
14
Task Order
  • Does not affect agency or contractor
    responsibilities
  • Can be used with
  • Systems Manager
  • Design Build
  • Essential for evolutionary development

15
In Summary - Youll Be Busy
  • Project manager/systems engineer must
  • Participate in walkthroughs
  • Review all documentation and training
  • Participate in all testing
  • Approve invoices
  • Contract for outside assistance
  • Ensure that configuration management is
    maintained
  • Lead the CCB
  • Coordinate with stakeholders

16
Project Execution Who has lead responsibility?
17
Cross Cutting Activities Who has lead
responsibility?
18
The Timeline Explains Why Youll be Busy
Project Management Configuration
Management Verification Risk Control
Contracting Stakeholders meetings Project
Planning
Risk Assessment
Concept of Operations
Develop Deploy
Acceptance Test
Requirements
Design
Walkthroughs
Establish CCB
Validation
Time
19
Staffing Guidelines
PM/SE P-Yrs/Yr
Projects gt 1 million/yr. Require gt 1 full time
person
3 2 1
Staffing range
Project Size (million/yr)
.5 1.0 2.0
From observation of representative systems
20
Staffing Considerations
  • Dont proceed if you cant staff the project
  • Client inexperience reduces probability of
    success by 30
  • Supplementary staff available
  • Consultants
  • Non-profits
  • Universities
  • Reference Capers

21
Course Learning Objectives
  • List the reasons that systems engineering is
    important for ITS
  • Name the steps in the systems engineering process
  • Differentiate between cross-cutting practices and
    the steps in the process
Write a Comment
User Comments (0)
About PowerShow.com