|
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] |
DOD-STD-2168
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-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] |
Waterfall Model
The waterfall model is a breakdown of project activities into linear sequential phases, meaning they are passed down onto each other, where each phase depends on the deliverables of the previous one and corresponds to a specialization of tasks. The approach is typical for certain areas of engineering design. In software development, it tends to be among the less iterative and flexible approaches, as progress flows in largely one direction ("downwards" like a waterfall) through the phases of conception, initiation, analysis, design, construction, testing, deployment and maintenance. The waterfall development model originated in the manufacturing and construction industries, where the highly structured physical environments meant that design changes became prohibitively expensive much sooner in the development process. When first adopted for software development, there were no recognised alternatives for knowledge-based creative work. History The first known presentation describ ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
DO-178C
DO-178C, Software Considerations in Airborne Systems and Equipment Certification is the primary document by which the certification authorities such as FAA, EASA and Transport Canada approve all commercial software-based aerospace systems. The document is published by RTCA, Incorporated, in a joint effort with EUROCAE, and replaces DO-178B. The new document is called DO-178C/ED-12C and was completed in November 2011 and approved by the RTCA in December 2011. It became available for sale and use in January 2012. Except for FAR 33/JAR E, the Federal Aviation Regulations do not directly reference software airworthiness. On 19 Jul 2013, the FAA approved AC 20-115C, designating DO-178C a recognized "acceptable means, but not the only means, for showing compliance with the applicable FAR airworthiness regulations for the software aspects of airborne systems and equipment certification." Background Since the release of DO-178B, there had been strong calls by DERs (FAA Designated Eng ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
United States Department Of Defense
The United States Department of Defense (DoD, USDOD or DOD) is an executive branch department of the federal government charged with coordinating and supervising all agencies and functions of the government directly related to national security and the United States Armed Forces. The DoD is the largest employer in the world, with over 1.34 million active-duty service members (soldiers, marines, sailors, airmen, and guardians) as of June 2022. The DoD also maintains over 778,000 National Guard and reservists, and over 747,000 civilians bringing the total to over 2.87 million employees. Headquartered at the Pentagon in Arlington, Virginia, just outside Washington, D.C., the DoD's stated mission is to provide "the military forces needed to deter war and ensure our nation's security". The Department of Defense is headed by the secretary of defense, a cabinet-level head who reports directly to the president of the United States. Beneath the Department of Defense are th ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Defense 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] |
Computer-aided Software Engineering
Computer-aided software engineering (CASE) is the domain of software tools used to design and implement applications. CASE tools are similar to and were partly inspired by Computer-Aided Design (CAD) tools used for designing hardware products. CASE tools were used for developing high-quality, defect-free, and maintainable software. CASE software is often associated with methods for the development of information systems together with automated tools that can be used in the software development process. History The Information System Design and Optimization System (ISDOS) project, started in 1968 at the University of Michigan, initiated a great deal of interest in the whole concept of using computer systems to help analysts in the very difficult process of analysing requirements and developing systems. Several papers by Daniel Teichroew fired a whole generation of enthusiasts with the potential of automated systems development. His Problem Statement Language / Problem Statement An ... [...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] |
Best Practice
A best practice is a method or technique that has been generally accepted as superior to other known alternatives because it often produces results that are superior to those achieved by other means or because it has become a standard way of doing things, e.g., a standard way of complying with legal or ethical requirements. Best practices are used to maintain quality as an alternative to mandatory legislated standards and can be based on self-assessment or benchmarking. Best practice is a feature of accredited management standards such as ISO 9000 and ISO 14001. Some consulting firms specialize in the area of best practice and offer ready-made templates to standardize business process documentation. Sometimes a best practice is not applicable or is inappropriate for a particular organization's needs. A key strategic talent required when applying best practice to organizations is the ability to balance the unique qualities of an organization with the practices that it has in common ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
