Task: Create Subsystem Model |
|
 |
This task creates a new subsystem model that will ultimately be populated with first the hand off from systems engineering, followed by the subsystem deployment architecture, and the software analysis and design. |
Disciplines: System Engineering Architecture |
|
Purpose
The purpose is to create a model-based environment in which the subsystem engineerings - of all disciplines - can work. |
Relationships
Roles | Primary Performer:
| Additional Performers:
|
Inputs | Mandatory:
| Optional:
|
Outputs |
|
Main Description
Following systems engineering, a hand off from the system team to each of the subsystem will be created. It will be a
package - or possibly even a separate model - that forms the model-based specification for the subsystem. This
task creates the subsystem model that will import that specification and provide a place for the subsystem team to
allocate the requirements into the various discipline, create the deployment architecture for the subsystem and for the
software engineers to put their software analysis and design.
|
Steps
Determine desired structure
This step outlines the model structure to be used. See guidance materials for recommended model organizations. |
Create empty model
Create model package structure
Import System Engineering Specification
Create a locally controlled copy of the engineering specifications handed off by systems engineering. The imported
specification will require refinement - including allocation to engineering disciplines and creation of derived
requirements - before it is ready to be used. |
Establish Subsystem baseline
The subsystem baseline includes the hand off information imported from system engineering, the deployment architecture of
the subsystem the allocated requirements and specified interdisciplinary interfaces. This forms the starting point of what
is commonly known as "down-stream engineering" or "development engineering" which includes design and development of
electronic, mechanical and software aspects of a subsystem. |
|
Key Considerations
It is not expected that the non-software engineering disciplines will continue to work in UML/SysML models after the
requirements are allocated and the deployment architecture defined. Nevertheless, this model provides the specification
for those hardware engineering disciplines.
|
Licensed Materials - Property of IBM
© Copyright IBM Corp. 1987, 2012. All Rights Reserved.
|
|