Implementation notes that relate to the IEEE interpretation of the ISO/IEC 14143-1:1998 standard are described.
Data messages, known as protocol data units (PDUs), that are exchanged on a network between simulation applications are defined. These PDUs are for interactions that take place within specified domains called protocol families, which include entity information/interaction, warfare, logistics, simulation management, distributed emission regeneration, radio
A set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process is described. This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software, but is more suited for use on modified-off-the-shelf software and
The standard is presented. The primary objective is to specify a standard approach to software unit testing that can be used as a basis for sound software engineering practice. A second objective is to describe the software engineering concepts and testing assumptions on which the standard approach is based. A third objective is to provide guidance and
IDEF1X 97 consists of two conceptual modeling languages. The key-style language supports data/information modeling and is downward compatible with the US government's 1993 standard, FIPS PUB 184. The identity-style language is based on the object model with declarative rules and constraints. IDEF1X 97 identity style includes constructs for the distinct but
The Software Test Description (STD) describes the test preparations, test cases, and test procedures to be used to perform qualification testing of a Computer Software Configuration Item (CSCI) or a software system or subsystem. Software Test Description (STD) PDF
Common Foundation Reference FOM (CF-RFOM) as defined by the SISO Reference FOM Study Group (see Simulation Interoperability Standards Organization, "Reference FOM Study Group Final Report," Version 1.0, March 9, 1998).
A methodology for establishing quality requirements and identifying, implementing, analyzing and validating the process and product software quality metrics is defined. The methodology spans the entire software life-cycle.