Description
This course
is an introduction to systems engineering and V-Model for project managers and
project staff. It provides a high-level view of a broad and rich topic area,
introducing basic concepts to individuals who are working on systems and
software engineering and IT projects. The goal is to allow these individuals to
understand the benefits of applying V-Model approaches as a means of developing
quality systems. The course covers technical practices such as principles of
V-Model, system modeling, prototyping, trade-off analysis and testing, and
management practices such as risk assessment and mitigation, which make up
"best practices" in the systems engineering arena.
Objectives
Upon
completion of the course, participants will be able to:
- Define Systems Engineering and
its application to ITS.
- Describe the system's life cycle
and its relationship to systems engineering.
- Develop, derive, and validate
requirements for a system.
- List the systems engineering
tools available to mitigate risk.
- Define and apply the concept of
earned value as a tracking mechanism.
- List three alternative strategies
that may be applied to decision making under uncertainty.
- Identify where to find
appropriate standards for developing ITS projects.
- Identify resources that may help
project personnel to look at systems as a whole.
Course Outline
Overview of Systems Engineering and
the Rational for the V-Model (Vee Model)
- Introduction to the systems
engineering
- Systems engineering process
- System Vision
- Organization
- Plan
- Process
- Tools
- Review of the notions of system,
subsystem and component
- Components, tools, and skills
required by systems engineering
- Purpose and benefits of systems
engineering
- Systems engineering participants
- Project Manager
- Identification of participants
- Contractor selection
- Impact and applicability of
systems engineering
- Resources
- Vee Diagram
- What is a Vee diagram?
- What are Vee diagrams good for?
- What are some examples of Vee
diagrams?
- TONEX Template for a Vee
diagram
- Classic System Engineering “Vee”
Diagram
- Lesson summary
- Quiz
Fundamentals of the "V"
Model
- Systems Engineering Views
- System Views
- Process View
- View process information through
the Vee Diagram
- Deliverable View for RFPs, SEMPs,
ConOps
- Checklist View
- Checklists that support process
and deliverable reviews
- Role View
- Relevant to your project role
- Document View
- Introduction to systems
engineering process
- The "V" Model
- Description of the steps of the
"V" Model
- Decomposition and recomposition
- Agency involvement in the systems
enigeering process
- Systems engineering strategies
- Once-through strategy
- Incremental strategy
- Evolutionary development strategy
- Examples of Systems engineering
process
- The
Vee-Model (V-Model) Principles
- Understand User Requirements,
Develop System Concept and Validation Plan
- Develop System Performance
Specification And System Validation Plan
- Expand Performance
Specifications 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 Perform
System Verification to Performance Specifications
- Demonstrate and Validate System
to User Validation Plan
- Lesson summary
- Quiz
The Concept of Operations (ConOps) in
the V-Model
- Introduction to the Concept of
Operations
- Definition of Concept of
Operations
- Contents of the Concept of
Operations
- Concept of Operations and Architecture
- Example: Variable Speed Limit
sign
- Concept of Operations
participants
- Role of the Concept of Operations
- Developing the Concept of
Operations
- 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 and
Specifications 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-written
requirements
- Characteristics of poorly-written
detailed 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 at
the 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 implementation
process
- Implementation within the system
development context
- Decomposition and Recomposition
- Recomposition Cycle
- Verification and Validation
Processes
- 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 system
development context
- Maintenance scope
- Hardware and software failures
- Enhancements within the system
development context
- Verification, Validation within
the system development context
- Training
- Importance of training
- Typical documentation
- Final documentation
- Documenting the requirements
- Lesson summary
- Quiz
Cross-Cutting Activities in the
V-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 within
the system development context
- Goals, necessity and functions
of 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 of
changes
- Risk Management
- Sources of Risk
- Risk Management Process
- Risk Planning Process
- Risk Control Strategy
- Real-life Example
- Cross-cutting activities
responsibilities
- 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
College Credit
| Credits Earned: |
20 |
| Cont. Education Units: |
0 |
More Information >>
Additional Fees apply. Call for details.
Who Should Attend
IT
professionals or technical persons at all levels of government and in the private
sector. IT project managers, technical team members, contractors, and staff are
all appropriate participants. Project managers would particularly benefit from
this course since they direct many peoples' efforts. Any level of professionals
involved in IT may attend to broaden their understanding of complex systems,
beyond current technical knowledge.
Prerequisites
Some
familiarity with the IT management and operation is recommended but necessary.