Report: Interface Design Specification |
 |
 |
This report describes how the requirements imposed on the system to support particular interconnections external to the system are met. The titles of this report and its companion, the Interface Requirements Specification , are chosen to make them familiar to those used to working with the Interface Requirements Specification (IRS) and Interface Design Description (IDD) that were required by software development standards such as Mil-Std-498. Its use here is extended beyond software interconnections to include, for example, mechanical, electrical, thermal, and human interconnections. Thus, a collection of these reports could cover the needs of the Interface Control Document (ICD), a well-known artifact to those in the systems engineering domain. Note that the usage of the term "interface" here is not strictly in accordance with UML. Described in these reports are interconnects , which have at least two interfaces, one to the system and one to the actor, and some type of connection between the two. From the perspective of the system, it offers, provides, or supports an interface (realizes it in UML terminology) and requires an interface to be realized by the actor (at the other end of the connection). In this way, the interconnect forms a contract between system and actor. This report is concerned with how required interfaces are realized , and so identifies actors, details the entities that flow between the actors and the system, describes the connection characteristics and design, and describes the (UML) interfaces provided and required by the system, in terms of their attributes and operations, and their associated protocol state machines. |
|
Relationships
Main Description
Identification and overview
Briefly identify the system and the interfacing entities which this report describes.
Interface design
Diagram
Include the Context Diagram in its intermediate and final forms. Label each interconnect (usually one for each
actor-system pair).
Interconnects
For each labeled interconnect, include a paragraph which briefly describes (as appropriate):
-
The interfacing entities (usually only the actor, because the other end is the system in each case).
-
The type of the interconnect (for example, data transfer, mechanical linkage, mass or energy transfer).
-
Logical and physical design decisions and characteristics for the connection, for example the medium,
bandwidth, reliability, latency, attenuation, security/privacy considerations (such as encryption), dimensions,
loads, tolerances, voltages, and so on. Do not specify physical characteristics if this can be deferred for
consideration with the deployment model.
-
Provided and required interfaces, including their attributes, operations and protocol state machines. For each
operation, describe its parameters - these are items that flow between actor and system, and there must be a
clear mapping to those specified in the IRS report.
|
© Copyright IBM Corp. 1987, 2006. All Rights Reserved.
|
| |
|