Describing an Application Environment
MEGA Architecture allows you to refine your analysis of the information system. Such an analysis usually focuses only on a small part of the information system.
In this way you can create an environment diagram of a specific application, describing information flows exchanged, databases used, org-units and procedures concerned.
The environment diagram enables placing of the application in its use context. In it are defined the exchanges identified or expected (service contracts).
+ Rather than use environment diagrams, MEGA recommends that you use internal application architecture diagrams to reference the applications. You must therefore create "system application" type parent applications (eg: Accounting Application System). This method is used to improve, in particular, the description of inter-applicative flows that will then be defined within an application system.
The environment diagram is not used to describe breakdown into application modules or services (see application tree). Nor does it contain the applications and services necessary for its operation (see internal architecture diagram).Its precise use framework enables proposal of suitable behaviors when introducing the application or service into the diagram. All applications added to the diagram are considered as "neighboring applications", and as a result there is no automatic link addition (breakdown or internal architecture participation link). You can also add to the diagram technical infrastructure elements such as the servers hosting the applications and databases, and the network connecting the servers with agency workstations.
The icon 
that appears under certain objects indicates they are described by a diagram..See:
For more details on diagrams and described objects, see: