Project Management

Interface Control Document (ICD)

last edited by: Dave Garrett on Mar 24, 2007 12:14 PM login/register to edit this page

Contents
1 Why Create One?
2 Examples

Interface Control Document (ICD) is a document that describes the interface(s) to a system or subsystem. It may describe the inputs and outputs of a single system or the interface between two systems or subsystems. It can be very detailed or pretty high level, but the point is to describe all inputs to and outputs from a system.

Interface control documents are a key element of systems engineering as they define and control the interface(s) of a system, and thereby bound its requirements. An ICD should only describe the interface itself, and not the characteristics of the systems which use it to connect.

An ICD doesnt have to be a textual document. It can come in many forms. For instance, an application programming interface (API) is a form of ICD.

Why Create One?

ICDs allow systems to be developed in smaller, well understood components.

ICDs are often used where subsystems are developed by distributed teams (perhaps offshore) as a way to communicate information about subsystems interfaces between different subsystem design teams.

Examples

A Database ICD for the Gemini Database Handling System.

For the Mars Orbiter

For the National Practicioner Data Bank's ITP.

One in the form of a GUI.


last edited by: Dave Garrett on Mar 24, 2007 12:14 PM login/register to edit this page


ADVERTISEMENTS

"In the fight between you and the world, back the world."

- Kafka