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.1 ActorsThe actor types in the above displayed use case diagram are structured in a
hierarchical way.
The "Maintenance" actor inherits the "Operator" actor. The "Planning Engineer"
actors inherits the use cases of the "Maintenance" actor. Both the
"Administrator" and the "OEM Service" can extend the inherited actors by
additional use cases. Use cases, which are passed on to an actor of higher level,
may act in an extended way to match their intention. The following tables will give a brief description of the actors' roles:
Actor Name: |
Observer |
Brief
Description: |
This actor
stands for a person that may only observe the current process. |
Inherits: |
None |
User Level: |
FDTUserInformation.userLevel = observer |
Access
Verification: |
The access
as "Observer"
actor may not have a password. |
Use Cases: |
None |
Actor Name: |
Operator |
Brief
Description: |
This actor
stands for a person who has to observe and manage the current process.
The "Operator"
may therefore check the current status of the device, modify set values
and check if the device is well functioning.
The use
cases for this actor role should enable the user to perform a complete
diagnosis, watch the actual status and parameter set as well as the
current process variables. |
Inherits: |
Observer |
User Level: |
FDTUserInformation.userLevel = operator |
Access
Verification: |
The access
as "Operator"
requires a password. |
Use Cases: |
User Login,
Online View,
Audit Trail,
Archive,
Report Generation,
Asset Management |
Actor Name: |
Maintenance |
Brief
Description: |
A "Maintenance"
person should have the possibility to perform all necessary maintenance
operations including device exchange, teaching, calibration, adjustment,
...
The person
may therefore download verified parameter sets, modify a subset of
parameters online or offline, perform device-specific online operations
and at the end of the processing, may have the possibility to upload the
complete parameter set. |
Inherits: |
>Operator |
User Level: |
FDTUserInformation.userLevel = maintenance |
Access
Verification: |
The access
as "Maintenance"
actor requires a password. |
Use Cases: |
Simulation,
Online Operation,
Repair,
Offline Operation,
Bulk Data Handling
User Login*,Online View*,
Audit Trail*,
Archive*,
Report Generation*,
Asset Management*
(*
Inherited use cases) |
Actor Name: |
Planning Engineer |
Brief
Description: |
Planning
Engineer" stands for person like a plant engineer, a
specialist (s. VDI/VDE2187) or any fully authorized person.
This Person
has access to the complete set of functions of the Frame Application and
can use DTM functions without any restrictions. Only OEM-specific
operations are locked. |
Inherits: |
Maintenance |
User Level: |
FDTUserInformation.userLevel = planningEngineer |
Access
Verification: |
The access
as "Planning
Engineer" actor requires a password. |
Use Cases: |
DTM Instance Handling,
Simulation*,
Online Operation*,
Repair*,
Offline Operation*,
Bulk Data Handling*,
User Login*,
Online View*,
Audit Trail*,
Archive*,
Report Generation*,
Asset Management*
(*
Inherited use cases) |
Actor Name: |
Administrator
(abstract actor) |
Brief
Description: |
The "Administrator"
actor stands for person that has to perform administrative operations
within an engineering environment.
He is
responsible for adding and removing of software components. |
Inherits: |
Depends on
the Frame Application |
User Flag*: |
FDTUserInformation.administrator = TRUE |
Access
Verification: |
The access
as "Administrator"
actor requires a password. |
Use Cases: |
Integration
and all inherited use cases |
Actor Name: | OEM Service
(abstract actor) |
Brief
Description: |
The actor "OEM
Service" may perform the complete set of DTM specific
functions.
OEM
specific operation may be accessible to an "OEM
Service" actor, like resetting of internal counters and
exchanging firmware.
OEM
Service" has only inherited use cases, but the inherited use
cases (especially the "Online
Operation" use case) may have significant extensions.
|
Inherits: |
Depends on
the Frame Application |
User Flag*: |
FDTUserInformation.oemService = TRUE |
Access
Verification: |
The access
verification for an "OEM
Service" must have two security levels:
1. Frame
Application password: enables access to the Frame Application
functionality
2.
Device-specific password: enables access to OEM operation with the
device.
The
verification of the device specific password lies in the responsibility
of the DTM or even the device itself. |
Use Cases: |
Inherited
use cases only |
* "User
Flags" may be combined with any "User Level", to specify the inherited actor
role of an "Administrator" or "OEM Service" actor.
|