The Scope Covered by HOPEX IT Architecture
The modules offered in standard mode are used to follow a top-down approach, beginning with a review of the business capabilities of the enterprise and its strategy, and ending with a precise definition of the components of the existing or future information system.
Each module addresses specific user profiles. Standard reports are offered to simplify analysis of the subjects handled.
The method described in this guide is represented by the modules described below.
The order of use of these modules is given by way of information.Describing and analyzing flows: this step is based on scenario diagrams that represent the flows between the components of your information system.
For more details, see Describing flow scenarios.Analyzing the functional coverage of the technical architecture: during this step the reports proposed by HOPEX IT Architecture are used to analyze the links between the components of the described application architecture and the expected functionalities.
For more details on modeling applications and services, see Describing Application Architecture and Describing Applications.Describing the upgrade strategy of the information system and architecture: this step consists in describing what the information system is able to deliver, through business capabilities, and how it plans to deliver them using the architectures.
For more details, see Analyzing the functional coverage of the architecture implemented and Building the Logical Architecture.Describing the application environment: this step consists in describing the deployment architecture and all the elements that compose it.
For more details, see Defining the Deployment Architecture of an Application.Describing the technical infrastructure: this module allows to manage deployment constraints and to associate adapted solutions to them.
For more details, see Defining the technical infrastructure.Using UML formalism: furthermore, you can use the UML (Unified Modeling Language) modeling lnaguage to model your IS.
For more details, see About UML implementation.