(Deprecated) HOPEX Application & Design > Introduction to HOPEX Application Design > Connection to the HOPEX Application Design Desktop
Connection to the HOPEX Application Design Desktop
*HOPEX Application Design is mainly intended for web users. Desktops described in this guide are accessible only to Web desktop users.
Prerequisite: Importing the Primitive Types
To access primitive types in HOPEX Application Design, the administrator must import the “Information Architecture” solution pack.
Preparing the import
Files to be imported are delivered in compressed files that you must decompress before importing them into a repository.
1. In the folder in which HOPEX is installed, open the Utilities folder, then the Solutions Pack folder.
2. Double-click the Information Architecture.exe file.
3. Extract the Contents of the file.
Importing the solution pack
To import the solution pack:
1. Launch "Administration.exe" and connect as a user with data administration rights.
*The "System" identifier enables connection with the "Administrator" user. This user is created by default, with repository administration rights. It has no profile (it has all rights) and no password is assigned at installation.
2. Select the environment then the repository on which you want to work.
3. Right-click the repository and select Object Management > Import a Solution Pack.
A dialog box with a list of solution packs appears.
4. Sélect Information Architecture - DataType and Information Architecture - XsdType and click OK.
5. Exit the Administration application.
Connecting to the solution
To connect to HOPEX Application Design, see HOPEX Desktop.
The HOPEX Application Design desktop
The menus and commands available in HOPEX Application Design depend on the profile with which you are connected.
* 
*For more details on using the Web platform for HOPEX solutions, see "Using HOPEX".
Presentation of space common to all roles 
All users have access to the HOPEX Application Design desktop and access to the following panes:
Home, Dashboards and List of Tasks that are common to all users of HOPEX solutions.
Ideation: refers to the management process for ideas that become possible project demands.
Reports: accesses all reports, improving understanding of terms and their use.
Presenting the application designer desktop 
In addition to the panes offered in standard mode to all HOPEX Application Design desktop users, the application designer has access to the following panes:
The Environment pane 
The Environment pane provides access to the following menus:
Organization, to access the list of org-units and repository processes.
Standard navigation, to build the Enterprises, allocate users to the different steps.
Projects, to access the list of projects and create new ones.
*For more details on project creation, see "Creating an Application Design Project", page 31.
The Current Design Project pane 
By default, on connection, this pane is not available.
Before defining a current project, confirm that you have created an ”Application Design” type environment in the properties of the project in question. See "Assigning a Working Environment to a Project", page 30.
To define a current project:
1. Click Main Menu.
2. Select Change Work Environment and select the previously created project concerned.
The Current Design Project pane integrates the method embedded in the HOPEX Application Design solution and it provides access to the following menus:
Current Project Definition, to describe the project scope, its structure and the stakeholders.
Identification of Needs, to describe the objectives and requirements of the project.
*For more details on describing the project objectives and requirements, see "Defining the Objectives and Requirements of a Project (AD)", page 41.
Functionalities and Rules Design, to build the functional specifications of the project.
*For more information on the functional specification tools, see "Defining the Objectives and Requirements of a Project (AD)", page 41.
Data Scope, to describe the packages and the logical and relational data of the project to define the database.
*For more details on project data, see "Describing the Data of a Project", page 65.
Application Architecture Design, to describe the technical elements of the project such as the applications, the IT services, the micro-services, the batch processes and the interfaces.
*For more information on technical specification tools, see "Describing the Technical Specifications of a Project", page 77.
Validation & Verification, this facility is based on workflows that are used to manage project progress.
See also "Creating an Application Design Project", page 31.
The Application Design Resource pane 
The Application Design Resource pane provides access to the objects in the repository referenced if applicable in the project:
Process, see the guide HOPEX Business Process Analysis.
Service Contracts & Catalogs, see Describing data exchanges.
Application Processes, Batches and Interface, see "Describing Application Processes", page 82.
Technologies, see the HOPEX IT Architecture guide.
Technological Stacks, see the HOPEX IT Architecture guide.
UML Implementation, see "About UML implementation".
Batch Processing, see "Describing Batch Processing", page 89.
The Collaboration pane 
The Collaboration pane provides access to the workflow management features.
Presenting the desktop of the functional administrator for application design 
The HOPEX Application Design functional administrator for application design has the application panes offered to the application designer.
The application design functional administrator also has the Administration pane that gives him access to user rights management.
*For more details on administrator tasks, see HOPEX Power Supervisor administration guide.
Presentation of the application owner desktop 
In addition to the panes offered in standard mode to all HOPEX Application Design desktop users, the application owner has access to the following panes:
The Application Design Resource pane which provides access to the objects in the repository referenced if applicable in the project:
Process, see the guide HOPEX Business Process Analysis.
Service Contracts & Catalogs, see Describing data exchanges.
Application Processes, Batches and Interface, see "Describing Application Processes", page 82.
Technologies, see the HOPEX IT Architecture guide.
Technological Stacks, see the HOPEX IT Architecture guide.
UML Implementation, see "About UML implementation".
Batch Processing, see "Describing Batch Processing", page 89.
The Application Design Resource pane provides access to the objects in the repository referenced if applicable in the project:
Process, see the guide HOPEX Business Process Analysis.
Service Contracts & Catalogs, see Describing data exchanges.
Application Processes, Batches and Interface, see "Describing Application Processes", page 82.
Technologies, see the HOPEX IT Architecture guide.
Technological Stacks, see the HOPEX IT Architecture guide.
UML Implementation, see "About UML implementation".
Batch Processing, see "Describing Batch Processing", page 89.
Presentation of the desktop of the application design contributor 
With HOPEX Application Design, the application design contributor has the same panes as the application owner, see Presentation of the application owner desktop.
Presentation of the application designer desktop 
In addition to the panes offered in standard mode to all user of the HOPEX Application Design desktop, the UML designer has access to the Application Design Resource which provides access to the objects of the repository referenced if applicable in the project:
Process, see the guide HOPEX Business Process Analysis.
Service Contracts & Catalogs, see Describing data exchanges.
Application Processes, Batches and Interface, see "Describing Application Processes", page 82.
Technologies, see the HOPEX IT Architecture guide.
Technological Stacks, see the HOPEX IT Architecture guide.
UML Implementation, see "About UML implementation".
Batch Processing, see "Describing Batch Processing", page 89.