• Introduction
  • Presentation of this Guide
    • Guide Structure
    • Additional Resources
  • MEGA Architecture Overview
    • Reasons for Modeling your Information System Architecture
    • A Complex and Extensive Information System
    • Creating Maps of the Applications and Databases
    • City Planning of an Information System
    • Defining the Functional Components of an Application
    • Describing Interactions Between Applications
    • Optimizing a Client/Server Architecture
    • Describing Technical Infrastructure
• Getting Started
  • Connecting to MEGA MEGA Windows Front-End
  • Connecting to MEGA WEB Front-End
  • Prerequisites for Using MEGA Architecture
    • Managing Message Options Messages
  • Using Diagrams
    • Creating an application
    • Creating a Diagram Describing an Application
    • Creating an "Overview of Applications" Diagram
    • Creating org-units
    • Modifying the Properties of an Object
    • Using flows
      • Creating a Message Flow With Content
      • Defining Message Flow Content
    • Creating a message
      • Creating messages while connecting them
      • Creating messages first and then connecting them
    • Managing Specialized Views
    • Improving the Layout of your Diagram
• Modeling Enterprise Architecture
  • Describing an Application Architecture
    • Information System Composition
      • Applications
      • Application system
      • Applications listing
      • Exchanges between applications
    • Managing Application Versions
  • Describing an Application Environment
    • Prerequisites to Using the Environment Diagrams of an Application
    • Opening an Application Environment Diagram
    • Creating an Application Environment Diagram
    • Copying Objects from Existing Diagrams
    • Reusing Objects
  • Detailing Application Internal Architecture
    • Opening an Application Internal Architecture Diagram
    • Describing Message Flows
    • Running the Check Tool (MEGA Windows Front-End)
      • Checking diagram objects
      • Applying consistency rules
  • Describing Internet Applications
  • Creating Application Trees
    • Creating the Application Tree of an Application
      • Creating an application
      • Creating services
      • Creating composition links
      • Creating architecture links
  • Describing Inter-Site Telecommunications Infrastructure
    • Consulting Existing Diagrams
    • Inserting Graphic Elements in a Technical Infrastructure Diagram (MEGA Windows Front-End)
  • Modeling Technical Infrastructures
  • Application Architecture Reports
    • Report Examples
    • MEGA Architecture Report Templates
• Describing Interactions
  • Use Context
    • Purchasing Management System Internal Architecture Diagram
    • Displaying Activities corresponding to Applications
    • Automating Exchanges: Interactions
  • Describing interactions
    • Creating an interaction with an Existing Exchange Contract
    • Describing Exchange Contracts
    • Describing Exchange Message Flows
• Modeling Complex Infrastructures
  • Context of use
    • Resource Architectures Example
      • Modeled system general architecture
      • Support Center Architecture
      • Call center architecture
    • Artifacts Example
  • Describing a Resource Architecture
    • Describing a Resource Architecture
      • Implementing Capabilities
    • Describing Resource Architecture Organizational Resources
      • Creating an architecture use
      • Creating a human asset
    • Describing Equipment Resources
      • Creating a physical asset
      • Channels and communication ports
    • Describing Resource Architecture Services and Requests
    • Describing Interaction in a Resource Architecture Diagram
  • Describing an Artifact
    • Creating an Artifact
    • Describing Artifact Components
      • Creating an artifact component
      • Creating an application host
      • Channels and communication ports
    • Describing Artifact Services and Requests
    • Describing Interactions in an Artifact Assembly Diagram
  • Describing Communications of a Complex Infrastructure
    • Describing services and requests
      • Service points
      • Request points
    • Creating a Service Point or a Request Point
    • Managing Interactions
      • Creating an Interaction
      • Connecting interaction points
    • Describing Communications at Equipment Level
      • Communication ports
      • Communication channels
      • Network communication protocols
      • Connecting Communication Element Points
  • Summary of Terms Used
    • Diagrams and their objects
      • Objects pop-up menu
      • Described element properties
      • Associated Object Properties
    • Resource Architecture Tree
• Application Deployment
  • Defining Required Architecture
  • Deploying Required Infrastructure
    • Creating a Mapping Tree
      • MEGA Windows Front-End
      • MEGA Web Front-End
    • Establishing Mappings
    • Object status
  • Analyzing Deployment of Applications
    • Analysis report example
    • Compliance indicators
• Information System City Planning
  • City Planning Use Context
    • City planning objectives
    • City planning justification
    • City Planning and Application Architecture
  • City plan
    • Creating a City Plan
    • Opening a City Planning Diagram
    • Duplicating a City Plan
      • City plan names in a multilingual environment
  • City Planning Level
    • Areas and Sub-Areas
    • Properties of areas, districts and blocks
    • Example of breakdown into areas, districts and blocks
    • Data Acquisition Area
    • Data Processing Area
    • Other areas
  • Communication channels
  • Correspondences Between City Planning Areas
  • Application System Compliance with City Plan
    • Specifying City Plan Compliance Rules
    • Indicating Elements Hosted by the Area
      • Linking hosted elements to city planning rules
      • Compliance Report Operation
    • Evaluating IS Compliance with City Plan
      • Report Results
• Service Oriented Architecture (SOA)
  • The Service, pivotal point between business functions and IT
  • Service Oriented Architecture principles
    • Designing a Service Oriented System
    • Designing the Reference Patterns
      • Reuse
      • Support services provision
      • Capacity management improvement
    • Characterizing Services
      • Services deduced from data models
      • Application services
      • Business process orchestration services
      • Communication services
      • Administration services
      • Security services
      • Identifying interactions
  • Adjusting the Application Architecture
    • Integrating New Applications
    • Service Accessibility
    • Deployment
    • SOA Analysis Reports
• Detail of concepts used
  • 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
  • Technical Infrastructure Diagram
    • Basic TID Concepts
      • Organizational elements: org-units, etc.
      • Distributed processing
      • Specialization
    • Main Uses of the TID
  • Applications Tree
  • Site Tree
  • Overview of Sites and Site Flow Assessment
  • Concepts managed by MEGA Architecture
    • Org-unit
    • Applications
    • Database
    • Information Flow (Message)
    • Node
    • Workstation
    • Project
    • Network
    • Server
    • Service
    • Site
    • Timer