|
MIL-STD-498
MIL-STD-498, ''Military Standard Software Development and Documentation'', was a United States military standard whose purpose was to "establish uniform requirements for software development and documentation." It was released Nov. 8, 1994, and replaced DOD-STD-2167A, DOD-STD-2168, DOD-STD-7935A, and DOD-STD-1703. It was meant as an interim standard, to be in effect for about two years until a commercial standard was developed. Unlike previous efforts like the seminal DOD-STD-2167A which was mainly focused on the risky new area of software development, MIL-STD-498 was the first attempt at comprehensive description of the systems development life-cycle. MIL-STD-498 was the baseline for certain ISO and IEEE standards that followed it. It also contains much of the material that the subsequent professionalization of project management covered in the Project Management Body of Knowledge (PMBOK). The document "MIL-STD-498 Overview and Tailoring Guidebook" is 98 pages. The "MIL-STD ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
DOD-STD-2167A
DOD-STD-2167A (Department of Defense Standard 2167A), titled "Defense Systems Software Development", was a United States defense standard, published on February 29, 1988, which updated the less well known DOD-STD-2167 published 4 June 1985. This document established "uniform requirements for the software development that are applicable throughout the system life cycle." This revision was written to allow the contractor more flexibility and was a significant reorganization and reduction of the previous revision; ''e.g..'', where the previous revision prescribed pages of design and coding standards, this revision only gave one page of general requirements for the contractor's coding standards; while DOD-STD-2167 listed 11 quality factors to be addressed for each software component in the SRS, DOD-STD-2167A only tasked the contractor to address relevant quality factors in the SRS. Like DOD-STD-2167, it was designed to be used with DOD-STD-2168, "Defense System Software Quality Prog ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
DOD-STD-2167
The terms "DOD-STD-2167" and "DOD-STD-2168" (often mistakenly referred to as "MIL-STD-2167" and "MIL-STD-2168" respectively) are the official specification numbers for superseded U.S. DoD military standards describing documents and procedures required for developing military computer systems. Specifically: "Frameworks for quality software process: SEI Capability Maturity...", Springerlink.com, 2007, webpage PDF: SL6-PDF states, "MIL-STD-2167 is the standard many DoD contractors have had to deliver...whereas MIL-STD-2168 is the DoD's quality assurance standard." * DOD-STD-2167 described the necessary project documentation to be delivered when developing a "Mission-Critical" computer software system. * DOD-STD-2168 was the DoD's software quality assurance standard, titled "Defense System Software Quality Program". On December 5, 1994, the standards DOD-STD-2167A and DOD-STD-2168 were superseded by MIL-STD-498, which merged DOD-STD-2167A, DOD-STD-7935A, and DOD-STD-21 ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
MIL-STD
A United States defense standard, often called a military standard, "MIL-STD", "MIL-SPEC", or (informally) "MilSpecs", is used to help achieve standardization objectives by the U.S. Department of Defense. Standardization is beneficial in achieving interoperability, ensuring products meet certain requirements, commonality, reliability, total cost of ownership, compatibility with logistics systems, and similar defense-related objectives. Defense standards are also used by other non-defense government organizations, technical organizations, and industry. This article discusses definitions, history, and usage of defense standards. Related documents, such as defense handbooks and defense specifications, are also addressed. Definition of document types Although the official definitions differentiate between several types of documents, all of these documents go by the general rubric of "military standard", including defense specifications, handbooks, and standards. Strictly speaking, ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
United States Military Standard
A United States defense standard, often called a military standard, "MIL-STD", "MIL-SPEC", or (informally) "MilSpecs", is used to help achieve standardization objectives by the U.S. Department of Defense. Standardization is beneficial in achieving interoperability, ensuring products meet certain requirements, commonality, reliability, total cost of ownership, compatibility with logistics systems, and similar defense-related objectives. Defense standards are also used by other non-defense government organizations, technical organizations, and industry. This article discusses definitions, history, and usage of defense standards. Related documents, such as defense handbooks and defense specifications, are also addressed. Definition of document types Although the official definitions differentiate between several types of documents, all of these documents go by the general rubric of "military standard", including defense specifications, handbooks, and standards. Strictly speaking, ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Contract Data Requirements List
In United States military contracts, the contract data requirements list (CDRL, pronounced ''SEE-drill'') is a list of authorized data requirements for a specific procurement that forms a part of the contract. Overview The CDRL identifies what data products are to be formally delivered to the government by a contractor, as well as when and possibly how (e.g. format and quantity) they are to be delivered. The list typically consists of a series of individual data items, each of which is recorded on a Data Item form (DD Form 1423) containing the tailored data requirements and delivery information. The CDRL is the standard format for identifying potential data requirements in a solicitation, and deliverable data requirements in a contract. The purpose of the CDRL is to provide a standardized method of clearly and unambiguously delineating the government's minimum essential data needs. The CDRL groups all of the data requirements in a single place rather than having them scattered thr ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
IEEE 12207
ISO/IEC/IEEE 12207 ''Systems and software engineering – Software life cycle processes'' is an international standard for software lifecycle processes. First introduced in 1995, it aims to be a primary standard that defines all the processes required for developing and maintaining software systems, including the outcomes and/or activities of each process. Revision history ISO/IEC/IEEE 12207:2017 is the newest version, published in November 2017. The IEEE Computer Society joined directly with ISO/IEC JTC 1/SC 7/WG 7 in the editing process for this version. A significant change is that it adopts a process model identical to the ISO/IEC/IEEE 15288:2015 process model (there is one name change, the 15288 "System Requirements Definition" process is renamed to the "System/Software Requirements Definition" process). This harmonization of the two standards led to the removal of separate software development and software reuse processes, bringing the total number of 43 processes from 12 ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Project Management Body Of Knowledge
The Project Management Body of Knowledge (PMBOK) is a set of standard terminology and guidelines (a body of knowledge) for project management. The body of knowledge evolves over time and is presented in ''A Guide to the Project Management Body of Knowledge'' (''PMBOK Guide''), a book whose seventh edition was released in 2021. This document results from work overseen by the Project Management Institute (PMI), which offers the CAPM and PMP certifications. Much of the ''PMBOK Guide'' is unique to project management such as critical path method and work breakdown structure (WBS). The ''PMBOK Guide'' also overlaps with general management regarding planning, organising, staffing, executing and controlling the operations of an organisation. Other management disciplines which overlap with the ''PMBOK Guide'' include financial forecasting, organisational behaviour, management science, budgeting and other planning methods. History Earlier versions of the ''PMBOK Guide'' were recogni ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Systems Development Life-cycle
In systems engineering, information systems and software engineering, the systems development life cycle (SDLC), also referred to as the application development life cycle, is a process for planning, creating, testing, and deploying an information system. The systems development life cycle concept applies to a range of hardware and software configurations, as a system can be composed of hardware only, software only, or a combination of both. There are usually six stages in this cycle: requirement analysis, design, development and testing, implementation, documentation, and evaluation. Overview A systems development life cycle is composed of a number of clearly defined and distinct work phases which are used by systems engineers and systems developers to plan for, design, build, test, and deliver information systems. Like anything that is manufactured on an assembly line, an SDLC aims to produce high-quality systems that meet or exceed customer expectations, based on customer ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
DO-178B
DO-178B, Software Considerations in Airborne Systems and Equipment Certification is a guideline dealing with the safety of safety-critical software used in certain airborne systems. It was jointly developed by the safety-critical working group RTCA SC-167 of the Radio Technical Commission for Aeronautics (RTCA) and WG-12 of the European Organisation for Civil Aviation Equipment (EUROCAE). RTCA published the document as RTCA/DO-178B, while EUROCAE published the document as ED-12B. Although technically a guideline, it was a ''de facto'' standard for developing avionics software systems until it was replaced in 2012 by DO-178C. The Federal Aviation Administration (FAA) applies DO-178B as the document it uses for guidance to determine if the software will perform reliably in an airborne environment, when specified by the Technical Standard Order (TSO) for which certification is sought. In the United States, the introduction of TSOs into the airworthiness certification process, and b ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
ARP4754
ARP4754, Aerospace Recommended Practice (ARP) ARP4754A (''Guidelines For Development Of Civil Aircraft and Systems''), is a guideline from SAE International, dealing with the development processes which support certification of Aircraft systems, addressing "the complete aircraft development cycle, from systems requirements through systems verification." Revision A was released in December 2010. It was recognized by the FAA in AC 20-174 published November 2011. EUROCAE jointly issues the document as ED–79. Objectives of the document The Aerospace Recommended Practice (ARP) is a guideline for development of civil aircraft and systems with an emphasis on safety aspects. Revision A is a substantial rewrite of the document which describes the safety process as a part of an Integrated Development Process. A significant new section is devoted to the process of determining Development Assurance Level (DAL) which determines the rigor of complex hardware and software development and ve ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
ARP4761
ARP4761, Guidelines and Methods for Conducting the Safety Assessment Process on Civil Airborne Systems and Equipment is an Aerospace Recommended Practice from SAE International. In conjunction with ARP4754, ARP4761 is used to demonstrate compliance with 14 CFR 25.1309 in the U.S. Federal Aviation Administration (FAA) airworthiness regulations for transport category aircraft, and also harmonized international airworthiness regulations such as European Aviation Safety Agency (EASA) CS–25.1309. This Recommended Practice defines a process for using common modeling techniques to assess the safety of a system being put together. The first 30 pages of the document covers that process. The next 140 pages give an overview of the modeling techniques and how they should be applied. The last 160 pages give an example of the process in action. Some of the methods covered: * Functional Hazard Assessment (FHA) *Preliminary System Safety Assessment (PSSA) *System Safety Assessme ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
