35 system implementation this involved putting

This preview shows page 29 - 32 out of 94 pages.

3.5 System Implementation This involved putting together or building various elements of a system for example MySQL for database Wamp Server for hosting the web pages. This is the stage in which the actual system was recognized. The technical architecture defined in the design stage was the baseline for developing the system. The interface ware designed using HTML and Java script languages. This is because these languages provided tremendous friendly user interfaces; that is easy to learn and affordable. The database was designed in MYSQL basing on Wamp Server software. MYSQL provides a high level of security to the database, that is, authentication which can either be during the logging in to the database or on DML commands such as delete, add or even edit, it also reduces redundancy. In here the researcher achieved his fourth objective. Input Design This was the input realization of input design. Tables, forms and reports were created and relationships defined among these tables and security constrains set. During the physical design the researcher translated the expected schemas into actual database structures and at this time, he had to map: Entities to tables Relationship to foreign key constraints Attributes to columns primary unique identifiers to primary key constraints Unique identifiers to unique key constraints Attributes to columns.
16 3.6 System Testing This involved testing the system in order to correct errors or remove defects that rose. This stage involved testing the source code to make sure that it produced the expected and desired results when subjected to a set of predefined conditions. It was subdivided into three major phases, that is, unit testing, system testing and user acceptance testing. Under unit testing, specific parts of the source code were tested. Emphasis was put on the website- database connections to ensure that information sent by a user from the web page form reaches the systems database. System testing involved putting the entire software to test in order to find out whether or not the functional requirements of the system had been efficiently and effectively integrated and satisfied Finally, User acceptance testing was done; this was a key factor for the success of the system performance. The system under consideration was tested for user acceptance by constantly keeping in touch with the system users that is, the airline customers and staff. 3.7 Database Structure The system was used by different customers to book seats and by different staff to schedule airplanes. And indeed the seats were reserved and flights schedules were on time. This helped the researcher to achieve his last objective. Customer’s table Column Name Data Type Nullable size ID (PK) Int No 1 Custid Varchar2 Yes 25 Surname Varchar2 Yes 25 Other_Name Varchar2 Yes 100 Email Address varchar2 Yes 50 Nationality Varchar2 Yes 50 Residence Varchar2 Yes 50
17 PhoneNo. Int Yes 15 DOB Varchar2 Yes 25 Tabl e 1 showing passenger’s details Flight table Column Name Data Type Nullable size ID (PK) int

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture