Professional Documents
Culture Documents
IN
Information Technology
BY
No Name ID No.
January 2013
BAHIR DAR, ETHIOPIA
Bahir dar University IOT Maintenance System
By
No Name ID No.
1 Abubeker Yimam ENG(R)/036/2002
2 Andualem Tilahun ENG(R)/097/2002
3 Foziya Mohammed ENG(R)/329/2002
4 Solomon Nigussie ENG(R)/704/2002
Information Technology
January 2013
The Project is our own and has not been presented for a degree in any other university and all
the sources of material used for the project/thesis have been duly acknowledged.
I certify that this project satisfies all the requirements as a project for the degree of Bachelor of Science.
This is to certify that I have read this project and that in my opinion it is fully adequate, in scope and quality, as
a project for the degree of Bachelor of Science.
It is approved that this project has been written in compliance with the formatting rules laid down by the school
of the university.
Automation of Bahir dar university IOT maintenance system 2012/13
ACKNOWLEGMENT
We would like to acknowledge the support of the maintenance system stuff members at Bahir
dar University IOT. They have given the required all documents essential for the study.
Particularly, Anteneh Asnake who maintenance system coordinator, Afework Adale who
profession of electrician, Destaw Mebratu who profession of water sanitation and hygiene
equipment and Adane Gedefawu who profession of office machine, allowed our group for
interview them at any time. We also would like to express the deepest appreciation to our
advisor Worku kelemework who has supported us in the past 3 months by his valuable
comments and corrections. He encouraged us to pursue on this topic and spent extra time by
helping our group to accomplish our study.
Finally we also appreciate the help and support from all persons who were directly or indirectly
involved in our project.
TABLE OF CONTENTS
BDU | School of Computing and Electrical Engineering Department of Information Technology program i
Automation of Bahir dar university IOT maintenance system 2012/13
Contents
ACKNOWLEGMENT...........................................................................................................................................................i
TABLE OF CONTENTS......................................................................................................................................................ii
LIST OF FIGURE................................................................................................................................................................iv
LIST OF TABLE.................................................................................................................................................................. v
LIST OF USER INTERFACE...............................................................................................................................................v
LIST OF SYMBOLS AND NOTATIONS...........................................................................................................................vi
ABSTRACT........................................................................................................................................................................vii
CHAPTER ONE...................................................................................................................................................................1
1.1. Introduction................................................................................................................................................................1
1.2. Background................................................................................................................................................................ 1
1.2.1 Mission.................................................................................................................................................................1
1.2.2 Vision................................................................................................................................................................... 1
1.3. Purpose of the system.................................................................................................................................................1
1.4. Existing System vs. Proposed System........................................................................................................................2
1.4.1 Existing System....................................................................................................................................................2
1. 4.2. Proposed system.................................................................................................................................................2
1.5. Objective of the project..............................................................................................................................................3
The general and specific objectives are described below..................................................................................................3
1.5.1 General objective..................................................................................................................................................3
1. 5.2 Specific objective................................................................................................................................................3
1.6. Scope of the project....................................................................................................................................................3
1.7. Methodology..............................................................................................................................................................3
1.7.1 Data collection method.........................................................................................................................................4
1.7.2 Development Tool................................................................................................................................................4
1.7.3 Analysis and Design Tool.....................................................................................................................................5
1.8. Significance of the Project..........................................................................................................................................5
1.9 .Time Schedule............................................................................................................................................................6
1.10. Individual Tasks.......................................................................................................................................................6
CHAPTER TWO: SYSTEM FEATURES............................................................................................................................7
2.1 Existing System Description.......................................................................................................................................7
BDU | School of Computing and Electrical Engineering Department of Information Technology program ii
Automation of Bahir dar university IOT maintenance system 2012/13
2.1.1 To request a service..............................................................................................................................................7
2.1.2 Updating information of technician......................................................................................................................7
2.1.3 Searching the file..................................................................................................................................................8
2.1.4 Problems encountered by the user........................................................................................................................8
2.1.5 Limitation of the maintenance office....................................................................................................................8
2.2 Proposed System Description......................................................................................................................................8
2.3 Functional Requirements.............................................................................................................................................9
2.3.1 User Requirements...............................................................................................................................................9
2.3.2 System Requirements.........................................................................................................................................10
2.4 Non Functional Requirements...................................................................................................................................28
2.5 Analysis Models........................................................................................................................................................28
2.5 .1 Sequence Diagram.............................................................................................................................................29
2 .5.2 Activity Diagram...............................................................................................................................................41
CHAPTER THREE: SYSTEM DESIGN............................................................................................................................55
3. System Design.............................................................................................................................................................55
3.1. Deployment Diagram...........................................................................................................................................55
3.2. Architectural Design.............................................................................................................................................57
3.3. User Interface Design...........................................................................................................................................59
3.4 Data Structure Design............................................................................................................................................70
3.5 Schema Diagram...................................................................................................................................................76
3.6 Algorithm Design..................................................................................................................................................78
3.7. Database Design...........................................................................................................................................................81
Bibliography........................................................................................................................................................................ 82
Appendix 1.......................................................................................................................................................................... 83
BDU | School of Computing and Electrical Engineering Department of Information Technology program iii
Automation of Bahir dar university IOT maintenance system 2012/13
LIST OF FIGURE
Figure 1: Time Schedule.......................................................................................................................................................6
Figure 2: Use Case Diagram...............................................................................................................................................12
Figure 3: Login.................................................................................................................................................................... 29
Figure 4 : Assigns technician..............................................................................................................................................30
Figure 5 : Views message....................................................................................................................................................31
Figure 6 : Generate report...................................................................................................................................................32
Figure 7: View report..........................................................................................................................................................33
Figure 8: Search for manage...............................................................................................................................................34
Figure 9: Search for technician............................................................................................................................................35
Figure 10: Update Information............................................................................................................................................36
Figure 11: Approve request.................................................................................................................................................37
Figure 12: Send request service...........................................................................................................................................38
Figure 13: Delete request....................................................................................................................................................39
Figure 14: Check status.......................................................................................................................................................40
Figure 15: Login ………………………………………………………………………………………………………………………….42
Figure 16: Assign technician...............................................................................................................................................43
Figure 17: Logout................................................................................................................................................................44
Figure 18: Generate report.................................................................................................................................................45
Figure 19:View account......................................................................................................................................................46
Figure 20: Cancel request…………………………………………………………………………………………………47
Figure 21: Check status.......................................................................................................................................................48
Figure 22: Delete request....................................................................................................................................................49
Figure 23: Search Information.............................................................................................................................................50
Figure 24: Update Information............................................................................................................................................51
Figure 25: View message....................................................................................................................................................52
Figure 26: View report........................................................................................................................................................53
Figure 27: Create account....................................................................................................................................................54
Figure 28: Deployment Diagram.........................................................................................................................................56
Figure 29: Class Diagram....................................................................................................................................................58
Figure 30: ER Diagram.......................................................................................................................................................70
Figure 31: Schema Diagram................................................................................................................................................77
BDU | School of Computing and Electrical Engineering Department of Information Technology program iv
Automation of Bahir dar university IOT maintenance system 2012/13
LIST OF TABLE
Table 1: Individual task.........................................................................................................................................................6
Table 2: Manager Login......................................................................................................................................................15
Table 3 : Technician login...................................................................................................................................................15
Table 4 : Logout.................................................................................................................................................................. 16
Table 5 : Assign technician.................................................................................................................................................17
Table 6 : Update Information..............................................................................................................................................18
Table 7: Search Information................................................................................................................................................19
Table 8 : Generate report.....................................................................................................................................................20
Table 9 : View account........................................................................................................................................................21
Table 10 : Cancel request....................................................................................................................................................22
Table 11 : Views message...................................................................................................................................................22
Table 12: Views report........................................................................................................................................................24
Table 13: Sends service request..........................................................................................................................................24
Table 14 : Delete request.....................................................................................................................................................25
Table 15 : Check technician status......................................................................................................................................26
Table 16: Create account.....................................................................................................................................................27
Table 17 : Change password...............................................................................................................................................27
BDU | School of Computing and Electrical Engineering Department of Information Technology program v
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program vi
Automation of Bahir dar university IOT maintenance system 2012/13
ABSTRACT
The system developed in this project, IOT Maintenance System, provides a simple and efficient
way of facilitating maintenance service. Achieving this objective is difficult using a manual
system due to redundant and collecting relevant malfunctioned materials information may be
very time consuming. All these problems will be solved by automating the manual system.
This document contains the introduction, methodology that uses tools like Notepad++, wamp
and VISIO, data sources like site observation, interview and document analysis, and for design
methodology we use object-oriented. For analysis model we use sequence and activity diagram.
For system design we include deployment diagram, architecture diagram, UI design, data
structure design, and algorithm design for the project that is going to be developed. To develop
the real system, designs had been made that covers the system architecture, user interfaces and
database designs.
BDU | School of Computing and Electrical Engineering Department of Information Technology program vii
Automation of Bahir dar university IOT maintenance system 2012/13
CHAPTER ONE
1.1. Introduction
Our project is concerned on Bahir Dar University institute of technology (IOT) maintenance
systems. Till now, the system is manual. The system should be automated to maximize the
benefits gained from information technology .The intension of this study is, therefore, to make
system simple, effective and efficient using information technology solution.
The new system will give best file management strategy, user friendly to the users and provide
correct and usable information for the users and customers to make timely decision.
1.2. Background
Bahir dar University Institution of Technology was upgraded to Degree Program in 1997. The
Polytechnic Institute was renamed to Bahir Dar University, Engineering Faculty. In year 2010,
it changes its institutional structure, from Bahir Dar University Engineering Faculty to Bahir
Dar University, Institute of Technology (IOT).
Bahir Dar University Institute of Technology maintenance system established by a few number
of peoples in 1963 G.C. At that time, the name of the system is office of machine and later
in1990 G.C year, the name is changed to (maintenance case team).The maintenance case team
serve all members of the IOT campus by maintaining devices and other materials.
1.2.1 Mission
The mission of Bahir Dar University is to contribute significantly for social, economic,
political, scientific and technological development of the nation through the provision of high
quality education, active commitment in research activities for the ease of life
1.2.2 Vision
The Vision of Bahir Dar University is to become one of the ten Premier Research Universities
in Africa for the future.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 1
Automation of Bahir dar university IOT maintenance system 2012/13
Files are exposed to loss and damage since the files are stored on a paper.
The System records documents on papers as result it needs more storage place
and resources and it is difficult to manage properly.
The system should be allowed to search, delete, and update stored data
automatically.
The system shall allow applicants to register about failed and/or malfunctioned
item information.
The manager responds for applicants request online.
Improve quality of service like facility of the system.
Provide secured system by checking user name and password
The customer data kept properly because we will use database application.
Avoid data redundancy by using database management system.
Prepare different documents and reports on required time automatically.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 2
Automation of Bahir dar university IOT maintenance system 2012/13
User friendly system, that means the customer and system interact in a good
manner.
Determining what to build and understand the problem domain of the system
using low fidelity models consisting of transforming user requirements in to
system requirements.
Reviewing the existing system problems
Determining how to build the proposed system and show the solution domain
of this system.
1.7. Methodology
The purpose of the methodology is to give an experienced investigator enough information to
replicate the study.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 3
Automation of Bahir dar university IOT maintenance system 2012/13
Document analysis: - Using this method the team will try to analyze written
documents in the organization which have importance to the project. This
include the organization mission strategy, sample business forms, reports
procedure manuals, Business rules, and documentation of existing systems, if
any document view. See Appendix 2
There are several types of web programming language that are used for making a site more
dynamic. But, for this project we are choosing php scripting language to design our database.
Because:
BDU | School of Computing and Electrical Engineering Department of Information Technology program 4
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 5
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 6
Automation of Bahir dar university IOT maintenance system 2012/13
If the required material that is going to be maintained or replaced is not found in the store
management:-
Check if the budget is found to purchase the material, if not the budget is approved by
deputy manager.
The purchasing officer assigns the Performa committee and opens the Performa.
If the purchasing cost is very high from the expected cost it must fail and review again
by the deputy manager to approve again the budget.
The budget approved by deputy manager then goes to the purchasing office and the
material will be bought and given to the store management.
The technician takes the material from store management and uses it to maintain
failed item.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 7
Automation of Bahir dar university IOT maintenance system 2012/13
The new system will include solution of existing system problems by giving services better than
the older one as much as possible. We proposed the following list of tasks included in our
system.
The system follows the following procedure to request service:
The customer of the system opens the website and click on applicant’s link to open
request form.
The customer fills the form that contain field that fill with kind of the failed item and
profile of applicant.
The customer clicks on send button to get the service.
Message is send to manager.
The customer who is the member of the campus, open the website and select the
applicant link.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 8
Automation of Bahir dar university IOT maintenance system 2012/13
The manager opens the website and login in to the system then view the failed items
information coming from the applicant. After observing the problem, he/she assign
the technician that is related to the problem.
Technician also login into the website and view failed item information that is send
from the manager. After viewing the problem the technician maintain the problem
encountered in the area by contacting physically with the problem area. After
accomplished his task, he/she generates and sends report to the manager.
Manager selects the report link and view if report is submitted or not. If report is
found, he view report and approves the report and finish the work. If the material
that is going to be replaced or maintained is not found in the store management.
Manager can cancel user request when the request is not announced by him. But he
accept and approve the request when request is valid or consider his responsibility
Manager deletes the request after he/she accepts the report. But the deleted request
saves in other places.
Requirement model is a collection of requirement artifacts including; essential use case model,
essential use case model description which in their entirety help us to capture the essential
aspect of the maintenance system.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 10
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 11
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 12
Automation of Bahir dar university IOT maintenance system 2012/13
UC 12.Delete request: manager delete request of user after solved the problem
but save this delete request in other table and administrator delete user account
when user leave the campus.
UC 13.Send message: User sends message to manager to indicate answered
his/her request.
UC14.Check technician’s status: Manager checks status of technician for
assigning technician.
UC15.Create account: Administrator creates an account for manager and
technician.
UC16.Change password: System administrator change password and user
account of manager and technician when both are leave the organization
BDU | School of Computing and Electrical Engineering Department of Information Technology program 14
Automation of Bahir dar university IOT maintenance system 2012/13
Assumptions:
Table 2: Manager Login
Alternative course: 5.1If the user name and password is not valid, back to
login page and return to error message
5.2If technician try more that 3 time, system close the
page.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 15
Automation of Bahir dar university IOT maintenance system 2012/13
Preconditions The manager and technician first login and finish the task.
Post condition The system is closed.
Assumptions:
BDU | School of Computing and Electrical Engineering Department of Information Technology program 16
Automation of Bahir dar university IOT maintenance system 2012/13
Table 4 : Logout
BDU | School of Computing and Electrical Engineering Department of Information Technology program 17
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 18
Automation of Bahir dar university IOT maintenance system 2012/13
Alternative course: 5.1If searched information is not found, back to search page.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 19
Automation of Bahir dar university IOT maintenance system 2012/13
Assumptions:
Use case No: UC-6
Use case Name: Generate report
Actor (s): Technician
Description: : System shall allow technician generate report which indicate the task
complete.
Typical course of Actor Action System Response
events 1. Open website. 4. Display report form.
2. Logged to website. 6.Display report
3. Click report link.
5.Click generate report
button
7.Click send report
Alternative course:
administrator request
button
5.View user account and
select one of status
technician
Alternative course: 5.1. If there is not account found, back to view search form and
return error message.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 21
Automation of Bahir dar university IOT maintenance system 2012/13
Preconditions UC-1
Post condition The manager sends message to technician and a technician maintain an
item
Assumptions:
BDU | School of Computing and Electrical Engineering Department of Information Technology program 22
Automation of Bahir dar university IOT maintenance system 2012/13
Alternative course: 5.1If the form is not fulfilling, back to the form and return error message that
inform manager.
Preconditions All require fields of form are correctly fill by the user.
Post condition The manager approve or reject for user asked when he/she sends failed item
Assumptions:
Table 12: Views report
Table 13: Sends service request
Use case No: UC-12
Use case Name: delete request
Actor (s): Manager
Description: This use case describes that a manager delete request of user after the failed
item is maintained but save this delete request in somewhere.
Typical course of Actor Action System Response
events 1. Open website. 4. Display search form.
2. Logged to website. 7.Display the request
3. Click on delete link. 9. Display successfully delete request
5. Enter id in to search
form
6.If searched id is found
BDU | School of Computing and Electrical Engineering Department of Information Technology program 24
Automation of Bahir dar university IOT maintenance system 2012/13
Alternative course: 6.1. If the form is not fulfilling, back to the form and return error
message that inform manager.
Alternative course: 3.1If the form is not fulfilling, back to the form and return error
message that inform manager.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 25
Automation of Bahir dar university IOT maintenance system 2012/13
Alternative course: 6.1 If the form is not fulfilling, back to the form and return error
message that inform manager.
Assumptions:
4. Select status.
5. Enter old user name and
password.
6.Click change password
button
Alternative course: 5.1 If the form is not fulfilling, back to the form and return error
message that inform manager.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 27
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 28
Automation of Bahir dar university IOT maintenance system 2012/13
Figure 3: Login
BDU | School of Computing and Electrical Engineering Department of Information Technology program 29
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 30
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 31
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 32
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 33
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 34
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 35
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 36
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 37
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 38
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 39
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 40
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 41
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 42
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 43
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 44
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 45
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 46
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 47
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 48
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 49
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 50
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 51
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 52
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 53
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 54
Automation of Bahir dar university IOT maintenance system 2012/13
3. System Design
The purpose of the design phase is to plan a solution of the problem specified by the
requirements document. The design of a system is perhaps the most critical factor affecting the
quality of the software; it has a major impact on the later phases, particularly testing and
maintenance.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 55
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 56
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 57
Automation of Bahir dar university IOT maintenance system 2012/13
UI 1: Main Screen
BDU | School of Computing and Electrical Engineering Department of Information Technology program 59
Automation of Bahir dar university IOT maintenance system 2012/13
UI 2: Login page
This user interface is displayed whenever the administrator wants to login into the system. The
administrator must have the valid user name and password. If the administrator enters valid
password and username the system will allow her/him to log in to the system and displays main
menu screen and the same as for other members.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 60
Automation of Bahir dar university IOT maintenance system 2012/13
UI 3: Sign Up
This user interface is used to select the activities admin wants to perform. The admin can select
one of the activities links and click sign up button. This user interface is used to create new user
account. When the admin clicks on Signup button, the system verifies the entered information.
If the admin clicks on clear, all the information on the form will be cleared.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 61
Automation of Bahir dar university IOT maintenance system 2012/13
UI 4: Manager Page
This user interface is used to view the activities of manager wants to perform. The manager can
select one of the activities links.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 62
Automation of Bahir dar university IOT maintenance system 2012/13
UI 5: View Page
This user interface is used to view failed item information that are reported from the customers
UI 6: Assign Technician
BDU | School of Computing and Electrical Engineering Department of Information Technology program 63
Automation of Bahir dar university IOT maintenance system 2012/13
This user interface is used to select the technician and assign to solve the problems
UI 7: Applicant Form
This user interface is used to report a problem of each customer as well as their detail personal
information to the manager
BDU | School of Computing and Electrical Engineering Department of Information Technology program 64
Automation of Bahir dar university IOT maintenance system 2012/13
UI 8: Technician Page
This user interface is used to view the activities of technician wants to perform. The technician
can select one of the links.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 65
Automation of Bahir dar university IOT maintenance system 2012/13
UI 9: Update
This user interface is used to update customer and technician information by the manager.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 66
Automation of Bahir dar university IOT maintenance system 2012/13
UI 10: Delete
This user interface is used to cancel the customer request after the technician solve the problem
and report to the manager, if he/she successfully maintain the material
BDU | School of Computing and Electrical Engineering Department of Information Technology program 67
Automation of Bahir dar university IOT maintenance system 2012/13
BDU | School of Computing and Electrical Engineering Department of Information Technology program 68
Automation of Bahir dar university IOT maintenance system 2012/13
UI 12: Search
This user interface is used to search customer and technician information.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 69
Automation of Bahir dar university IOT maintenance system 2012/13
3.4.1 ER Diagram
BDU | School of Computing and Electrical Engineering Department of Information Technology program 70
Automation of Bahir dar university IOT maintenance system 2012/13
ER Diagram Key:
Lname:-Last Name
Fname:-First Name
TechId:-Technician Identification Number
CustId:-Customer Identification Number
AdminId:- Administrator Identification Number
WSHE:-Water, sanitation and hygiene equipment
WSHEmarkNo:- Water, sanitation and hygiene equipment mark number
ElecNo:-Electronic number
FurnNo:-Furniture number
Acqdate:-Acquired date
3.4.1.1 ER Description
Entity’s:- manager, technician, administrator, material, customer, WSHE, electric,
furniture, office machine, account and service
Attribute: - Fname, lname, Sex,managerID, TechID, custID,
location,type,status,serialNo,salary,applicantDate,ElecNo,phoneNo,size,
WSHEmarkNo, FurNo,account , user name, password, acq date, and serviceDate etc..
Relationship: Receive request, offers, assigns, create, request, has, uses and maintains.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 71
Automation of Bahir dar university IOT maintenance system 2012/13
Material
Electric
Office Machine
BDU | School of Computing and Electrical Engineering Department of Information Technology program 72
Automation of Bahir dar university IOT maintenance system 2012/13
t
Mapping Customer_Material Entity
Customer_Material
Manager
Customer
custID Fname
Lnam account Sex Location requsetDate
e
Mapping Technician_Material Entity
Technician _Material
System Administrator
Customer_Account
BDU | School of Computing and Electrical Engineering Department of Information Technology program 73
Automation of Bahir dar university IOT maintenance system 2012/13
password username
Mapping Manager_Service Entity
Manager_Service
serviceDate applicantDate
1. First normal form (remove multi valued attributes)
Technician(phone No)
BDU | School of Computing and Electrical Engineering Department of Information Technology program 74
Automation of Bahir dar university IOT maintenance system 2012/13
Foreign key=------------
Primary key=
BDU | School of Computing and Electrical Engineering Department of Information Technology program 75
Automation of Bahir dar university IOT maintenance system 2012/13
Electric
ElecNo
Office Machine
serialNo
Furniture
FurNo
WSHE
WSHEmarkNo
Technician
Manager
Customer_Material
Account
username Password
Customer_Account
serviceDate applicantDate
Manager_Service
BDU | School of Computing and Electrical Engineering Department of Information Technology program 77
Automation of Bahir dar university IOT maintenance system 2012/13
3.6.1 Login
3.6.2 Search
4. Else
Display error message and return to form
End if
End
End If
End
Input: string technician id, Name, Gender, Status, Block, Room Number
Output: Display successful message or error message
Procedure:
Begin
a. Enter all input information in to assign form
4. If (is valid)
Display successful message
5. Else
Display error message and return to assign form.
End If
End
BDU | School of Computing and Electrical Engineering Department of Information Technology program 81
Automation of Bahir dar university IOT maintenance system 2012/13
Bibliography
Ambler, S. W. (June 22, 2001). The Object Primer 2nd Edition:Introduction to Techniques for
Agile Modeling. In Introduction to Techniques for Agile Modeling (p. 9). Ronin International.
Ambler, S. W. (June 22, 2001). The Object Primer:Introduction to Techniques for Agile
Modeling. In S. W. Ambler, Introduction to Techniques for Agile Modeling (p. 29). Ronin
International.
Ambler, S. W. (June 22, 2001). The Object Primer:Introduction to Techniques for Agile
Modeling. In S. W. Ambler, A Ronin International White Paper (p. 24). Ronin International.
Ambler, S. W. (June 22, 2001). The Object Primer:Introduction to Techniques for Agile
Modeling. In S. W. Ambler, Introduction to Techniques for Agile Modeling (p. 18). Ronin
International.
BDU | School of Computing and Electrical Engineering Department of Information Technology program 82
Automation of Bahir dar university IOT maintenance system 2012/13
Appendix 1
BDU | School of Computing and Electrical Engineering Department of Information Technology program 83