M&M FDT 1.2.1 Online Specification
 5.4 Frame Application Use Case Realization


Interfaces and Methods   -   Schemas   -   FDT Specification   -   Quicklinks   -   Abbreviations

Up to FDT Specification

5.1 Actors
5.2 Use cases
5.2.1 Observation
5.2.2 Operation
5.2.3 Maintenance
5.2.4 Planning
5.2.5 OEM Service
5.2.6 Administrator
5.3 DTM Use Case Realization
5.4 Frame Application Use Case Realization

5.4 Frame Application Use Case Realization

This section describes any operation the Frame Application must provide for the realization of the FDT Uses Cases.The operations are again listed in tabular form and introduced in a brief description explaining their function in the context of the FDT-concept.

Operation:

GUI

Brief Description:

This main operation logically links all GUIs the Frame Application realizes into an element of the software concept.

Also in this case, two types of realization are viewed like in the realization of the GUI operation.

Operation:

Print

Brief Description:

The print operation is a central part in the Frame Application which realizes Frame Application-internal print operations and communicates with the interfaces in order to print DTM-specific data.

Operation:

Archive View

Brief Description:

A Frame Application may provide an archive for storing sensor data for example. The realization of display and analysis of archive data is performed by this operation.

Operation:

Asset Management

Brief Description:

Frame Application provides asset management functions.

Operation:

Audit Trail

Brief Description:

Frame Application provides mechanism for storage and display of audit trail information.

Operation:

Bulk Data Handling

Brief Description:

Frame Applications provide an option to apply individual functions like the Upload and Download of groups of devices.

This operation realizes the parameterization and management of a wide range of devices.

Operation:

Busmaster Config

Brief Description:

If Frame application provides access to Fieldbus communication this operation allows configuration of the communication.

Operation:

Data Format Association

Brief Description:

Frame Application manages the format information of stored data sets and is able to associate DTM to the data sets. Refer to chapter 6.25.2

Operation:

DTM matching

Brief Description:

Frame Application compares the results from Scan to the information that is available in the Device Catalogue and finds the correct DTM for a physical device. Refer to chapter 6.2.1.1

Operation:

Login

Brief Description:

Before an actor is entitled to work within the Frame Application and one of his/her DTMs, his/her user role must have been specified and verified.

Contrary to the Device-Specific Login the user's role can also remain valid for several sessions.

Operation:

Parameter Migration

Brief Description:

Frame Application provides mechanism to copy data from one DTM instance to an other DTM instance. This mechanism is handled with SingleDataAccess interfaces and may need additional user interaction.

Operation:

Repair Device

Brief Description:

This use case stands for operations which must be performed to repair or change a device.

Example: A Frame Application supports a temporary deletion of a device with automatically parameterization download when the device has been reinstalled.

Operation:

Software Configuration

Brief Description:

The configuration operation lets a user define the structure of complex devices. Configuration is used online and offline.

Operation:

System Planning

Brief Description:

The operation element is responsible for bracketing all functions that the Frame Application must provide in order to define the data structure, the communication and the communication links of the entire system.



© by M&M Software GmbH, parts of this website taken from FDT Interface Specification Version 1.2.1, © by FDT Group, AISBL.
This website is published for support of M&M products as granted in license conditions, chapter 2.1.
Last updated 2015-02-05 15:17
Email: FDT Technical Support Line.