The document describes a bus management system project for Assosa University. It includes: - An introduction describing the background, objectives, methodology and benefits of the new system. - An analysis of the existing manual system and its problems. - The conceptual and logical database design of the new system using ER diagrams and normalization. - Implementation details including creating tables, inserting sample data, and updating records.

1. i
PREPAREDBY GROUP 3 MEMBERS
(SECONDYEAR COMPUTER SCIENCE)
ASU BUS
MANAGEMENT
SYSTEM
ASSOSA UNIVERSITY
COLLEGE OF COMPUTING AND INFORMATICS
DEPARTMENT OF COMPUTER SCIENCE
FUNDAMENTALS OF DATABASE
GROUP PROJECT
=
Submitted to Mr.Eshetu.G
Submission date
21 January 2019

2. i
Contents
Acknowledgement............................................................................................................................. ii
1 Introduction.....................................................................................................................................1
1.1 Background of Information ...............................................................................................1
1.2 Statement of the Problem .......................................................................................................1
1.3 Scope of the Project...............................................................................................................1
1.4 Objective of the Project........................................................................................................2
1.4.1 General Objective of the Project....................................................................................2
1.4.2 Specific Objective of the Project ..........................................................................................2
1.5 Methodology .........................................................................................................................2
1.5.1 Data Collection Methodologies ............................................................................................2
1.5.2 Development Tools .............................................................................................................3
1.6 Benefits and Beneficiaries of the new system...........................................................................3
2 Existing System Analysis.............................................................................................................3
2.1Overview of Purposes/services of the existing system...................................................................3
2.2 Problems in the existing System .................................................................................................4
2.3 Business rules ...........................................................................................................................4
2.4 Forms Used...............................................................................................................................5
3. Database Design .............................................................................................................................6
3.1 Conceptual Database design of the new System...........................................................................6
3.1.1 Entities and Attributes description ...........................................................................................6
3.1.2 Relationship in the existing System ......................................................................................8
3.1.3 EntitiesPrimary Key and Foreign Key....................................................................................9
2.1.4 Initial E-R Diagram of the System.................................................................................10
3.2 Logical Database Design of the new System.............................................................................11
3.2.1 E-R Relationship or Table mapping .......................................................................................11
3.2.2 Validate Model using Normalization ..................................................................................11
3.2.3 Relational Schema with Referential Integrity after normalization .........................................14
4. Implementation............................................................................................................................14
4.1 Coding the Database................................................................................................................14
5.Annexs..........................................................................................................................................16
5.1 Screenshots of the interfaces........................................................................................................16
5.2 Conclusion ..........................................................................................................................17

3. ii
Acknowledgement
We would like to express our special thanks of gratitude to our teacher Mr Eshetu.G who gave
us this opportunity to do this project. which also helped us in doing a lot of Research and we
came to know about so many new things and we would like to thank you.

4. 1 | P a g e
1 Introduction
Here, we will try to describe briefly about the Bus Management System of Assosa University.
Major aspects that will be discussed include background of the system, problem of statement,
objectives of the project, scope of the project, data collection methodology and benefits and
beneficiaries of the new system.
1.1 Background of Information
Bus is one of the main service providers in the Assosa University especially for employees.
Which is used for the employees as a service. This system was developed as one of the solution
to transfer from current manual practices to a more systematic computerized system.
1.2 Statement of the Problem
In Assosa University, most of the driver information kept in a file.
Therefore it is quite hard for them to search the driver information and employees information
when needed. Moreover it uses a lot of papers in and increase of data lost because no backup
provided for the data.
1.3 Scope of the Project
Assosa University Bus management performs its basic tasks manually. The scope of this project
is to develop and implement a new web based Bus Management system in ASU which will avoid
the problems associated with the manual processing.
The proposed system includes:-
 Developing user friendly interface.
 To minimize the work load of the Administrators.
 To assign a driver based on their experience and quality of information they provided.
 Record drive information,

5. 2 | P a g e
1.4 Objective of the Project
1.4.1 General Objective of the Project
This System is developed to build a common platform for integrated monitoring and passenger
information services. By gathering relevant information from drivers and administrators attitude
towards the system. The system can improve the quality and reliability of the transport services
which will lead to better acceptance and usage of this service by employees.
1.4.2 Specific Objective of the Project
In order to achieve our general objective we need to have the following Specific objective.
 To assign the bus for the employees without any fault.
 To reduce the requirement of resource like paper.
 To simplify the problem
 To get clear and effective response from the employees.
1.5 Methodology
The main methodology involves feasibility study, data collection, system analysis and design,
developing and implementing Bus Management System. The data consider necessary to build the
system where collected and analyzed. The Methodology is very important to ensure that the new
system would give benefits to the University.
1.5.1 Data Collection Methodologies
The required data including Driver details, Bus details, Employee details…etc, were collected.
The data collected would help to identify attributes, relationships, entities that describe, relate
and interact with the system.
 Interview
 Interview is a powerful tool for data gathering since it allows the interviewer to probe
and clarify a number of issues. Face to face interview was used to interact with the
administrator and the users of the proposed system to obtain the data required for the
database management system.
 Observation
 Observation is active acquisition of information from primary source.

6. 3 | P a g e
1.5.2 Development Tools
 System Development Software Tool
 SQL Server 2014 Management studio to data and secure information.
 Edraw Max to draw the E-R diagram and Entity relationship diagram
 Neatbeans IDE to create the forms and the interface
 Microsoft word 2010 to prepare this project
 Microsoft power point to create slide for the presentation.
 System Hardware Development Tools
 Processor Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz 3.60 GHz
 RAM 4GB of RAM
 Hard Disk 500 GB on installation drive
 Operating System
 Windows 10 pro 64 bits Operating system for developing this System.
1.6 Benefits and Beneficiaries of the new system
 Benefits of the new System
 This system will reduce the paper work in the bus administrator office.
 To manage the relation between the driver and the bus
 To manage the relation between the driver and the administrator
 To minimize time and efforts.
 It will reduce redundancy of data.
 Help employees to arrive at University on time.
 Locates the employees which bus they have to use based on their location
 Beneficiaries of the new system
The beneficiaries of the new system are:
 Employees- This system will help employees to arrive on time and it will
save them money.
 University- It will give a better gesture(image) for the University.
 Driver- The driver will avoid the confusion with the Administrators.
2 Existing System Analysis
2.1Overview of Purposes/services of the existing system
The main purpose of the existing system is, it retrieves information based on manual
approach and it doesn’t give proper information for assigned Driver or bus and also for the
employees. In this system there is redundancy of data, the employees will use the bus
randomly without being assigned and this kind of system is uncomfortable for the employees.

7. 4 | P a g e
2.2 Problems in the existing System
The problems of the existing system are the following:
 There is a lot of paper work.
 It requires more human resource
 There’s redundancy of data
 Poor relationship between bus administrator and the driver.
 There’s also a poor a relation between the driver and the bus.
2.3 Business rules
 An Administrator can manages buses based on bus information
 An Administrator also assigns Employees based on their location
 Employees will be assigned to a Bus based on their location
 Drivers will be assigned to a bus by Administrator based on their level and experience

8. 5 | P a g e
2.4 Forms Used

9. 6 | P a g e
3. Database Design
3.1 Conceptual Database design of the new System
Conceptual database design is the source of information for the logical design phase
and it uses an entity relationship model to describe the data.
3.1.1 Entities and Attributes description
 Administrator is an entity which assign and controls the information of bus, driver and
employee and this Entity has the following Attributes.
 Attributes
 Name This is an attribute of Administrator entity which is used as a name of
Administrator.
 Aid This is also an attribute of Administrator which is used as a primary key for this
entity.
 Tel This is also one of attribute of Administrator and its uses as communication for the
Administrator.
 Bus is an Entity which is being assigned by the Administrator for the use of Employees
and this entity has following Attributes.
 Attributes
 Bname This is an attribute of Bus entity which is used as a name of Bus
 Plate No This is also an attribute of Bus which is used as a primary key for this
entity
 Location This is also one of attribute of Bus and it describes where the Bus is
going from the university.
Administrator
Name Aid
Tel
Administrator
Bus
Bus
Bname
mmmm
Plate No
Location

10. 7 | P a g e
 Driver is an Entity who drives the bus by getting permission from the Administrator and
this Entity has the following Attributes.
 Attributes
 Dname This is an attribute of Driver entity which is used as a name of Administrator.
 Did This is also an attribute of Driver which is used as a primary key for this entity
 Tel This is also one of attribute of Driver and its uses as communication for the Driver
with the Administrator.
 Employee is an Entity who uses the bus being assigned by the Administrator based on
their location and this Entity has the following Attributes.
 Attributes
 Ename This is an attribute of Administrator entity which is used as a name of employee.
 Eid This is also an attribute of Employee which is used as a primary key for this entity.
 Tel This is also one of attribute of Employee and its uses as communication for the
Administrator
 Location This attribute shows the place where employee lives.
Driver
NameTel
DId
Driver
Employee

11. 8 | P a g e
3.1.2 Relationship in the existing System
 Relation between Administrator and Bus
 This is one to many relationship
 One Administrator can manage many buses.
 Many buses can be managed by Administrator.
 The participation of Administrator and Bus is partial.
 Relation between Administrator and Driver
 This one to many relationship
 One Administrator can assign many Drivers.
 Many Drivers are assigned by Administrator.
 The participation of Administrator and Employee is partial.
 Relation between Administrator and Employee
 This is one to many relationship
 One Administrator can control many Employees.
 Many Employees are controlled by Administrator.
 The participation of Administrator and Employee is partial.
 Relation between Employee and Bus
 This is many to many relationship

12. 9 | P a g e
 Many Employees use 1 Buses
 One Bus is used by many Employees.
 The participation of Employee and Bus is total.
 Relation between Driver and Bus
 This is one to one relationship
 One Driver can only drive one Bus.
 One bus can only have one Driver.
 The participation of Driver and Bus is partial.
3.1.3 EntitiesPrimaryKey and ForeignKey
Entity Primary key Foreign key
Administrator Aid
Driver Did Aid
Employee Eid Aid
Bus Bid Aid,Did,Eid

13. 10 | P a g e
2.1.4 Initial E-R Diagramofthe System

14. 11 | P a g e
3.2 Logical Database Designof the new System
3.2.1 E-R Relationship or Table mapping
3.2.2 Validate Model using Normalization
 Unnormalized Form
Did Dname Tel No
plate
Bname BLocation Eid Ename Elocation Tel
001 Abebe 099 4433 Tata Mazoriya E012 Shimelis Mazoriya 0911
E021 Fatuma Mazoriya 0921
002 Abay 0994 3332 Sunlong Gebreal E444 Alemu Gebreal 0908
003 Alex 091 2322 Daewoo Adisuaspalt E099 Azeb Adisuaspalt 0913
004 Sami 092 3443 Starbus Tena E009 Belay Tena 0988

15. 12 | P a g e
 First Normal Form(1NF)
Did Dname Tel No
plate
BName Blocation Eid Ename Elocation Tel
001 Abebe 099 4433 Tata mazoriya E012 Shemilis Mazoriya 0911
001 Abebe 099 4433 Tata mazoriya E021 Fatuma Mazoriya 0921
002 Abay 0994 3332 sunlong gebreal E444 Alemu Gebreal 0908
003 Alex 091 2322 daewoo adisuaspalt E099 Azeb adisuaspalt 0913
004 Sami 092 3443 starbus tena E009 Belay Tena 0988
 Second Normal Form(2NF)
Employee Table
Eid Ename Tel Elocation
E012 Shimelis 0911 Mazoriya
E444 Aalemu 0908 Gebreal
E099 Azeb 0913 Adsuaspalt
E009 Belay 0988 Tena
Bus-Driver Table
Bus-Employee Table
No plate Eid ELocation
4433 E012 Mazoriya
4433 E021 Mazoriya
3332 E444 Gebreal
2322 E099 Adisuaspalt
3443 E009 Tena
No plate Bname Blocation Did Dname Tel
4433 Tata Mazoriya Dr001 Abebe 099
3332 sunlong Gebreal Dr002 Abay 0994
2322 daewoo Adisuaspalt Dr003 Alex 091
3443 Starbus Tena DR004 Sami 092

16. 13 | P a g e
 Third Normal form(3NF)
Driver Table

Employee Table
Bus- Table
Bus-Employee Table
Plate no Eid ELocation
4433 E012 Mazoriya
4433 E021 Mazoriya
3332 E444 Gebreal
2322 E099 Adisuaspalt
3443 E009 Tena
Did Dname Tel
Dr001 Abebe 099
Dr002 Abay 0994
Dr003 Alex 091
Dr004 Sami 092
Eid Ename Tel Elocation
E012 Shimelis 0911 Mazoriya
E444 Alemu 0908 Gebreal
E099 Azeb 0913 Adisuaspalt
E009 Belay 0988 Tena
Plate No Bname BLocation Did
4433 Tata Mazoriya Dr001
3332 Sunlong Gebreal Dr002
2322 Daewoo Adisuaspalt Dr003
3443 Starbus Tena DR004

17. 14 | P a g e
3.2.3 Relational Schema with Referential Integrity after normalization
Admin table
Driver table
Employee table
Bus table
4. Implementation
4.1 Coding the Database
 DDL_STATEMENTS
1. Administrator
create table administrator(Aid int,Aname varchar(20),Tel int,Apassword
varchar(10),primary key (Aid));
2. Driver
create table driver(Did int,Dname varchar(20),TEL int,
primary key (Did), Aid int foreign key references administrator(Aid));

18. 15 | P a g e
3.Employee
create table employee(Eid int,Ename varchar(29),Location varchar(26),Tel int,
primary key (Eid),Aid int foreign key references administrator(Aid));
4.Bus
create table bus(PlateNo int,Bname varchar(20),Location varchar(15),
primary key (PlateNo),Did int foreign key references driver (Did), Eid int
foreign key references employee(Eid),Aid int foreign key references
administrator(Aid));
DML_STATEMENTS
1.Administrator
insert into administrator values('023','Meberatu','094802','1234');
select * from administraor where Aid='2345';
To change(update) the name of administrator
update administrator set Aname='alemu' where Aid='023';
2.Driver
insert into driver values('012','Samson','091718','023');
insert into driver values('013','Alemu','094536','023');
insert into driver values('014','Tamiru','092423','023');
To select one row from Bus table
select * from driver where Did='012';
To select all from Driver table
select * from driver;
To update one name from a driver table
update driver set Dname='samuel' where Did='012';
3.Employee
insert into employee values('0003','Alemitu','Mazoriya','09122','023');
insert into employee values('0004','Chala','Gebreal','09655','023');
insert into employee values('0005','Kebede','Menaheria','09854','023');
To select one row from Employee table
select * from employee where Eid='0005';
To select all from Employee table
select * from employee;
To update one name from an Employee table
update employee set Ename='selam' where Eid='0003';

19. 16 | P a g e
5.Annexs
5.1 Screenshots of the interfaces
4.Bus
insert into bus values('4433','Starbus','Mazoriya','012','0003','023');
insert into bus values('3344','selambus','Gebreal','013','0004','023');
insert into bus values('2345','Tata','Menaheria','014','0005','023');
To select one row from Bus table
select * from bus where PlateNo='2345';
To select all from Bus table
select * from bus;
To update a single bus name from a bus table
update bus set Bname='daewoo' where PlateNo='2345';
To delete one row from a bus table
delete from bus where PlateNo='4433';

20. 17 | P a g e
5.2 Conclusion
This system is developed to record the driver information based on their
forms they filled and record the information bus based on their plate number
and assign the buses for the employees based on the employee location and
its controlled by the administrator also the administrator can assign drivers
for each buses.
5.2.1 References
 Student handout
 www.Youtube.com
 www.tutorialspoint.com