Systems Interface Document

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 9

DOCUMENT NAME VERSION:

PROJECT NAME: DATE:

SYSTEMS INTERFACE DOCUMENT FOR


<PROJECT NAME>

AUTHOR:
CLIENT:
RELEASE DATE:
BUSINESS SPONSOR:

PAGE 1 OF 9
DOCUMENT NAME VERSION:
PROJECT NAME: DATE:

TABLE OF CONTENTS
PART 1: VERSION HISTORY...................................................................................................................................3
PART 2: APPROVALS AND SIGN-OFF..................................................................................................................4
PART 3: KEY RESOURCES AND DOCUMENT CIRCULATION......................................................................5
PART 4: INTRODUCTION........................................................................................................................................6
1. OBJECTIVES OF THE DOCUMENT.........................................................................................................................6
2. SCOPE..................................................................................................................................................................6
3. SYSTEMS ARCHITECTURE DIAGRAM/DATA FLOW DIAGRAMS...........................................................................6
PART 5: <<FROM SYSTEM – TO SYSTEM>>......................................................................................................7
SECTION 5.1 : <<MESSAGE NAME>>..........................................................................................................................7
PART XX: GLOSSARY...............................................................................................................................................8
PART XX: APPENDICES...........................................................................................................................................9

PAGE 2 OF 9
DOCUMENT NAME VERSION:
PROJECT NAME: DATE:

PART 1: VERSION HISTORY


Version Author Date Comments

PAGE 3 OF 9
DOCUMENT NAME VERSION:
PROJECT NAME: DATE:

PART 2: APPROVALS AND SIGN-OFF


This document has been approved as the vision and scope report for the project and accurately reflects the current
understanding of the proposed solution, its scope and associated risks. Following approval of this document,
requirement changes will be governed by the project’s change management process, including impact analysis,
appropriate reviews, and approvals under the general control of the project plan and according to company policy.

Prepared by

NAME Date

Approved by

NAME Date

NAME Date

NAME Date

NAME Date

PAGE 4 OF 9
DOCUMENT NAME VERSION:
PROJECT NAME: DATE:

PART 3: KEY RESOURCES AND DOCUMENT CIRCULATION


# Department Name

1 Business
2 Project Management
3 Technology

PAGE 5 OF 9
DOCUMENT NAME VERSION:
PROJECT NAME: DATE:

PART 4: INTRODUCTION
1. Objectives of the Document
The objectives of this document are to establish the system interfaces to transmit messages between the various
systems involved in this project.

2. Scope
This document is limited to the business-related messages transmitted between systems. Any messages required
for a purely technical purpose are out of scope for this document
<List all the systems covered by this interface document>

3. Systems Architecture Diagram/Data Flow Diagrams


<Add the high level systems architecture or data flow diagrams and describe the key interfacing systems>

PAGE 6 OF 9
DOCUMENT NAME VERSION:
PROJECT NAME: DATE:

PART 5: <<FROM SYSTEM – TO SYSTEM>>


Section 5.1 : <<Message Name>>
From System To System Messaging Format Comments
(XML etc)

<<Describe each field within the message along with values and their business descriptions in below tabular
format. Use first row in below example as a guidance>>

Message Details
ID / Tag Field Possible
Mandatory?
Number Name Field Values Description
I = Internal Client/ Entity.
Used if order generated for Nomura entities
32 ClientType I/N Y N = External Client
Used if order generated by external clients/non-
Nomura entities
N

<<Instructions- Repeat Part 5 for each pair of interfacing systems in the project. Repeat Section 5.1 for each
message used within the interface>>

PAGE 7 OF 9
DOCUMENT NAME VERSION:
PROJECT NAME: DATE:

PART XX: GLOSSARY

PAGE 8 OF 9
DOCUMENT NAME VERSION:
PROJECT NAME: DATE:

PART XX: APPENDICES

PAGE 9 OF 9

You might also like