Compliance with the application programmer interfaces defined in this specification will permit simulation developers to interchange link compatible HLA RTIs without recompiling federate source code or re-linking federate object code with Dynamic Link-Compatible (DLC) RTI libraries. The use of DLC compliant RTIs does not ensure that federations will have
FIPS 199 is the acronym for Federal Information Processing Standard Publication 199. FIPS 199 is the Standards for Security Categorization of Federal Information and Information Systems of the United States Federal Government standard. It establishes security categorization of the information systems used by the Federal Government, one component of risk
The processes and procedures that should be followed by users of the High Level Architecture (HLA)to develop and execute federations are de .ned in this recommended practice.This recommended practice is not intended to replace low-level management and systems engineering practices native to HLA user organizations,but is rather intended as a higher-level
This guide describes the scope of application and interrelationships for the members of the IEEE 1175 family of standards. It points the reader to the appropriate member standard that addresses issues involved in effectively integrating computing system tools into a productive engineering environment.
Minimum requirements for the structure, information content, and format of user documentation, including both printed and electronic documents used in the work environment by users of systems containing software, are provided in this standard.
The format and contents of a concept of operations (ConOps) document are described. A ConOps is a user-oriented document that describes system characteristics for a proposed system from the users' viewpoint. The ConOps document is used to communicate the overall quantitative and qualitative system characteristics to the user, buyer, developer and other
The content and qualities of a good software requirements specification (SRS) are described, and several sample SRS outlines are presented. This recommended practice is aimed at specifying the requirements of software to be developed, but can also be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance
Guidance for the development of the set of requirements, System Requirements Specification (SyRS), that will satisfy an expressed need is provided. Developing an SyRS includes the identification, organization, presentation, and modification of the requirements. Also addressed are the conditions for incorporating operational concepts, design constraints, and
The standard specifies the format and content of software quality assurance plans. It meets the IEEE/EIA 12207.1 requirements for such plans.
IEEE Std 1462-1998 is an adoption of international standard ISO/IEC 14102:1995. The international standard deals with the evaluation and selection of computer-aided software engineering (CASE) tools, covering a partial or full portion of the software engineering life cycle. The adoption of the international standard by IEEE includes an implementation note,