-P-

< Day Day Up >

Peer review: A formal review where a product is examined in detail by a person or group other than the originator. See inspection, walk-through.
Perfective maintenance: Software maintenance performed to improve the performance, maintainability, or other attributes of a computer program.
Performance measures: A category of quality measures that address how well a system functions.
Performance measurement and capacity planning: A set of procedures to measure and manage the capacity and performance of information systems equipment and software.
Performance review: A formal review conducted to evaluate the compliance of a system or component with specified performance requirements.
Phase: A defined stage in the SEP Systems Development Life Cycle.
Phase review: A formal review conducted during a life cycle phase; usually at the end of the phase or at the completion of a significant activity.
Physical Configuration Audit: An audit to ensure that all physical attributes listed in the design requirements have been met by the configuration item being delivered.
Pilot: An alternative work pattern to develop a system to demonstrate that the concept is feasible in an operational environment. Pilots are used to provide feedback to refine the final version of the product and are fielded for a preset, limited period of time. Compare with prototype.
Planning phase: The period in the SEP Systems Development Life Cycle in which a comprehensive plan for the recommended approach to the systems development or maintenance project is created.
Post-Implementation Review: A formal review to evaluate the effectiveness of the systems development effort after the system is operational ( usually for at least six months).
Post-Implementation Review Report: A formal document detailing the findings of the Post-implementation Review. See Post-Implementation Review.
Post-Termination Review: A formal review to evaluate the effectiveness of a system disposition.
Post-Termination Review Report: A formal document detailing the findings of the Post-termination Review. See Post-Termination Review.
Procedure: A series of steps (or instructions) required to perform an activity. Defines how to perform an activity. Compare with process.
Process: A finite series of activities as defined by its inputs, outputs, controls (e.g., policy and standards), and resources needed to complete the activity. Defines what needs to be done. Compare with procedure.
Process model: A graphical representation of a process.
Process review: A formal review of the effectiveness of a process.
Product: General term for an item produced as the result of a process; can be a system, subsystem, software component, or a document.
Product baseline: The set of completed and accepted system components and the corresponding documentation that identifies these products. See baseline.
Production: A fully documented system, built according to the SDLC, fully tested, with full functionality, accompanied by training and training materials, and with no restrictions on its distribution or duration of use.
Product review: A formal review of a product software (or document) to determine if it meets its requirements. Can be conducted as a peer review.
Program specification: A description of the design logic in a software component, generally using pseudocode. See code.
Project: The complete set of activities associated with all life cycle phases needed to complete a systems development or maintenance effort from start to finish (may include hardware, software, and other components); the collective name for this set of activities. Typically a project has its own funding, cost accounting, and delivery schedule.
Project management: The process of planning, organizing, staffing, directing, and controlling the development and/or maintenance of a system.
Project Management Plan: A formal document detailing the project scope, activities, schedule, resources, and security issues. The Project Management Plan is created during the planning phase and updated throughout the project.
Project Manager: The person with the overall responsibility and authority for the day-to-day activities associated with a project.
Prototype: A system development methodology to evaluate the design, performance, and production potential of a system concept (it is not required to exhibit all the properties of the final system). Prototypes are installed in a laboratory setting and not in the field; nor are they available for operational use. Prototypes are maintained only long enough to establish feasibility. Compare with pilot.

< Day Day Up >

–P–