ACKNOWLEDGEMENTWe would like to recognize the people who helped me to reach this far our lecture Bajuna Salehe, who provided us with lectures, Mr Abdallah Siphy , Mr Christopher Rabi our tutors chance for their guidance on tutorials. Lastly we highly appreciate the participation and the cooperation of our team, we are proud of ourselves.

iABSTRACTSince we have being given a chance to assume that we are hired at airport as Database Administrator thus we had to design and develop airports database as a system that will manage and control all the database activities conducted at the airport. The following steps were performed to reach this far, first task was the collection of all necessary information concerning the air, then showing the entity relationship diagram from the information collected on the airport, then translating ER model into the logical design showing the relational schemas and integrities then developing the database using MySql together with visual basic 6.0 then developing the front end application to perform the required operations.

iiCHAPTER ONE1 INTRODUCTION1.1 INTIAL TASKSThis an Airport Flights Database System project report gives a brief description on the tasks worked out, development of ERD from the given scenario whereby we had seven entities Employee, Traffic controller, Technician, Test, Airport, Model, Airplane with their attributes. Afterward we were able to build the database using MySQL whereby we had twelve tables that we developed from the ERD which had seven entities thus by breaking many to many relationships we were able to come up with twelve tables. Then on developing the front end application we used Visual basic 6.0. Thus the other task was to write and apply the SQL queries that could answer the provided questions. 1.2 PurposeThe purpose for this project is to design a database system for Airport Flights and to produce the front-end applications together with the required queries.1.3 Objectives and OutcomesTo come with the database-driven front end applications, queries or requests on the front end application.

1

CHAPTER TWO2.0 INTRODUCTIONThis chapter gives a dramatically presentation of the scenario provided through the use of the Entity relationship diagram, together with the relationship diagram showing the relationships involved. 2.1 ENTITY RELATIONSHIP DIAGRAM CONCEPTUAL DESIGN

2

2.2 RELATIONSHIP DIAGRAM

32.3 REALATIONAL SCHEMAAccommodation (model_no,air_port_name)Air_plane( RegNo, model_no)Air_port( air_port_name)Employee( SSN, salary, country, city, street, house_no,e_name, air_port_name,union_member_no)Expert ( TSSN, model_no)Model ( model_no,model_name,capacity, weight)Phone( Tphone_no,TRphone_no,TSSN, TRSSN)Technician (TSSN,Tname,country,city,house_no,street,salary,union_member_no)Test (TAA_test_no,test_name, max_test_score)Testing (testing_date, testing_hours,testing_score,TAA_test_no,RegNo,TSSn)Traffic_controller( TRSSN, Trfname, country, city,house_no, street, salary, union_member_no, medical_examination_date)Administrator( username, password)

AccommodationATTRIBUTEDATA TYPELENGTHKEY

model_no Varchar30Primary key

air_port_nameVarchar30Primary key

AdministratorATTRIBUTEDATA TYPELENGTHKEY

usernameVarchar30Primary key

PasswordVarchar30

4

Air_plane

ATTRIBUTEDATA TYPELENGTHKEY

RegNoVarchar15Primary key

model_noVarchar30

Air_portATTTRIBUTEDATA TYPELENGTHKEY

air_port_nameVarchar30Primary key

EmployeeATTRIBUTEDATA TYPELENGTHKEY

SSNVarchar15Primary key

salaryVarchar13

union_member_noVarchar10

countryVarchar30

cityVarchar30

streetVarchar30

house_noVarchar30

e_nameVarchar30

air_port_nameVarchar30

ExpertATTRIBUTEDATA TYPELENGTHKEY

TSSNVarchar15

model_noVarchar15

ModelATTRIBUTEDATA TYPELENGTHKEY

model_noVarchar30Primary key

model_nameVarchar30

capacityVarchar15

WeightVarchar15

5

PhoneATTRIBUTEDATA TYPELENGTHKEY

Tphone_noVarchar15Primary key

TRphone_noVarchar15

TSSNVarchar15

TRSSNVarchar15

TestATTRIBUTEDATA TYPELENGTHKEY

TAA_test_noVarchar15Primary key

Test_nameVarchar30

max_test_scoreVarchar4

TechnicianATTRIBUTEDATA TYPELENGTHKEY

TSSNVarchar15Primary key

TnameVarchar30

countryVarchar30

cityVarchar30

house_noVarchar15

streetVarchar30

salaryVarchar13

union_member_noVarchar10

TestingATTRIBUTEDATA TYPELENGTHKEY

testing_dateDate

testing_hourstime

testing_scorevarchar3

TAAvarchar15

RegNovarchar15

TSSNvarchar15

6

Traffic_controllerATTRIBUTEDATA TYPELENGTHKEY

TRSSNVarchar15

TrfnameVarchar30

countryVarchar30

cityVarchar30

house_noVarchar15

streetVarchar30

salaryVarchar30

union_member_noVarchar10

Medical_examination_datedate

7CHAPTER THREE3 IMPLEMENTATION3.0 Database ImplementationIn Database implementation we includes coding and testing database processing programs, completing database documentation, and installing databases and converting data, as necessary, from prior systems. Here, at last, is the point in the systems development life cycle for which our thought have been preparing. Our prior activities, conceptual data modeling and logical and physical database design are necessary previous stages.3.1 Coding and TestingThe coding we are using are truly compiled well and tested well. Our system runs well and performs queries well and with meaningful output. We are truly sure that this database system will give the desired needed and wanted by the system administrator wants. 3.2 Database Processing ProgramsWe have use MySQL database as our database engine and storing our data. Also we have use Visual Basic 6.0 for designing our front-end application interface. We also assure that by deploying these programs we will come with a well represented Flight Database System. An administrator wills do all queries through the front-end application.3.3 Database InstallationWe install our database in the laptop which runs Windows 7 Operating Systems.At the end of implementation, we expect a functioning database system that meets administrators information requirements. After that, the system will be put into production use, and database maintenance will be necessary for the life of the system.

8

3.4 Major SQL Queries

FORM 1: select * from model where model_no= " & "'" & LTrim(keyword)

9

FORM 2: select m.model_name,m.model_no,a.RegNo,m.capacity,m.weight from model m,air_plane a where m.model_no=a.model_no

10

FORM 3:select * from test

FORM 4:select count(RegNo) from air_plane11

FORM 5: select RegNo,model_no from air_plane

FORM 6: select * from technician12

FORM 7: select * from traffic_controler

13

FORM 8: select distinct t.testing_date,t.testing_hours,t.testing_score,s.TAA_test_no,s.test_name from testing t, test s where testing_date between ('2010/01/01') and ('2010/12/31')

14

FORM 9: select * from test

FORM 10: select m.model_name,m.model_no,m.capacity,m.weight from model m where m.weight>500015

FORM 11: SHOWS THE SUBSCRIBING LINK

16

FORM 12: FROM BOEING LINK

FORM 12: Airbus flight available for subscribing.

173.5 Front End ApplicationThe front end application we developed for our system comprises of eighteen forms. Form one (as home page) and form two is for login by the administrator.

FORM 13: front end application

FORM 14: ADMINISTRATOR LOGIN FORM

18Form three or Operation form is where SQL command buttons are. These commands are for searching airplane model, subscribing new flight model, adding new technicians and air traffic controllers, display the available flights, display tests that are performed periodically, to calculate number of airplanes that are served by the airport and also the flight that has decided not to land in addition to that, to calculate number of tests performed to particular flight per month. An administrator what he or she does is just press the button to perform operation he or she wants.

FORM 15: OPERATION FORMConsider when an administrator press Add new command, the two forms will pop up, first for adding employee particulars and the next form for adding airplane particulars such as of Model, Test, Expert, Testing, Airplane, Airport. Employee particulars are such as Technician, Traffic Controller and Phone.

19

FORM 16: Employee particular form

FORM 17: Aiplane particulars from.

20CHAPTER FOURCONCLUSIONThus due to the design and development of airports database as a database administrator we were able to organize all the information necessary about the airplanes stationed and maintained at the airport. The complete and proper implementation of all the required detail will lead to the effective management and control of the most airport facing problems on airplane management.

21

ContentsABSTRACT.iACKNOWLEDGMENT..iiCHAPTER ONE....11 INTRODUCTION11.1 INTIAL TASKS11.2 Purpose11.3 Objectives and Outcomes1CHAPTER TWO22.0 INTRODUCTION22.1 ENTITY RELATIONSHIP DIAGRAM CONCEPTUAL DESIGN22.2 RELATIONSHIP DIAGRAM32.3 REALATIONAL SCHEMA43 IMPLEMENTATION83.0 Database Implementation83.1 Coding and Testing83.2 Database Processing Programs83.3 Database Installation83.4 Major SQL Queries8FORM 18FORM 210FORM 311FORM 411FORM 512FORM 612FORM 713FORM 814FORM 915FORM 1015FORM 1116FORM 1217FORM 13183.5 Front End Application18FORM 1418FORM 1519FORM 1620FORM 1720CHAPTER FOUR21CONCLUSION21

Traffuc Controller

Model

Airplane

Test

Techinician

Airport

Employee

Works

ISA

Expert

Testing

Accomodate

Belongs to

Salary

City

Union_member_no

ename

SSN

Address

Medica_examination_date

Air_port_name

Model_no

Capacity

Weight

RegNo

Testing_hours

Testing_date

Testing_score

TAA_test_no

Max_test_score

Test_name

Phone_no

Street

Country

House_no

Mode_name