HOPEX IT Architecture : HOPEX IT Architecture : Detail of concepts used : Application Architecture Diagram
   
Application Architecture Diagram
 
Basic AAD Concepts
Organizational elements: the org-units
Hardware and technical elements: servers and workstations
Specialization
Distributed processing
Inter-site Analysis
Main Uses of the AAD
Application architecture diagrams enable description of the software environment of an application, an application system or of the enterprise itself. They also enable description of the internal architecture of an application system, an application or a service.
To respond to these different requirements, there are several specializations:
Applications overview
This diagram presents the main applications of the enterprise and their interactions.
Application environment diagram
This diagram presents exchanges between the application and its main user applications. It enables placing the application in its environment without considering its internal architecture. It defines exchanges expected or identified (expected interfacing contracts, "service contracts"). It does not however describe breakdown of the application into application modules, services, etc. and does not contain the applications, services or databases required for its operation.
Application internal architecture diagram
This diagram details exchanges between components (applications and services) involved in application behavior. It enables definition of architecture and internal exchanges required for correct application operation and the explanation of how exchanges with the application environment are processed.
Service architecture diagram
This diagram details exchanges between components involved in service behavior.
Its main concepts are applications and communications that exist between them.