Task: Define Interdisciplinary Interfaces |
|
 |
This task defines the interfaces among the different engineering disciplines (e.g. sw-electronics, electronics-mechanical) and clarifies their structure, information, behavior, and performance. |
Disciplines: System Engineering Architecture |
|
Purpose
The purpose of this task is to clearly define the means by which the design elements from different engineering disciplines
will communicate and collaborate. |
Relationships
Roles | Primary Performer:
| Additional Performers:
|
Inputs | Mandatory:
| Optional:
|
Outputs |
|
Illustrations
Key Considerations
It is important that all the involved disciplines partake in this task or a suboptimal interface will emerge. The interface
should include the services, data, physical data schema (where appropriate), constraints, performance, and physical
mechanisms of the interface. Engineers should evaluate the interface with careful consideration of adequacy, completeness,
performance, cost, and ease of development. |
Alternatives
This can be done in a UML Class or SysML Block diagram or in a textual document. |
Licensed Materials - Property of IBM
© Copyright IBM Corp. 1987, 2012. All Rights Reserved.
|
|