This is an old revision of the document!
Table of Contents
Systems Engineering Workflow Use Case Workshops
The Model Capture and Management Team
| Name | Organization | |
|---|---|---|
| John Watson | Lockheed Martin | john.watson@lmco.com |
| Rick Steiner | Skygazer Consulting | rick@ricksteiner.net |
| Dick Welling | Boeing | dick.welling@boeing.com |
| Eldad Palachi | IBM | eldad.palachi@il.ibm.com |
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 use cases identified. We have selected five to work on first.
The goal of these sessions will be to refine the selected Systems Engineering Workflow Use Cases.
If you would like to participate, read the goal of the use cases below and email John Watson at john.watson@lmco.com indicating which use cases you would like to help refine. Please prioritize your selections.
Reserved Meeting Rooms
| Date | Time | Location |
|---|---|---|
| Tuesday, 1/27/2015 | 9 AM PT | TBD |
| Tuesday, 1/27/2015 | 1 PM PT | TBD |
Initial Use Cases
| 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 all 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. |
