1. Finding transactions through your application
A transaction is a flow through the application in terms of how a user starts to interact with the application.
Transaction usually starts with a screen data capture, and then traverse through the application logic to update or retrieve data
Flex
Spring
DB2z/OS
Java
Cobol
Oracle MQ
Example transaction
Transaction flow from Flex page all the way down to the Oracle database

2. Finding transactions through your application
Key terminology
Entry point – starting point of the transaction
Typical examples are: JSP Page, JCL program invoking COBOL, ASP.NET pages
Non-typical example: specific reports
End point – tables and view where the data is accessed (retrieve, modify, create and delete)
Architecture Context diagram
A single diagram showing the technology & framework interactions
The aim of this diagram is for the application SME to document the logical high level architectural interaction between various the technologies of the application and the application boundary (see next point)
Transaction flow
A unique flow through the application from start to end (point)
Application Boundary
Within boundary means the technology/source code of the application that is maintained by the application
Examples of boundary elements to be considered entry or exist points are the following:
External database or file systems
Incoming web service
Outgoing Messages to queues

3. Example Architecture Context diagram
Application Name : Example App
The example diagram shows:
The logical components of the application i.e. Internet, common, and Intranet.
The logical flow through the various technologies e.g.  JSP (Entry) calls Struts Action Servlets (intermediate) calls Struts Action (intermediate) , calls Spring Bean (intermediate), calls DAO (intermediate) , calls database (end).
Entry and End (Exit) points, and intermediary processes of the application. Entry and End points are explained below.
Application Boundary marked in red
External logical components outside the boundary
Application Boundary
Entry Point
Exit Point
Intermediate Process

4. How to complete the Architecture Context Diagram
This template document contains an example of what is required as explained below. If an equivalent diagram already exists which shows what is required then provide that instead of creating a new diagram
Create the your diagram on the next slide as explained below (est. 30 mins)
Show the logical flows from the entry technology components (entry point) of the application,  through various intermediate technology component layers, through to the end technology components (end/exit points) layers of the application. An explanation of Entry and End Points is given below.
Each component should be labelled with the technology name.
The flow between each technology component should indicate the direction of the flow.
Use the colour coding in the template to clearly the entry (yellow), intermediate (grey) , and end/exit  (blue) technology components accordingly which should be placed inside the Application Boundary shown by a red border.
Add any external database or system outside of the application boundary.

5. Draw Your Application Context Diagram Here
Architecture Context diagram – <<Write Your Application Name Here>>
Draw Your Application Context Diagram Here
Write Your technology here
External Database/system
Write Your technology here
Write Your technology here
Write Your Database here
Entry Point
Exit Point
Intermediate Process
Application Boundary