Let’s Help Bo
Requirements Specification
Version 1.4
Let's Help Bo
Requirements Definition
Version:
1.4
Date: 2012-12-26
Revision History
Date
Version
Description
Author
2012-10-26
0.1
Initial Draft
Antonio Gallucci
2012-10-28
0.2
Added use case diagrams
Antonio Gallucci
2012-10-30
0.3
Nives Bučić
2012-10-31
0.4
2012-11-01
0.5
2012-11-01
0.6
2012-11-02
0.7
2012-11-02
0.8
2012-11-02
0.9
2012-11-02
1.0
Revised draft, added
functional requirements by
personas
Added use case scenarios
UM1-4, WO1-5
Added use case scenarios
SC1-5, IC1-6, MA1-6
Updated
use
case
diagrams
Wrote the remaining use
cases and reviewed the
document
Wrote
requirement
definitions,
added
remaining
nonfunctional
requirements
Revised
functional
requirement
Document revision
2012-11-08
1.1
Nives Bučić
2012-11-09
1.2
2012-11-25
1.3
2012-12-26
1.4
Added additional
information for nonfunctional req., changed
priorities and renamed
component
Removed Schedule
component
Added solution web pages,
removed leftover
comments
Updated use cases and
requirements table
Nives Bučić
Nives Bučić
Antonio Gallucci
Antonio Gallucci
Nives Bučić
Antonio Gallucci
Nives Bučić
Antonio Gallucci
Nives Bučić
Nives
Novak
Bučić,
Hrvoje
Page 2
Let's Help Bo
Requirements Definition
Version:
1.4
Date: 2012-12-26
Table of Contents
1.
2.
3.
Introduction
5
1.1
1.2
1.3
1.4
Purpose of this document
Intended Audience
Scope
Definitions and acronyms
1.4.1 Definitions
1.4.2 Acronyms and abbreviations
1.5
References
5
5
5
5
5
5
5
Requirements Description
6
2.1
2.2
2.3
2.4
6
6
6
6
6
6
7
7
7
Introduction
General requirements
Functional requirements
Non-functional requirements
2.4.1 Usability
2.4.2 Security
2.4.3 Reliability and Robustness
2.4.4 Portability and compatibility
2.4.5 Performance
Use Cases
3.1
3.2
3.3
3.4
3.5
3.6
3.7
Actors of the system
User use case diagram
3.2.1 Use case “Login”
3.2.2 Use case “Logout”
Machine operator use case diagram
3.3.1 Use case “View work orders”
3.3.2 Use case “View notifications”
3.3.3 Use case “Edit own work order”
3.3.4 Use case “Book a spare part”
3.3.5 Use case “View bookings”
3.3.6 Use case “Search a spare part”
Production supervisor use case diagram
3.4.1 Use case “Create work order”
3.4.2 Use case “Edit work order”
3.4.3 Use case “View all work orders”
Maintenance supervisor use case diagram
3.5.1 Use case “Create spare part”
3.5.2 Use case “Edit spare part”
3.5.3 Use case “Delete spare part”
3.5.4 Use case “View all bookings”
Mine control room operator use case diagram
3.6.1 Use case “Create tunnel”
3.6.2 Use case “Edit tunnel”
3.6.3 Use case “Delete tunnel”
3.6.4 Use case “Create hotspot”
3.6.5 Use case “Edit hotspot”
3.6.6 Use case “Delete hotspot”
3.6.7 Use case “View mine map”
3.6.8 Use case “Find shortest route”
System administrator use case diagram
3.7.1 Use case “Create user”
3.7.2 Use case “View user details”
7
7
8
8
9
9
9
10
10
10
11
11
12
12
12
13
13
13
14
14
14
15
15
16
16
16
17
17
18
18
19
19
19
Page 3
Let's Help Bo
Requirements Definition
3.7.3 Use case “Edit user”
3.7.4 Use case “Delete user”
4.
5.
Version:
1.4
Date: 2012-12-26
20
20
Requirements Definition
21
4.1
4.2
4.3
21
21
21
22
Requirement Group Definitions
Requirement Sources
Requirement definitions
4.3.1 Change Log
Future Development
23
Page 4
Let's Help Bo
Requirements Definition
Version:
1.4
Date: 2012-12-26
1.
Introduction
1.1
Purpose of this document
This document describes in detail all the requirements for the project “Let’s Help Bo”. In addition this
document gives also an overview on all the functionalities that will be implemented.
1.2
Intended Audience
This document is addressed to all the project team members, the supervisor, the DSD teachers and
the customers.
1.3
Scope
In this document will be described the requirements, use cases and future developments for the
product.
1.4
Definitions and acronyms
1.4.1
Definitions
Keyword
NFR
1.4.2
Acronyms and abbreviations
Acronym or
abbreviation
LHB
DSD
UM
WO
SC
IC
MC
1.5
Definitions
Non-functional Requirements
Definitions
Let's Help Bo
Distributed Software development
User management component
Work order component
Schedule component
Inventory component
Map component
References

Project DSD home page
http://www.fer.unizg.hr/rasip/dsd/projects/lets_help_bo

Project Google group
http://groups.google.com/group/dsd-project2012

Project solution desktop web page
http://161.53.67.226:8080/Desktop

Project solution mobile web page
http://161.53.67.226:8080/Mobile
Page 5
Let's Help Bo
Requirements Definition
2.
Requirements Description
2.1
Introduction
Version:
1.4
Date: 2012-12-26
Inventory support system will support the machine operators in their working activities.
Besides that, it will have other extra functionalities that aim to help in the daily activities of
other people that work in the mine. As main actor we have the machine operator, that works
underground, but there are also other actors that will have a part in our system. They will be
presented in details in the next chapters.
2.2
General requirements
The system must provide the functions to manage an inventory system into a mine. Inventory
system will be used by different kind of personas. From one side we have the machine
operator that needs to use the spare parts, and on the other side the person that manage the
inventory for the mine (e.g. take care that the essential spare parts are always available). Also
the functionalities to manage the work orders for the machine operators will be included in the
system. In addition, it will be also possible to view the map of the mine, and search for the
shortest path to a destination (e.g. warehouse).
One of the main requirements is to develop easy to use software considering the environment
in which it will be used.
2.3
Functional requirements








The system will provide:
private access to all the users
The booking functionality for the machine operators.
The view of the shortest and safest route from location a to location b (e.g. mine exit,
warehouse. working position). Additional information can be added to the map shown to the
machine operator, like closed galleries, machine that block galleries, galleries in which there
has been a blast etc.
the functionalities to view the work orders for the machine operator
the functionalities for the production supervisor to create, edit and delete work orders
the functionalities to View the state of all work orders
the functionalities to create, edit and delete spare parts in inventory
the functionalities to add, update and delete user accounts
2.4
Non-functional requirements
2.4.1
Usability





2.4.2



The software will be developed taking into account the environment in which it will be used.
The colors of the user interface will be decided taking into account that there can be some low
light condition when the mobile application will be used.
The contrast between the background and the text will be chose to facilitate the view of the
elements in the screen of the device
The application will be easy to use, and its use will not be frustrating for the users that will use
it.
Usability managers will make sure this requirement is achieved in every project component
Security
The application will identify all of its human users before allowing them to use its functionality;
The application will ensure that users can only access data and services for which they have
been properly authorized
Implementation in data layer
Page 6
Let's Help Bo
Requirements Definition
2.4.3


2.4.4



2.4.5


Version:
1.4
Date: 2012-12-26
Reliability and Robustness
The application should maintain its performance over time and able to handle error conditions
without failure
Catching exceptions caused by errors and forwarding them to certain actions
Portability and compatibility
It will be possible to use application on all browsers, different operating systems and different
platforms
For different browsers: using only common attributes and methods and using tips to make
content and content layout available for all browsers
For different operating systems and different platforms: by using web development techniques
Performance
The database and the code will be written to minimize the lag of the response from the server.
The performance of the code and database will be considered and not the performance of the
wireless network and the server that are used in the mine, because we don't have control on
it.
3.
Use Cases
3.1
Actors of the system
We identified 6 different actors that will interact with our system:






User
Machine operator
Production supervisor
Maintenance supervisor
Mine control room operator
System administrator
Figure 1: User hierarchy
In the next paragraphs the relation of the actors with the system will be presented.
For each of them is presented the relative use case diagram. In each use case diagram are shown
Page 7
Let's Help Bo
Requirements Definition
Version:
1.4
Date: 2012-12-26
the different use cases for each component of the system and with which use cases the actor is
related. After each use case diagram, the relative use cases descriptions are presented. If a use case
is related to more than one user, only once it will be described.
3.2
User use case diagram
The actor "User" is related with the basic operations that interest all the actors of the
system.
Below will be presented in detail use cases considering user: Login, Logout, View
user details and Recover password use case.
3.2.1
Use case “Login”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
Exceptions
Extensions
Dependent UC
UM1
Login
Successful login into system
User
● User has device with internet connection
1. User access to the login page
1.1. User type his username and password
1.2. User picks a role from the dropdown list which
automatically fills the user credentials
2. The system checks if username and password are correct
3. User is logged in
2.a User forgot his password
2.a.i User calls System administrator to generate new password
2.a.ii User gets password from System administrator in person
all
Page 8
Let's Help Bo
Requirements Definition
3.2.2
Version:
1.4
Date: 2012-12-26
Use case “Logout”
Use case ID
Name
Goal
Participating actors
Precondition
UM2
Logout
Successful logout from the system
User
 User is logged in
Main scenario
1. User selects logout option
2. User is logged out
Exceptions
Extensions
Dependent UC
3.3
Machine operator use case diagram
In this diagram all the use cases related to the machine operator are presented.
3.3.1
Use case “View work orders”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
WO1
View work orders
View the list of work orders
Machine Operator
1
2
The user access to the work order management page
The system shows the list with all work orders for user
Exceptions
Extensions
Dependent UC
Page 9
Let's Help Bo
Requirements Definition
3.3.2
Version:
1.4
Date: 2012-12-26
Use case “View notifications”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
WO2
View notifications
View updated work orders
Machine operator
Production supervisor updated user’s work order
1 The user chooses notification icon
2 The system shows the list with all updated work orders
3 User selects updated work order
4 System shows updated work order details and removes
notification
Exceptions
Extensions
Dependent UC
3.3.3
Use case “Edit own work order”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
Exceptions
Extensions
Dependent UC
3.3.4
WO3
Edit own work order
Update own work order in the list of his work orders
Machine Operator
The user is on the screen that shows list of work orders he needs to
do
1 The user selects the work order that he wants to update
2 The system shows all the information about the work order.
3 The user updates status of the work order
4 The user saves the changes.
3.i User looks work order on map and updates status of the work
Use case “Book a spare part”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
Exceptions
Extensions
Dependent UC
IC1
Book a spare part
Book a spare part from the inventory
Machine Operator
The user is on the screen that show the list of spare parts
1 The user chooses to make a booking of a spare part from the
list
2 The system shows a booking window
3 The user specifies the amount and checks the warehouse(s)
which he wants the parts from
4 The user submits the booking
5 The system informs the user on the success of the booking
3.i User checks warehouse(s) on the map and specifies amount
Page 10
Let's Help Bo
Requirements Definition
3.3.5
Version:
1.4
Date: 2012-12-26
Use case “View bookings”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
IC2
View bookings
View all spare parts bookings in the system made by user
Machine operator
1
2
3
4
The user access to the bookings page
The system shows the list with all active and completed
Bookings made by user
User selects to show on map certain active booking
System shows booking on the map
Exceptions
Extensions
Dependent UC
3.3.6
Use case “Search a spare part”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
Exceptions
Extensions
IC3
Search a spare part
Search a spare part in the inventory
Machine Operator or Maintenance Operator
1 The user access to the screen where to search the spare parts
2 The system show a form where to insert the information of
the spare parts
3 The user chooses a criteria to search by
4 The user enters the search term
5 The system shows the list of the spare parts that match the
search criteria.
4.i There are not spare part matching the search criteria and the list
presented is empty
Dependent UC
Page 11
Let's Help Bo
Requirements Definition
3.4
Production supervisor use case diagram
3.4.1
Use case “Create work order”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
Exceptions
Extensions
Dependent UC
3.4.2
Version:
1.4
Date: 2012-12-26
WO4
Create work order
Create new work order in system
Production supervisor
The user is on the main screen of the application
1 The user access to the work order management page
2 The system shows the screen with all work orders and options
3 The user choose to add a new work order
4 The system shows the screen with a form to fill in with the
information of the work order.
5 The user inserts all the necessary information (description,
time, details etc.), selects hotspot of work order and assigns this work
order to certain machine operator.
6 The user saves the work order.
Edit work order
Use case “Edit work order”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
WO5
Edit work order
Updated work order
Production supervisor
The user is on the screen that shows all work orders
1 The user choose to modify the certain active work order
2 The user updates the information of the work order and save
the changes.
3 The system sends a notification message about update to
machine operator.
Page 12
Let's Help Bo
Requirements Definition
Exceptions
Extensions
Dependent UC
3.4.3
Version:
1.4
Date: 2012-12-26
View notifications
Use case “View all work orders”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
WO6
View all work orders
View all the work orders in the system
Production supervisor
3
4
The user access to the work order management page
The system shows the list with all work orders
Exceptions
Extensions
Dependent UC
3.5
Maintenance supervisor use case diagram
3.5.1
Use case “Create spare part”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
IC4
Create spare part
Create a new spare part in the inventory system
Maintenance supervisor
1
The user accesses to the inventory management page
And chooses to add a new product or product item.
2 The system shows the fields to fill in with the information of
the spare part.
3 The user fills the needed information for the spare part.
Page 13
Let's Help Bo
Requirements Definition
Exceptions
Extensions
Dependent UC
3.5.2
Version:
1.4
Date: 2012-12-26
4 The user saves his work.
4.i The user inserted wrong information
4.ii The system show a notification stating that the information are
wrong and need to be corrected.
4.iii Go to step 3
Edit spare part, Delete spare part
Use case “Edit spare part”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
Exceptions
IC5
Edit spare part
Edit the information of a spare part in the inventory system
Maintenance supervisor
1
The user accesses to the inventory management page
And chooses the spare part product to update.
2 The system shows all the information of the spare part
product
3 The user update the information
4 The user saves the changes
4.i The user inserted wrong information
4.ii The system show a notification stating that the information are
wrong and need to be corrected.
4.iii Go to step 3
Extensions
Dependent UC
3.5.3
Use case “Delete spare part”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
IC6
Delete spare part
Delete spare part from the inventory system
Maintenance supervisor
1 The user accesses to the inventory management page.
2 The system shows all the information of the spare part
3 The user choose to delete the spare part product from the
inventory
Exceptions
Extensions
Dependent UC
3.5.4
Use case “View all bookings”
Use case ID
Name
Goal
Participating
actors
Precondition
IC7
View all bookings
View all spare parts bookings in the system
Maintenance supervisor
Page 14
Let's Help Bo
Requirements Definition
Main scenario
Version:
1.4
Date: 2012-12-26
5
6
The user access to the bookings page
The system shows the list with all active and completed
bookings
Exceptions
Extensions
Dependent UC
3.6
Mine control room operator use case diagram
3.6.1
Use case “Create tunnel”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
MC1
Create tunnel
Create a new tunnel in the map of the mine
Mine control room operator
1
2
3
4
5
Exceptions
Extensions
Dependent UC
The user accesses to the map management page
and chooses to create a new tunnel.
The system shows the form to fill in with the information of the
tunnel.
The user fills the needed information for the tunnel
The user saves his work.
The system notifies that the operation succeed
4.i The user inserted wrong information
4.ii The system show a notification stating that the information are
wrong and need to be corrected.
4.iii Go to step 3
Edit tunnel, Delete tunnel
Page 15
Let's Help Bo
Requirements Definition
3.6.2
Version:
1.4
Date: 2012-12-26
Use case “Edit tunnel”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
MC2
Edit tunnel
Edit the information of a tunnel in the map of the mine
Mine control room operator
1
2
3
4
5
6
7
Exceptions
The user accesses to the map management page
And chooses to select tunnel.
The system shows all the information of the tunnels on the
map
The user select the tunnel to update
The system show the form with the information of the tunnel
The user update the information
The user saves the changes
The system notifies that the operation succeed
6.i The user inserted wrong information
6.ii The system show a notification stating that the information are
wrong and need to be corrected.
6.iii Go to step 5
Extensions
Dependent UC
3.6.3
Use case “Delete tunnel”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
MC3
Delete tunnel
Delete a tunnel in the map of the mine
Mine control room operator
1
2
3
4
5
6
7
8
Exceptions
Extensions
Dependent UC
3.6.4
The user accesses to the map management page
and chooses to select tunnel.
The system shows all the information of the tunnels on the
map
The user select the tunnel to delete
The system show the form with the information of the tunnel
The user choose to delete the tunnel
The system show a confirmation window
The user confirm the operation
The system notifies that the operation succeed
6.i The user does not confirm the operation
Use case “Create hotspot”
Use case ID
Name
Goal
Participating
MC4
Create hotspot
Create a new hotspot in the map of the mine
Mine control room operator
Page 16
Let's Help Bo
Requirements Definition
actors
Precondition
Main scenario
Exceptions
Extensions
Dependent UC
3.6.5
Version:
1.4
Date: 2012-12-26
1 The user accesses to the map management page
and chooses to create a new hotspot.
2 The system shows the form to fill in with the information of the
hotspot.
3 The user fills the needed information for the hotspot
4 The user saves his work.
5 The system notifies that the operation succeed
4.i The user inserted wrong information
4.ii The system show a notification stating that the information are
wrong and need to be corrected.
4.iii Go to step 3
Edit hotspot, Delete hotspot
Use case “Edit hotspot”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
MC5
Edit hotspot
Edit the information of a hotspot in the map of the mine
Mine control room operator
1
2
3
4
5
6
7
Exceptions
The user accesses to the map management page
And chooses to select hotspot.
The system shows all the information of the hotspots
The user select the hotspot to update
The system show the form with the information of the hotspot
The user update the information
The user saves the changes
The system notifies that the operation succeed
6.i The user inserted wrong information
6.ii The system show a notification stating that the information are
wrong and need to be corrected.
6.iii Go to step 5
Extensions
Dependent UC
3.6.6
Use case “Delete hotspot”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
MC6
Delete hotspot
Delete a hotspot in the map of the mine
Mine control room operator
1
The user accesses to the map management page
And chooses to select hotspot.
2 The system shows all the information of the hotspots on the
map
Page 17
Let's Help Bo
Requirements Definition
Version:
1.4
Date: 2012-12-26
3
4
5
6
7
8
Exceptions
Extensions
Dependent UC
3.6.7
The user select the hotspot to delete
The system show the form with the information of the hotspot
The user choose to delete the hotspot
The system show a confirmation window
The user confirm the operation
The system notifies that the operation succeed
6.i The user does not confirm the operation
Use case “View mine map”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
MC7
View mine map
View the map of the mine
Mine control room operator, Machine operator,
supervisor, Production supervisor, System administrator
Maintenance
1
The user accesses to the map management page
And chooses to view the map of a level of the mine.
2 The system shows all the information regarding the map of
the level
Exceptions
Extensions
Dependent UC
3.6.8
Use case “Find shortest route”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
MC8
Find shortest route
Find the shortest path from the current position to a place (warehouse,
vehicle, entrance, other hotspots)
Mine control room operator, Machine operator, Maintenance
supervisor, Production supervisor
User is on the page which shows element (warehouse, spare part,
booking, work order) with option show on map
1 User choose option to show on map certain element
2 System calculates shortest path to the place element is
positioned
3 System shows shortest path on map
Exceptions
Extensions
Dependent UC
Page 18
Let's Help Bo
Requirements Definition
Version:
1.4
Date: 2012-12-26
3.7
System administrator use case diagram
3.7.1
Use case “Create user”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
Exceptions
Extensions
Dependent UC
3.7.2
UM3
Create user
Add new user to system
System administrator
The user received a request to create a new user
1 The user opens user management panel
2 Selects option to add new user
3 User enters all the information regarding the new user
4 The user save the new user in the system
4.i The user can select cancel button which will redirect him to the
homepage
Edit user, Delete user
Use case “View user details”
Use case ID
Name
Goal
Participating actors
Precondition
Main scenario
Exceptions
UM4
View user details
View details of user
System administrator
User is logged in
1.
2.
3.
4.
5.
The user opens user management panel
User enters search parameters
The system shows the informations relative to search results
User selects certain user whose details he wants to see
System shows selected user details
4.i If user is on desktop version user details are shown inside search
results
Extensions
Dependent UC
Page 19
Let's Help Bo
Requirements Definition
3.7.3
Version:
1.4
Date: 2012-12-26
Use case “Edit user”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
UM5
Edit user
Updates user account info in system
System administrator
●
The user receives new message from headquarters with the
list of names and IDs, which information have to be updated or
he gets request from user to change his password.
1
2
3
4
5
6
The user goes to user management panel
The system list all the users in the system
The user select the relative user
The system shows the information regarding the user
The user updates user information
The user saves changes
Exceptions
7.i The user inserted wrong information
7.ii The system show a notification stating that the information are
wrong and need to be corrected.
7.iii Go to step 5
Extensions
Dependent UC
3.7.4
Use case “Delete user”
Use case ID
Name
Goal
Participating
actors
Precondition
Main scenario
UM6
Delete user
Delete user from system
System administrator
1
2
3
4
5
6
7
The user goes to user management panel
The system list all the users in the system
The user select the relative user
The system shows the information regarding the user
The user choose to delete the selected user
The system shows a confirmation window
User confirms operation
Exceptions
Extensions
Dependent UC
Page 20
Let's Help Bo
Requirements Definition
Version:
1.4
Date: 2012-12-26
4.
Requirements Definition
4.1
Requirement Group Definitions
Identificatio
n
UM
IC
MC
WO
NR
4.2
Requirement Group
User management component
Inventory component
Map component
Work order component
Nonfunctional requirements
Requirement Sources
Source
Ctm
Sys
Dev
4.3
Description
Customer(ABB) defined requirement
Required as a consequence of system design (contractor’s
requirement)
Developers
Rem.
Requirement definitions
Identity
Status
Priority
Reference
UM-1
UM-1.1
UM-2
UM-2.1
UM-2.2
UM-2.3
UM-2.3.1
UM-2.4
I
I
I
I
I
I
D
I
1
1
2
2
2
2
3
2
3.2.1, UM1
3.2.2, UM2
WO-1
WO-1.1
WO-1.1.1
WO-1.2
WO-2
WO-2.1
WO-2.2
WO-2.2.1
WO-2.2.2
I
I
A
I
I
I
I
I
I
D
D
D
D
D
1
1
1
1
1
1
1
1
1
SC-1
SC-1.1
SC-1.2
SC-2
Rem.
3
3
3
3
3.7.1, UM3
3.7.2, UM4
3.7.3, UM5
3.2.4, UM3
3.7.4, UM6
3.3.1, WO1
3.3.2, WO2
3.4.3, WO6
3.4.1, WO4
3.3.3, WO3
3.4.2, WO5
3.3.7, SC1
3.4.6, SC4
Description
User management component
Logging in
Logging out
Managing users
Creating user
Viewing user details
Editing user
Recovering password
Deleting user
Work order component
Viewing work orders
Viewing assigned work orders
Viewing updated work orders
Viewing all work orders
Managing work orders
Creating work order
Editing work orders
Machine operator editing
Production supervisor editing
Schedule component
Viewing schedules
Viewing own schedule
Viewing all schedules
Managing schedules
Source
Sys
Sys
Sys
Sys
Sys
Sys
Sys
Sys
Ctm
Dev
Dev
Dev
Ctm
Ctm
Ctm
Dev
Dev
Ctm
Dev
Dev
Ctm
Page 21
Let's Help Bo
Requirements Definition
Version:
1.4
Date: 2012-12-26
SC-2.1
SC-2.2
D
D
3
3
3.4.4, SC2
3.4.5, SC3
IC-1
IC-2
IC-2.1
IC-2.2
IC-3
IC-3.1
IC-4
IC-4.1
IC-4.2
IC-4.3
I
A
A
A
I
D
I
I
I
I
1
1
1
1
1
1
1
1
1
1
3.3.4, IC1
MC-1
MC-1.1
MC-1.1.1
MC-1.1.2
MC-1.1.3
MC-1.2
MC-1.2.1
MC-1.2.2
MC-1.2.3
MC-2
MC-2.1
I
I
I
I
I
I
I
I
I
I
I
2
2
2
2
2
2
2
2
2
1
1
NR-1
NR-2
NR-4
NR-5
NR-6
I
I
I
I
I
1
2
2
1
3
3.3.5, IC2
3.5.4, IC7
3.3.6, IC3
3.3.3, IC1
3.5.1, IC4
3.5.2, IC5
3.5.3, IC6
3.6.1, MC1
3.6.2, MC2
3.6.3, MC3
3.6.4, MC4
3.6.5, MC5
3.6.6, MC6
3.6.7, MC7
3.6.8, MC8
2.4.1
2.4.2
2.4.4
2.4.5
2.4.6
Creating schedule
Editing schedule
Inventory component
Booking spare part
Viewing bookings
Viewing own bookings
Viewing all bookings
Searching spare part
Viewing spare part details
Managing spare parts
Creating spare parts
Editing spare parts
Deleting spare parts
Map component
Managing map
Managing tunnels
Creating tunnel
Editing tunnel
Deleting tunnel
Managing hot spots
Creating hot spot
Editing hot spot
Deleting hot spot
Viewing map
Finding shortest route
Nonfunctional requirements
Usability
Security
Reliability and Robustness
Portability and compatibility
Performance
Ctm
Ctm
Ctm
Dev
Dev
Dev
Ctm
Ctm
Ctm
Ctm
Ctm
Ctm
Ctm
Dev
Dev
Dev
Dev
Dev
Dev
Dev
Dev
Ctm
Ctm
Ctm
Sys
Sys
Sys
Sys
Requirement status:
I = initial (this requirement has been identified at the beginning of the project),
D = dropped (this requirement has been deleted from the requirement definitions),
H = on hold (decision to be implemented or dropped will be made later),
A = additional (this requirement was introduced during the project course).
4.3.1
Change Log
Identity
SC1, SC2
UM-2.3.1
IC-2
IC-3.1
WO-1.1.1
Action
Date
D
8.11.2012.
D
20.11.2012.
A
D
A
25.11.2012.
30.11.2012.
14.12.2012.
Comments
The team agreed to simplify the database by dropping schedule
component.
Users will be able only to get new password direct from system
administrator
Added view bookings functionality
Viewing spare part details included in search spare parts
Added notification for updated work orders
Requirement status:
D = dropped (this requirement has been deleted from the requirement definitions),
H = on hold (decision to be implemented or dropped will be made later),
A = added (this requirement was introduced during the project course).
R = resurrected (dropped or on hold requirement was reactivated)
Page 22
Let's Help Bo
Requirements Definition
5.
Version:
1.4
Date: 2012-12-26
Future Development
Since the time is limited we decided to focus on the functionalities described above, but we also
identified additional functionalities to add to the system:





The machine operator can report a crack in a tunnel, he can take also a picture and write a
short description, and the report is sent to the relative responsible. Based on this information
a map of all the cracks in the tunnels of the mine can be made. A history of the cracks can be
made. And it can be used also to make statistics;
When a vehicle is used to perform a work order, at the end of the work order, the path to the
right location should be shown to the driver. In this way the vehicle can be driven to the
closest place where that vehicle is needed for the next work order;
For each vehicle it should be available the list of all maintenance activities (past, actual,
planned). In addition, for the maintenance supervisor it should be possible to add/remove/edit
maintenance activity for a vehicle;
The maintenance supervisor should see, where are the vehicles (or where supposed to be)
planned for maintenance operations, and if there are late work orders that are using them, he
should see who is using the vehicles and should be able to call the driver or send him a
notification.
It can be developed an application for the maintenance supervisor to help to plan the
maintenance operations for the vehicles of the mine.
Page 23