Copyright
Wideman Comparative Glossary of Common Project Management Terms v3.1 is copyright by R. Max Wideman, March 2002.

Please feel free to point to this document. For non-profit purposes you may copy this page, either whole or as whole definitions provided the above copyright notice is attached. For inclusion in for-profit works, please contact the author at maxw@maxwideman.com

File: PMG_S09.htm generated 12/19/2002 9:25:58 AM
Generated by program: PMGlosGen v1.33 Program Author: Graham Wideman

Introduction | What's New in Version 6.1 | International Recognition
About the Author | Sources and References
Content Index |
Order Your V6.1 Copy Here!

Surplus/Deficit - to - Systems Scope Description

***  prev

Term
Definition     Editor's Choice
 
Source
Surplus/Deficit
The current financial year budget allocation minus total anticipated expenditures. [D01964]

 PMIS
Surprise
The surfacing of an unanticipated uncertainty, either opportunity or risk event. [D01965]

 RMH
Surveillance
A term used in C/SCSC to mean the monitoring of continued compliance with an approved/validated management control system. [D04662]

 QWF
Survey
An activity designed to either
  1. Collect comprehensive data for analysis, or
  2. Determine the form, extent, position and/or topography of land by taking measurements and using geometry or trigonometry.
[D03318]

 Webster
Survey, Product Oriented
A review and evaluation to determine the adequacy of the technical requirements relating to quality and product conformance to design intent. [D01966]

 FAR
QMPP
Suspension of Work
Two possible types:
  1. Constructive: An act or failure to act on the part of an owner which is not a directed suspension of work but which has the effect of delaying or interrupting all or part of the work
  2. Directed: An order or directive from the owner to the contractor to stop all or part of the work. [D05129]

 PDG
SV
See Schedule Variance

  
SWAG
See Scientific Wild Anatomical Guess

  
SWOT Analysis
A process whereby a group of people determine:
  1. What Strengths do we have? (How can we take advantage of them?)
  2. What Weaknesses do we have? (How can we minimize them?)
  3. What Opportunities are there? (How can we capitalize on them?)
  4. What Threats might prevent us from getting there? (Consider technical obstacles, competitive responses, values of people within the organization, etc.)
  5. For every obstacle identified, what can we do to overcome or get around it? (This helps to develop contingency plans.)
[D02333]

 PPS&C p68
Synergy
Combined action or operation of two or more parties, systems, or parts, in which the results are greater than they would be acting separately. [D03319]

 RMW
Synthesis
The composition or combination of parts or elements so as to form a whole. Also, deductive reasoning. [D03320]

 Webster
System
A methodical arrangement of activities or parts designed to achieve repetitive or reproducible results. [D01970]

 CCCP
A group of interacting, interrelated, or interdependent elements forming a complex whole. This includes a set of ideas or principles grouped together for classification or analysis. [D01967]

 VPM 19
A methodical assembly of actions or things forming a logical and connected scheme or unit. [D01968]

 PMK87
The complete technical output of the project including technical products. [D01969]

 WST
Either
  1. A collection of connected units that are organized to accomplish a specific purpose. A system can be described by one or more models, possibly from different viewpoints. Synonym: physical system, or
  2. A top-level subsystem.
[D04883]

 RUP
System Acceptance
The act of taking custody based on satisfactory verification at factory or at site. [D04250]

 CSM
System Acceptance Letter
A letter signed by the senior technical member of the project board after ensuring the project has completed system test requirements and is ready for user acceptance. [D01971]

 WST
Prepared by the project manager or stage manager for signature by the senior technical member of the project board after ensuring that the project has completed system test requirements and is ready for user acceptance tests. [D03956]

 PNG
System Analysis
The logical development of user requirements into system requirements, system concepts, and system specifications through the knowledgeable application of state-of-the-art technology and system evaluation criteria applied in analytical trade-off analysis. [D04251]

 CSM
System Analysis and Design
The process of evaluating alternative solution candidates against predetermined decision criteria to select a best value solution. [D04252]

 CSM
System Architecture Development
The development of the top-level decomposition of a system concept. [D04253]

 CSM
System Concept Review ("SCR")
A buyer control gate which reviews and approves the recommended system concept configured to satisfy the system requirements document. The SCR is the decision point to proceed with the development of the system specification. [D01972]

 VPM 291-4
System Decomposition
The hierarchical functional and physical partitioning of any system into hardware assemblies, software components, and operator activities that can be scheduled, budgeted, and assigned to a responsible manager. [D04254]

 CSM
System Deployment Procedures
Step-by-step instructions to deploy the project into its operational environment. [D04255]

 CSM
System Design Review ("SDR")
A seller control gate which reviews and approves the top-level system design solution and rationale. The SDR is the decision point to proceed with system specification flowdown to hardware and software configuration items. [D01973]

 VPM 291-4
System Development
Converting user requirement into an operational system. [D04256]

 CSM
System Development Project
A project with a high percentage of new product design. [D04257]

 CSM
System Engineer
The person responsible for system integrity and the advocate for orderly, systematic technical development. The responsibility begins with the identification of the user needs and ends with validation that the user needs have been satisfied. The system engineer ensures that all appropriate technical and operational disciplines are applied to the system development process in the applicable phases and that the authorized tasks will satisfy the control gate requirements of each phase. [D04258]

 CSM
System Hierarchical Structure
A set of ranked terms defining the composition of a system. The terms and the corresponding level numbers from highest to lowest rank are:
  1. System
  2. Segment
  3. Element
  4. Subsystem
  5. Assembly
  6. Subassembly
  7. Part
For software projects, computer software components may reside at all levels below the segment level 2, and computer software units usually reside at the subassembly level 6. A configuration item can be specified at any level in the System Hierarchical Structure. [D04259]

 CSM
System Integration
The successive combining and testing of hardware and software system components in a prescribed manner to prove compatibility and performance. [D04260]

 CSM
System Integration and Testing
The successive combining and testing of hardware and software system components in a prescribed manner to prove compatibility and performance. The activity of the right leg of the Vee model. [D04261]

 CSM
System Integration Plan
A document that describes the intended approach to system integration from the hardware assembly level or software unit level up to the system level. [D04262]

 CSM
System Library
A library containing all the configuration items in the project. [D03957]

 PNG
System O&M Project
A project to deliver the operations and maintenance of an existing system. [D04263]

 CSM
System Performance Report
The summary and rating of system performance by operations personnel as compared to the Operations and Maintenance Document requirements. [D04264]

 CSM
System Requirement
A condition or capability that must be met or possessed by a system or system component to satisfy a condition or capability needed by a user to solve a problem. [D05215]

 SA-CMM
System Requirements Document
The document that states what the system must do to satisfy all or a part of the user's requirements. System requirements must be traceable to user requirements. This document is the basis for developing the System Concept and the associated System Specification. [D04265]

 CSM
System Requirements Review ("SRR")
The buyer control gate at which the system requirements document is reviewed and approved determines which needs of the total user requirements statement will be satisfied by the proposed project. The SRR is the decision point to allow the project to proceed with the in-depth analyses and tradeoffs necessary to select a preferred system concept with associated budget and schedule estimates. [D01974]

 VPM 291-4
System Specification
Defines the system baseline in terms of system description, functional requirements, quantitative technical parameters, design constraints and the criteria for acceptance. It must be formulated in terms that are quantifiable and verifiable. [D04266]

 CSM
System Test Plan
A document that describes the approach to all system development, integration, qualification, and acceptance testing. Usually part of the System Engineering Management Plan [D04267]

 CSM
System User
The individual or group responsible for delivery, operations, and maintenance of the system. [D04268]

 CSM
System Validation
The process of developing evidence in accordance with the user validation plan and system validation procedures to prove that the system meets user's needs. [D04269]

 CSM
System Validation Procedures
Step by step instructions that implement the inspection, demonstration, testing, and analysis required by the System Validation Plan. They include equipment to be used, calibration requirements, facility requirements, etc. [D04270]

 CSM
System Verification
Proof of compliance with system specifications. Verification may be determined by test, analysis, inspection, or demonstration. [D04271]

 CSM
System Verification Procedures
Step by step instructions that implement the inspection, demonstration, testing, and analysis required by the verification plan. They include equipment to be used, calibration requirements, facility requirements, etc. [D04272]

 CSM
Systems Administration
The organizational department responsible for selection, implementation, maintenance and upgrading of systems in support of the organization's main activities. [D03321]

 RMW
Systems Analysis
The study of the management systems required to be put in place to accomplish the project. Before establishing any system, especially those to be computerized, it is essential to establish who needs and who wants the information output, why, when and at what level. Only then can the best system for the purpose be established. More often than not on a project, systems "happen" ad-hoc because of some urgent need and without the knowledge or participation of others who may be affected. Systems analysis often provides the opportunity both to improve performance on the project and to eliminate wasted or marginal effort. See also Contribution Analysis. [D03093]

 CCCP
Systems Analyst
The computer person responsible for analyzing users' needs and defining the functional requirements of the computer and procedural solutions to meet those needs. [D01975]

 SPM 304-9
Systems and Procedures
The standard methods, practices and procedures for handling frequently occurring events within the project. [D01976]

 WST
A document or manual detailing the standard methods, practices and procedures for handling frequently occurring events within the project. These will cover management approvals, controls and technical requirements, etc. Systems will also cover methods of handling information transfer and storage. Such systems are sometimes called methodologies. Every project should have a set of systems and procedures. [D03958]

 PNG
Systems Approach
A wide-ranging method for addressing problems that considers multiple and interacting relationships. This approach is often contrasted with the analytic approach. project management is a systems approach to managing projects. [D01977]

 OTOB 271-4
Systems Architect
Job category of computer software personnel responsible for the high level systems design; the allocation of basic functions across applications and systems software and hardware. [D01978]

 SPM 304-9
Systems Documentation
Documentation in support of the organization's systems. [D03322]

 RMW
Systems Management
Management that includes the prime activities of systems analysis, systems design and engineering and systems development.
Editor's Note: "Development" in this context means the implementation of the design and engineering. [D01979]

 WST
The elaboration of the specification for the technical, organizational, cost, time and other parameters of a system and the subsequent management of the planning, design/engineering, procurement, implementation and testing areas of the work needed to realize the system concept. Systems management comprises the prime activities of systems analysis, systems design and engineering and systems development.
Editor's Note: "Development" in this context means the implementation of the design and engineering. [D03959]

 PNG
Systems Programmer
Programmer whose primary responsibility is to write or modify operating systems, usually to customize them to the particular hardware used and software running at an installation for the application programmers' use. [D01980]

 SPM 304-9
Systems Scope Description
A description of the entire set of systems required to satisfy the approved, affordable stakeholder requirements as agreed with the stakeholders and justified at the conclusion of the projectÍs concept Phase 1. This description includes the scope and technical performance of each system. [D01981]

 PMGdLns
Definitions for page S09: 58


***  prev
next  ***

Home | Issacons | PM Glossary | Papers & Books | Max's Musings
Guest Articles | Contact Info | Top of Page