<Project Name>

AP310 Integration Functional Design Template

Template Version Number: 1.2

!!! Delete all blue instructions in the final version of your work product !!!
The following document is provided to use with Integration Functional Design work product. The blue
text provides guidance to the author, and it should be deleted before publishing the document.
Document Details
Document Title Custom Field
Error! Unknown document property name. / Error! Unknown document property
Status / Version
name.
Reference Code Error! Unknown document property name.

Disclaimer

If you are reading a copy of this document (i.e. print out of controlled electronic document or an electronic copy of a
wet ink signed paper document) you may be reading an uncontrolled version. Before making updates, please
ensure that you are using the latest version of this document and the associated template.

Document Approval / Review

Criteria Name & Role Signature Date
Author
Approved
Approved

Approved Add more rows as needed

Version Control
Version Date Description of Changes Author

Add more rows as needed

Referenced Documents
No. Document Title and ID Version Location
1

3 Add more rows as needed

09/04/2018 AP310 Integration Functional Design Template Page 1 of 4

 Table of Contents

1 Executive Summary............................................................................................................................... 3
1.1 Introduction..................................................................................................................................... 3
1.2 Objectives...................................................................................................................................... 3
1.3 Scope............................................................................................................................................. 3
1.4 Intended Audience.......................................................................................................................... 3
1.5 Assumptions................................................................................................................................... 3
1.6 Definitions...................................................................................................................................... 3
2 Business Activity Diagrams across Systems............................................................................................ 3
2.1 Business Process #1....................................................................................................................... 3
3 Business Objects................................................................................................................................... 3
3.1 Application Specific Business Objects.............................................................................................. 3
3.2 Common Business Object Attributes................................................................................................3
3.3 Entity Level Object Mappings.......................................................................................................... 3
3.4 Field Level Object Mappings........................................................................................................... 3
4 Business Event(s).................................................................................................................................. 3
5 Event Sequence Diagrams..................................................................................................................... 3
6 Business Process Automation Design..................................................................................................... 3

09/04/2018 AP310 Integration Functional Design Template Page 2 of 4

1 Executive Summary

1.1 Introduction
Provide background information regarding the scope of the engagement. Focus this section on the main
business goals.

1.2 Objectives
List your project’s objectives. See the boilerplate text below for an example. Add to or delete information
relevant to your project.

This document contains the functional design of a portion of the end-to-end integration solution,
providing a lower level of detail than the Conceptual Design. This document is used to tie together the
functionality, including the process and data design for the designated portion of the solution. The design
will include the UML Business Process Activity Diagrams with swimlanes depicting the activities that take
place within each in scope system and identifying the in scope interfaces. This design will also include
the detailed definitions of the objects (both application specific and common) used within the process and
the mapping of the application specific objects to the business objects. This document will also include
the Event Sequence Diagrams, which show the sequence and flow of messages through the various
solution components. Finally, this design will illustrate the proposed physical implementation of the
automated business process.

1.3 Scope
Define what is and isn’t in scope for this conceptual design.

1.4 Intended Audience

Define the design’s audience. See the boilerplate text below for an example. Add to or delete information
relevant to your project.

This template should be used by the EI Design team members responsible for developing the EI
Functional Designs, this includes the EI Architect as well as EI interface and EI process designers. This
document will be a primary input into the Interface Detailed Designs. This document will also be
leveraged by the application support team to gain understanding of the functionality and design of the
solution to be maintained.

1.5 Assumptions
Document any assumptions that are implied within the content of this deliverable.

1.6 Definitions
Provide a glossary of terms that may be helpful to the reader.

2 Business Activity Diagrams across Systems

2.1 Business Process #1

Include the activity diagrams or their locations for the in-scope business processes. Then provide a
detailed explanation of each step in the swimlane diagram.

09/04/2018 AP310 Integration Functional Design Template Page 3 of 4

3 Business Objects

3.1 Application Specific Business Objects

Include or reference the Application Specific Business Object (ASBO) Designs for the key entities
included within the scope of this Functional Design. There should be some correlation between the
ASBOs and the Common Business Objects identified in the Class Diagram located within the Integration
Solution Conceptual Design.

3.2 Common Business Object Attributes

List each attribute and its characteristics in the table below.

Attribute Description Type Length Is Key Is Req Notes/Issues

Name

3.3 Entity Level Object Mappings

Describe the mapping of the key entities across systems at a high level, such as the mapping of
customer and account (customer, billing, service account) hierarchies or product hierarchies across all
systems. This is important if you need to maintain hierarchy structures across systems or when the
applications do not natively support the same hierarchical capabilities.

3.4 Field Level Object Mappings

Reference the mapping spreadsheet or tools that capture the mapping of the Application Specific
Business Objects to the Common Business Objects. This mapping is down to the field level.

4 Business Event(s)
Within the Field Level Object Mappings, identify which fields are to be utilized within each business
event.

5 Event Sequence Diagrams

Include the various UML-based Event Sequence Diagrams outlining the sequence in which the event
interacts with each system and solution component (queues/channels, DB tables, process models, etc).

6 Business Process Automation Design

Include the Automated Business Process Design or UML based State Transition Diagram for each in-
scope process.

09/04/2018 AP310 Integration Functional Design Template Page 4 of 4