CS 4311 Flight Planning and Management System Software Requirements Specification Version <1.0> 2/20/2015 2001 CS 4311 Software Requirements Specification Document Control Approval The Guidance Team and the customer shall approve this document. Document Change Control Initial Release: 1.0 Current Release: 1.0 Indicator of Last Page in Document: * Date of Last Review: 2/16//2015 Date of Next Review: 3/16/2015 Target Date for Next Update: 3/16/2015 Distribution List This following list of people shall receive a copy of this document every time a new version of this document becomes available: Guidance Team Members: Dr. Ann Gates Elsa Tai Yadira Jacquez Customer: Dr. Calvin Han Software Team Members: CS 4311 Change Summary The following table details changes made between versions of this document Version Date Modifier Description 1.0 1/13/2015 Yadira Jacquez Initial version Software Requirements Specification Date Page 2/20/2015 10:07 AM ii Software Requirements Specification TABLE OF CONTENTSDOCUMENT CONTROL ................................................................................ II APPROVAL .................................................................................................................................................... II DOCUMENT CHANGE CONTROL ................................................................................................................... II DISTRIBUTION LIST ...................................................................................................................................... II CHANGE SUMMARY ..................................................................................................................................... II 1. INTRODUCTION ................................................................................................................................. 4 1.1. PURPOSE AND INTENDED AUDIENCE ................................................................................................ 4 1.2. SCOPE OF PRODUCT .......................................................................................................................... 4 1.3. DEFINITIONS , ACRONYMS , AND ABBREVIATIONS ............................................................................. 4 1.3.1. Definitions ............................................................................................................................... 4 1.3.1. Acronyms ................................................................................................................................. 7 1.3.2. Abbreviations ........................................................................................................................... 7 1.4. OVERVIEW ....................................................................................................................................... 7 1.5. REFERENCES .................................................................................................................................... 8 2. GENERAL DESCRIPTION ................................................................................................................. 8 2.1. PRODUCT PERSPECTIVE .................................................................................................................... 8 2.2. PRODUCT FEATURES ........................................................................................................................ 9 2.3. USER CHARACTERISTICS ................................................................................................................ 10 2.4. GENERAL CONSTRAINTS ................................................................................................................ 10 2.5. ASSUMPTIONS AND DEPENDENCIES ................................................................................................ 10 3. SPECIFIC REQUIREMENTS ........................................................................................................... 11 3.1. EXTERNAL INTERFACE REQUIREMENTS ......................................................................................... 11 3.1.1. User Interfaces ...................................................................................................................... 11 3.1.2. Manage Flight Plans Screen ................................................................................................. 14 3.1.3. Manage Resources ................................................................................................................. 14 3.1.4. Start Flight ............................................................................................................................. 17 3.1.5. Google Glass Screen ............................................................................................................. 17 3.1.6. Hardware Interfaces .............................................................................................................. 18 3.1.7. Software Interfaces ................................................................................................................ 18 3.1.8. Communications Interfaces ................................................................................................... 18 3.2. BEHAVIORAL REQUIREMENTS ........................................................................................................ 18 3.2.1. Same Class of User ................................................................................................................ 18 3.2.2. Related Real-world Objects ................................................................................................... 18 3.2.3. Stimulus ................................................................................................................................. 21 3.2.4. Related Features .................................................................................................................... 26 3.2.5. Functional .............................................................................................................................. 26 3.3. NON -BEHAVIORAL REQUIREMENTS ................................................................................................ 26 3.3.1. Performance Requirements ................................................................................................... 26 3.3.2. Qualitative Requirements ...................................................................................................... 26 3.4. OTHER REQUIREMENTS .................................................................................................................. 26 Software Requirements Specification Date Page 2/20/2015 10:07 AM iii Software Requirements Specification 1. Introduction 1.1. Purpose and Intended Audience The purpose of this document is to outline the requirements, both functional and non-functional, of the Flight Planning and Management System. The document serves as a communication medium and a contract between the developers and the stakeholders; the system must adhere to all the requirements that are listed. The intended audience for this document includes Dr. Han, the guidance team, the software engineering team, and all other entities who may have an interest in the FPMS. 1.2. Scope of Product The software product to be developed is the Flight Planning and Management System (FPMS). The software is intended to address the pilot’s problem of having to look away from the trajectory to view information that can help guide him or her during flights on the iPad. The customer identified an additional need for the system to assist in flight planning and management of an aircraft from a departure airport to an arrival airport. The FPMS has the potential to improve safety by displaying in-flight information on the Google Glass directly to the pilot’s sight. The Google Glass is a device that can communicate with the iPad; therefore, there is no need to create new hardware or develop an interface for communication between the iPad and the Google Glass. The software will provide the following capabilities to the pilot: • create and edit flight plans prior to a flight • support decision-making in case of a reroute during flight • track in-flight status of relevant information in real-time • maintain a repository with information that can be used in defining new flight plans or rerouting during flights. Ultimately, the system only provides decision making support to the pilot. It is capable of suggesting flight plans and generating alerts if it detects that a reroute is needed, but the pilot decides which flight plan to use and whether or not to reroute. However, the system will ensure that any decision made by the pilot does not conflict with other flight plans created by different pilots by utilizing an external system to approve flight plans. In providing in-flight information or any information relevant to creating a flight plan, the system is not responsible for generating data. It will gather in-flight data, such as weather information and aircraft location, from other devices that are part of the larger system it is embedded into. Additional data that is taken into considered when creating a flight plan, such as aircraft characteristics and waypoint information, is acquired from external resources. The FPMS will only manipulate the data as needed to present the information in the correct format to the pilot. 1.3. Definitions, Acronyms, and Abbreviations 1.3.1. Definitions Active Flight Plan A flight plan for which the departure