Course Number: 904
Length: 3 Days
College Credits: 20
This courseis an introduction to systems engineering and V-Model for project managers andproject staff. It provides a high-level view of a broad and rich topic area,introducing basic concepts to individuals who are working on systems andsoftware engineering and IT projects. The goal is to allow these individuals tounderstand the benefits of applying V-Model approaches as a means of developingquality systems. The course covers technical practices such as principles ofV-Model, system modeling, prototyping, trade-off analysis and testing, andmanagement practices such as risk assessment and mitigation, which make up”best practices” in the systems engineering arena.
Who Should Attend
ITprofessionals or technical persons at all levels of government and in the privatesector. IT project managers, technical team members, contractors, and staff areall appropriate participants. Project managers would particularly benefit fromthis course since they direct many peoples' efforts. Any level of professionalsinvolved in IT may attend to broaden their understanding of complex systems,beyond current technical knowledge.
Objectives
Uponcompletion of the course, participants will be able to:
- Define Systems Engineering andits application to ITS.
- Describe the system's life cycleand its relationship to systems engineering.
- Develop, derive, and validaterequirements for a system.
- List the systems engineeringtools available to mitigate risk.
- Define and apply the concept ofearned value as a tracking mechanism.
- List three alternative strategiesthat may be applied to decision making under uncertainty.
- Identify where to findappropriate standards for developing ITS projects.
- Identify resources that may helpproject personnel to look at systems as a whole.
Outline
Overview of Systems Engineering andthe Rational for the V-Model (Vee Model)
- Introduction to the systemsengineering
- Systems engineering process
- System Vision
- Organization
- Plan
- Process
- Tools
- Review of the notions of system,subsystem and component
- Components, tools, and skillsrequired by systems engineering
- Purpose and benefits of systemsengineering
- Systems engineering participants
- Project Manager
- Identification of participants
- Contractor selection
- Impact and applicability ofsystems engineering
- Resources
- Vee Diagram
- What is a Vee diagram?
- What are Vee diagrams good for?
- What are some examples of Veediagrams?
- TONEX Template for a Veediagram
- Classic System Engineering “Vee”Diagram
- Lesson summary
- Quiz
Fundamentals of the "V"Model
- Systems Engineering Views
- System Views
- Process View
- View process information throughthe Vee Diagram
- Deliverable View for RFPs, SEMPs,ConOps
- Checklist View
- Checklists that support processand deliverable reviews
- Role View
- Relevant to your project role
- Document View
- Introduction to systemsengineering process
- The "V" Model
- Description of the steps of the"V" Model
- Decomposition and recomposition
- Agency involvement in the systemsenigeering process
- Systems engineering strategies
- Once-through strategy
- Incremental strategy
- Evolutionary development strategy
- Examples of Systems engineeringprocess
- TheVee-Model (V-Model) Principles
- Understand User Requirements,Develop System Concept and Validation Plan
- Develop System PerformanceSpecification And System Validation Plan
- Expand PerformanceSpecifications into “Design-to” Specifications and Verification Plan
- Evolve “Design-to”Specifications into “Build-to” Documentation and Inspection Plan
- Inspect to “Build-to”Documentation
- Assemble and perform system/sub-system Verification to syetm/sub-system “Design-to” Specifications
- Design Engineering
- Decomposition and Definition
- Integration and Qualification
- Fabricate, Assemble, and Code to“
- Inspect to “Build-to”Documentation
- Integrate System and PerformSystem Verification to Performance Specifications
- Demonstrate and Validate Systemto User Validation Plan
- Lesson summary
- Quiz
The Concept of Operations (ConOps) inthe V-Model
- Introduction to the Concept ofOperations
- Definition of Concept ofOperations
- Contents of the Concept ofOperations
- Concept of Operations and Architecture
- Example: Variable Speed Limitsign
- Concept of Operationsparticipants
- Role of the Concept of Operations
- Developing the Concept ofOperations
- Definition of goals/objectives
- Characteristics of the vision
- Example: the soda machine
- Sample vision
- Operational scenarios
- Attributes of scenarios
- Identification of scenarios
- Example: the soda machine
- Importance of scenarios
- Other considerations
- Maintenance
- Concept of Operations Workshop
- Lesson summary
- Quiz
V-Model Systems Requirements andSpecifications Writing
- Definition of requirements
- Source of requirements
- Responsibilities for requirements
- Types of requirements
- Functional requirements
- Performance requirements
- Interface requirements
- Data requirements
- Hierarchy of requirements
- Writing style for requirements
- Characteristics of well-writtenrequirements
- Characteristics of poorly-writtendetailed requirements
- Requirement writing guidelines
- Requirements Workshop
- Lesson Summary
- Quiz
System Design in the V-Model
- Introduction to system design
- Definition of system design
- Good design practices
- Design alternatives
- Considering the alternatives atthe system, subsystem, and unit levels
- Assessing the alternatives
- Design specifications
- Writing rules
- Types of specifications
- Examples
- Design workshop
- Operations and Maintenance & M needs
- Operator needs
- Prototyping
- ITS Standards
- Description of standards
- Interface standards
- Using standards
- System design responsibilities
- Lesson summary
- Quiz
Implementation, Testing, Operations,and Maintenance
- Introduction to implementationprocess
- Implementation within the systemdevelopment context
- Decomposition and Recomposition
- Recomposition Cycle
- Verification and ValidationProcesses
- Verification
- What is Verification?
- Verification testing
- Acceptance tests
- Accepance tests thoroughness
- From Implementation to O&M
- Validation
- Transition factors
- Transition planning decisions
- Operations and Maintenance
- O&M within the systemdevelopment context
- Maintenance scope
- Hardware and software failures
- Enhancements within the systemdevelopment context
- Verification, Validation withinthe system development context
- Training
- Importance of training
- Typical documentation
- Final documentation
- Documenting the requirements
- Lesson summary
- Quiz
Cross-Cutting Activities in theV-Model
- Cross-Cutting Activities
- Stakeholder Involvement
- Elicitation
- Project Management Practices
- Risk Management
- Metrics
- Configuration Management
- Project Process Improvement
- Decision Gates
- Decision Support/Trade Studies
- Technical Reviews
- Traceability
- Configuration Management
- Configuration Management withinthe system development context
- Goals, necessity and functionsof Configuration Management
- Configuration identification
- Traceability
- Role of Traceability
- Traceability matrix
- Example
- Traceability Workshop
- Change control
- Configuration Control Board
- Change control steps
- Causes of change requests
- Controlling for the impact ofchanges
- Risk Management
- Sources of Risk
- Risk Management Process
- Risk Planning Process
- Risk Control Strategy
- Real-life Example
- Cross-cutting activitiesresponsibilities
- Lesson summary
- Quiz
Risk Management
- Determining the SE approach
- Low-risk projects
- High-risk projects
- Types of IT projects
- Managing Project Resources
- Project Management
- Technical Management
- SE Management Plan
- SEMP Development Stages
- SE Resources
- SE Impact on Institutions
- Types of Institutional Impacts
- Additional Resources
- Lesson summary
- Quiz