Managing Software Deliverables: A Software Development Management Methodology - page 176

< Day Day Up >

–G–

Gantt chart: A list of activities plotted against time, showing start time, duration, and end time; also known as a bar chart.

< Day Day Up >

–H–

Hardware: The physical portion of a system (or subsystem), including the electrical components . Compare with software .
Host: The computer that controls communications in a network that administers a database; the computer on which a program or file is installed; a computer used to develop software intended for another computer. See target .

< Day Day Up >

–I–

Implementation: Installing and testing the final system, usually at the user (field) site; the process of installing the system.
Implementation phase: The period of time in the Systems Development Life Cycle when the system is installed, made operational, and turned over to the user (for the beginning of the Operations and Maintenance phase).
Implementation Plan: A formal document that describes how the system will be installed and made operational.
Information Technology: The application of engineering solutions in order to develop computer systems that process data.
In-Process Review: Formal review conducted (usually annually) during the Operations and Maintenance phase to evaluate system performance, user satisfaction with the system, adaptability to changing business needs, and new technologies that might improve the system.
In-Process Review Report: A formal document detailing the findings of the in-process review. See In-Process Review .
Input/output: The process of entering information into a system (input) and its subsequent results (output). A hardware device that enables input (for example, a keyboard or card reader) and output (for example, a monitor or printer). Collectively known as I/O.
Inspection: A semiformal to formal technique in which software requirements, design, or code are examined in detail by a person or group other than the originator to detect errors. See peer review, walk-through .
Integrated Product Team: A multidisciplinary group of people who support the Project Manager in the planning, execution, delivery, and implementation of life cycle decisions for the project.
Integration Document: A formal document that describes how the software components, hardware components , or both are combined and the interaction between them.
Integration and Test phase: Life cycle phase during which subsystem integration, system, security, and user acceptance testing are conducted; done before the Implementation phase.
Integration Test: Testing in which software components, hardware components, or both are combined and tested to evaluate the interaction between them.
Integrity: The degree to which a system (or system component) prevents unauthorized access to, or modification of, computer programs or data.
Iterative: A procedure in which repetition of a sequence of activities yields results successively close to the desired state (e.g., an iterative life cycle in which two or more phases are repeated until the desired product is developed).
Interface: To interact or communicate with another system (or system component). An interface can be software and/or hardware. See user interface .
Interface Control Document: Specifies the interface between a system and an external system(s).
Interoperability: A measure of the ability of two or more systems (or system components) to exchange information and use the information that has been exchanged. Same as compatibility .
Information Technology Systems Security Certification and Accreditation: A formal set of documents showing that the installed security safeguards for a system are adequate and work effectively.