Download Network Interface Requirements: User Functionality and Use Cases and more Study notes Software Engineering in PDF only on Docsity!
Table of Contents
1.0 Introduction
1.1 Purpose 1.2 Scope 1.3 Definitions and Abbreviations 1.4 References 1.5 Overview
2.0 Overall Description
2.1 Product Perspective
2.1.1 Interface Requirements
2.1.1.1 User Logical Interface Requirements 2.1.1.2 User Interface Optimization 2.1.1.3 Network Interface Requirements
2.2 Product Functions 2.3 User Characteristics 2.4 Constraints
3.0 Specific Requirements
3.1 Functional Requirements
3.1.1 User Class: User 3.1.2 User Use Cases 3.1.3 User Class: Pilot 3.1.4 Pilot Use Cases 3.1.5 User Class: Manager 3.1.6 Airport Manager Use Cases 3.1.7 User Class: Super User 3.1.8 Functionality Use Cases from the Perspective of the Control Tower
1.0 Introduction
1.1 Purpose
This Software Requirement Specification document is intended to aid in the development of an Airport Traffic Control Simulator (ATCS). This is done by clearly and concisely explaining the uses and functionality that is to be expected of the ATCS. The audience for this paper is the intended designers, developers and users of this software.
1.2 Scope
This software will enable simulation of the ground traffic on a user defined airport ground network. Users will have the capability to dynamically create airports and airplanes. The simulation of the airport ground traffic will be monitored by the software by way of location and intended action of airplanes as well as system security and airplanes’ status. This ATCS will not manage airplane traffic that is in the air. This is not an intended requirement of the software. The possible benefits of the ATCS are to better understand the software development process. The software is intended to be an aid in helping to reduce the amount of ground traffic accidents in airports. Hopefully, this software will aid in identifying potential accidents that may occur, and may in effect prevent future ground accidents at airports.
1.3 Definitions and Abbreviations
Actor: A role played by an outside entity that interacts directly with the system. An actor can be a human, a machine, or a program
Airplane Status: The status of an airplane can be any one of the following: arrival flow, landing on a certain runway, taking off on a certain runway, taxiing on a certain taxiway, parking at a certain gate.
Airport Manager: A user that has created an airport and may manually control or view certain aspects of that airport.
Airport Status: The status of an airport can be described by the status of each airplane and any pending request for an airplane.
ATCS: Airport Traffic Control Simulator. The software that simulates airport ground traffic control.
Junction: A junction is a point where a taxiway or runway starts
2.1 Product Perspective
The ATCS software is self contained and not used with any other software. This software does however interact with other users of the software on the distributed network.
2.1.1 Interface Requirements
2.1.1.1 User Logical Interface Requirements
The logical interface will be a windows “application style” display with buttons and menus for the user to navigate through the software. When information from the keyboard is needed a text box or textbox equivalent will be displayed.
2.1.1.2 User Interface Optimization
- Minimize text based user response, buttons or menu navigation is more efficient and easier to handle
- Error or Response messages must be displayed in a clear concise manner.
- When displaying an Airplane or Airport status, it must be easy to read
2.1.1.3 Network Interface Requirements
The ATCS software is designed to be run on a distributed network. The ATCS software is designed with the requirement that messages can be passed between multiple users running the software. This application will have a client/server architecture.
2.2 Product Functions
The Control Tower handles allocation of the airport ground network resources A) Runways B) Taxiways C) Gates
The ATCS will be a user defined Network that simulates Ground Traffic Control
User must be able to Create A) Airport 1.1 set the ground network structure, 1.2 set related constraints 1.3 Becomes Airport manager of that Airport
B) Create an airplane and make requests for
1.1 Becomes Pilot of the Airplane
Actions the User must be able to do on an Airplane/Airport A) Open/Close an Airport (if the User is the manager of the Airport) B) Request to Enter Airport airspace C) Request to taxi D) Request to be at a Gate E) Request to Take off/ land
View the status of Airplanes or Airports run by the User
Network Structure of Airports Created by the User should include
A) Junctions 1.1. Number 1.2 Names 1.3 Connectivity Information of the Junctions. B) Runways, Taxiways (either intersection or ending) C) Runways 1.1 Number 1.2 Names 1.3 Landing is ok 1.4 Take off is ok 1.5 Junctions that intersect D) Taxiways 1.1 Number 1.2 Names 1.3 Name of Junctions at the Ends E) Gates 1.1 Name 1.2 Junctions that are connected
Airplane Direction may determined by source and destination junctions
User may specify Constraints on traffic Control by A) Assigning Priorities to taxiways and runways
Airport Status changes will be broadcasted to, network structures may be viewed by A) Super users B) Users that are Pilots around the Airport C) The Airport’s Manager
Airplane Status may be viewed by A) Super Users B) Pilots of the Airplane
Control Tower
Create Airplane
Create an airport
Become a Super User
View list of All airports
Airport Manager
User
Super User Pilot
Security
Control Tower Control Tower
Control TowerControl Tower
Create Airplane
Create an airport
Become a Super User
View list of All airports
Airport Manager
User
Super User Pilot
Security
Control Tower Control Tower
Create Airplane
Create Airplane
Create an airport
Create an airport
Become a Super User
Become a Super User
View list of All airports
View list of All airports
Airport ManagerAirport Manager
UserUser
Super UserSuper User PilotPilot
SecuritySecurity
Control TowerControl Tower Control TowerControl Tower
Figure 1: User Functionality. 3.1.2 User Use Cases
Use Case : Obtain a List of Airports on the Network
Actor: User
Main Success Scenario:
1 User selects an option for obtaining a list of Airports. 2 System (User Broadcast) broadcasts a message to System (Control Towers) requesting Airport Name/ID 3 System (User Listen) listens for System (Control Towers Broadcast) sending a message of the Airport Name/ID 4 Each Time the System (User Listen) receives an Airport Name/ID message it adds it to the list of Airports searchable by the User
Post-condition:
System (User Listen) should always be listening for a System (Control Towers Broadcast) sending a message of Airport Name/ID .1 If one is received it should be added to the list of Airports searchable by the User .2 If one is received the also has a remove Id then the Airport is no longer valid and should be removed from the list of Airports selectable by the User
Use Case: Creates an Airplane.
Actor: User.
Main Success Scenario:
1 The User creates an airplane. 2 The system creates it and associates an airplane ID and owner ID.
Extensions: 2a The system fails to create the airplane. .1 The User tries again or gives up.
Post-conditions: -The newly created airplane status must be in flow without granting entrance of any airport.
- The user becomes a pilot.
Use Case: Become Super User
Actors: User, Security
Main Success Scenario:
1 User Selects Super User option 2 System (Security) prompts for Password 3 User enters the correct password 4 System (Security) authorizes Super User status 5 System (Security) sends a request for System (Planes) in order to create a list of planes on the network 6 System (Security) Displays that the User now has Super User status
Extensions:
3a: user enters invalid password .1 User may reenter password .2 User may return to the main display
3.1.3 User class Pilot:
Figure 2 shows the functionality of the pilot and the interactions with the Plane Administrator and the Control Tower.
Check Status Of Airplane
Request a Runway
Request to Enter airplane
Request to Take off
Request to Land in
Request to Use a taxiway
Request to Park at a gate
Plane Administrator
Pilot
Control Tower
Check Status Of Airport
Check Status Of Airplane
Check Status Of Airplane
Request a Runway
Request a Runway
Request to Enter airplane
Request to Enter airplane
Request to Take off
Request to Take off
Request to Land in
Request to Land in
Request to Use a taxiway
Request to Use a taxiway
Request to Park at a gate
Request to Park at a gate
Plane AdministratorPlane Administrator
PilotPilot
Control TowerControl Tower
Check Status Of Airport
Check Status Of Airport
Figure 2. Pilot Functionality
3.1.4 Pilot Use Cases
Use Case: Check status of airplane.
Actors: Pilot, Plane Administrator.
Precondition: The airplane must exist.
Main Success Scenario:
1 The User (Pilot) requests the system (plane administrator) for the status of the airplane. 2 The System (Plane Administrator) sends the status of the airplane (arrival flow, landing on a certain runway, taking off on a certain runway, taxiing on a certain taxiway, parking on a certain gate).
Extensions:
- a: The system(Plane Administrator) fails to send the status of the airplane .1: Pilot may request again for the status of the airplane or gives up.
Use Case: Request Entrance of airplane X into the Airspace of the Airport.
Actors: Pilot, Control Tower, Plane administrator
Precondition: Airplane X must be in Flow mode
Main Success Scenario:
1 The user (Pilot) of airplane X request to the System (Control Tower) to enter the airspace of the airport 2 The System (Control Tower) grants permission to enter the airspace. 3 The airplane X enters the airport’s airspace. 4 The system (Plane Administrator) updates the status of the airplane.
Extensions:
2a System (Control Tower) does not grant permission to airplane X to enter the airport’s airspace. .1 Pilot may request again the entrance or try another airport.
Post-condition: -Status of the airplane must be entering status.
Use Case: Request a Runway
Actors: Pilot, Control Tower
Pre-conditions: The status of the airplane must be entering or at a taxiway.
Main Success Scenario:
- The user ( Pilot) request the system ( Control Tower) to use a runway.
- The system ( Control Tower) grants permission to use a runway.
Use Case: Request to get an assignment of a gate.
Actors: Pilot, Control Tower, Plane Administrator.
Pre-conditions: Airplane must be in a runway, taxiway, or in Entering status.
Main Success Scenario:
1 The user (Pilot) requests the system (Control Tower) to get an assignment of a gate.
- The system (Control Tower) assigns a gate to the airplane.
- The system (Plane Administrator) updates the status of the airplane.
Extensions: 2a: The system (Control Tower) fails to get an assignment of a gate. .1 The user (Pilot) waits and try again.
Post-conditions: A gate has been assigned to the airplane.
Use Case: Request to use a Taxiway
Actors: Pilot, Control Tower, Plane Administrator.
Pre-conditions: The airplane must be in a runway or a taxiway.
Main Success Scenario:
- The user (Pilot) requests the system ( Control Tower) to use a taxiway.
- The system (Control Tower) grants permission to use a taxiway.
- The system (Plane Administrator) updates status of airplane.
Extensions: 2a: The system (Control Tower) fails to grant permission. .1 The user (Pilot) waits and try again. .2 The user (Pilot) request the use of another taxiway.
Post-conditions: A taxiway has been reserved.
Use Case: View Status of airport
Actors: Pilot, Control Tower
Pre-conditions: The pilot must be associated with that airport.
Main Success Scenario:
- The user (Pilot) requests to the System (Control Tower) to view the status of the airport.
- The System (Control Tower) reply with the view.
Extensions: 2a: The System (Control Tower) fails to reply the view. .1 The user (Pilot) waits and try again.
Use Case: Pilot view status of an airport
Actor: Pilot, Control Tower
Main Success Scenario:
1 Pilot selects to view airport status. 2 System (Control Tower) checks to make sure the Pilot is associated with the Airport. 4 System (Control Tower) sends a message to the Pilot displaying status of the Airport
Extension
2a) Pilot does not have association .1) message is displayed to the Pilot telling him/her that he has no association with the Airport/Plane
Post-condition: A gate can be positioned on a junction, if and only if no runways start at that position.
Use Case: Open or Close airport
Actors: Airport Manager, Control Tower
Precondition: User is the creator of the airport
Main Success Scenario: (the same steps are used for opening the airport)
- Manager sends a closing request to the control tower.
- Airport is closed.
Post-condition: If the airport is closed for good, the manager will return to a normal user, otherwise, he will remain the manager as the airport will used again.
Use Case: Updating ground network structure and related constraints
Actors: Airport Manager, Control Tower
Precondition: User is the creator of the airport
Main Success Scenario:
- Manager requests to update the junctions, the runways, the taxiways, and/or the gates from the control tower.
- Control tower performs the updates.
Post-condition: All the users related to the specific airport should be notified with the new updates.
3.1.6 User class: Super User
List of all Users with Mode
View status Of every airplane
View status of Every airport
Super User
Control Tower
Control Tower
Control Tower
Plane Administrator
Plane Administrator
Plane Administrator
List of all Users with Mode
List of all Users with Mode
View status Of every airplane
View status Of every airplane
View status of Every airport
View status of Every airport
Super UserSuper User
Control TowerControl Tower
Control TowerControl Tower
Control TowerControl Tower
Plane AdministratorPlane Administrator
Plane AdministratorPlane Administrator
Plane AdministratorPlane Administrator
Figure 4. Super user Functionality
3.1.7 Super User Use Cases
Use Case: Super User view status of an airplane
Actors: Super User, Plane Administrator
Main Success Scenario:
1 Super User selects the view plane status option 2 System (Plane Administrator) send the list of all airplanes. 3 Super User selects the plane X and send request to the System ( plane administrator) 4 System (Plane Administrator) send the status of airplane X.
Use Case: Super User view status of an airport
Actors: Super User, Control Tower
Use Case: Control Tower Grants Plane's Entrance into Airspace
Actor: Control Tower, Pilot
Precondition: Airplane X must be in Flow mode
Main Success Scenario:
1 System (Control Tower) receives a request from a Pilot to Enter Airport Airspace with a Plane X 2 System (Control Tower) sends a message to the Pilot of the Status of the Airport 3 System (Control Tower) sends a message to the Pilot that the request has been granted
Extensions:
2a) If the System (Control Tower) does not want the Plane to enter the airspace based on some constraints .1 The System (Control Tower) sends a message to the Pilot stating the request has been denied
Post-condition: System (Control Tower) Update Status of the Airport if the Airplane has entered the Airport Airspace
Use Case: Control Tower Grants Plane X permission to land in.
Actor: Control Tower, Pilot
Precondition: Plane X must be in entering mode, Plane X must be assigned a runway
Main Success Scenario:
1 System (Control Tower) receives a request from a Pilot to land Plane X 2 System (Control Tower) sends a message to the Pilot that Plane X has permission to land 3 System (Control Tower) Broadcasts a message to all Around Airport of Update Airport Status 4 System (Control Tower) Broadcast a message to Super Users of the Update in Airport Status
Extensions
1a) If the Pilot has not specify a runway .1 The System (Control Tower) tells Pilot he has not been assigned a runway
.2 Send a list to the Pilot of Available runways
Use Case: Control Tower Assigns Plane X to Park at gate
Actor: Control Tower, Pilot
Precondition: System (Plane) X must be in entry or plane must be in a runway, taxiway
Main Success Scenario:
1 System (Control Tower) receives a request from a Pilot to be assigned to park at Gate 2 System (Control Tower) checks to see if a gate is available 3 System (Control Tower) sends a message to the Pilot that Plane X has been assigned gate G
Extensions
2a) If no Available gates .1 The System (Control Tower) sends a message to the Pilot stating the request has been denied
Post-condition : Gate G has become reserved
Use Case: Control Tower Grants Plane X to use taxi way T
Actor: Control Tower, Pilot
Precondition: System (Plane) X must be in taxi mode, or a runway, if taxi way is a gate then Plane x must be assigned to that gate
Main Success Scenario:
1 System (Control Tower) receives a request from a Pilot to taxi Plane X to taxi way T 2 System (Control Tower) checks to see if Plane has an assigned Gate (Landing) or Runway (Take OFF) 3 System (Control Tower) checks to see if taxi way is a path to the specified Gate (Landing) or Runway (take OFF) 4 System (Control Tower) checks to see if taxi way is attached to a junction where the plane X is located 5 System (Control Tower) checks to see if taxi way is available 6 System (Control Tower) grants request to use taxi way by sending a message to pilot 7 System (Control Tower) Updates Airport status 8 System (Control Tower) Broadcasts a message to all Around Airport of Update Airport Status
