Length: 4 Days
Introduction to Systems Engineering – Lifecycle and Processes
Introduction to Systems Engineering Training Course Description
Introduction to Systems Engineering training course introduces you to systems engineering with the focus of lifecycle and processes. We intend to show you the advantages of using systems engineering techniques as a tool of developing quality systems. Introduction to Systems Engineering training course covers technical exercises such as modeling, prototyping, trade-off analysis and testing, and management practices including (but not limited to) risk analysis and mitigation, which builds “best practices” in the field of systems engineering. This hands-on training is specifically concentrated on project lifecycle planning, lifecycle technical and management processes, and relation to the principles of systems thinking.
TONEX Introduction to Systems Engineering training course is a combination of theory and practice. Through a fun, interactive presentation, you will learn all the principals, concepts, theories, and logics that the systems engineering is founded on. Then, you will learn about the methods and techniques associated with this field. Once you received sufficient information, you will get to practice them in the hands-on section. We encourage our students to bring in their own project sample to work on in the class, however, they can also use the real-life projects provided by our instructors. This section of the class include labs, individual/group activities, and hands-on workshops.
Audience
Introduction to Systems Engineering training is a 4-day course designed for:
- Systems engineers
- Project managers
- Project engineers
- IT engineers
- All the individuals who are interested in learning systems engineering, in particular lifecycle and processes.
Training Objectives
Upon the completion of Introduction to Systems Engineering training, the attendees are able to:
- Understand and define Systems Engineering and its application
- Explain the system’s life cycle and its relationship to systems engineering
- Develop, derive, and validate requirements for a system
- List the systems engineering tools to reduce risk
- Apply the concept of earned value to track the system
- List three different strategies to decision making under uncertainty
- Determine where to find suitable standards for developing projects.
- Determine resources that assist the personnel to look at systems as a whole
- Distinguish the effect of boundary, context, purpose and relationship on understanding systems
- Explain correlation between lifecycle, methods and processes
- Describe the lifecycle, methods and processes roles in a complicated environment
- Explain the applicability of Systems Engineering standards and the relationship between competencies and Systems Engineering roles
- Choose and adjust a lifecycle method for your own problems
- Write requirements consistent with system context which can be verified and validated
- Choose proper verification and validation techniques throughout the lifecycle
Course Outline
Overview of Systems Engineering
- Systems engineering definition
- Notions of system, subsystem and component
- Systems engineering process
- Components, tools, and skills required by systems engineering
- Purpose and benefits of systems engineering
- Impact and applicability of systems engineering
The “V” Model
- Introduction to systems engineering process
- The “V” Model
- The steps of the “V” Model
- Decomposition and re-composition
- The “V” diagram and Federal Rule 940
- Regional Architecture
- Agency involvement in the systems engineering process
- Systems engineering strategies
- Once-through strategy
- Incremental strategy
- Evolutionary development strategy
- Examples of Systems engineering process
The Concept of Operations
- Concept of operations
- Definition
- Contents
- Concept of operations and architecture
- Role of the concept of operations
- Developing the concept of operations
- Definition of goals/objectives
- Characteristics of the vision
- Sample vision
- Operational scenarios
- Characteristics of scenarios
- Identification of scenarios
- Importance of scenarios
- Other considerations
- Maintenance
- Concept of operations workshop
Systems Requirements
- 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
- Features of well-written requirements
- Features of poorly-written requirements
- Requirement writing rules
- Requirements workshop
System Design
- System design definition
- Best practices
- Design alternatives
- Considering the alternatives at the system, subsystem, and unit levels
- Analyzing the alternatives
- Design requirements
- Writing guidelines
- Types of requirements
- Examples
- Design workshop
- Operations and maintenance
- O & M demands
- Operator needs
- Prototyping
- System design responsibilities
Implementation, Operations, and Maintenance
- Introduction to implementation process
- Implementation within the system development context
- Decomposition and re-composition
- Re-composition cycle
- Verification
- What is verification?
- Verification testing
- Acceptance tests
- Acceptance tests thoroughness
- From Implementation to O&M
- Validation
- Transition aspects
- Transition planning decisions
- Operations and Maintenance
- O&M relevant to the system development
- Maintenance scope
- Hardware and software failures
- Improvements within the system development context
- Verification, Validation within the system development context
- Training
- Importance of training
- Documentation
Cross-Cutting Activities
- Configuration management
- Configuration management within the system development context
- Goals, necessity and functions
- 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
Risk Management
- Determining the systems engineering approach
- Low-risk projects
- High-risk projects
- SEA as a Decision Tool
- Managing project resources
- Project management
- Technical management
- SE management plan
- SEMP development stages
- SE resources
- SE Impact on institutions
Systems Engineering- Life Cycle
- Concept development
- Operational needs evaluation
- Concept of operations
- Operational requirements
- High-Level conceptual definition
- Requirements engineering
- Eliciting, collecting, and developing requirements
- Assessing and defining requirements
- Exceptional deliberations for conditions of uncertainty: prototyping and experimentation
- System architecture
- Architectural structures, models, and views
- Methods to architecture development
- Architectural patterns
- System design and development
- Derive system-level technical requirements
- Derive top-level system design
- Evaluate the design’s capability to meet the system requirements
- Systems integration
- Determine and analyze Integration and Interoperability (I&I) challenges
- Develop and assess I&I solution approaches
- Evaluate integration testing methods
- Interface management
- Test and analysis
- Generate and analyze test and evaluation approaches
- Analyze test and evaluation plans and processes
- Verification and validation
- Generate and analyze certification and accreditation strategies
- Implementation, O&M, and transition
TONEX Hands-On Workshop Sample
- Defining the system, sub-systems, and components
- Choose the design suitable for your system
- Define the goals, mission, vision, and scope
- Evaluate the operational needs
- Finding out the requirements
- Designing the relevant tests
- Verifying and validating tests
- Evaluating the resutls
Introduction to Systems Engineering