Application Domain
- A term that refers to the nature of the application. Real time flight control systems is an example of one application domain. Management information systems represents another.
Availability
- The relative time that an operational product must be available for use. Usually expressed as the ratio of time available for use to some total time period or as specific hours of operation.
Change Control
- A part of configuration management that reviews, approves and tracks progress of alterations in the configuration of a configuration item delivered, to be delivered, or under formal development, after formal establishment of its configuration identification.
Configuration Management
- A discipline applying technical and administrative direction and surveillance to identify and document the functional and physical characteristics of a controlled item, control changes to a configuration item and its documentation, and record and report change processing and implementation status.
Configuration Management Function
- The organizational element charged with configuration management.
Configuration Management System
- The processes, procedures, and tools used by the development organization to accomplish configuration management.
COTS (Commercial Off-The-Shelf)
- A type of non-developmental software that is supplied by commercial sources.
Customer
- The person or organization who is receiving a product or service. There may be many different customers for individual organizations within a program structure. Government program offices may view the customer as the user organization for which they are managing the project. Contractors may view the program office as well as the user organization as customers.
Design Specifications
- A document that prescribes the form, parts, and details of the product according to a plan.
Design-To-Cost
- A term describing the bidding a selected, reduced set of requirements in order to meet cost objectives.
Development Computer
- The hardware and supporting software system used for software development.
Development Facilities
- The office space, furnishings, and equipment that support the development staff.
Development Model
- The abstract visualization of how the software development functions (such as requirements definition, design, code, test, and implementation) are organized. Typical models are the waterfall model, the iterative model, and the spiral model.
Development Process
- The implemented process for managing the development of the deliverable product. For software, the development process includes the following major activities, which may overlap and may be applied iteratively or recursively:
- System Requirements Analysis/Design
- Software requirements Analysis
- Preliminary Design
- Detailed Design
- Coding and Computer Software Unit Testing
- Computer Software Component Integration and Testing
- Computer Software Configuration Item Testing
- System Integration and Testing
Development Sites
- The locations at which development work is being conducted.
Development System
- The hardware and software tools and supporting equipment that will be used in product development including such items as CASE tools, compilers, configuration management systems, and the like.
External Dependencies
- Any deliverables from other organizations that are critical to your product's success.
Extemal Interfaces
- The points where the software system under development interacts with other systems, sites, or people.
Hardware Specifications
- A document that prescribes the functions, materials, dimensions and workmanship that a hardware item must meet.
Implementation
- The act of preparing the product for use by the customer.
Integration
- The act of assembling individual hardware and/or software components into a usable whole.
Integration Environment
- The hardware, software, and supporting tools that will be used to support product integration.
Internal Interfaces
- The points where the software system under development interacts with other components of the system under development.
Long Term Issues
- Issues of strategic importance to the project that can be compromised in the heat of battle. Issues such as employee training and development, establishing and improving processes and procedures, and similar activities are important to the long term viability of the project and the organization.
Non-Developmental Software (NDS)
- Deliverable software that is not developed under the contract but is provided by the contractor, the Govemment, or a third party. NDS may be referred to as reusable software, Government furnished software, or commercially available software, depending on its source.
Orange Book
- A security standard set by the U. S. Government.
Product Integration
- The act of assembling individual hardware and software components into a functional whole.
Re-engineering
- The practice of adapting existing software artifacts or systems to perform new or enhanced functions. Re-engineered artifacts may be substantially different from the existing artifact.
Reliability
- Is the degree of dependability that an operational product must meet. Usually expressed as the average time to failure.
Reusing
- Hardware or software developed in response to the requirements of one application that can be used, in whole or in part, to satisfy the requirements of another application.
Safety
- Is the degree to which the software product minimizes the potential for hazardous conditions during its operational mission.
Security
- Is the degree to which a software product is safe from unauthorized use.
Software Requirements Specification - A document that contains the complete set of engineering requirements for each Computer Software Configuration Item.
System Integration
- Is the act of assembling hardware and/or software components into a deliverable product.
Target Computer
- Is the hardware and supporting software system which will actually be used when the software system is fielded.
TBDs
- Requirements in formal requirements statements that are To Be Defined.
Test Specifications
- A document that prescribes the process and procedures to be used to verify that a product meets its requirements.
Traceability Mechanism
- Processes and procedures (manual and/or automated) that map all software components and artifacts from source requirements through test cases.
Transition Plan
- A plan (documented in the Computer Resources Integrated Support Document) specifying how products are to be transitioned from development to support.
Unit Testing
- Testing performed by the developers on individual software or hardware components to verify the component meets its allocated requirements.
