|
EXPERT
TRACKING AND MAINTENANCE SYSTEM
|
OBJECT ORIENTED MODEL OF EXPERT TRACKING AND MAINTENANCE SYSTEM
This chapter shows
the step-by-step process of Design of Expert tracking and Maintenance System
by using UML Diagrams. Beginning with Object oriented analysis using the UML
notation: Business activity diagram use case, sequence diagrams, collaboration
diagrams and followed by class diagram are going to explain
and illustrate the system model.
4.1
Object oriented Analysis
4.1.1
Business process model for Expert tracking and maintenance system
The business process model of the Expert tracking and maintenance system is shown below.
4.1.2
Use Case Diagram for ETMS
There are four main actors in expert tracking and maintenance system. The actors are user, managerial staff, technical staff and clerical staff. The use case diagram for the Expert tracking and maintenance system is shown in Figure4.1.
Figure 4.1 Use case diagram of Expert tracking and maintenance system
4.1.2.1
Definition of Actors
The following are the actors for the system:
i)
User
The main tasks performed by user in the system are:
o Personal details entry
o Edit personal details
o View personal details
o System Request Entry
o Edit the system request details
o View system request details
o Maintenance request entry
o Edit their maintenance request details
o View their maintenance request details
ii)
Managerial Staff
The main tasks performed by Managerial staff in the system are:
o View All system request details
o Assign system for request
o View all maintenance request details
o Assign technician for request
o View all MOS details
o View all maintenance report
o View all user details
o Search user details by option
iii)
Technical Staff
The main tasks performed by Technical staff in the system are:
o View maintenance request details
o Enter maintenance report
iv)
Clerical Staff
The main tasks performed by Clerical staff in the system are:
o New stock details entry
o View and Edit stock details
o IP Address details entry
o Edit IP Address details
o View IP Address details
o Location details entry
o Edit location details
o View location details
4.1.2.2
Explanation of Use Case For ETMS
The explanation of each use case is as follows:
a. Personal details entry
The user starts this use case. It provides the capabilities to create, edit and view the personal details.
b. System Request entry
The user starts this use case. It provides the capabilities to create, edit and view their system request details.
c. Maintenance Request entry
The user starts this use case. It provides the capabilities to create, edit and view the Maintenance request details.
d. View search user details
The managerial staff starts this use case. It provides the capabilities to search the user details.
e. View system request of user
The managerial staff starts this use case. It provides the capabilities to view all the user’s system request details and assign the system for the user request.
f. View All MOS details
The managerial staff starts this use case. It provides the capabilities to view all the MOD details assigned for user’s request.
g. View Maintenance request of user
The managerial staff starts this use case. It provides the capabilities to view all the user’s maintenance request details and assign the technician for maintenance request.
h. View maintenance request
The technical staff starts this use case. It provides the capabilities to view maintenance request of the user assigned to him/her.
i. Report entry
The technical staff starts this use case. It provides the capabilities to enter the maintenance report details.
j. View all Maintenance Report
The managerial staff starts this use case. It provides the capabilities to view all the Maintenance report details.
k. Stock details entry
The clerical staff starts this use case. It provides the capabilities to create, edit and view stock details.
l. IP Address and location details entry
The technical staff starts this use case. It provides the capabilities to create, edit and view IP Address and location details.
4.2.1
Sequence Diagram for personal info entry
The sequence diagram to enter personal details is illustrated in Figure 4.2.
4.2.2
Sequence Diagram for edit personal details
The sequence diagram to edit personal details is illustrated in Figure 4.3.
4.2.3
Sequence Diagram for view personal details
The sequence diagram to view personal details is illustrated in Figure 4.4.
4.2.4
Sequence Diagram for View All User details
The sequence diagram to view all user details is illustrated in Figure 4.5.
4.2.5
Sequence Diagram for search user
The sequence diagram to search user details is illustrated in Figure 4.6.
Figure 4.6. Sequence diagram to search user details
4.2.6
Sequence Diagram for system request entry
The sequence diagram to system request entry is illustrated in Figure 4.7.
Figure 4.7. Sequence diagram for system request entry
4.2.7
Sequence Diagram for system request edit
The sequence diagram to edit system request details is illustrated in Figure 4.8.
Figure 4.8. Sequence diagram to edit system request details
4.2.8
Sequence Diagram for view system request
The sequence diagram to view system request details is illustrated in Figure 4.9.
4.2.9
Sequence Diagram for maintenance request entry
The sequence diagram to enter maintenance request details is illustrated in Figure 4.10.
4.2.10
Sequence Diagram for edit maintenance request
The sequence diagram to edit the maintenance request details is illustrated in Figure 4.11.
Figure 4.11. Sequence diagram to edit the maintenance request details
4.2.11
Sequence Diagram for view maintenance request
The sequence diagram to view maintenance request details is illustrated in Figure 4.12.
Figure 4.12. Sequence diagram to view maintenance request details
4.2.12
Sequence Diagram for view all system request
The sequence diagram to view all system request details is illustrated in Figure 4.13.
Figure 4.13. Sequence diagram to view all system request details
4.2.13
Sequence Diagram for view all MOS
The sequence diagram to view all MOS details is illustrated in Figure 4.14.
Figure 4.14. Sequence diagram to view all MOS details
4.2.14
Sequence Diagram for view all maintenance request
The sequence diagram to view all maintenance request details is illustrated in Figure 4.15.
Figure 4.15. Sequence diagram to view all maintenance request details
4.2.15
Sequence Diagram for mrtech view
The sequence diagram to view assigned maintenance request details is illustrated in Figure4.16.
Figure 4.16. Sequence diagram to view assigned maintenance request details
4.2.16
Sequence Diagram for view all report
The sequence diagram to view all report details is illustrated in Figure 4.17.
Figure 4.17. Sequence diagram to view all report details
4.2.17
Sequence Diagram for stock entry
The sequence diagram to enter stock details is illustrated in Figure 4.18.
Figure 4.18. Sequence diagram to enter stock details
4.2.18
Sequence Diagram for stock edit
The sequence diagram to edit stock details is illustrated in Figure 4.19.
Figure 4.19. Sequence diagram to edit stock details
4.2.19
Sequence Diagram for stock view
The sequence diagram to view stock details is illustrated in Figure 4.20.
Figure 4.20. Sequence diagram to view stock details
4.3
Collaboration Diagrams
4.3.1
Collaboration Diagram for user personal entry
Figure 4.21. Collaboration
diagram to enter personal details
4.3.2
Collaboration Diagram for View all system request
Figure 4.22. Collaboration diagram to view all SR details
4.4
Class Diagram
Figure 4.23 below illustrated class diagram
Expert tracking and maintenance system.
4.5
Summary
The step by steps of Design of Expert tracking and Maintenance System has been discussed. Beginning with Object oriented analysis using the UML notation: Business activity diagram use case, sequence diagrams, collaboration diagrams and followed by class diagram were explained and illustrated.