|< Day Day Up >|
To copy software files onto a different media that can be sorted separately from the original files and used to restore the original files, if needed. The act of creating these files.
The set of
A work product (such as software or documentation) that has been
A standard against which measurements or comparisons can be made.
The process of designing a system by designing the low-level components first, then integrating them into large subsystems until the complete system is designed; bottom-up testing tests these low-level components first, using software drivers to simulate the higher-level
An operational version of a software product incorporating a specified subset of the complete system functionality. See version .
The redesign of an organization, culture, and business processes to achieve significant improvements in costs, time, service, and quality.
|< Day Day Up >|
|< Day Day Up >|
A measure of the expected use of a system.
A measure of the amount of input a system could process and/or amount of work a system can perform (e.g., number of users, number of
Comprehensive analysis of the technical and nontechnical security features and other safeguards of a system to establish the extent to which a particular system meets a set of specified security requirements.
In configuration management, a
In configuration management, the process by which a change is proposed, evaluated, approved (or disapproved), scheduled, and tracked. See change, change directive, change impact assessment, change implementation notice .
Formal documents used in the configuration management process to track, control, and manage the change of configuration items over the systems development or maintenance life cycle. See system change request, change impact assessment, change directive, and change implementation notice .
The formal change control document used to implement an approved change. See Change Control Documents .
The formal Change Control Document used to determine the effect of a proposed change before a decision is made to implement it. See Change Control Documents .
The formal Change Control Document used to report the actual implementation of a change in a system. See Change Control Documents .
A network application in which the end-
v. To transform the system logic and data from design specifications into a programming language. n. The computer program itself; pseudocode is code written in an English-like logical representation; source code is code written in a programming language; object code is code written in machine language.
A measure of the ability of two or more systems (or system
An electronic tool that is used to assist in the design, development, and coding of software. See tools .
The person who ensures that all activities are undertaken at the user site. Includes security activities for planning, awareness training, risk management, configuration management, certification and accreditation, compliance assurance, incident reporting, and guidance and procedures.
A formal document that describes the user's environment and process relative to a new or modified system; defines the users, if not already known. Called a CONOPS.
The functional and/or physical collection of hardware and software components as set forth in formal documentation. Also, the requirements, design, and implementation that define a particular version of a system (or system component). See configuration control, configuration item, configuration management, configuration management plan, configuration status accounting .
Formal review of a project for the purpose of assessing compliance with the Configuration Management Plan.
The process of evaluating, approving or ( disapproving), and coordinating changes to hardware/software configuration items.
The formal entity charged with the responsibility for evaluating, approving (or disapproving), and coordinating changes to hardware/software configuration items.
An aggregation of hardware and/or software that satisfies an end-use function and is designated by the customer for configuration management; treated as a single entity in the configuration management process. A component of a system requiring control over its development throughout the life cycle of the system.
The discipline of identifying the configuration of a hardware/software system at each life cycle phase to control changes to the configuration and maintain the integrity and traceability of the configuration through the entire life cycle.
A formal document that establishes formal configuration management practices in a systems development/ maintenance project. See configuration management .
The recording and reporting of the information that is needed to effectively manage a configuration, including a listing of the approved configuration identification, status of proposed changes to the configuration, and the implementation status of approved changes. See configuration .
A formal document that establishes continuity of operations processes in case of a disaster. Includes
The process of converting (or exchanging) data from an existing system to another hardware or software environment.
A formal document that describes the strategies involved in converting data from an existing system to another hardware or software environment.
Maintenance performed to correct faults in hardware or software.
The degree to which a system or component is free from faults in its specification, design, and implementation.
The costs for design, development, installation, operation and maintenance, and
The comparison of alternative courses of action or alternative technical solutions to determine which alternative would realize the greatest cost benefit; cost-benefit analysis is also used to determine if the system development or maintenance costs still yield a benefit or if the effort should stop.
The process of determining the total cost associated with a software development or maintenance project, to include the effort, time, and labor required.
A standard on which a decision or judgement may be based (e.g., acceptance criteria to determine whether to accept a system).
Used in project planning; the sequence of activities (or
A formal board that guides and
An individual or organization that specifies the requirements for and formally accepts delivery of a new or modified system; one who pays for the system. The customer may or may not be the user. See user .
|< Day Day Up >|