Describing the Functionalities of a Project
The HOPEX Application Design solution makes a distinction between the technical functionalities and the other functionalities.
A functionality is a capability expected from an equipment item (hardware or software) to ensure the operation of a business function or an organization.A technical functionality is a capability expected from an equipment item (hardware or software) to ensure the operation of a technical element or an application.Prerequisite
You must first define a work environment for a project in progress. See "The Current Design Project pane", page 21.
Describing the Functionality Map
A functionality map is a set of functionalities with their dependencies that, jointly, define the scope of a hardware or software architecture.
In our example, a functionalities map is presented in the form of the following diagram.
The expected functionalities of the project for processing urgent purchases are relative to the response times and to the availability of the application from the rental agencies. The main functionalities are divided into sub-functionalities.
Accessing the list of functionality maps
To access the list of functionality maps:
1. Click the navigation menu, then Current Design Project.
2. In the navigation window, select Functionality and Rules Design.
3. Click the List of Functionality Maps folder and select the Functionality Maps tab.
The list of functionality maps appears in the edit area.
Creating a functionality map
To create a functionality map diagram:
1. Click Current Design Projects > Functionalities and Rules Design in the navigation menu.
2. Click List of Functionality Maps and select the Functionality Maps tab.
3. Click the New button.
A Functionality Map creation window opens.
4. Specify the Name of the new functionality map.
5. Click OK.
The new functionality map appears in the list.
Describing a functionality map
A functionality map is described by a diagram.
To create a functional map diagram:
Right-click the functionality map that interests you and select New > Functionality Map.The diagram opens in the edit area. The frame of the functionality map described appears in the diagram.
To add a sub-functionality in a diagram, see Creating a functionality component in a functionality map.
To define the dependencies of sub-functionalities, see Describing the dependencies between the functionalities using the functionality map
Creating a functionality component in a functionality map
The components represented in a functionality map are functionalities.
To add a new functionality to a functionality map diagram:
1. In the diagram insertion toolbar, click Functionality Component.
2. Click the functionality map frame.
An add functionality dialog box appears:
3. Enter the name of the functionality you wish to create.
4. Click OK.
The new functionality component appears in the diagram.
Describing the dependencies between the functionalities using the functionality map
A dependency link between one functionality and another is used to specify the elements on which this dependency is based.
For example, the functionality relating to response times depends on the time to access the list of suppliers and on the time to access the availability of parts in stock.
To create dependency links between two functionalities in a functionality map diagram:
1. In the insert toolbar, click Functionality Dependency.
2. Click the functionality, and keeping the left mouse button pressed, move the cursor to the functionality used.
3. Release the mouse button.
The link appears in the diagram.
A single sub-functionality can have more than one dependency within a single functionality map.The properties of a functionality map
The Characteristics properties page of a functionality map provides access to:
• its Owner, by default during creation of the functionality map, this is the current project.
• its Name,
• the text of its Description.
With HOPEX Application Design, a functionality map is described by the following pages:
• the Structure page, which is used to specify a list of functional components owned and the dependencies between them.
For more information on the components of a functionality map, see Creating a functionality component in a functionality map and Describing the dependencies between the functionalities using the functionality map.Describing a Functionality
A functionality is a capability expected from an equipment item (hardware or software) to ensure the operation of a business function or an organization.Accessing the list of functionalities
To access the list of functionality maps from the Current Design Project navigation pane:
1. Click Functionalities and Rules Design in the navigation menu.
2. Click the List of Functionality Maps folder and select the Functionalities tab.
The list of functionalities appears in the edit area.
Functionality properties
The Characteristics properties page of a functionality provides access to:
• its Owner, by default during creation of the functionality map, this is the current project.
• its Name,
• the text of its Description.
Describing a Technical Functionality
A technical functionality is a capability expected from an equipment item (hardware or software) to ensure the operation of a technical element or an application.With HOPEX Application Design, the use of technical functionalities and technical functional maps is identical to that of the functionalities and functionality maps.
For more details on the operation of functionality maps and functionalities, see Describing the Functionality Map et Describing a Functionality.To access the list of technical functionality maps from the technical functionality map navigation pane:
1. Click Functionalities and Rules Design in the navigation menu.
2. Click the Technical Functionality Maps folder and select the Technical Functionality Maps tab.
The list of technical functionality maps appears in the edit area.
To access the technical functionality list, select the Technical Functionality tab.