Principles of Systems Engineering
This course utilizes the INCOSE SE Handbook version 4 in teaching the fundamentals of Systems Engineering. The course contextualizes the various Organizational, Project and Technical processes that are necessary to realize a “System-of-Interest.” With the aid of a comprehensive Process Flow diagram (created specifically for this course), the Instructor will walk the students from the Portfolio Management Process to the Disposal Process in a logical and sequential manner, while covering all 31 processes within the INCOSE SE Handbook.
By the end of the course, the student will:
- Have a good grasp of the fundamentals of Systems Engineering, including the understanding of Systems Engineering management and Systems Engineering processes, from the INCOSE perspective.
- Be able to apply the INCOSE SE Handbook to a project.
Anyone seeking to gain a understanding of core Systems Engineering principles, including but not limited to Program Managers, Project Managers, Quality Personnel, Configuration Managers, Developers, and Testers.
Register 21 days before class start date and save 10%! Enter discount code EARLY10 during registration.
Register 21 days before class start date and save $250! Enter discount code EARLY250 during registration.
1 The Context of Systems Engineering – From Organization to Project level: The need for Systems Engineering from an organizational point of view. These processes help ensure the organization’s capability to realize a system through the initiation, support and control of projects by providing resources and infrastructure.
- 1.1 Introduction to Systems Engineering: Identify what a system is and how systems engineering is used to create them.INCOSE SE Handbook and SE Standard – ISO/IEC/IEEE 15288:2015; concept of the System Life Cycle Model. Processes covered: 7.1 Life Cycle Model Management and 8.0 Tailoring
- 1.2 Organizational Processes – Project-Enabling and Agreements: Identify the processes an Organization needs to use in order to create and resource a project. Processes covered: 7.3 Portfolio Management; 7.5 Quality Management; 7.6 Knowledge Management; 7.2 Infrastructure Management; 7.4 Human Resource Management; 6.1 Acquisition; 6.2 Supply
2 Requirements: From Stakeholder to System: Analyze mission needs and then transform this stakeholder, user-oriented view of desired capabilities into a technical view of a solution that meets the operational needs of the user.
- 2.1 Mission and Stakeholder Requirements: Analyze mission needs and document stakeholder, user-oriented view of desired capabilities. Processes covered: 4.1 Business or Mission Analysis; 4.2 Stakeholder Needs and Requirements Definition; Life Cycle Concepts; Characteristics of Good Requirements
- 2.2 System and Interface Requirements: Transform stakeholder desired capabilities into a technical view of a solution that meets the operational needs of the user. Processes covered: 9.3 Functions-Based Systems Engineering Method; 4.3 System Requirements Definition; 4.4 Architecture Definition; 9.6 Interface Management; 4.5 Design Definition
3 Design Considerations: While considering the system design, the Systems Engineer needs to address specialized engineering areas, and consult Subject Matter Experts and assign them, as appropriate, to conduct specialty engineering analysis.
- 3.1 Specialty Engineering Activities Part 1: Design impact from Cost, Electromagnetic, Environmental, Interoperability and Logistics concerns. HDBK Sections covered: 10.1 Affordability/Cost-Effectiveness/Life Cycle Cost Analysis; 10.2 Electromagnetic Compatibility; 10.3 Environmental Engineering Impact Analysis; 10.4 Interoperability Analysis; 10.5 Logistics Engineering;
- 3.2 Specialty Engineering Activities Part 2: Design impact from Manufacturing, Mass, RAM, Resilience, Safety, Security, Training and HSI concerns. HDBK Sections covered: 10.6 Manufacturing and Producibility Analysis; 10.7 Mass Properties Engineering; 10.8 Reliability, Availability, and Maintainability; 10.9 Resilience Engineering; 10.10 System Safety Engineering; 10.11 System Security Engineering; 10.12 Training Needs Analyses; 10.13 Usability Analysis/Human Systems Integration
4 Technical Processes – From Element Design to Disposal: Designing and then realizing the specified system elements that make up the solution, then integrating them together, and ensuring the completed system fulfills its specified requirements characteristics and mission. Deploy and sustain the system within its operational environment. When use is no longer required, dispose the system properly.
- 4.1 Implementation to Verification: Understand the processes for realizing the specified system elements that make up the solution, then integrating them together, and ensuring the completed system was built right. Processes covered: 4.7 Implementation; 4.8 Integration; 4.9 Verification
- 4.2 Transition to Disposal: Understand the processes for ensuring the right system was built to fulfills its mission, that the system is deployed, operated and sustained within its operational environment, and eventually disposed of properly.Processes covered: 4.1 Transition; 4.11 Validation; 4.12 Operation; 4.13 Maintenance; 4.14 Disposal
Is there a discount available for current students?
UMBC students and alumni, as well as students who have previously taken a public training course with UMBC Training Centers are eligible for a 10% discount, capped at $250. Please provide a copy of your UMBC student ID or an unofficial transcript or the name of the UMBC Training Centers course you have completed. Online courses are excluded from this offer.
What is the cancellation and refund policy?
Student will receive a refund of paid registration fees only if UMBC Training Centers receives a notice of cancellation at least 10 business days prior to the class start date for classes or the exam date for exams.