|
|
This is only a preview of the paper
Click here to register and get the full text.
Existing members click here to login
|
|
|
C6.2 Design Output content and format Output to be produced by the system will be… · tickets · boarding passes · letters · the output displayed on the monitor (forms) Tickets will be created within the system and also boarding passes. Tickets will be sent to the customer’s house but boarding passes will be issued on the day of check-in in order for the customer to travel. Letters will be sent out with the customer’s travel ticket. Also, if Buzzair plans to do a special offer such as a cheap flight then letters can be sent out to all the customer’s in the system to advertise this. Letters will be created using mail-merge in a word processing program such as Microsoft Word. The output displayed on the monitor will be all the forms and the menu system which the user is faced with after logging in successfully. The user interface must be user friendly in order for the user to be able to use the system as easily as possible so that customers can be booked onto flights as quickly and easily as possible. The user interface for Buzzair is going to be a graphical user interface, which consists of windows, icons, menus and a pointer (WIMP environment), which is user-friendly making navigation around the system fairly easy. When the user uses the system, they will see icons on the monitor and a start menu at the bottom. Buzzair’s database software should first be installed then the database can easily be accessed through the start menu. In Microsoft Access, in the Buzzair database, the user will be able to follow the on screen menus and instructions. Help screens are also available. Command buttons have been put on each form to help the user access, add, delete, search and edit data quickly. Splash Form This is a small screen used as a ‘welcome’ screen at the start up of the database. It flashes on for around 5 seconds. Main Password Logon screen This small form is the form that comes up so the user can enter his/her individual password, which is chosen by the user, and each user has a different password at this stage. User Level Screen This screen asks the user to enter in their user level. This will either be manager or user and then they will be taken to the correct menu. Either the managers main menu or the users main menu. Managers Main Menu The main menu form for the users and managers looks pretty much the same however some of the functions, the user is not allowed to perform. For example, the users are not allowed to print or view boarding passes or tickets. Users main menu The user main menu will look exactly the same as the managers main menu but certain functions are blocked and command buttons will be hidden on certain forms. Customer Form This is where all the customer details are stored. This form will look exactly like the form for the CP3 but there will be more command buttons. As for the CP3 section also, a booking cannot be made until the person’s details are stored in this table. Booking Form This form is exactly the same as the booking form for the CP3 but it will be more updated with more command buttons. As you can see from the diagram of the form below, there are buttons for ‘print boarding pass or ticket’ and ‘view boarding pass or ticket’. These were on the ‘switchboard’ last year. The switchboard was very limited and now, there is a whole new menu system. Prices Form This form is like the form used in the CP3 section. It is where all the details concerning the prices of flights are kept. At the moment, Buzzair doesn’t offer any special offers such as a bargain flight week. If this needs to be created, a new price can simply be added. Staff and Passwords Form This is a new form, which has been added this year in the CP6 module. It includes all information about the staff, their user level and also their login passwords and usernames. Change Password This is a newly added feature for the CP6 module. It means staff can change their passwords. This is recommended every now and then so that no-one else finds out anyone else’s password. Check Availability This form is the form used to book a customer onto a flight. Very different from last year, a customer is not booked onto a flight using only the booking form. The user of the system must first check there is a place on a flight for the customer using this form. If there is a place, the user can simply click on book ticket. Check A Booking Form This form is a new form to be able to find a ticket for someone. Report Dialogue Box for View Ticket or Boarding Pass This is a selection box that comes up when the user wishes to view or print tickets or boarding passes. The user of the system must simply select which they would like to view. A help menu will be created to help the person using the system if needed. The user of the system can obtain help through command buttons on forms, which will take them to other forms with information on them. The user of the system can also obtain help on the menus (user or manager) by placing their cursor over the command button and the help appears in the help screen at the right hand side. Input content, structure and access Data Collection and Data Entry Data will be collected either via a telephone call to the airline directly or through a travel agent phoning us to try and book a customer onto a flight. I intend to create a screen to check availability on a flight. In order for a customer to be booked onto a flight, hopefully, this is how it will take place… · the customer rings up · if they have not used Buzzair to travel before then their details will be entered into the customer menu · The customer states whether the they would like business class or tourist class, the date they wish to travel and a seat preference (window or aisle) · The user clicks check availability and the user can report back to the customer stating whether there are any seats available and if they can match the seat preference then if the customer still wishes to book then the user is taken to the booking menu · The customer then states whether they require an adult ticket or a child ticket and any special dietary requirements e.g. vegetarian, diabetic so the in-flight meal can be sorted out · The customer is finally asked how the customer wishes to pay for the ticket(s). e.g. credit card, cash and details recorded · The customer is booked onto the flight Below is a data flow chart demonstrating the process of a customer being booked onto a flight. Files content, structure and access There are several different types of file structure in which Buzzair could use. These are… · Serial File organisation – In a serial file, there is no specific order for the records. The records are stored in the order transactions happen. This makes it easy to add a record as it can just be added onto the end of the file. Adding, deleting and searching on a serial file – To add to a serial file, the new record can simply just be added to the end of the file. To delete however, the whole file must be read from the beginning in order to find the record to be deleted then the whole file must be copied onto a new file leaving out the record to be deleted. To search for a record, there is no other way apart from reading through the whole file starting at the beginning until the right record is located. · Sequential File organisation – Records are stored one after the other in sequential file organisation like in serial file organisation but the records are sorted into key sequence. Adding, deleting and searching on a sequential file – As records stored on sequential file are stored in key sequence, to add to a sequential file, the whole file must be copied onto a new file writing in the new record in it’s place. Deleting a record from sequential file is exactly the same as serial file organisation, the file is copied onto a new file leaving out the record to be deleted. To search for a record on sequential file, this is like serial file organisation also as the whole file must be read from the beginning until the specific file is found. · Random File organisation – Random files are also known as hash files, direct files or relative files.
Approximate Word count = 5892
Approximate Pages = 23.6
(250 words per page double spaced)
|
|
|
|
|
|