Delegates need to have a prior OCSMP Model Builder - Fundamental certification before attending the training
The OCSMP Model Builder – Intermediate examination tests the knowledge and skills used to develop system models using the full SysML feature set. This capability enables more detailed and precise modeling of requirements, structure, behavior, and parametric constraints than those modeled at the Fundamental level. In addition, this engineer has the understanding needed to organize complex models, define the inter-relationships among model elements and diagrams, and assess aspects of model quality including conformance to language and method constraints. The level of knowledge tested by this certification, accompanied by a corresponding level of expertise in model based systems engineering methods and tools, is appropriate for a System Modeling Lead for a project and for the top-ranked team members who contribute independently to the model or to the system, such as a Lead Systems Engineer. The OCSMP Model Builder - Intermediate Certification is a prerequisite for the program's highest certification, OCSMP Model Builder – Advanced, and requires the OCSMP Model Builder – Fundamental certification as its prerequisite.
The course structure is based upon the book - A Practical Guide to SysML: The Systems Modeling Language by Friedenthal, Moore, and Steiner.
Introduction to Systems Engineering Overview
- Motivation
- The Systems Engineering Process
- Typical Application of the Systems Engineering Process
- Document-Based vs Model-Based Approach for Systems Engineering
- Quick Revision of SysML
- SysML Purpose and Key Features
- SysML Diagram Overview
- Introducing SysML-Lite
- A Simplified MBSE Method
- The Learning Curve for SysML and MBSE
- OCSMP Certification Coverage and SysML
- Overview on SysML Models with Diagrams
The Package Diagram
- Overview
- Defining Packages Using a Package Diagram
- Organizing a Package Hierarchy
- Showing Packageable Elements on a Package Diagram
- Packages as Namespaces
- Importing Model Elements into Packages
- Showing Dependencies between Packageable Elements
Blocks
- Block Definition Diagram
- Modeling the Structure and Characteristics of Blocks Using Properties
- Flows
- Block Behavior
- Modeling Interfaces Using Ports
- Modeling Classification Hierarchies Using Generalization
- Modeling Block Configurations Using Instances
- Semantics of Blocks
Constraints
- Constraint Expressions
- Encapsulating Constraints in Constraint Blocks to Enable Reuse
- Using Composition to Build Complex Constraint Blocks
- Using a Parametric Diagram to Bind Parameters of Constraint Blocks
- Constraining Value Properties of a Block
- Capturing Values in Block Configurations
- Constraining Time-Dependent Properties to Facilitate Time-Based Analysis
- Using Constraint Blocks to Constrain Item Flows
Activities
- The Activity Diagram
- Actions—The Foundation
- Object abd Control Flows
- Signals and Other Events
- Structuring Activities
- Advanced Flow Modeling
- Modeling Constraints on Activity Execution
- Relating Activities to Blocks and Other Behaviors
- Modeling Activity Hierarchies Using Block Definition Diagrams
- Enhanced Functional Flow Block Diagram
- Executing Activities
Modeling Message-Based Behavior with Interactions
- The Sequence Diagram
- The Context for Interactions
- Lifelines
- Exchanging Messages between Lifelines
- Representing Time on a Sequence Diagram
- Complex Scenarios Using Combined Fragments
- Complex Interactions
- Decomposing Lifelines to Represent Internal Behavior
State Machine Diagram
- Event-Based Behavior and State Machine
- Specifying States
- Transitioning between States
- Operation Calls
- State Hierarchies
- Contrasting Discrete and Continuous States
Use Case Diagram
- Using Actors to Represent the Users of a System
- Using Use Cases to Describe System Functionality
- Elaborating Use Cases with Behaviors
Modeling Text-Based Requirements and Their Relationship to Design
- Requirement Diagram
- Representing a Text Requirement in the Model
- Types of Requirements Relationships
- Cross-Cutting Relationships
- Depicting Rationale for Requirements Relationships
- Depicting Requirements and Their Relationships in Tables
- Modeling Requirement Hierarchies in Packages
- Modeling a Requirement Containment Hierarchy
- Modeling Requirement Derivation
- Asserting That a Requirement Is Satisfied
- Verifying That a Requirement Is Satisfied
- Reducing Requirements Ambiguity Using the Refine Relationship
- Using the General-Purpose Trace Relationship
- Reusing Requirements with the Copy Relationship
Allocations
- Allocate Relationship
- Allocation Notation
- Kinds of allocation
- Reuse: Specifying Definition and Usage in Allocation
- Allocating Behavior to Structure Using Functional Allocation
- Allocating Behavioral Flows to Structural Flows
- Allocating between Independent Structural Hierarchies
- Modeling Structural Flow Allocation
- Allocating Deeply Nested Properties
- Evaluating Allocation across a User Model
Customizing SysML for Specific Domains
- The SysML Specification and Language Architecture
- Defining Model Libraries to Provide Reusable Constructs
- Defining Stereotypes to Extend SysML Concepts
- Extending the SysML Language Using Profiles
- Applying Profiles to User Models in Order to Use Stereotypes
- Applying Stereotypes when Building a Model
- Defining and Using Viewpoints to Generate Views of the Model
Object-Oriented Systems Engineering Method
- Method Overview
- A case study/example
Integrating SysML into a Systems Development Environment
- Specifying an Integrated Systems Development Environment
- Data Exchange Mechanisms
- Selecting a System Modeling Tool
Deploying SysML in an Organization
- Improvement Process
- Elements of a Deployment Strategy