Scribd
Upload
25 views4 pages

Interface Control Document

Uploaded by

RajVatsayana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
25 views4 pages

Interface Control Document

Uploaded by

RajVatsayana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

<PROJECT NAME>

INTERFACE CONTROL
DOCUMENT
Version: <Type Version #>
Date:

Prepared by:

Project Manager
Approved by:

Project Sponsor
Approved by:

Agency CIO
Approved by:

Executive Sponsor
Table of Contents
1 INTRODUCTION 5
1.1 Purpose and Scope 5
1.2 System Overview 5
1.2.1 Integration Diagram 5
1.2.2 Unit Description 5
1.3 Security and Integrity 5
1.4 Project References 5
1.5 Glossary 5
2 INTEGRATION SUPPORT 6
2.1 Resources and their Allocation 6
2.2 Training 6
2.3 Testing 6
2.3.1 Change procedures and history 6

Revision History
Date Version Description Author

XX/XX/XXXX 0.0 Baseline <First Name, Last


Name>

Template Overview and Instructions:

The integration document defines the activities necessary to integrate the software units and
software components into the software item. The integration document contains an overview of
tile system, a brief description of the major tasks involved in the integration, the overall
resources needed to support the integration effort. The plan is developed at the beginning of the
Implementation Phase and is updated throughout with final version delivered at closeout.
1 INTRODUCTION
<This section provides an overview of the information system and includes any additional
information that may be appropriate.>

1.1 Purpose and Scope


<This section describes the purpose and scope of the Integration Document. Reference the
system name and identify information about the system to be integrated.>

1.2 System Overview


<This section provides a brief overview of tile system to the integrated, including a description of
the system and its organization. Describe the environment/infrastructure and how this unit or
system will integrate into it. Include any risk involved and the mitigating procedures to reduce or
eliminate that risk.>

1.2.1 Integration Diagram


<This section provides a pictorial view of the interface flow and control across the system.
Provide high-level detail into:
● Communication protocol
● Source, recipient
● Frequency
● Security
● Flow control (ack/nak), etc.>

1.2.2 Unit Description


<This section provides an overview of the processes the unit (or module) is intended to support.
If more than one unit is being integrated, provide descriptions of each unit in this section. List
out each integration unit’s message format and field/element definition such as names,
identifiers, frequency, validation rules, etc.>

1.3 Security and Integrity


<Briefly describe how access security will be implemented and how data transmission security
will be implemented for the interface being defined. Include a description of the transmission
medium to be used and whether it is a public or a secure line. Include a brief description of how
data will be protected during transmission and how data integrity will be guaranteed. Include a
description of how the two systems can be certain they are communicating with each other and
not with another system masquerading as one of them.>
1.4 Project References
<This section provides key project references and deliverables that have been produced before
this point in the project development.>

1.5 Glossary
<Provide a glossary of all terms and abbreviations used in the document. If it is several pages
in length, it may be placed in an appendix.>

2 INTEGRATION SUPPORT
<This section describes the support software, materials, equipment, and facilities required for
the integration, as well as the personnel requirements and training necessary for the
integration.>

2.1 Resources and their Allocation


<In this section, list all support software, materials, equipment, and facilities required for the
integration. Describe the test environment and any resources needed. Describe the number of
personnel needed and an estimate of the costs for them.>

2.2 Training
<This section addresses the training, if any, necessary to prepare for the integration and
maintenance of the system; it does not address user training, which is the subject of the
Training Plan. If contractors are performing the integration functions and activities, this may not
be necessary. It however, State staff are performing these activities some training might be
needed. List the course(s) needed by title, instructor and cost.>

2.3 Testing
<In this section, list all the test requirements for each unit. If more than one unit is being tested,
include a description for each unit. Include the descriptions of the data included, procedures for
testing, who is responsible for the testing and a schedule. This could be accomplished in one
plan or several depending on the complexity of the unit being tested.>

2.3.1 Change procedures and history


<Include all changes made during the unit testing. This information should be included in the
Configuration Management Plan and updated during the Implementation Phase.>

You might also like