Building Application Layer Diagrams

Application layer diagrams allow you to model the architecture of your systems in order to identify your applications and their main components, and to analyze their interactions and how they implement business process and functions:

• Application Architecture Diagram Basics
  An application architecture diagram provides a high-level graphical view of the application architecture, and helps you identify applications, sub-applications, components, databases, services, etc, and their interactions.
• Service-Oriented Diagram Basics
  A service-oriented diagram provides a graphical view of your business and application services and the relationships between them, and helps you associate applications and other application layer objects with business services and processes to assist with SOA design.
• Application and Business Services (EAM)
  An application service is an externally visible unit of functionality, provided by one or more applications or components, and exposed through well-defined interfaces.
• Systems, Applications, and Databases (EAM)
  A System is a packaged application that can contain sub systems, applications, services and other application elements.
• Components (EAM)
  A component is an encapsulated, reusable, and replaceable part of an application, which can be used to implement a service or an application.
• Forms, Documents, and Reports (EAM)
  A form represents a UI component of an application.
• ETL Jobs (EAM)
  An ETL job represents a task in an ETL data transformation.
• Application Links (EAM)
  An application link is an oriented link that is used to connect objects in the application layer.
• Contracts (EAM)
  A contract is an agreement between services.