Interface Protocol Document

This template requires a Premium Subscription

Please log in. Don't have a log-in? Sign up now. Already a Member? Log in to upgrade immediately and get the file! A Premium subscription is only $14.95/month or $149/year and gets you over 200 templates, guidelines, and checklists.

15-day free trial period for new Premium subscribers! Learn more

Log in to download this file

Username:
Password:
Forgot your password or username?

Quick Summary
An annotated outline created as a product or system's architecture is being defined, to specify how the different "building blocks" of the system will interface with other.

What this is

An Interface Protocol Document is usually created as a new product or system's architecture is being defined. It specifies how the different "building blocks" of the will interface with other.

Why it's useful

A good interface specification ensures that the technical team has thoroughly investigated and identified what interface hardware and/or software each "subsystem" must implement and how the components of the system will work together during operation to execute commands, handle error conditions, etc.

The contents of the Interface Document will be referenced by the various developers who are designing and implementing the subsystem. It may also be used by testers later in the project.

How to use it

• During the "investigation and planning" phase of the project, high-level system design should be underway. The team may create an architecture document that defines the sub-system blocks that make up the entire system or product being created or enhanced by this project.
• The Interface Protocol Document (IPD) should either contain a copy of the system block diagram with all its interfaces, or reference the appropriate interface in the Architecture document.
• The Interface Protocol Document will then specify the details of an interface as noted in the outline starting on the next page.
• The IPD should be reviewed by the developers involved in the subsystems on both sides of the interface, as well as the system architect. It test personnel will be involved in integrating the system later in the project, they should also review the document to aid their test planning and test case and pass criteria development.

This template requires a Premium Subscription

Please log in. Don't have a log-in? Sign up now. Already a Member? Log in to upgrade immediately and get the file! A Premium subscription is only $14.95/month or $149/year and gets you over 200 templates, guidelines, and checklists.

15-day free trial period for new Premium subscribers! Learn more

Log in to download this file

Username:
Password:
Forgot your password or username?

©Copyright 2000-2008 Emprend, Inc. All Rights Reserved.
About us   Site Map   View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy