Downloaded 138 times
Uploaded byuow
Airport flight schedule System UML diagrams
This document describes an airport flight schedule system (AFSS) project. It includes the project title, group members, and outlines of the contents, introduction, functional requirements, non-functional requirements, language and tools used, and various UML diagrams including class, component, deployment, use case, activity, state transition, sequence, and collaboration diagrams. The introduction provides an overview of the AFSS for maintaining flight, passenger, and fuel records with privacy and accessibility restrictions. The functional requirements specify storing and managing flight, passenger, and fuel data. The UML diagrams further illustrate the system design and structure.
More Related Content
![Airline Management System [for presentation]](https://cdn.slidesharecdn.com/ss_thumbnails/airlinemanagementsystem-200114162441-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Airport flight schedule System UML diagrams
Airport flight schedule System UML diagrams
- 2. Project Title AIRPORTFLIGHT SCHEDULE SYSTEM
- 3. Presented To MamSadaf Anwar
- 4. Group Members RAJAHAMZA TARIQ (143) BILAL ABBAS (142) MOHAMMAD SIRAJ (126)
- 5. CONTENTS Introduction FunctionalRequirements Non Functional Requirements Language and tools Use case diagram
- 6. Introduction This is theflight schedule software for airport. This is for the accuracy of work. Time efficiency is created. This software handle air traffic of airport. Maintain record of flights, passengers and fuel etc. Administrator easily handle all the records. Privacy is maintained in AFSS, data is secured. Information of passengers not accessible to anyone without administrator. Only next 24 hour status of flights are accessible to website administrator.
- 7. Functional Requirements Storetakeoff and landing flights data with date and time. Store data related to flights e.g. passengers traveled in a flight, flight registration number etc. Store route of flights and destination. Automatically warning is issued when weather is not suitable. Automatic message is created if route and time is same for two flights. Fuel consumption for every flight is stored. Data stored separately for international and domestic flights and passengers.
- 8. Non Functional Requirements Privacy requirement Availability requirement Capacity requirement Backup and recovery requirement Performance requirement Security requirement Reliability requirement Maintainability
- 9. Language and Tools Java language is used for coding. Used tool net beans in java for fulfilling the requirements. SQL database system is used for storing all the data.
- 10. UML diagrams UMLstands for Unified Modeling Language which is used in object oriented software engineering. Although typically used in software engineering it is a rich language that can be used to model an application structures and behaviour. There are basically two types of UML diagrams 1. Structural diagrams 2. Functional diagrams
- 11. Structural diagrams Structural diagramsare those diagrams which basically show structure of a system or software. It basically show the things in the system being modeled. Some structural diagram of AFSS are:- 1. Class Diagram 2. Component Diagram 3. Deployment diagram
- 12.
- 13.
- 14.
- 15.
- 16. Advantages / Disadvantagesand Uses of Component Diagram Component Diagram is useful when we have to make design of some device, which has input output socket e.g. Camera, Mobile phones. It is not useful for designing of some software like web page, application etc. In our system AFSS, component diagram is not useful for better understanding because AFSS is a software in which only data is needed. It represent the implementation of system.
- 17.
- 18. AFSS: DBA <<artifact>> Flight Timing <<artifact>> CreateReport AFSS: Controller <<artifact>> Plane Avalibilty <<artifact>> Route Configuration <<artifact>> Fuel Usage Database
- 19. Advantages / Disadvantagesand Uses of Deployment Diagram In deployment diagram, three dimensional rectangle is used to represent node. Deployment diagram is structural diagram. It is used to create architecture of some system, e.g. architecture of computer which has processor, RAM, Hard disk etc. Deployment diagram is not useful for AFSS because AFSS is a software. It show clear architecture of system when some architectural design is created.
- 20. Behavioral Diagrams Behavioraldiagram show the behavior of a system. It show how system behave in a particular situation. It show what happen in a system. Some behavioral diagram of AFSS are:- 1. Use case Diagram 2. Activity Diagram 3. State Transition Diagram 4. Sequence Diagram 5. Collaboration Diagram
- 21. Use case log in Homepage <<include>> Store flight data take off and landing flight with date and time store route of flight fuel consumption bad pin <<extend>> warning!! route already in use <<extend>> passengers data Maintinance create report fuel report passengers and total flights report <<include>>
- 22. Discription In thisuse case diagram only one administrator handle all the records. Administrator log in firstly which is non functional requirement. After log in home page is appeared. Administrator enter data on required field and automatically message is issued if data is already in use. Administrator is also responsible for maintaining and creating reports.
- 23.
- 24. State Transition Diagram IdleLogin Getting Pin Flight Data Getting data Validation validate pin timing and route Passenger Data Getting Data Start transaction exit transaction
- 25.
- 26. Collaboration Diagram AFSS Management System DBA ReportsPassengers Flight Schedule Flight Route Fuel Usage Create_Report()
- 27. Advantages / Disadvantagesand Uses of Collaboration Diagram Collaboration diagram is the interaction diagram which show the interaction between the entities. It show the functionality and behaviour of individual object as well as overall operation of the system. It is suited in AFSS to show relationship between flights, planes, passengers, timing& route etc. Collaboration Diagram harder to keep track of the flow of control.