User Tools

Site Tools


Back to the MBSE Workshop at INCOSE IW 2015

Systems Engineering Workflow Use Case Development Workshops

The Model Capture and Management Team

Name Organization email
John Watson Lockheed Martin
Rick Steiner Skygazer Consulting
Dick Welling Boeing
Eldad Palachi IBM

Overview Of the Project

The Systems Engineering Workflow Use Cases project originated as part of the SysML Roadmap effort within the OMG Systems Engineering Domain Special Interest Group (SE DSIG).

The intent of capturing these use cases is to identify the capabilities and infrastructure required by SE to develop systems across the product lifecycle. The near term goal is to utilize these use cases to better understand where SysML may be used in the future to better support these needs.

Plans at the 2015 INCOSE IW

There have been 31 Systems Engineering Workflow Use Cases identified. We have selected five to work on initially.

On Tuesday, January 27, we plan to have two working sessions to refine two or more of the use cases provided in the “Initial Use Cases Table” below. The times and location of these sessions is provided in the “Reserved Meeting Rooms Table” below.

If you would like to participate in these session, examine the “Initial Use Cases Table” and email John Watson, at, indicating which use cases you would like to help refine. Please prioritize your selections.

Based on your input we will select the use cases with the most interest and post them in the “Reserved Meeting Rooms Table”.

Meeting Documentation

Reserved Meeting Rooms Table

Date Time Location Use Cases Selected
Tuesday, 1/27/2015 9:00 - 11:00 AM PT Executive Suite 1635
Tuesday, 1/27/2015 1:00 - 2:30 PM PT Executive Suite 1635

Remote Access - PARTICIPANT GlobalMeet Join Details

Meeting Web Address:
Dial-in Number:

Access Number: 1-719-325-2630

Guest Passcode: 827 509 8579

Initial Use Cases Table

Use Case Name Use Case Goal
1. Analyze Stakeholders Needs The goal of this workflow use case is to identify all stakeholders and better understand and capture their required needs expectations, goals, and objectives across the entire product life cycle.
2. Derive System Requirements The goal of this workflow use case is to derive a set of system level requirements for the system-of-interest based on the stakeholder's needs requirements.
3. Derive Product Architecture The goal of this workflow use case is to evaluate the System Requirements and from them derive the most appropriate architecture to satisfy the customer needs.
4. Evaluate System Safety The goal of this workflow use case is to evaluate the system for safety related hazards and derive a plan to mitigate these risks.
5. Collaborate with Implementation Domain Team - (software, mechanical, electrical)Goal of this workflow use case is provide an automated capability to effectively share information between Systems Engineering and the component implementation engineering domains, such as the software, electrical, and mechanical domains.
mbse/methodology/iw2015_agenda.txt · Last modified: 2015/01/27 12:00 by jcwatson