Guidance for Planning, Design, and Operations of Airport Communications Centers (2018)

Below is the uncorrected machine-read text of this chapter, intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text of each book. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

131 A P P E N D I X A General • Key Concepts in Operations Management, Michel Leseure, 2010, SAGE Publications • Strategic Operations Management, Steve Brown, 2015 • “1362-1998 - IEEE Guide for IT - System Definition - Concept of Operations (CONOPS) Document,” IEEE December 22, 1998 and updated August 06, 2002. (This is standards- type document describes the format and content of a CONOPS document for an IT system, including how users and other stakeholders can establish system quantitative and qualitative characteristics, and how to address user interactions with the system. • Concept of Operations for the Future Digital System, U.S. Government Printing Office, October 01, 2004 • “Operational Concept Description (OCD)”, U.S. Department of Defense DI-IPSC-81430A, January 10, 2000 • “Concept of Operations for Commercial Space Transportation in the National Airspace System” Version 2.0, U.S. Federal Aviation Agency, May 11, 2001 http://www.faa.gov/air_traffic/satms/ media/CONOPS_narrative_v2.pdf Systems Engineering Systems engineering integrates the CONOPS approach with developing technical solutions. Examples of system engineering documents that address the standards process in both technical and management respects and that have general applicability to airports and to airport security systems follow: • ANSI/EIA-632, Processes for Engineering a System. Provides an integrated set of fundamental processes to aid in the engineering or re-engineering of a system. • IEEE Standard 12207:2008 (ISO/IEC 12207:2008(E)), Systems and Software Engineering— Software Life Cycle Processes. Establishes a common framework for the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. • IEEE 42010:2011 (ISO/IEC), Recommended Practice for Architectural Description of Software- intensive Systems. Addresses the creation, analysis, and sustainment of architectures of systems through the use of architecture descriptions. • ISO/IEC 15288:2008, System Life Cycle Processes. Establishes a common framework for describ- ing the life cycle of systems created by humans and defines a set of processes and associated terminology within that framework. • IEEE 16326, Systems and Software Engineering Project Management. Specifies the content of a project management plan. Concept of Operations Reference Guide