Beruflich Dokumente
Kultur Dokumente
• This document provides its user with a brief and essential overview
of the process and issues regarding interface design.
Data end
data object
control flow
Customer
Requirements
Identify system
System
boundaries
Constraints
[1-b]
System in its
Environment
[1-a]
External
Interface
Requirements
Top Level
Design & Identify internal Identify interface
Functional interfaces [5-c] constrains
Analysis
Top Level
Interface
Definitions*
Verify interface
Interface
consistency
Detailed Design
[2-d],[4-a],[6-a]
Interface
Detailed Design*
Conceptual Test
Plan**
Detailed
Interface POD†
Plan
† POD = Proof of Design
Methodologies Working Group &Tools 13 System Interfaces – Definition and Design
Interface Management and Control
– External Interface
– Internal Interface
– Physical Interface
– Logical Interface
– H/W Interface
– S/W Interface
Note: Any single interface may be classified into more than one
of the above
• Synchronization method
• Periodic / event-driven
• The test plan should include (beside schedule and tasks list)
the tests for each interface, the pre-conditions and success
criteria for transition from one test to the other.
• The test plan should take into account need for simulators,
sniffers and recordings, needed for testing the interfaces.
b) 4.3.1.4.4.2 N2 Charts
* copyright © by INCOSE
Methodologies Working Group &Tools 25 System Interfaces – Definition and Design
References (3)