System Analysis and Design

I. Overview

Fixed Based Operators $($FBO$)$ are the means in businesses that supply needs of the aviation community to schedule their Fuel Stops, Meals, Aircraft and Passengers needs during Flight Operations.

ll$.$ Goal

The Ability for the Pilots of an aircraft to pre schedule the needs of their Aircraft and passengers during the flight operations across the U$.$S$.$ or even foreign flights, using the FBO community of Businesses.

The goats for this project are as follows:

$1.$ The ability to schedule fuel needs in advance or upon arrival.

$2.$ The ability to supply needs for the aircraft and passengers.

a$.$ Food, rental Cars, hotels, Ambulances.

b$.$ Aircraft Maintenance, Oil, Storage of Aircraft

$3.$ The ability to be notified on a mobile device, that an order has been received.

$4.$ An ability to be notified that work in completed by mobile device.

Scoring

The scoring for this competition will be on a percentage system. All development work will be weighted as follows:

$50\%$ Functionality $($Does the Application allow Ordering of Needs?$)$

$25\%$ Design $($Is it an efficient design with user interface acceptance?$)$

$25\%$ Documentation $($Does the Documentation follow the program$)$

Non$-$functioning code will not be considered for judging. Therefore, if the required user interface was attempted but did not work and the team still provided documentation for it$,$ they would not receive any credit for that component of the application. Ifvour application does not compile, it will not be evaluated!

$$ Student

Ill. Requirements $($check boxes if attempted$)$

You may use any combination of forms, pages, menus, etc. to provide the application's functionality; but design your user interface with ease of use in mind. You may include any graphic elements that you wouid like. The flow should inform the FBO of the Pilot, Times of Arrival and needs of everyone.

User Interface

The interface should be an easy to follow step by step process that a pilot would understand. Step $1$ followed by $2$ and so on$.$ Not a go here then there approach.

$$ B$.$ Functional

$$ User Requirements

$$ Databases

$$Should include Aircraft by Pilot.

O FBO Reservation Database which is filled out.

O Databases should be secure to that one pilot and that one FBO$($no one is allowed to see other pilots requests$)$

$$Actions

C$]$ The application should allow the pilot to fill out their FBO Needs

Request form, in an orderly fashion.

$$Administrative Requirements $$Reports

$[3$ It would be nice to print out the request form so the FBO could give it to the line crew to fuel aircraft and check off the needs of the pilot.

$$Actions

C$]$ The application should allow the FBO to mark the request form as completed or in process so the pilot can check on the status of their order during the process.

$$ c$.$ Proofing

$$The application shall check all date fields and times given on the form.

$$All mandatory data in the database should be verified.

$$There should be a unique key to every form submitted so it can be researched.

$$ Sfu&nt

IV$.$ Documentation $($check boxes if attempted$)$

$$Create documentation detailing out the necessary steps involved in compiling the source code of the application as well as steps necessary to run the application. $$Create a step by step user guide that a user with no knowledge of the application can use to perform any function of the final system. Note: This will be judged on detail and conciseness.

$$Create high level technical design documentation that details out how the solution was implemented $($class diagram, sequence diagrams$)$

V$.$ Bonus $($check boxes if attempted$)$

$$ A$.$ Testing

$$Create Test Script document that details out sample data utilized within the application and expected output.

$$ B$.$ Additional Enhancements

Include FBO incentives on such things as FUEL pricing.

Specials to pilots that $[$and there like Free Lunch.

VI$.$ In Specifications

$$ A$.$ Entities

$$ Pilot o Name o Phone Number$($mobile$)$ o Airport Based From o Email Address o Pilot Id$($Assigned By Application$)$

$$ Aircraft o Tail Number o Unique Pilot Id$.$ o Type Of Aircraft