Home' RTCA Documents for Review : DO-230H FRAC Contents 226
© 2017, RTCA, Inc.
ISO/IEC/IEEE 42010:2011, 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
describing 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 (PMP).
ISO/IEC 16326: 2009, Systems and Software Engineering Project Management Processes,
provides content specifications for project management plans covering software projects.
ISO/IEC 26702:2007, Application and Management of Systems Engineering Process, defines the
life cycle interdisciplinary tasks required to transform customer needs, requirements and constraints
into a system solution. It also specifies requirements for the systems engineering process and its
application throughout the product life cycle.
ISO/IEC TR 24766, Guide for Requirements Engineering Tools, provides guidance on desirable
capabilities of requirements engineering tools.
Several industry groups have standardized protocols for digital video systems and for their integration with
other elements of physical security systems. Their common goal is improved hardware and software
compatibility, but each group has its own focus, and their standards differ in important respects including
their span of coverage and how they specify and test for compatibility compliance.
The Open Network Video Interface Forum (ONVIF) is composed of most of the leading
manufacturers of video hardware and software. ONVI standards focus on camera, encoder, and
software compatibility including VMS and PSIM integration.
The Physical Security Interoperability Alliance (PSIA) also includes video manufacturers as
members, but it also includes leading access control hardware and software manufacturers and
suppliers of building automation systems. PSIA’s emphasis is on making these elements
interoperable, e.g., being able to hand off access control alerts so that video imagery and decision -
making software can utilize such information.
The Security Industry Association (SIA) is working on access control integration using
specifications of leading access control hardware and software manufacturers, which have been
regarded by many system integrators as de facto standards for many years.
All of these groups have published specifications and/or standards, which continue to be developed and
refined, and all continue to expand their memberships.
Stating that an item of equipment, such as a video camera, “complies” with a published industry standard
does not assure that it will interoperate with “compliant” products of other manufacturers. Even within a
given camera product line, there can be models which comply with a given standard while other models do
Equipment specifications, however detailed, are not sufficient to reveal to an airport operator the full level
of operational performance or the compliance of a specific device to a standard. Always check equipment
model details against the standards to which they have been tested, and whenever possible physically test
the products under local operational and environmental conditions of use.
Airports continually must deal with moves-adds-changes, and this often includes elements of the
airport’s security system. A major issue is often the ability to upgrade or replace an item of hardware or
software independently of a manufacturer’s proprietary design data and protocols. Airport design and
procurement packages should:
Links Archive Navigation Previous Page Next Page