Use Case: 1 Revision History

Use Case Emis
1 Revision History
Version Date Description Author
1.4 12th September Use case as pr 12th September 2007 Stig Sperrevik
2007
2 October 2008 Updated 4.15.3 and added supplementary Espen Lodden
information
(Version numbers will from now be in
whole numbers only)
New text is marked in blue.
Functionality that is not yet implemented
is marked in green.
3 3rd – 4th of All occurrences of Emis changed to Teams Espen Lodden
November 2008 SR
New text is marked in blue.
Updated text is marked violet.
Functionality that is not yet implemented
is marked in green.
4 21st November Updated Use case Manage Roles, Manage Espen Lodden
2008 Data Entry, Approve Data Entry, Create Murali Krishna
Credit Data Entry
5 29th November, Updates Use case Manage Property, Murali Krishna
1st, 2nd Manage Resource, Manage Schema, Santosh R
December 2008 Manage Schema form, Manage Resource
form, Manage navigation, Manage Query
builder, Manage Report Designer, Manage
Dash Board, Manage Data Drilling, Manage
Transfer, Manage Export, Manage Import,
Manage Import from XML, Manage Roles,
Manage Options, Manage System
Messages, Manage User task, Manage Data
entry
Added Use case for Users and Favourite

folders.
4.21 and 4.22
Added General Extensions
26226536.doc Page 1 of 57 Printed 03.11.2008

Use Case Emis
2 Contents
1 Revision History.............................................................................................................................1
2 Contents........................................................................................................................................2
3 Use Cases.......................................................................................................................................4
3.1 Definition of the Actors..........................................................................................................4
3.2 Overview of the Use Cases.....................................................................................................5
4 Use Cases – Detailed description...................................................................................................6
4.1 Use Case: ”Manage Properties and Resources”......................................................................7
4.1.1 Manage Property............................................................................................................7
4.1.2 Manage Resources..........................................................................................................9
4.2 Use Case: “Manage Unit Systems”.......................................................................................11
4.2.1 Short description of SI...................................................................................................11
4.2.2 Use Case: “Manage System of Unit”.............................................................................13
4.2.3 Use Case: “Manage Quantity”......................................................................................14
4.2.4 Use Case: “Manage Unit”..............................................................................................16
4.3 Use Case: “Manage Schema”................................................................................................18
4.4 Use Case: “Manage Form”....................................................................................................21
4.4.1 Manage Form for Schemas...........................................................................................21
4.4.2 Manage Form for Resources.........................................................................................24
4.4.3 Manage Navigation.......................................................................................................24
4.5 Use Case: “Manage Workflow”............................................................................................24
4.5.1 General Description......................................................................................................24
4.6 Use Case: “Manage User Tasks”...........................................................................................24
4.7 Use Case: “Manage Data Entry”...........................................................................................25
4.7.1 Create Data Entry for Schema.......................................................................................25
4.7.2 Create Data Entry for Resource....................................................................................25
4.7.3 Read Schema Data Entry...............................................................................................26
4.7.4 Read Resource Data Entry............................................................................................26
4.7.5 Update schema Data Entry..........................................................................................26
4.7.6 Update Resource Data Entry.........................................................................................27
4.7.7 Delete Data Entry..........................................................................................................27
4.8 Use Case: “Approve Data Entry”...........................................................................................27
4.8.1 Approve Data Entry......................................................................................................27
4.9 Use Case: “Manage Credit Data Entry”.................................................................................28
4.9.1 Create Credit Data Entry...............................................................................................28
4.10 Use Case: “Run Report”........................................................................................................28
4.11 Use Case: “Manage Forecasting/Budget/Limit/Target”........................................................28
4.11.1 Use Case “Manage Forecasting”...................................................................................28
4.11.2 Use Case “Manage Budget/Limit/Target”.....................................................................29
4.12 Use Case: “Manage Import and Export”...............................................................................29
1.1.1 Manage Export.............................................................................................................29
4.12.2 Manage Import.............................................................................................................31
4.12.3 Manage Transfer...........................................................................................................33
4.13 Use Case: “Manage Reports”................................................................................................34
4.14 Use Case: “Manage Dashboard”...........................................................................................35
4.15 Use Case: “Manage Data Drilling/Graph”.............................................................................37
4.16 Use Case: “Manage Roles and Access Rights”......................................................................38
4.16.1 Manage Operations......................................................................................................38
4.16.2 Manage Tasks...............................................................................................................38

Use Case Emis
4.16.3 Manage Roles...............................................................................................................40

4.16.4 Use Case: “Manage Access Rights”...............................................................................48
4.17 Use Case: “System Documentation”.....................................................................................48
4.18 Use Case: “Manage Options”................................................................................................49
4.19 Use Case: “Create Query Builder”........................................................................................49
4.20 Use Case: “Manage System Messages”................................................................................49
4.21 Use Case: “Manage Favorites Folder”……………………………………………………………………………… 55
4.22 Use Case: “Manage Users”………………………………………………………………………………………………. 56
Use Case: “General extensions”………………………………………………………………………………………..57

Use Case Emis
3 Use Cases
3.1 Definition of the Actors
The final users of Teams SR are from very different backgrounds and systems. In order to cover all
problem areas, we use different access rights as Actors (see User Analyses for further discussion).
Actor Definition
Reader This actor can only read information in Teams SR
Contributor This actor can do the same as the Reader, plus enter data into the system.
Creator This actor can do the same as the Contributor, plus creating setup things.
Administrator This actor can do everything possible in Teams SR

Use Case Emis
3.2 Overview of the Use Cases

The main Use Cases for Teams SR, is as shown in the following diagram:
The Management Use Case, can be split up in several Use Cases, as shown in this diagram:

Use Case Emis
The Manage Workflow Use Case will be a part of the Teams SR solution. This Use Case is described in
another document, and will be developed by Teams SRoft.
4 Use Cases – Detailed description

This chapter describe each use case in detail. See also Supplementary Specification.
All the Use Cases expect a User to be logged on, and has the appropriate Access Rights.
All concepts will also have Created By, Created Time, Last Updated By, Last Updated Time. These will
be updated in a normal way, and is not described here.
The User can also attach icons.
The Descriptions are built up as follows:

Pre-Condition – states what must always be true before a scenario is begun in the use case.
Post-Condition – states what must be true on successful completion of the use case.

Use Case Emis
Basic Flow – describes the typical success path.

Extensions – describes other possible paths, both success and failure.
In the description User and System is used. The User is an actor interacting with the system, and the
System is how the solution should behave and respond.
4.1 Use Case:” Manage Properties and Resources”

Each Resource and Property that is defined will always have a Description, Help and Yellow Tip (only
exception is “Blank Nodes”).
The tree of Resources/Properties are built up using their Id, separated with ‘/’. The Id is actually a
“namespace”, where the user only will see the last part of the name, and the rest of the name is
indicated with a tree-structure.
Resources can also be seen in a tree using their “isA” relation.
Each Use Case will be possible to cancel, before it is saved!
4.1.1 Manage Property
4.1.1.1 Create Property

Pre-Condition:
Post-Condition: A Property was created.
Basic Flow:
1. The user indicates show property.
2. The System shows a list of all properties sorted through caption (see Read Property).
3. The User indicates Create Property.
4. The User enters a property Caption and Name.
5. The user enters Help and Yellow text.
6. The User Selects an Icon.
7. The User indicates Domain.
8. The System shows a list of Resources/Schema/Thing as Domain.
9. The User selects Resource/Schema/Thing as Domain.
10. The system creates Resource/Schema/Thing as Domain.
11. The User indicates Range.
12. The system shows Range list.
13. The User selects Resource/Data Types as Range.
Repeat from 7. until Finish
14. The System creates the selected Resources/DataType as Range
15. The System saves the new Property
16. The System creates a new Instance Operation for reading, updating and deleting the Property
and adds them to Roles.
Extensions:
4a. The Name exists
1. The System gives an error message
2. The System starts again from 4
13a. The User wants to create a Data Type Property
1. The System shows a list of Data Types
2. The User selects a Data Type
1a. The User selected Integer or Decimal

Use Case Emis
1a. The User indicates a Unit to be added for the Property Range
1. The System displays a list of Units
2. The User selects a Unit
3. The System adds the Unit to the Range
3. The System continues at step 14
7b. The User wants to have a combination of several Resources
1. The System adds a “Blank Node”
2. The System goes to “Create Resource” Use Case, where the Id is already given by the System
(and is not editable)
16a. The User wants to add the newly created Instance Operations to other Roles
1. The System proceeds to Manage Access Rights Use Case, with focus on the Operations
the System just created
4.1.1.2 Read Property

Pre-Condition:
Post-Condition: A list of Properties was shown
Basic Flow:
1. The User indicates Read Properties
2. The System shows a list of all Properties, indicating which Property is a DataType Property and
which is a Resource Property (with the possibility of searching on Name)
4.1.1.3 Update Property

Pre-Condition:
Post-Condition: A Property was updated
Basic Flow:
1. The User indicates an Update Property
2. The System shows a list of Properties
3. The User selects a Property
4. The System shows the details for the Property
5. The User edits the Property
6. The System saves the Property
Extensions:
5a. The User wants to have a combination of several Resources
1. The System adds a “Blank Node”
2. The System goes to “Create Resource” Use Case, where the Id is already given by the System
(and is not editable)
5b. The User indicate adding Resources to the Range
1. The System shows a list of Resources
2. The User selects a Resource
Repeat from step 1. until finish
5c. The User indicates deleting Resources from the Range
1. The System shows the list of Resources that is the Property’s Range
3. The System deletes the Range
5a. The User indicates change the Range from Resources to DataType
1. The System removes all the Resources in the Range
2. The System deletes all “Blank Node” created for this Property
3. The System shows all DataTypes

Use Case Emis
2. The User selects a DataType

1a. The User selected Integer or Decimal
1a. The User indicates a Unit to be added for the Property Range
1. The System displays a list of Units
3. The System adds the Unit to the Range
5b. The User indicates changing the Range from DataType to Resources
1. The System removes the Data Type from the Range
Repeat from step 2. until finish
6a. There are Properties, Resources, Data Entries or Schemas that refer to the Property
1a. The system will not be consistent after the change (e.g. because a Schema now uses the
Property with a Target which is no longer a specification of the Property’s Range)
1. The System gives message that the Property can not be updated
2. The operation ends without changing the Property
4.1.1.4 Delete Property

Pre-Condition:
Post-Condition: A Property was deleted.
Basic Flow:
1. The User indicates a Delete Property
3. The User selects a Property
4. The System shows the details for the Property
5. The User indicate delete
6. The System deletes the Property
Extensions:
6a. There are Properties, Resources, Data Entries or Schemas that refer to the Property
1. The System gives message that the Property can not be deleted
2. The operation ends without deleting the Property
4.1.2 Manage Resources

Manage Resources should have Constraints similar to Schema (see Use Case: “Manage Schema”
chapter for the details).
4.1.2.1 Create Resource

Pre-Condition:
Post-Condition: A Resource was created.
Basic Flow:
1. The User indicates to manage Resources
2. The System show the Resource tree sorted through caption. (See Read Resource)
3. The User indicates Create Resource
4. The System shows the new Resource in the Resource Tree, and shows all the inherited Properties
(all the Heritage Properties of the parent) – these are not editable.
5. The User gives a caption and name
6. The User enters Help and Yellow tip.
7. The User selects an Icon.
8. The User adds properties

Use Case Emis
9. The User indicates an end of creation

10. The System saves the Resource as inherited from the Selected Resource (specifying an isA
Property for the newly created Resource with Target the parent)
11. The System creates a new Instance Operation for creating, reading, updating and deleting the
Resource and adds them to Roles.
Extensions:
3a. The User creates Child Resource for existing Resource.
1. The User selects an existing Resource.
2. The User indicates create Child Resource.
3. The system lists all the inherited Properties to Child Resource.
4. Repeats the steps from 5 to 11.
5a. The Name already exists
1. The System gives an error message, and goes back to step 4.
8a. The User indicate a new Personal or Heritage Property for the Resource
2. The User Selects a Property
2a. The User creates a new Property
1. The System does the Create Property Use Case
2. The System selects the newly created Property
3. The System gives the Property a target equal to the Range
4. The System shows possible target values for the Property
5. The User specify the Target value for the Property
6. The User indicates which Group to add the Property to (or to create a new Group)
7. The System adds the Poperty to the indicated Group
8. User selects “Required”.
9. User selects “Read only”.
10. User selects Unit as read only.
11. User Sets min Range and Max Range for types ‘Decimal’, ‘Integer’, ‘String’ and ‘Date’.
12. User enters a name for Group Property.
13. User Set 1: n for a property Group.
14. User selects multiple values for a selected property.
15. User creates ‘n’ number of Groups for a Resource.
4.1.2.2 Read Resource

Pre-Condition:
Post-Condition: A list of Resources was shown
Basic Flow:
1. The User indicates a Read Resource
2. The System shows Resources in a tree structure, built up using Caption
4. The System shows the details for the Resource
Extensions:

Use Case Emis
2a. The User indicates a view

1. The System shows the Resources Names.
4.1.2.3 Update Resource

Pre-Condition:
Post-Condition: A Resource was updated
Basic Flow:
2. The System show the Resource tree (see Read Resource)
5. The User updates the Resource details
6. The System saves the updated Resource
Extensions:
5a. The User indicate a new Personal or Heritage Property for the Resource
2. The User Selects a Property
2a. The User creates a new Property
1. The System does the Create Property Use Case
2. The System selects the newly created Property
3. The System shows a tree of Resources that are the Target for the Property, or specialization of
the Target
4. The User selects the target value for the Property
5. The User indicates which Group to add the Property to (or to create a new Group)
6. The System adds the Poperty to the indicated Group
7. User selects “Required”.
9. User selects Unit as read only.
12. User Set 1: n for a property Group.
13. User selects multiple values for a selected property.
14. User creates ‘n’ number of Groups for a Resource.
5b. The User indicates an update of a Personal or Heritage Property for the Resource
1. The System shows a tree of Resources that are the Range of the Property, or specialization of the
Range.
2. The User selects the target value for the Property
5c. The User indicates a delete of a Personal or Heritage Property for the Resource
1. The System deletes the Resource
6a. There are Properties, Data Entries or Schemas that refer to the Resource or a Resource inherited
from the selected Resource
1. The System gives message that the Resource can not be updated
2. The operation ends without changing the Resource
4.1.2.4 Delete Resource

Pre-Condition:
Post-Condition: A Resource was deleted.
Basic Flow:

Use Case Emis

2. The System show the Resource tree (see Read Resource)
5. The User indicates to delete the Resource
6. The System deletes the Resource, and all the inherited Resources
Extensions:
6a. There are Properties, Data Entries or Schemas that refer to the Resource or a Resource inherited
from the selected Resource
1. The System gives message that the Resource can not be deleted
2. The operation ends without changing the Resource
4.2 Use Case: “Manage Unit Systems”

Teams SR will implement International System of Units (SI). Other user defined Systems of Units will
be built up in a similar way, with possible reference (conversion rules) to SI.
<Open question: Can Name/Symbol be the same for two different Units from different
Quantities/System of Units?>
The Name and Symbols will be unique within Teams SR.
4.2.1 Short description of SI

In SI there are seven base quantities, and several derived quantities.
A base quantity is “One of the quantities that, in a system of quantities, are conventionally accepted
as functionally independent of one another”. In SI each base quantity has one base unit, defined as
follows:
SI base unit
Base quantities Name Symbol
Length metre m
Mass kilogram kg
Time second s
electric current ampere A
thermodynamic temperature Kelvin K
amount of substance mole mol
luminous intensity candela cd
Derived units are units which may be expressed in terms of base units by means of the mathematical
symbols of multiplication and division. Certain derived units have been given special names and
symbols, and these special names and symbols may themselves be used in combination with those
for base and other derived units to express the units of other quantities.
SI derived unit
Name Symbol Expressed in Expressed in terms of
Derived quantity terms of SI base units
other SI
units
area square m2 m*m
meter
volume cubic m3 m*m*m
meter
density, mass density kilogram kg/m3 kg/(m*m*m)

Use Case Emis
per cubic
metre
force newton N m*kg*s-2
energy, work, quantity of heat joule J N*m m2*kg*s-2
power, radiant flux watt W J/s m2*kg*s-3
electric potential difference, volt V W/A m2*kg*s-3*A-1
electromotive force
There can be several units in one quantity. All units in one particular quantity can be expressed by
any of the other units in the quantity multiplied by a number. E.g. in SI, we have the base quantity
Length, which has the following units (there are more):
Name Symbol Relation

meter m (base)
kilo meter km 1000 m
deci meter dm 1/10 m
centi meter cm 1/10 dm
milli meter mm 1/10 cm
And, also in SI, we have density, which has the following units:

kilogram per cubic metre kg/m3 kg/(m*m*m) – Expressed in base units
gram per cubic metre g/m3 1/1000 kg/m3
kilogram per cubic decimetre kg/dm3 1000 kg/m3
gram per cubic decimetre g/dm3 kg/m3
gram per litre g/l g/dm3
4.2.1.1.1 Teams SR’ SI

In Teams SR we will limit some of the ways the units can be defined (see Glossary, especially
definition of Quantity/Unit Type). This will not limit the possible Units, or conversions of Units, but
will limit only the way it can be defined!
We will do this, by defining a Prefixed Unit, and saying that a Quantity/Unit Type is a collection of
Units, which contains either one Derived Unit or one Base Unit. Other units in a Quantity/Unit Type
will then be Prefixed Units.
Further will a Prefixed Unit only be defined with a relation to Base Unit in the same Quantity, and a
Base Unit can only have relation to a Base Unit in another Quantity.
4.2.1.1.2 Example of a new System of Unit created by user

A user could create a System of Unit, like the Imperial Unit. We could make the following
Quantity/Unit Type named Length:

inch in 2,54 cm – Base Unit with a
conversion rule to SI
0,0254m – Base Unit with a
conversion rule to Base Unit in
SI
foot ft 12 in
yard yd 3 ft36 in

Use Case Emis
rod, pole, perch rod 5,5 yd198 in

chain ? 4 rod792 in
furlong ? 10 chain7920 in
mile ? 8 furlong63360 in
league ? 3 miles190080 in
Notice that the Base Unit could have a conversion rule to the SI system of Units.
We could also have the following Quantity/Unit Type named Volume, which contains a Derived Unit:

fluid ounce 1/160 gallon
gill 5/160 gallon fluid ounce
pint 4 gills1/8 gallon
quart 2 pint1/4 gallon
gallon 277,42 in*in*in – Derived Unit expressed in Base
Units from same System Of Units
barrel 36 gallon
4.2.2 Use Case: “Manage System of Unit”
4.2.2.1 Create System of Unit

Pre-Condition:
Post-Condition: A System of Unit was created
Basic Flow:
1. The User indicates to create a new System of Unit
2. The System displays a “new System of Unit” form
3. The User gives a name
4. The User gives a optionally a Description
5. The System saves
6. The System creates a new Instance Operation for reading, updating and deleting the System of
Unit and adds them to Roles.
7. The user creates only one main System of Units.
Extensions:
3a. The name already exists
1. The System gives error message and returns to step 3
4.2.2.2 Read System of Unit

Pre-Condition:
Post-Condition: A list of all System of Units was shown
Basic Flow:
1. The User indicates a Read System of Unit
2. The System shows System of Units
3. The User selects a System of Unit
4. The System shows the details for the System of Unit

Use Case Emis
4.2.2.3 Update System of Unit

Pre-Condition: A user-defined System of Unit exists
Post-Condition: A user-defined System of Unit was updated
Basic Flow:
1. The User indicates an Update of System of Unit
2. The System shows a list of System of Units
4. The System shows the details for the System of Unit
5. The User edits the System of Unit
6. The System saves the System of Unit
Extension:
5a. The User change the name to an already existing System of Unit
1. The System gives an error message, and goes to step 5
5b. The User indicates edit on SI
1. The System gives message that this System of Unit can not be edited
4.2.2.4 Delete System of Unit

Post-Condition: A user-defined System of Unit was deleted
Basic Flow:
1. The User indicates a Delete System of Unit
4. The System shows the details for the System of Unit, including Properties, Resources, Data Entries
and Schemas that refer to Units in the selected System of Unit
5. The User indicates a delete
6. The System deletes the System of Unit, and the Quantities and Units that belongs to the System of
Unit
Extensions:
5a. The User indicates delete on SI
1. The System gives message that this System of Unit can not be deleted
5b. There are Properties, Resources, Data Entries and Schemas that refer to Units in the selected
System of Unit
1. The System gives message that this System of Unit can not be deleted
2. The operation ends without deleting the System of Unit
4.2.3 Use Case: “Manage Quantity”
4.2.3.1 Create Quantity

Post-Condition: A Quantity was created and associated with a user-defined System of Unit
Basic Flow:
1. The User indicates a create Quantity
4. The System shows a list of Quantities
5. The User indicates a new Quantity

Use Case Emis
6. The System displays a “new empty form”

8. The User gives a Description
9. The System saves the new Quantity belonging to the selected System of Unit
10. The System creates a new Instance Operation for reading, updating and deleting the Quantity and
adds them to Tasks and Roles
Extensions:
5a. The User selected SI
7a. the name already exists for another Quantity under the same System of Unit
1. The System gives an error message and return to step 7.
The System proceeds to Manage Access Rights Use Case, with focus on the Operations the
System just created
4.2.3.2 Read Quantity

Pre-Condition: A System of Unit exists
Post-Condition: List all Quantities associated with a System of Unit
Basic Flow:
1. The User indicates a read Quantity
4. The System shows a list of Quantities belonging to the selected System of Unit
5. The User selects a Quantity
6. The System shows the Quantity’s detail
4.2.3.3 Update Quantity

Pre-Condition: A user-defined Quantity exists
Post-Condition: A user-defined Quantity was updated
Basic Flow:
1. The User indicates an update of a Quantity
2. The System displays a list of System of Units
4. The System display a list of Quantities
6. The System the Quantity’s detail
7. The User edits the Quantity’s details
8. The System saves the Quantity
Extensions:
7b. The User gives the Quantity a name that another Quantity belonging to the same System of Unit
has
1. The System gives an error message and starts at 7
4.2.3.4 Delete Quantity

Pre-Condition: A user-defined Quantity exists
Post-Condition: A user-defined Quantity was deleted

Use Case Emis
Basic Flow:
1. The User indicates a delete of a Quantity
2. The System displays a list of System of Units
4. The System display a list of Quantities
6. The System shows the details for the Quantity, including Properties, Resources, Data Entries and
Schemas that refer to Units in the selected Quantity
7. The User indicates a delete of the Quantity
8. The System deletes the Quantity
9. The System deletes all the Units belonging to the Quantity
Extensions:
7b. there are Properties, Resources, Data Entries and Schemas that refer to Units in the selected
Quantity
1. The System gives message that the selected Quantity can not be deleted
2. The operation ends without deleting the Quantity
4.2.4 Use Case: “Manage Unit”
Create Unit
Pre-Condition:
Post-Condition: A Unit was created, and associated with a user-defined Quantity
Basic Flow:
1. The User indicates a create Unit
6. The System shows a list of Units
7. The User indicates a new Unit
8. The System displays a “new empty form”
10. The User selects the type of Unit (Basic, Derived or Prefixed)
11. The User gives a symbol to the Unit
12. The System saves the new Unit belonging to the selected Quantity
13. The System creates a new Instance Operation for reading, updating and deleting the Property and
adds them to Tasks and Roles according to parent Property
Extensions:
10a. The User indicates a Base Unit
1. The User enters optionally a conversion rule to the SI system
10b. The User indicates a Derived Unit
1. The User types the relations to a Base Unit, using multiplication and division
10c. The User indicates a Prefixed Unit

Use Case Emis
1. The User enters an expression in terms of a number multiplied by another Unit in the same
Quantity
The System proceeds to Manage Access Rights Use Case, with focus on the Operations the System
just created
Read Unit
Pre-Condition:
Post-Condition: A list of Units was shown
Basic Flow:
1. The User indicates a read Unit
8. The System shows the details for the Unit
Extensions:
4.2.4.1 Update Unit

Pre-Condition: A user-defined Unit exists
Post-Condition: A user-defined Unit has been updated
Basic Flow:
1. The User indicates an update Unit
8. The System displays the details for the Unit
9. The User edits the name
10. The User selects the type of Unit (Basic, Derived or Prefixed)
11. The System saves the Unit
Extensions:
10a. The User indicates a Base Unit
1. The User enters optionally a conversion rule to the SI system
10b. The User indicates a Derived Unit
1. The User types the relations to a Base Unit, using multiplication and division
10c. The User indicates a Prefixed Unit
1. The User enters an expression in terms of a number multiplied by another Unit in the same
Quantity

Use Case Emis
4.2.4.2 Delete Unit

Pre-Condition: A user-defined Unit exists
Post-Condition: A user-defined Unit has been deleted
Basic Flow:
1. The User indicates an update Unit
8. The System shows the details for the Unit, including Properties, Resources, Data Entries and
Schemas that refer to the Unit
9. The User indicates delete
10. The System deletes the Unit
Extensions:
9b. there are Properties, Resources, Data Entries or Schemas that refer to the Unit
1. The System gives message that the selected Unit can not be deleted
2. The operation ends without deleting the Unit
4.3 Use Case: “Manage Schema”

Each Schema that is defined will always have a Description, Help and Yellow Tip.
The tree of Schemas is built up using their Caption. It is possible to create children of a schema. The
children of a schema will inherit all groups that are marked with “heritage”. This relation is displayed
in a tree where schemas that are children of other schemas are displayed as sub nodes in the tree.
The tree can also be displayed with the names of each schema instead of captions.
I this chapter, we use “tree of Schema” to mean one of the two views.
4.3.1.1 Create Schema

Pre-Condition: User is logged on
Post-Condition: A Schema was created
Basic Flow:
1. The User Indicates show Schema.
2. The System shows a tree of all Schemas sorted through caption.
3. The User indicates create new
4. The System shows all Properties that have this schema in their domain
5. The User creates a Caption and name.
6. The User enters Help and yellow tip.
8. The User enters a Valid From and To Dates.
9. The User adds Properties to new or existing groups.
10. A default group will be present with the name “Common”.
11. The User indicates the end of the creation
12. The System saves the Schema
13. The System creates a new Instance Operation for creating, reading, updating and deleting the
Schema and adds them to Roles.

Use Case Emis
14. User can Copy and Paste the existing schema as parent/child.
14.1 The User indicates copy Schema.
14.2 The system copies the schema.
14.3 The User indicates Paste Schema.
14.4 The systems paste the Schema.
14.5 The System creates a new Instance Operation for creating, reading, updating and
deleting the Schema and adds them to Roles.
Extensions:
5a. The Name already exists.
1. The System gives an error message, and goes back to step 5.
5b. The User wants to create a new Schema from an existing Schema
1. The User indicates which Schema to make a new one from
2. The System creates a new Schema, containing all groups of the schema built from that are
marked as “Heritage”
5c. The User indicates that this is a “virtual” Schema
1. The System marks the Schema as “virtual”.
9a. the user wants a new or existing group to be heritage
1a. the user indicates that the group is heritage
1. The system sets the group as heritage and copies the group to all children of the schema.
9b. The User wants to handle Constraints
1a. The User indicates a Target of DataType for which to create a constraint
1. The User enters the Constraint details
1a. The User indicates a Precision (Input Format) Constraint
1. The User enters a Input Format using a standard (decided by developers)
1b. The User indicates a Restriction Constraint
1. The User enters a Restriction, possibly using reference to other Targets
associated with the Schema, or associated with an Export, or a
WebService (etc.), expressed with a standard (decided by developer).
[Repeat step 1 until finished] – The Restriction Constraints will be ‘anded’ together
2. The User enters conditions for when this constraint is to be enforced (IF)
1b. The User indicate a Target not of DataType for which to create constraint on
1. The User enters a filter criteria, possibly using reference to other Targets associated with
the Schema, Export, or WebService (etc.), expressed with a standard (decided by
developer)
1c. The User indicate to delete a Constraint
1. The System deletes the Constraint
1d. The User indicate an update of a Constraint
1. The System treats this as if a delete and create was done
1e. User selects” Required”.
1f. User selects “Read only”.
1g. User can select Unit as read only.
1h. User Sets min Range and Max Range for types ‘Decimal’, ‘Integer’, ‘String’ and ‘Date’.
1i. User enters a name for Group Property.
1j. User creates ‘n’ number of Groups.
9c. The User wants to handle Reference
1a. The User indicates to create a new Reference
1. The User enters a reference to a Target within the Schema, to an Export, or to a
WebService.

Use Case Emis
3. The System sets the Property to be treated as ReadOnly for Data Entries
9d. The User wants to edit Calculation Workflow
1a. the user adds an activity to the calculation workflow
1. The system displays the activity in the calculation workflow
2. The user specifies the name and formula for the activity
1b. the user indicates delete on an activity in the calculation workflow
1. The system shows the updated workflow
1c. the user indicates move on an activity in the calculation workflow
1. The system shows the updated workflow
1d. the user indicates update on an activity in the calculation workflow
1. The user specifies the new name or formula for the activity
9e. User creates “Table Group”
1. User selects “New Table Group” form from schema designer.
2. User enters a name for table group.
3. User adds “Row header”.
3.1 User selects a Resource from resource list.
3.2 User selects a property.
3.3 User filter and Target a resource from “Table filter” table.
3.4 User adds ‘n’ of Row header Levels.
3.5 User selects “Editable” and “Visible” options.
4. User creates “Table Columns”.
4.1 User selects property for table columns.
4.2 User selects ‘n’ number of table columns.
4.3 User selects data for the columns.
4.4 User selects “Editable” and “Visible”.
5. User saves the Table group by clicking OK.
6. The system saves the Table group.
4.3.1.2 Read Schema

Pre-Condition: User is logged on
Post-Condition: Schemas was shown
Basic Flow:
1. The User indicates read Schema
2. The System displays Schemas in a tree
3. The User select a Schema
4. The System shows all details (including which Forms that uses this Schema)
Extensions
3-4a. The User Activates the Look For functionality
1. The User type a text to look for (this might be extended later to be regular expression)
2. The System shows all Schemas that matches the text. The Search will be similar as to SPARQL
(but needs to be user-friendly)
3-4a. The User wants to set some Access Rights for the Schema
1. The System continues to Use Case Manage Access Rights
4.3.1.3 Update Schema

Pre-Condition: A Schema exists

Use Case Emis
Post-Condition: A Schema has been updated

Basic Flow:
1. The User indicates show Schema.
2 The User indicates update Schema.
3 The System displays Schemas in a tree
4. The User selects a Schema
5. The System shows all details.
6. The User makes some changes to the Schema.
7. The System shows what Workflow will be triggered (if any)
8. The User says ok to the changes
9. The System runs the workflows
10. The System saves the Schema, and all the other changes this implies (including going to Transfer).
Extension
10a. the schema refers to a form that has data entries
1. The system indicates that the schema cannot be updated
6a. The User wants to handle Constraints
1a. The User indicates a Target of DataType for which to create a constraint
1. The User enters the Constraint details
1a. The User indicates a Precision (Input Format) Constraint
1b. The User indicates a Restriction Constraint
associated with the Schema, or associated with an Export, or a WebService
(etc.), expressed with a standard (decided by developer).
1b. The User indicate a Target not of DataType for which to create constraint on
1. The user indicates required or read only as constraints
1c. The User indicate to delete a Constraint
1. The System deletes the Constraint
1d. The User indicate an update of a Constraint
1. The System treats this as if a delete and create was done
6b. The User wants to handle Reference
1. The User enters a reference to a Target within the Schema, to an Export, or to a
WebService.
3. The System sets the component to read-only
6c. User wants to handle validations
2. User can select Unit as read only.
5. User creates ‘n’ number of Groups.
8a. The User says not ok to the changes.
1. The Update Schema ends with no changes.
10a: The Schema is used by Forms.
1. The System shows the Forms using the Schema.
1a. The User does not have the appropriate access rights to the Forms.
1. The Update Schema ends without updating.

Use Case Emis
2. The user indicates which Form to put in a User Task list, to be attended to later.
3. The System creates a new User Task for each of the selected Forms.
4. The Update Schema ends with no updates.
10b. The Schema is referred to by Data Entries.
1a. The User does not have the appropriate access rights to the Data Entries.
1. The Update Schema ends without updating.
4.3.1.4 Delete Schema

Pre-Condition: A Schema exists
Post-Condition: A Schema has been deleted
Basic Flow:
1. The User indicates show Schema.
2. The System displays Schemas in a tree.
3. The User selects a Schema.
4. The System shows what Workflow will be triggered.
5. The User indicate delete.
6. The System deletes the Schema.
Extension
6a: The Schema is used by Forms.
1. The System shows the Forms using the Schema.
1a. The User does not have the appropriate access rights to the Forms
1. The Delete Schema ends without updating
2. The user indicates which Form to put in a User Task list, to be attended to later
3. The System creates a new User Task for each of the selected Forms
4. The Delete Schema ends with no deletion
6b. The Schema is referred to by Data Entries, schema form.
1. The Delete Schema ends without deleting.
4.4 Use Case: “Manage Form”

4.4.1 Manage Form for Schemas
Each component on the Form will have Help and Yellow Tip.
The following Use Cases uses a list of Forms. The list of forms is filtered by a list of schemas, where
only the forms using the currently selected schema will be displayed.
4.4.1.1 Create Form

Pre-Condition: A Schemas exists
Post-Condition: A Form has been created, and associated with Schemas.
Basic Flow:
1. The User indicates show schema forms
2. The system shows Schemas and schema forms below schemas
3. The User selects a schema
4. The system shows schema form for selected schema.
5. The User indicates create Form.
6. The System shows an empty Form.
7. The User enters a name for the form.
8. The User indicates a Schema to which this Form should be associated with.
9. User selects Overlap Column resource.
10. User selects Display Column.

Use Case Emis
11. The User enters Help text.

13. The virtual option is non editable.
14. The User selects form back ground colour.
15. The user selects Valid from and Valid to dates.
16. The User indicates properties that will be displayed on data entry list in data entry.
17. The user indicates table groups.
18. The user saves the schema form.
19. The system creates a new schema form.
18. The System creates a new Instance Operation for reading, updating and deleting the Form
Extension:
16a. The User wants to handle Constraints.
1a. The User indicates a component referring to a DataType for which to create a constraint.
1. The User enters the Constraint details.
1a. The User indicates a Precision (Input Format) Constraint.
1b. The User indicates a Restriction Constraint.
associated with the Form, or associated with an Export, or a WebService
(etc.), expressed with a standard (decided by developer).
2. The User enters conditions for when this constraint is to be enforced (IF).
1b. The User indicates a component referring not to a DataType for which to create a
constraint on.
1ba. the user indicates required or read only as constraints.
1bb1. The User enters a filter criteria, possibly using reference to other Targets associated
with the Form, Export, or WebService (etc.), expressed with a standard (decided by
developer).
1bb2. The User enters conditions for when this constraint is to be enforced (IF).
1c. The User indicates to delete a Constraint.
1. The System deletes the Constraint.
1d. The User indicates an update of a Constraint.
1. The System treats this as if a delete and create was done.
1e. User sets the validation for Table Groups like caption, Precision length.
1f. User sets min Range, Max Range, and Font style.
1g, The User enters Caption, Help and Yellow tip.
1h. User selects Label, Image.
1i. User indicates Tab order.
1j. User indicates Value edition for property.
9b. The User wants to handle Formulas.
1a. The User indicates to create a new Formula.
1a. This is not a Property with Target Decimal or Integer, or the Property already has a
Formula
1. The Systems displays an error message, and ends Formula handling
1b. this is a Property with Target Decimal or Integer, and does not have a Formula
1. The User enters a Formula, possibly using reference to other Targets within
the Schema, Export, or WebService (etc.), expressed with a standard
(decided by developer).

Use Case Emis
1b. The User indicates an update an existing Formula

1. The System acts as if it is deleting the old Formula, and creating a new
1c. The User indicates to delete an existing Formula
1. The System deletes the Formula
2. The System sets the component to not read-only
9c. The User wants to handle Reference
1. The User enters a reference to a Target within the Form, to an Export, or to a
WebService.
4.4.1.2 Read Form

Pre-Condition:
Post-Condition: A list of all Forms was shown
Basic Flow:
1. The User indicates show Form
2. The user selects a Schema.
3. The system shows Schema form.
4. The System displays Forms in a tree
5. The User selects a Form
6. The System shows all details
Extensions
3-4a. The User Activates the Look For functionality
1. The User type a text to look for (this might be extended later to be regular expression)
2. The System shows all Forms that match the text. The Search will be done using start of Name
3-4a. The User wants to set some Access Rights for the Form
1. The System continues to Use Case Manage Access Rights
4.4.1.3 Update Form

Pre-Condition: A Form exists
Post-Condition: A Form has been updated. Associations to Schemas has possibly been created
and/or deleted.
Basic Flow:
1. The User indicates show Schema form.

2. The User selects a Schema.
3. The system shows all the Schema forms for the selected Schema.
4. The User edits the data for Schema form.
5. The User indicates save.
6. The system saves the Schema form with updates.
4.4.1.4 Delete Form

Pre-Condition: A Form exists
Post-Condition: A Form has been deleted.
Basic Flow:

Use Case Emis
1. The User indicates show Form.

2. The System displays Forms in a tree.
3. The User selects a Form.
4. The System shows all details.
5. The User indicates delete.
6. The System deletes the Form.
Extensions:
6a. The Schema form has Data Entry.
1. The system can not delete the Schema form.
4.4.2 Manage Form for Resources

This Use Case is similar to the Use Case “Manage Form for Schema”, except that reference is done to
a Resource.
1. There is no Overlap columns for resource forms
2. There is no Virtual/non virtual options
4.4.3 Manage Navigation

The Administrator or Creator can use manage navigation to create a navigation tree for the forms.
This menu is common for all users, but it will be filtered according to each user’s access right.
There are two types of navigation nodes:

1. Navigation Folders
2. Form groups
4.4.3.1 Navigation folders

Navigation folders behave just like any folder in a tree. Navigation folders cannot contain forms
directly
4.4.3.2 Form groups

Form groups can only contain forms. Each group can contain multiple forms as long as the validation
periods for the forms don’t overlap.
 Form groups decide which period type the end user has to use when creating data entries.
This is set in the administrative tool.
 Form groups decide whether data entries created by the end user are allowed to overlap in
time. The overlap is checked towards the overlap property set in form. This is set in the
administrative tool.
 Form groups decide whether series of data entries created by the end user are allowed to
have holes. This is checked towards the overlap property set in form. This is set in the
administrative tool.
Extensions:
1. User creates subfolder for a folder to assign resource forms
2. The system lists user created reports in a default Reports folder
3. The system lists all the schema form and resource form under Unassigned forms
4. User selects and moves schema forms to group folders
5. User selects and moves resource forms to user created folders/sub folders

Use Case Emis
4.5 Use Case: “Manage Workflow”

The Manage Workflow Use Case will be a part of the Teams SR solution. This Use Case is described in
another document, and will also be developed internally by Teams SRoft developers.
The following chapter is added for information only.
4.5.1 General Description

The Workflow will be able to do most of the functionally (Use Cases) described in this document, but
in an automatic manner. There will be different Events that can start the Workflow. E.g. a change in a
Resource, Property, Schema or DataEntry, or just that a certain time has been reached.
The Workflow will also be able to send messages to users in Teams SR.
4.6 Use Case: “Manage User Tasks”

Each user task consists of:
 Subject
 Description
 User
There is no User Tasks in Teams SR, but Teams SR will integrate with other system that has Tasks (e.g.
Outlook). From main Use Cases in Teams SR, we should be able to choose “Create Task”, which will
create and open a new Task in the external system, containing the following:
 A Subject reflecting from where the Create Task was chosen
 A Text indicating what the User were currently doing
 A Link/Shortcut which can, by clicking on it, bring a User back to what the User was doing
when choosing “Create Task”.
4.7 Use Case: “Manage Data Entry”

Data entries are done through the web client.
Web client displays the forms in a navigation tree with folders and group folders. (More information
on this see, Manage Navigation)
4.7.1 Create Data Entry for Schema

Pre-Condition:
Post-Condition: A Data Entry was created
Basic Flow:
1. The User indicates show navigation tree.
2. The System displays navigation tree. (Folders, group folders and resource forms in a tree).
3. The User Selects a Group Folder and indicates add new Data Entry.
4. The System shows a Form where the user can enter From date and To date and the user selects
data column for the schema form.
5. Based on from date and to date the system display the correct form.
6. The User enters data.
7. The User indicates Calculate.
8. The system calculates the data entry.
9. The User indicates save the Data Entry.
10. The System saves the Data Entry.
11. The System creates a new Instance Operation for reading, updating and deleting the Data entry
Extensions:

Use Case Emis
4a. The group folder has an overlap property

1. The system displays the Range of property filtered according to the user access rights.
2. The user selects a resource for which he has “select” access rights.
4b. The system informs the user when wrong periods are selected for the data entries which are
not allowing holes and overlaps.
4c. The system shows a Note regarding Valid period type Overlap and Allow holes.
4d. The User enters same from date and to date for data entry form, the system shows an error
message.
6a. The User indicates calculate
1. The System shows the result.
6b. One or more of the values have validations defined in the form.
1. The system checks the validations and informs the user if there are any breaches.
6c. User adds filtered resource from the lookups to table group.
6d. User deletes the added rows from the table group.
6d. The system informs user when wrong decimal separator is entered for decimal type property.
4.7.2 Create Data Entry for Resource

Pre-Condition:
Post-Condition: A Data Entry was created
Basic Flow:
2. The System displays navigation tree. ( folders, group folders and resource forms in a tree)
3. The User Selects a resource form and indicate new add Data Entry.
4. The System shows the resource Form.
5. The User enters data.
7. The System saves the Data Entry.
Extensions:
6a. The user clicks Back button, the system will not save the form.
4.7.3 Read Schema Data Entry

Pre-Condition:
Post-Condition: A Data Entry details was shown
Basic Flow:
2. The System displays folders, group folders and resource forms in a tree
3. The User selects a group folder.
4. The system displays a list of data entries.
5. The user selects a data entry and indicates read.
6. The System shows the details for the Schema form and the values of data entry itself.
Extensions:
4a. The User wants to search for a Data Entry
1. The System gives the User a way of searching for a Data Entry
4.7.4 Read Resource Data Entry

Pre-Condition:

Use Case Emis
Post-Condition: A Data Entry details was shown

Basic Flow:
3. The User selects a resource form.
4. The system displays a list of resource data entries.
6. The System shows the details for the resource form and the values of data entry (resource)
itself.
Extensions:
4a. The User wants to search for a Data Entry
1. The System gives the User a way of searching for a Data Entry
4.7.5 Update schema Data Entry

Pre-Condition: A Data Entry exists
Post-Condition: A Data Entry has been updated
Basic Flow:
5. The user selects a data entry.
7. The User edits the data
9. The System saves the Data Entry
Extensions:
7a. The User indicates calculate.
7. The System shows the result.
7b. User edits the date for schema form.
8a. The system will return to schema form list without saving the form when back button is
Clicked.
4.7.6 Update Resource Data Entry

Post-Condition: A Data Entry has been updated
Basic Flow:
3. The User selects a resource form.
6. The System shows the details for the Resource form and the values of data entry (resource)
itself.
7. The User edits the data
8. The User indicates finish
9. The System saves the Data Entry

Use Case Emis
4.7.7 Delete Data Entry

Post-Condition: A Data Entry was deleted.
Basic Flow:
3. The User selects a group folder / resource form.
5. The user selects a data entry and indicates delete.
6. The User indicates ok
7. The System deletes the Data Entry.
Extensions:
6a. Approved data entries cannot be deleted.
6b. if the data entry has references it cannot be deleted.
4.8 Use Case: “Approve Data Entry”

4.8.1 Approve Data Entry
Pre-condition: A Data Entry exists which is not approved
Post-Condition: A Data Entry was approved.
Basic Flow:
7. The User indicates Approve.
8. The system approves data entry and the data entry can no longer be modified or deleted.
4.9 Use Case: “Manage Credit Data Entry”

4.9.1 Create Credit Data Entry
Pre-condition: A Data Entry exists which does not have any Credit Data Entry referring to it
Post-Condition: A Credit Data Entry was created
Basic Flow:
7. The user indicates Create credit data entry.
8. The User indicates finish
9. The System saves the Credit Data Entry.
10. The credit data entry cannot be modified or deleted.
Extensions:
1. The user creates new schema form for the credit data entry form when user not having

Use Case Emis
allowed holes checked.
4.10 Use Case: “Run Report”

Pre-condition: A Report exists
Post-condition: A report is showing data from the system.
Basic Flow:
1. The User indicates run report
2. The System shows a list of Reports
3. The User selects a Report
4. The System shows the details for the Report
5. The User indicates run
6. The System runs the Report and displays the result
Extensions:
3a. The User selects Report date filter.
3b. The system shows report on selected From date and To date.
5a. The user indicates that the Data Entries participating in the report should be marked.
1. The System marks all the Data Entries participating in the report, with a DateTime stamp, and
the Name for the Report.
2. The mark should have a specific name for future easy retrieval and re-run.
4.11 Use Case: “Manage Forecasting/Budget/Limit/Target”

In order to get Forecasting (or What If), Budget, Limit and Target into the system, we will make use
of”virtual” data, and other concepts and Use Cases functionality.
This Use Case should be implemented in a general way so that similar integration tasks can be
handled using the same approach.
4.11.1 Use Case “Manage Forecasting”

To do a Forecasting is similar to the following steps:
1. Export
2. Do a forecasting based on the exported data. This will be done outside of Teams SR.
3. Import into a Schema of”virtual” type or enter manually the”virtual” data.
4. Run a Report or a Dashboard, comparing”virtual” data with “real” data.
Since this Use Case is only using the functionality of Use Cases written other places, its functionality
will not be repeated here.
4.11.2 Use Case “Manage Budget/Limit/Target”

To do Budget, Limit or Target is to do the following:
1. Import data into a Schema of”virtual” type or enter manually”virtual” data.
2. Run a Report or Dashboard comparing ”virtual” data with “real” data
4.12 Use Case: “Manage Import and Export”

It will be possible to do a transformation when doing Import and Export. Properties, Resources,
Schemas and Data Entries are especially important when it comes to Import and Export.
Both Import and Export should be possible to cover with WebServices.

Use Case Emis
Teams SR data Import/Export
Teams SR
Resources XSD
XSDs XSDs
XSD XSD XSD
XSD XSD
XML
Mappings Mappings
XML
Database
4.12.1 Manage Export

The Result of an Export is in XML. It should be possible to do a mapping of data from Teams SR
(extracted using Query Builder) to an XML Schema. This is similar to doing a mapping in BizTalk (see
picture below). The XML Schema describes the structure of the exported XML data.
4.12.1.1 Create Export

Pre-Condition:
Post-Condition: An Export has been created
Basic Flow:
1. The User indicates show Export.
2. The System shows Export form.
3. The User selects Export from Query.
4. The User indicates a Query.
5. The system shows Query dialog box.
6. The User selects a Query to Export.
7. The User selects a Format either EXCEL, PDF, HTML, XML to Export Query.
8. The User indicates Export.
9. The system shows a save File dialog, for either EXCEL, PDF, HTML or XML.

Use Case Emis
10. The User indicates finish.

11. The System saves the Export.
Extensions:
3a. The User selects Export from object.
1. The system gives a choice to Export either Property, Resource, Schema, Unit Systems or Data
entries on form.
2. The User indicates an Export of either Property, Resource, Schema, Unit Systems or Data
entries on form.
3. The user indicates Export.
4. The system shows a Save File dialog, for XML file.
5. The User indicates finish.
6. The system saves Exported XML file.
4.12.1.2 Read/Run Export

Pre-Condition: An Export exists
Post-Condition: An Export was done
Basic Flow:
1. The User indicates run Export.
2. The System shows a list of Exports.
3. The User selects an Export.
4. The System shows the details for the Export.
5. The User indicates run.
6. The System runs the Export and displays the result with the option of saving to file.
4.12.2 Manage Import

The Imported data is in XML. To do an Import we need an XML Schema that validates the XML data.
The result of an Import can be new Properties, Resources, Schemas or Data Entries. The structure of
the imported data will be as follows:
1. The structure of Properties will be according to the Property concept in Teams SR

2. The structure of Resource will be decided by what Resource the new Resources are mapped to
(that is; what Resource is to be the parent of the imported Resources)
3. The structure of Schemas will be according to the Schema concept in Teams SR
4. The structure of Data Entries will be decided by which Teams SR Schema the Data Entries will be
mapped to.
There might be a calculation in the mapping from the XML Schema to the Teams SR concepts.
This is similar to a mapping in BizTalk (see picture below).
4.12.2.1 Create Import

Pre-Condition:

Use Case Emis
Post-Condition: An Import has been created

Basic Flow:
1. The User indicates show Import.
2. The system lists all the Imports.
3. The User selects Import from teams XML.
4. The User indicates File name.
5. The System shows a File Open dialog, for XML files.
6. The User indicates an XML file to import from.
7. The user indicates an import of either Properties, Resources, Schemas, Unit Systems or Data
Entries.
8. The User indicates Import.
9. The System Imports the data.
10. The System creates a new Instance Operation for reading, updating and deleting the Import and
gives the User these access rights.
Extensions:
3a. The User indicates Import from Excel.
1. The System gives the user a choice to import either Properties, Resources, Schemas, Unit
Systems or Data Entries.
2. The User indicates an import of either property, Resource, Schema, Unit System,
Quantity or Unit.
3. The User indicates File name.
4. The system shows a File Open dialog, for XLS files.
5. The User indicates an XLS file to Import from.
7. The system saves the Import.
8. The System creates a new Instance Operation for reading, updating and deleting the
Import and gives the User these access rights.
7a. The User indicates Resources
2. The User indicates a Resource that will be the parent to the imported data
7b. The User indicates Data Entries
1. The System shows a list of Teams SR Schema
2. The User indicates a Schema that will be validating the imported data
4.12.2.2 Read/Run Import

Pre-Condition: An Import exists
Post-Condition: An Import was done
Basic Flow:
1. The User indicates show Import.
2. The System shows a list of Imports.
3. The User selects an Import.
4. The System shows the details for the Import
6. The System shows an Open XML dialog (e.g. file or WebService).
7. The User indicates what should be imported
8. The System validates the XML file to the XML Schema

Use Case Emis
9. The System Imports the data, and flags that this is an Import (this is important for Database
Triggers, that will possibly react in a special way for Import)
Extensions:
8a. 000000000000000000000the validation fails
1. The System gives an error message and ends.
4.12.3 Manage Transfer

A transfer is to move or copy from one Resources, Schemas or Data Entries to another
Resource/Schema/Data Entries.
There might be a calculation in the mapping of the Transfer. This is similar to doing a mapping in
BizTalk (see picture below).
4.12.3.1 Create Transfer

Pre-Condition:
Post-Condition: A Transfer has been created
Basic Flow:
1. The User indicates show Transfer.
2. The System lists all Transfers.
3. The User indicates create.
4. The User enters a name.
5. The System gives the user a choice to Transfer Resources or Data Entries.
6. The User indicates a Transfer of either Resources or Data Entries.
7. The System shows a mapper (see picture above), with the structure of the chosen Resources or
Schemas on the left and right side.
8. The User creates a mapping.
9. The System displays the mapping.
11. The System saves the Transfer.
12. The System creates a new Instance Operation for reading, updating and deleting the Transfer and
gives the User these access rights.
Extensions:
5a. The User indicates Resources
2. The User indicates which Resources will be transferred
3. The User indicates a Resource that will be the parent to the transferred Resources
5b. The User indicates Data Entries
1. The System shows a list of Teams SR Schema
2. The User indicates which Schema’s Data Entries will be transferred
3. The User indicates a Schema that will be validating the transferred Data Entries

Use Case Emis
5c. The user indicates Schema
1.1 The system shows a list of schemas
1.2 The User indicates from which schema to be transferred
1.3 The user indicates to which schema the data to be transferred
1.4 User does the mapping between the indicated schemas
1.5 User saves the transfer.
1.6 The system saves the transfer.
4.12.3.2 Read/Run Transfer

Pre-Condition: A Transfer exists
Post-Condition: A Transfer was done
Basic Flow:
2. The System shows a list of Transfers.
3. The User selects a Transfer.
4. The System shows the details for the Transfer.
6. The System runs the Transfer and displays the result.
4.12.3.3 Update Transfer

Pre-Condition: A Transfer exists
Post-Condition: A Transfer was updated
Basic Flow:
3. The User selects the Transfer that should be updated.
4. The System shows the detail for the Transfer.
5. The User edits the Transfer.
6. The System saves the updated Transfer.
4.12.3.4 Delete Transfer

Pre-Condition: A Transfer
Post-Condition: A Transfer was deleted
Basic Flow:
3. The User selects a Transfer.
4. The System shows the details for the Transfer.
6. The System deletes the Transfer.
4.13 Use Case: “Manage Reports”

This use case describes Create, Update and Delete. The “Read” (or “Run”) is described in a separate
chapter.
Users often need to view a report, before they can decide that the report has been defined the way
they want. If the report takes long time to view, we should consider showing fewer data (in a draft
view), or sample data, while the user is making the report.

Use Case Emis
4.13.1.1 Create Report

Pre-Condition:
Post-Condition: A Report has been created
Basic Flow:
1. The User indicates show Report.
2. The system lists all the Reports.
3. The User indicates create Report.
5. The User selects a Query from Query look up dialog box.
6. The system adds Query.
7. The User selects From date and To date.
8. The User selects which information should be displayed in the Report, and in which form it
should be displayed, possibly aggregating and grouping data.
9. The user indicates create.
10. The System saves the Report.
11. The System creates a new Instance Operation for reading (running), updating and deleting
the Report and gives the User these access rights.
Extensions:
1. The System proceeds to Manage Access Rights Use Case, with focus on the Operations the
System just created
4.13.1.2 Update Report

Pre-Condition: A Report exists.
Post-Condition: A Report has been updated.
Basic Flow:
1. The User indicates show Report.
2. The System shows a list of Reports.
3. The User selects the report that should be updated.
4. The System shows the detail for the Report.
5. The User updates the Report.
6. The System saves the updated Report.
4.13.1.3 Delete Report

Pre-Condition: A Report exists
Post-Condition: A Report has been deleted
Basic Flow:
1. The User indicates delete Report.
2. The System shows a list of Reports.
3. The User selects a Report.
4. The System shows the details for the Report.
6. The System deletes the Report.
4.13.1.4 Copy and Paste

1. The User indicates show Reports.
2. The system lists all the Reports.
3. The user indicates Copy by right clicking the mouse.
4. The system copies the Report.

Use Case Emis
5. The User indicates Paste Report.

6. The system creates a copy of Report.
8. The system saves copy of Report.
4.14 Use Case: “Manage Dashboard”

Dashboards are visualisation of key indicators. A User will want to set this up to “constantly” monitor
the data.
The User can have several Dashboards; each with a set of frames or “boxes” that displays
(Runs/Reads) either a Data Drilling, a Graph or a Report.
4.14.1.1 Create Dashboard

Pre-Condition:
Post-Condition: A Dashboard has been created
Basic Flow:
1. The User indicates show Dashboard.
2. The system shows list of Dashboards.
3. The User indicates create a Dashboard.
5. The User indicates Reports.
6. The User selects a Report.
7. The user indicates save.
8. The System saves the Dashboard.
Dashboard and gives the User these access rights.
Extensions:
4a. Enter existing name.
1. The User enters an existing name.
2. The system shows an error message, name already exists.
3. Repeat step 4.
9. The System proceeds to Manage Access Rights Use Case, with focus on the
Operations the System just created.
4.14.1.2 Read Dashboard

Pre-Condition: A Dashboard exists
Post-Condition: A Dashboard was shown
Basic Flow:
2. The System shows a list of Dashboards.
3. The User selects a Dashboard.
4. The System shows details of the Dashboard.
4.14.1.3 Update Dashboard

Post-Condition: A Dashboard has been updated
Basic Flow:

Use Case Emis
3. The User selects the Dashboard that should be updated.

4. The System shows the Dashboard.
5. The User selects a different Report.
6. The System shows a list of Reports that can be shown in the frame
7. The User chooses a Report.
8. The User updates the Access rights
10. The System saves the updated Dashboard.
4.14.1.4 Delete Dashboard

Post-Condition: A Dashboard has been deleted
Basic Flow:
3. The User selects a Dashboard.
4. The System shows the Dashboard.
6. The System deletes the Dashboard.
4.15 Use Case: “Manage Data Drilling”

Data Drilling is a visual data analysis. A User should be able to do analysis in a visual and clear way.
4.15.1.1 Create Data Drilling

Pre-Condition:
Post-Condition: A Data Drilling was created
Basic Flow:
1. The User indicates show Data Drilling.
2. The User indicates create Data Drilling.
3. The User enters Name.
4. The User indicates Resource.
5. The User selects a resource to display in the Data Drilling.
6. The User enters all the Data.
7. The user indicates save Data Drilling.
8. The System saves the Data Drilling.
9. The System creates a new Instance Operation for reading (running), updating and deleting
the Data Drilling and gives the User these access rights.
Extensions:
3a. Enter existing name
1. The User enters an existing name
2. The system gives an error message
3. The system control goes back to step 3.
6a. The User selects queries and data fields
1. The user selects Actual query
2. The User selects Actual Query Data field.
3. The User selects Target Query.
4. The User selects Target Query Data field.
5. The user selects Aggregation type either ‘sum’, ‘Avg, ‘min’, ‘max’, or ‘count’ from the list.
6. User enters ‘Green Value’ and ‘Yellow value’.

Use Case Emis
6.1 The User enters Green Value greater than Yellow Value
6.2 The system shows an error message.
7. The User indicates Apply to Children.
8. The User selects Apply to Children.
9. The system creates values for all the Children.
10. The User saves the Data Drilling.
11. The system creates the Data Drilling.
1. The System proceeds to Manage Access Rights Use Case, with focus on the Operations the
System just created
4.15.1.2 Read Data Drilling

Pre-Condition: A Data Drilling exists
Post-Condition: A Data Drilling has been shown
Basic Flow:
2. The System shows a list of Data Drilling.
3. The User selects a Data Drilling.
4. The System shows the details for the Data Drilling.
5. The User can only read the details.
4.15.1.3 Update Data Drilling

Pre-Condition: A Data Drilling
Post-Condition: A Data Drilling has been updated
Basic Flow:
2. The System shows a list of Data Drillings.
3. The User selects the Data Drilling that should be updated.
4. The System shows the detail for the Data Drilling.
5. The User updates the Data Drilling.
6. The System saves the updated Data Drilling.
4.15.1.4 Delete Data Drilling

Pre-Condition: A Data Drilling exists
Post-Condition: A Data Drilling has been deleted
Basic Flow:
2. The System shows a list of Data Drillings.
3. The User selects a Data Drilling.
4. The System shows the details for the Data Drilling.
5. The User indicates delete
6. The System deletes the Data Drilling.
4.16 Use Case: “Manage Roles and Access Rights”

The Roles will be associated with Users and Groups which is defined in Active Directory.
The system of Operations, Tasks and Roles is built up as Azman (from Microsoft).
4.16.1 Manage Operations

The Following Concept Operation exists in this solution:

Use Case Emis
 Create Resource Instance, Read Resource, Update Resource, and Delete Resource
 Create Property Instance, Read Property, Update Property, and Delete Property
 Create DataEntry Instance, Read DataEntry, Update DataEntry, and Delete DataEntry
 Create Schema Instance, Read Schema, Update Schema, and Delete Schema
 Create Form Instance, Read Form, Update Form, and Delete Form
 Create Workflow Instance, Read Workflow, Update Workflow, and Delete Workflow
 Create Export Instance, Read/Run Export and Update Export.
 Create Import Instance, Read/Run Import and Update Import.
 Create Transfer Instance, Read/Run Transfer, Update Transfer, and Delete Transfer.
 Create Report Instance, Read/Run Report, Update Report, and Delete Report.
 Create Data Drilling/Graph Instance, Read Data Drilling/Graph, Update Data Drilling/Graph,
Delete Data Drilling/Graph.
 Create System Message Instance, Read System Messages, Update System Messages, and
Delete System Messages.
 Create Dashboard Instance, Read Dashboard, Update Dashboard, and Delete Dashboard.
Extensions:
1. User selects ‘View’ and ‘Apply to children’ operations for roles.
2. User selects full rights at once.
3. The system shows gray colour for parent object if partially selected.
 Create Manage navigation Instance, View manage navigation, Read Manage navigation,
Update Manage navigation, Delete Manage navigation and Apply to children.
 View Approve data entry.
 View Make Credit data entry.
 Create Query builder Instance, View Query builder, Read Query builder, Update Query
builder, Delete Query builder and Apply to Children.
 Create User Instance, View Users, Read Users, Update Users and Delete Users.
 Create Roles Instance, view Roles, Read Roles, Update Roles and Delete Roles.
 Create User tasks Instance, View User tasks, Read User tasks, Update User tasks and
Delete User tasks.
 Create Import from XML Instance, View Import from XML, Read Import from XML,
Update Import from XML and Delete Import from XML.
 Create Unit Systems Instance, View Unit Systems, Read Unit Systems, Update Unit
Systems, Delete Unit Systems and Apply to Children Unit Systems.
 Create System Documentation Instance, View System documentation, Read System
documentation, Update System documentation, Delete System documentation and
Apply to Children System documentation
 Create System Documentation reports Instance, View System documentation reports,
Read System documentation reports, Update System documentation reports, Delete
System documentation reports and Apply to Children System documentation reports
 Create Manage options Instance, View Manage options, Read Manage options, Update
Manage options and Delete Manage options
 Create Change history, View Change history, Read Change history, Update Change history
and Delete Change history
Read Operations
Pre-Condition:
Post-Condition:
Basic Flow:

Use Case Emis
1. Enter search criteria for Operations

2. List Concept and Instance Operations
4.16.2 Manage Tasks
4.16.2.1 Create Task

Pre-Condition:
Post-Condition: A new Task has been created, and possibly associated with other Tasks and
Operations.
Basic Flow:
1. The User indicates create Task
2. The System lists all Tasks
3. The User indicate to create a new Task
4. The System shows a new “empty form”
5. The User enters a name for the Task
6. The System saves the Task.
Extensions:
5a. Another Task has the same name
1. The System give an error message, and return to step 5
5b. The User wants to add Operations to the Task
1. The System shows all Operations not already belonging to Task
2. The User selects an Operation
3. The System adds the Operation to the Task
[Repeat from step 1 until finish]
5c. The User wants to add other Tasks to the Task
1. The System shows all Tasks
2. The User selects a Task
3. The System adds the Task to the Task
4.16.2.2 Read Tasks

Pre-Condition:
Post-Condition: A list of Tasks was shown
Basic Flow:
1. The User indicates read Task
2. The System shows all the Tasks
4. The System shows the details for the Task (including which Tasks and Operations belongs to the
Task)
4.16.2.3 Update Task

Pre-Condition: A Task exists.
Post-Condition: A Task has been updated. And possibly some new associations to other Tasks or
other Operations has been created. And possibly some associations to other Tasks
and Operations has been deleted.
Basic Flow:
1. The User indicates update task
2. The System lists all Tasks
3. The User select a Task

Use Case Emis
4. The System shows all details for the Task

5. The User edits the Task
6. The System Saves the edited Task
Extensions:
5a. Another Task has the same name
5b. The User wants to add Operations to the Task
1. The System shows all Operations not already belonging to Task
2. The User selects an Operation
3. The System adds the Operation to the Task
5c. The User wants to add other Tasks to the Task
1. The System shows all Tasks
3. The System adds the Task to the Task
5d. The User wants to delete Operations from the Task
1. The System shows all the Operations belonging to the Task
2. The User Selects an Operation
3. The System deletes the Operation from the Task
5e. The User wants to delete a Task from the Task
1. The System shows all the Tasks belonging to the Task
3. The System deletes the Task form the Task
4.16.2.4 Delete Task

Pre-Condition: A Task exists.
Post-Condition: A Task has been deleted.
Basic Flow:
1. The User indicates delete task
2. The System shows a list of Tasks
4. The System shows the details for the Task
6. The System deletes the Task
4.16.3 Manage Roles
4.16.3.1 Create Role

Pre-Condition:
Post-Condition: A Role is created.
Basic Flow:
1. The User indicates show Role
2. The System lists all Roles
3. The User indicate to create a new Role
4. The User enters a name for the Role
5. The System shows a full list of objects and operations in Teams SR
6. The user sets access rights for one or more objects and operations in Teams SR. (Available rights
are View, Create, Read, Delete ,Update and Select)

Use Case Emis
7. The System saves the Role.
Extensions:
5a. Another Role has the same name
4.16.3.2 Read Roles

Pre-Condition:
Post-Condition:
Basic Flow:
1. The User indicates read roles
2. The System lists the Roles
3. The User selects a Role
4. The System displays the details for the Role, including all the operations and objects belonging to
the Role
4.16.3.3 Update Role

Pre-Condition: A Role exists.
Post-Condition: A Role has been updated.
Basic Flow:
1. The User indicates update Role
2. The System lists all Roles
4. The System shows all details for the Role
5. The User edits the Role
6. The System Saves the edited Role
Extensions:
5a. Another Role has the same name
4.16.3.4
4.16.3.5 Delete Role

Pre-Condition: A Role exists.
Post-Condition: A Role has been deleted.
Basic Flow:
1. The User indicates delete Role
2. The System shows a list of Roles
4. The System shows the details for the Role
6. The System deletes the Role
4.16.3.6 Supplementary information on Roles

Roles will serve two purposes in Teams SR. The main purpose is to limit access for all users that are
not administrators. The second purpose is to serve as a tool for customisation of the user interface
for all users in order to hide all information that is not strictly needed.

Use Case Emis
There are six permissions that can be set for each object or operation:
1. View
This is a weaker access right than read. It indicates that the user is allowed to see the name
of the resource. But she/he is not allowed to see the contents of the object. This means that
the resource can be shown in lists and trees, but the user will not be allowed to show the edit
forms for the object.
User is not allowed to select the object in lookups.
For data entries it indicates that the user is allowed to see the data entry list, but not the
contents of the data entry.
2. Create
This indicates that the user is allowed to create new objects of this type. If the object is
located in a tree, it means that the user is allowed to make new children to this object (not
siblings)
3. Read
Indicates that the user is allowed to view the object’s name and the contents of the object in
the object editor. (The read access right implicitly implies view rights)
For data entries it means that the user is allowed to see both the data entry list and the data
entry itself.
4. Update
Indicates that the user is allowed to view the objects name and contents as well as edit them
5. Delete
Indicates that the user is allowed to delete the object
6. Select
Indicates that the user is allowed to select the object in lookups.
4.16.3.7 Concrete interpretations of the “View” access right only

Note: All examples in this section assume that the object in question has view access right and no
read access right applied to them.
Resources
1. The resource will be shown in lookup trees in data entry, and the user is not allowed to select
the resource from a lookup tree.
2. The user is not allowed to open the resource in the Resource editor.
3. The user may not create any resource forms for the resource as this will expose the contents
of the resource.
Properties
1. The property can be shown and used in schema and resource editor, but the user can not
open the property in the property editor
Schema
1. Schema forms may not be created for the schema
2. If the user has access rights to create data entries for forms for this schema, this is not
affected by the view access right for the schema itself.
3. User is allowed to create data entries for the schema.
Schema forms

Use Case Emis
1. The form can not be opened in the form designer and will be displayed in the form list in
schema forms. It will not be displayed in the manage navigation.
2. “View” access right on forms does not affect whether users are allowed to create data
entries for the form, this is controlled by the “Data entry for form” access right
Resource forms
1. The form can not be opened in the form designer and will not be displayed in the form lists in
resource forms. It will not be displayed in the manage navigation.
2. “View” access right on resource form does not affect whether users will be allowed to create
resources with the form. This is controlled by the “Data entry for resource” access right
Data entry for resource

1. The form may be displayed in the web client (if it is assigned to a folder in manage
navigation)
2. If the user has View access right for a resource, name of the resource will be displayed in the
resource list when the user selects the form in the navigation tree.
3. The user is not allowed to click on the resource in the resource list in order to open it in the
resource form
Manage navigation
1. The user is allowed to see the navigation node in the windows client and the web client.
2. If the node contains a form, the user cannot see the data entry list for the form unless
he/she has “View” access right on the data entry for the form.
3. If the node contains a report, the user cannot run the report unless she/he has “Read”
access right on the report too.
Data entry for schema

navigation)
2. If the user has View access right for a schema form, she/he will be allowed to see the data
entry list for that form. (However, he/she needs to have read access right on data entry in
order to open the data entry in the form)
4.16.3.8 Concrete interpretations of the “Read” access right
Resources
4. The user is allowed to read the resource in the resource editor. This includes expanding
groups to see the contents of these.
Properties
1. The user is allowed to read the property in the resource editor. If the user is hovering over
the domain or range of the property and the selection is a resource, the whole path of the
resource should be displayed in yellow tip.
Schema
1. The user is allowed to read the schema in the schema editor. This includes expanding groups
and table groups and reading formulas in the calculation workflow.
Schema forms
1. The user is allowed to display a schema form in the form editor.

Use Case Emis
Resource forms
1. The user is allowed to display a resource form in the form editor.
Manage navigation
1. The user is allowed to see the navigation node in the windows client and the web client.
2. If the navigation node contains a form, the user is allowed to see the data entry list if he/she
has view access on data entry for the form.
3. If the navigation node contains a form, the user is not allowed to open data entries on the
form unless she/he has “Read” access to the data entries on the form too.
4. If the node contains a report, the user cannot run the report unless she/he has “Read” access
right on the report too.

navigation)
3. If the user has View access right for a resource, the resource will be displayed in the resource
list when the user selects the form in the navigation tree.
4. If the user has sufficient privileges for reading the resource, he may click on it in the resource
list in order to open it in the resource form
4.16.3.9 Concrete interpretations of the “Create” access right
Resources
1. The user is allowed to create resources as children of the given resource in the windows
client and in the web client
2. The “Create” access right needs to be set for the top level for the user to be allowed to
create new independent resources both in web and in the windows client.
Properties
1. The user is allowed to create properties
Schema
1. The user is allowed to create schema as children of the given schema.
2. The “Create” access right needs to be set for the top level for the user to be allowed to
create new independent schemas.
Schema forms
1. The user is allowed to create schema forms, if the user has read access for the selected
schema.
Resource forms
1. The user is allowed to create resource forms, if the user has read access for the selected
resource.

1. N/A. Creation of resources is controlled by the “Create” access right for “Resources”
Manage navigation

Use Case Emis
1. The user is allowed to create new navigation nodes under the node with “Create” access
right
2. If the “Create” access right is assigned to the top level node (“Manage navigation”) the user
is allowed to create new top level nodes
3. The user is allowed to add forms and reports to the node if the node is of a type that accepts
this

1. The user may create data entries for the form.(Schema)
4.16.3.10 Concrete interpretations of the “Delete” access right

Resources
1. The user is allowed to the resource in the windows client or the web client if it is not
referenced.
Properties
1. The user is allowed to delete the property if it is not referenced.
Schema
1. The user is allowed to delete schema if there are no data entries on the schema
Schema forms
1. The user is allowed to delete schema forms if they don’t have data entries
Resource forms
1. The user is allowed to delete resource forms (can even be done if the form has been used to
create resources and the resources still exist)

1. N/A. Deletion of resources is controlled by the “Delete” access right for “Resources”
Manage navigation
1. The user is allowed to delete the navigation node, if there are no references.
2. This access right does not affect whether the user is allowed to delete data entries.

1. If the form is visible and the data entry is not approved the user may delete data entries on
that form.
2. Credit data entries cannot be deleted.
4.16.3.11 Behavior of the property tree

The property tree displays all objects in the application and database in a tree. To the left of each box
there is a checkbox that displays the status for the “View” access right for that node. The remaining
access rights “Create”, “Read”, “Update”, “Select” and “Delete” are displayed to the right.
Selections of the “View” access right

Use Case Emis
If the user clicks on the “View” box for a node, the same selection is applied to all nodes below this
node. Parent nodes of a selected node will get a gray checked checkbox indicating that the node is
partially selected (I.e.: All the children are not selected, as in certain windows installers)
If the user clicks on the “View” box for a node, the selection is not applied to all nodes below this
node. Parent nodes of a selected node will get a gray checked checkbox indicating that the node is
partially selected (I.e.: All the children are not selected, as in certain windows installers).if the user
wants to apply the selection to all its children he use apply to children button.
Figure 1: Before user clicks

Use Case Emis
Figure 2: After user clicks
Selection of ”Create”, ”Read”, ”Delete” ,”Select” and ”Update” access rights

Selection of ”Create”, ”Read”, ”Delete” ,”Select” and ”Update” access rights is done to the right of
the tree through a dropdown menu.
The user can select one or more or all access rights, and once the selection is done (and the
dropdown is closed) the selection is applied to all children too.
The user can select one or more or all access rights, and these will not be applied to the children if he
wants to apply to the children he will click apply to child button located in separate column.

Use Case Emis
If the user selects at least one of the access rights in the dropdown, the “View” access right is also
automatically applied.
4.16.4 Use Case: “Manage Access Rights”

In manage access right the user can:
1. See a list of users and selecting them will show the roles for the user.
2. See a list of roles and selecting them will show the users with that role.
Create Access Right

Pre-Condition: Users exists in Active Directory, and Roles exists.
Post-Condition: A new Access Right has been created.
Basic Flow:
1. The User indicates show Access Rights
2. The System lists all Users who previously logged in or attempt to login to the system.
3. The User selects a User
4. The System shows a list of Roles
5. The Users selects Roles.
6. The System saves the Access Right
4.16.4.1 Read Access Rights

Pre-Condition:
Post-Condition:
Basic Flow:
1. The User indicates read Access rights
2. The System lists all Access Rights (see introduction for details)
4.16.4.2 Delete Access Right

Pre-Condition: Access Right exists
Post-Condition: An Access Right has been deleted.
Basic Flow:
1. The User indicates show users
2. The System lists all Users.
3. The User selects an User
4. The System shows a list of Roles belonging to the User
5. The User selects the role and indicates delete
6. The System deletes the Access Right
4.17 Use Case: “System Documentation”

This Use Case can be reached from other Use Cases, and will then bring along items already in the list
of things to document (the item will be the selection done in the starting Use Case).
The purpose of this Use Case is to document the structure of the system rather than to document the
actual Data Entry values. This can be seen as an extension of the general reporting concept. The user
should be able to perform the following tasks:

Use Case Emis
- For a Schema:
 Document Resources, properties and equations (text formula).
 Document Calculations as an image from the graphical modelling tool.
 Document the History.
 Document which Data Entry Forms are referring to this Schema
- For a Resource / Property:

 Document which Schemas are referring to this item.
- For a Data Entry Form
 Document which Schemas are referring to this item.
4.18 Use Case: “Manage Options”

This use case is for setting the Options in Teams SR. This Use Case is not expected to be advanced,
and will be extended as we develop the system. It is therefore important to design this in a way that
it will be easy to extend.
Today we want to set the following options:
 First Day of Week. Possible values are Monday to Sunday.
 First Day of Year.
 First Week of Year (Possible values are: “Starts on Jan 1”, “First 4-day week” and “First full
week”.
 Help Files added to Teams SR (Values will be a list of File-Paths)(Not in scope for present
version).
 External Email system to use for sending Email notifications and creating User Tasks (Not in
Scope for present version).
1. User selects show comment while updating/deleting on Admin client.
2. User selects show system messages on Admin client.
3. User cancels the selected options.
4. User selects 5 different main languages for the application.
3.1 User indicates to create languages.
3.2 User selects a language from the language lists.
3.3 User set language as main language.
3.4 User saves the language.
3.5 User creates child languages to main language.
3.6 User saves the language.
5. Update Language option
4.1 User selects the existing language.
4.2 User changes the language by selecting another language from the list.
4.3 User unchecks the main language option.
4.4 User saves the changes made.
4.19 Use Case: “Create Query Builder”

This chapter describes how to set up a Query Builder. Query Builder has on its own no use, but is
used by Export, Report or Data Drilling/Graph Use Cases. A Query Builder has Create, Read, Update
and Delete as the using Use Case.

Use Case Emis
4.19.1.1 Create Query builder:

Pre-Condition: Started Use Case Export, Report or Data Drilling/Graph
Post-Condition: Forwarding Properties and Resources, possibly grouped and sorted, back to the
calling Use Case.
Basic Flow:
1. The user indicates show Query builder.
2. The system shows the list of Query builder.
3. The User indicates create new Query builder.
4. The User enters name.
5. The User selects Virtual/Non-Virtual options.
6. The User selects From date and To date.
7. The User indicates Filter.
8. The User selects ‘overlap column’ resource in “filter” section by drag and drop.
8.1 The User enters alias name for the selected resources.
8.2 User enters values in DQ conditions section by expanding resource node.
8.3 The User selects resource from the resource look up dialog box.
9. The User indicates Columns.
10. The User selects resource for “columns” by drag and drop.
11. The User enters alias names for the selected resources in “columns”.
12. The User enters precision length.
13. The User selects either not null, parent level, container, unit.
14 The User indicates Preview.
15. The User indicates Execute Query.
16. The system shows the data.
17. The User indicates save Query builder.
18. The system creates the Query builder.
19. The System creates a new Instance Operation for reading, updating and deleting the Query
builder and adds them to Roles.
Extensions:
4a. Name already exists
1. The User enters existing name.
2. The system shows an error message that name already exists.
3. Repeat the step 4.
4.19.1.2 Update query builder

1. The user makes necessary changes by updating the fields with new data.
2. The user save the changes and system saves and update the changes.
3. User changes the date and returns back and then system informs to save. User
Selects “no” then returns without saving updated data.
Extensions:
2a. The Query refers to Data Drilling, Reports.
1. The system indicates that the Query cannot be updated.
4.19.1.3 Delete query builder

1. The User indicates show Query builder.
2. The system lists the entire Query builder.

Use Case Emis
3. The user selects a Query builder.

4. The system shows details of the Query builder.
5. The User indicates delete Query builder.
6. The system deletes Query builder.
Extensions:
6a. The Query builder refer to Data Drilling, Report
1. The system indicates that Query can not be deleted.
4.19.1.4 Copy and Paste

1. The User indicates show Query builder.
2. The system shows list of Query builder.
3. The User indicates Copy Query builder.
4. The system copy Query builder.
5. The user indicates Paste Query builder.
6. The system creates a copy of Query builder.
7. The User indicates Save Query builder.
8. The system saves the Query builder.
4.20 Use Case: “Manage System Messages”

The System Messages is the text displayed under title “System Message” in both the Browser
solution and the Smart Client solution. A System Message box will show all System Messages in the
system that has visible period covering the current system datetime.
4.20.1.1 Create System Message

Pre-Condition:
Post-Condition: A System Message was created
Basic Flow:
1. The User indicates show System messages.
2. The System shows a list of all System Messages, with visible time.
3. The User indicates create System Message.
4. The System shows an editor box, where the user can enter HTML text, a from and a to datetime
(default is today).
5. The User enters the HTML text, and selects a from and to time.
6. The User indicates a User to whom message should display.
7. The User indicates Save.
8. The System saves the System Message.
4.20.1.2 Read System Message

Pre-Condition: System Messages exists
Post-Condition: System Messages with Valid time has been shown
Basic Flow:
1. The User indicates show System Messages
2. The System shows a list of System Messages including Valid time.
3. The User selects a System Message.
4. The system shows details of System Message.
4.20.1.3 Update System Message

Pre-Condition: A System Message exists

Use Case Emis
Post-Condition: A System Message has been updated

Basic Flow:
1. The User indicates show System Message.
2. The System shows a list of System Messages.
3. The User selects the System Message that should be updated.
4. The System shows the details for the System Message.
5. The User edits the System Message details.
6. The User indicates save System Message.
7. The System saves the updated System Message.
4.20.1.4 Delete System Message

Pre-Condition: A System Message exists
Post-Condition: A System Message has been deleted
Basic Flow:
1. The User indicates show System Message.
2. The System shows a list of System Messages.
3. The User selects a System Message.
4. The System shows the details for the System Message.
6. The System deletes the System Message.
4.21 Manage Favourite Folders

4.21.1.1 Create favourite folders
1. The system displays favourite folders on maim menu.
2. The User indicates Favourite folders.
3. The User indicates create favourite folders.
4. The system shows favourite folders dialog box.
5. User creates a folder.
6. User selects schema group folder/resource form and moves to a selected folder.
7. The User closes the dialog box.
8. The system saves the favorite folder.
Favorites folder and adds them to Roles.
4.21.1.2 Update Favorites folders

1. User selects an existing folder.
2. User enters an existing name for the folder.
3. The system message shows a user message, name already exists.
4. User selects group folders/resource forms and adds to folders.
5. The system adds/removes the group folders/resource forms to folders.
6. User closes the favorites folders dialog boxes.
7. The system updates the changes.
4.21.1.3 Rename Favorites folders

1. The User indicates Favorites folder.
2. The system shows Favorites folders.
3. The User selects a Favorites folder.
4. The User renames the Favorites folder.
5. The system updates Favorites folder with the new name.

Use Case Emis
4.21.1.4 Delete folders

1. User indicates Favorites folder.
2. The system shows Favorites folders.
3. The User selects a Favorites folder.
4. User indicates to delete the folder.
5. The system asks to confirm delete.
6. User selects “yes”.
7. The system deletes the selected folder.
8. User closes the favorite folder dialog box
4.22 Manage Users

4.21.1.5 Create User
1. The User indicates Users.
2. The system shows list of all Users.
3. The User indicates create new Users.
4. The User enters Name with a Domain name.
5. The User indicates Role to the User.
7. The system saves the User details with role.
8. The System creates a new Instance Operation for reading, updating and deleting the Users
Extensions:
4a. Enter existing name
The User enters existing name.
The system gives an error message, name is already exists.
Repeat step 4.
4.21.1.6 Update User

1. The User indicates show Users.
2. The system lists all the Users.
3. The Users selects a User.
4. The User edits the data.
6. The system saves the User with Updates made.
4.21.1.7 Delete User

1. The User indicates Users.
2. The system lists all the Users.
3. The User selects the User.
4. The User indicates delete User.
5. The system deletes the User.

Use Case Emis
General Extensions:
1. The user can user ‘ctrl N’ to create parent object and ‘ctrl M’ to create child object.
2. The User can selects decimal separator from the system control panel for both win client
(admin) and data entry.
3. The User can select different languages strings from the status bar for the win client
(admin).
4. The User can select different languages from the internet options for the data entry.

Use Case: 1 Revision History

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Use Case: 1 Revision History

Uploaded by

Copyright:

Available Formats

Use Case Emis

Added Use case for Users and Favourite

Added General Extensions

26226536.doc Page 1 of 57 Printed 03.11.2008

26226536.doc Page 2 of 57 Printed 03.11.2008

4.16.3 Manage Roles...............................................................................................................40

26226536.doc Page 3 of 57 Printed 03.11.2008

26226536.doc Page 4 of 57 Printed 03.11.2008

3.2 Overview of the Use Cases

26226536.doc Page 5 of 57 Printed 03.11.2008

4 Use Cases – Detailed description

The Descriptions are built up as follows:

26226536.doc Page 6 of 57 Printed 03.11.2008

Basic Flow – describes the typical success path.

4.1 Use Case:” Manage Properties and Resources”

Each Use Case will be possible to cancel, before it is saved!

4.1.1 Manage Property

4.1.1.1 Create Property

26226536.doc Page 7 of 57 Printed 03.11.2008

4.1.1.2 Read Property

4.1.1.3 Update Property

26226536.doc Page 8 of 57 Printed 03.11.2008

2. The User selects a DataType

4.1.1.4 Delete Property

4.1.2 Manage Resources

4.1.2.1 Create Resource

26226536.doc Page 9 of 57 Printed 03.11.2008

9. The User indicates an end of creation

4.1.2.2 Read Resource

26226536.doc Page 10 of 57 Printed 03.11.2008

2a. The User indicates a view

4.1.2.3 Update Resource

4.1.2.4 Delete Resource

26226536.doc Page 11 of 57 Printed 03.11.2008

1. The User indicates to manage Resources

4.2 Use Case: “Manage Unit Systems”

4.2.1 Short description of SI

26226536.doc Page 12 of 57 Printed 03.11.2008

Name Symbol Relation

Name Symbol Relation

4.2.1.1.1 Teams SR’ SI

4.2.1.1.2 Example of a new System of Unit created by user

Name Symbol Relation

26226536.doc Page 13 of 57 Printed 03.11.2008

rod, pole, perch rod 5,5 yd198 in

Name Symbol Relation

4.2.2 Use Case: “Manage System of Unit”

4.2.2.1 Create System of Unit

4.2.2.2 Read System of Unit

26226536.doc Page 14 of 57 Printed 03.11.2008

4.2.2.3 Update System of Unit

4.2.2.4 Delete System of Unit

4.2.3 Use Case: “Manage Quantity”

4.2.3.1 Create Quantity

26226536.doc Page 15 of 57 Printed 03.11.2008

6. The System displays a “new empty form”

4.2.3.2 Read Quantity

4.2.3.3 Update Quantity

4.2.3.4 Delete Quantity

26226536.doc Page 16 of 57 Printed 03.11.2008

4.2.4 Use Case: “Manage Unit”

26226536.doc Page 17 of 57 Printed 03.11.2008