Metrics Glossary

Software Metrics Glossary - P : Part 2


Project The structure of authorities, resources and controls established by an enterprise in order to acquire or supply a specified product or service. ( Reference : SC7/WG7:15288)
project A temporary endeavor undertaken to create a unique product or service (PMI, Guide to Project Management Body of Knowledge) ( Reference : IEEE SESC:729)
project An undertaking that is focused on acquiring a specific product. The product may include hardware, software, and services. Typically, a project has its own funding, cost accounting, and delivery schedule. ( Reference : SEI:SA-CMM)
project The aggregate of effort and other resources focused on developing and/or maintaining a specific product. The product may include hardware, software, and other components. Typically a project has its own funding, cost accounting, and delivery schedule. [CMM for Software] ( Reference : SEI:SE-CMM)
Project A temporary endeavor undertaken to create a unique product or service. ( Reference : PMI:PMBOK)
Project Charter A document issued by senior management that provides the project manager with the authority to apply organizational resources to project activities. ( Reference : PMI:PMBOK)
Project Communications Management A subset of project management that includes the processes required to ensure proper collection and dissemination of project information. It consists of communications planning, information distribution, performance reporting, and administrative closure. ( Reference : PMI:PMBOK)
project control The activities concerned with monitoring the progress of a project, its direction, quality, and resource utilization, as compared with project plans. ( Reference : ISO/IEC JTC1/SC1:2382-20)
Project Cost Management A subset of project management that includes the processes required to ensure that the project is completed within the approved budget. It consists of resource planning, cost estimating, cost budgeting, and cost control. ( Reference : PMI:PMBOK)
Project Delivery Rate Measures the rate at which a project delivers software functionality to the end user as a factor of the effort, which was required to do so. It is defined as the Functional Size of the delivered software (measured in function points), over Project Work Effort, (measured in hours). It is expressed as hours per function point ( Reference : ISBSG-Release 6 1999)
Project Elapsed Time The calender period in months between the project start and end including any period of inactivity (i.e. end date minus start date). ( Reference : ISBSG-Release 6 1999)
Project End The date when the work product is delivered (i.e. the project software is placed in production, or the project deliverable is delivered). ( Reference : ISBSG-Release 6 1999)
Project Human Resource Management A subset of project management that includes the processes required to make the most effective use of the people involved with the project. It consists of organizational planning, staff acquisition, and team development. ( Reference : PMI:PMBOK)
Project Inactive Time Total time (rounded to whole months) during the project elapsed time, in which no project activity took place. ( Reference : ISBSG-Release 6 1999)
Project Integration Management A subset of project management that includes the processes required to ensure that the various elements of the project are properly coordinated. It consists of project plan development, project plan execution, and overall change control. ( Reference : PMI:PMBOK)
Project leader A person who manages or leads projects. May be a synonym for Project Manager. ( Reference : IFPUG CPM 4.1)
Project level The management level responsible for managing individual new development or major enhancement projects. ( Reference : IFPUG CPM 4.1)
Project Life Cycle A collection of generally sequential project phases whose name and number are determined by the control needs of the organization or organizations involved in the project. ( Reference : PMI:PMBOK)
project management The activities concerned with project planning and project control. ( Reference : ISO/IEC JTC1/SC1:2382-20)
Project Management (PM) The application of knowledge, skills, tools, and techniques to project activities in order to meet or exceed stakeholder needs and expectations from a project. ( Reference : PMI:PMBOK)
Project Management Body of Knowledge (PMBOK) An inclusive term that describes the sum of knowledge within the profession of project management. As with other professions such as law, medicine, and accounting, the body of knowledge rests with the practitioners and academics who apply and advance it. The PMBOK includes proven, traditional practices which are widely applied as well as innovative and advanced ones which have seen more limited use. ( Reference : PMI:PMBOK)
Project Management Professional (PMP) An individual certified as such by the Project Management Institute. ( Reference : PMI:PMBOK)
Project Management Software A class of computer applications specifically designed to aid with planning and controlling project costs and schedules. ( Reference : PMI:PMBOK)
Project Management Team The members of the project team who are directly involved in project management activities. On some smaller projects, the project management team may include virtually all of the project team members. ( Reference : PMI:PMBOK)
Project manager A person who manages one or more projects or groups of projects. ( Reference : IFPUG CPM 4.1)
project manager The role with total business responsibility for an entire project; the individual who directs, controls, administers, and regulates a project acquiring software, a hardware/software system, or services. The project manager is the individual ultimately responsible to the end user. ( Reference : SEI:SA-CMM)
Project Manager (PM) The individual responsible for managing a project. ( Reference : PMI:PMBOK)
Project Network Diagram Any schematic display of the logical relationships of project activities. Always drawn from left to right to reflect project chronology. Often incorrectly referred to as a "PERT chart." ( Reference : PMI:PMBOK)
project office The aggregate of individuals assigned the primary responsibility for software acquisition in the contracted effort. A project office may vary in size from a single individual assigned part time to a large organization assigned full time. ( Reference : SEI:SA-CMM)
Project Phase A collection of logically related project activities, usually culminating in the completion of a major deliverable. ( Reference : PMI:PMBOK)
project plan A document that describes the technical and management approach to be followed for a project. The plan typically describes the work to be done, the resources required, the methods to be used, the procedures to be followed, the schedules to be met, and the way that the project will be organized (for example, a software development plan). [IEEE STD 610.12-1990] ( Reference : SEI:SE-CMM)
Project Plan A formal, approved document used to guide both project execution and project control. The primary uses of the project plan are to document planning assumptions and decisions, to facilitate communication among stakeholders, and to document approved scope, cost, and schedule baselines. A project plan may be summary or detailed. ( Reference : PMI:PMBOK)
Project Plan Development Taking the results of other planning processes and putting them into a consistent, coherent document. ( Reference : PMI:PMBOK)
Project Plan Execution Carrying out the project plan by performing the activities included therein. ( Reference : PMI:PMBOK)
project planning The activities concerned with the specification of the com-ponents, timing, resources, and procedures of a project. ( Reference : ISO/IEC JTC1/SC1:2382-20)
Project Planning The development and maintenance of the project plan. ( Reference : PMI:PMBOK)
Project Procurement Management A subset of project management that includes the processes required to acquire goods and services from outside the performing organization. It consists of procurement planning, solicitation planning, solicitation, source selection, contract administration, and contract close-out. ( Reference : PMI:PMBOK)
Project Quality Management A subset of project management that includes the processes required to ensure that the project will satisfy the needs for which it was undertaken. It consists of quality planning, quality assurance, and quality control. ( Reference : PMI:PMBOK)
Project Register A repository of information about projects that are within the scope of the organisations software portfolio. Repository information is used to assist with the scheduling of function point counting activity. Summary function point count results and project attributes are recorded within the register. ( Reference : Total Metrics)
Project Risk Management A subset of project management that includes the processes concerned with identifying, analyzing, and responding to project risk. It consists of risk identification, risk quantification, risk response development, and risk response control. ( Reference : PMI:PMBOK)
Project Schedule The planned dates for performing activities and the planned dates for meeting milestones. ( Reference : PMI:PMBOK)
Project Scope Management A subset of project management that includes the processes required to ensure that the project includes all of the work required, and only the work required, to complete the project successfully. It consists of initiation, scope planning, scope definition, scope verification, and scope change control. ( Reference : PMI:PMBOK)
project software manager The role with total responsibility for all the software activities for a project. The project software manager is the individual the project manager deals with in terms of software commitments and who controls all the software resources for a project. ( Reference : SEI:SW-CMM)
project specification A Specification of the objectives, requirements, and scope of a project and its relations to other projects. ( Reference : ISO/IEC JTC1/SC1:2382-20)
Project Start A client/management decision is made formally/informally to involve Information Technology personnel in the development.This point is commonly known as the commencement of the 'Survey', 'Feasibility Study' or 'Project Initiation Phase' of the system development life cycle. ( Reference : ISBSG-Release 6 1999)
project team All individuals that have an assigned software acquisition responsibility in the contracted effort. A project team may vary in size from a single individual assigned part time to a large organization assigned full time. ( Reference : SEI:SA-CMM)
Project Team Members The people who report either directly or indirectly to the project manager. ( Reference : PMI:PMBOK)
Project Time Management A subset of project management that includes the processes required to ensure timely completion of the project. It consists of activity definition, activity sequencing, activity duration estimating, schedule development, and schedule control. ( Reference : PMI:PMBOK)
Project Work Effort All personnel effort that is directed towards the completion of a particular project including out-of-hours effort, whether paid or unpaid. It includes the effort of Client representatives in addition to that of Information Technology personnel. A good test as to whether an activity constitutes PROJECT WORK EFFORT is to ask the question"Would the activity be undertaken if there was no project?" It excludes NON-PROJECT ACTIVITIES, these being:Public Holidays,,Annual Leave, Sick Leave,Training (Non-Project).It is measured in whole HOURS. ( Reference : ISBSG-Release 6 1999)
Project/application attribute. Characteristics of a project or an application that may have a significant impact on productivity. Examples include hardware platform, personnel experience, tools, and methodology. The project/application attribute is used to categorize project data during analysis. ( Reference : IFPUG CPM 4.1)
Projectized Organization Any organizational structure in which the project manager has full authority to assign priorities and to direct the work of individuals assigned to the project. ( Reference : PMI:PMBOK)
project's defined process The operational definition of the process as used by a specific project. Well characterized and understood, it is described in terms of standards, procedures, tools, and methods. It is developed by tailoring the organization's standard process to fit the specific characteristics of the project. [Jones - IBM] ( Reference : SEI:SE-CMM)
project's defined software acquisition process The project's tailored version of the acquisition organization's standard software acquisition process. ( Reference : SEI:SA-CMM)
Promotion for SCI: the transition of state; for a baseline: the passage through the software life cycle. ( Reference : SC7/WG8:15846)
Proof final copy of a paper document presented to the acquirer for review prior to publication NOTE Unless alterations are requested, the finished document should be identical to the proof copy in all respects other than paper stock, binding and colours. Proofs are generally photocopies of the camera-ready originals. ( Reference : ISO/IEC JTC1/SC7:15910)
proposed capability the process capability that the organization proposes to bring to bear in meeting the specified requirement ( Reference : ISO/IEC JTC1/SC7:15504-9)
proposed change A report of anomaly, required or recommended enhancement from the time the idea is recorded until the disposition by the designated change authority. ( Reference : SC7/WG8:15846)
prototype A model or preliminary implementation suitable for evaluation of system design, performance, and production potential; or for better understanding Or determination of the requirements. ( Reference : ISO/IEC JTC1/SC1:2382-20)
Prototype A prototype is a preliminary type, form, or instance of a system that serves as a model for later stages or for the final, complete version of the system. A prototype is a usable product. ( Reference : SC7:14759)
Prototype Refers to any artefact created for the purpose of demonstration to users in order to elicit or test user feedback. This includes inter alia demonstrators, mock-ups, paper prototypes, simulations, role-plays, dummy systems or documents, scenarios etc. (extension of ISO 13407) ( Reference : ISO/TC159/SC4/WG 6:HCLP-PAS)
Prototype model or preliminary implementation of a piece of software suitable for the evaluation of system design, performance or production potential, or for the better understanding of the software requirements ( Reference : ISO/IEC JTC1/SC7:15910)
prototyping A hardware and software development technique in which a preliminary version of part or all of the hardware or software is developed to permit user feedback, determine feasibility, or investigate timing or other issues in support of the development process. [IEEE STD 610.12-1990] ( Reference : SEI:SE-CMM)
provisional assessor a person who has the skills and competencies to carry out assessments under the guidance and supervision of a competent assessor ( Reference : ISO/IEC JTC1/SC7:15504-9)
PSA Projected Service Availability (Reference ITIL® Sept 2002)
Purpose of the Count The purpose of a function point count is to provide an answer to a business problem. ( Reference : IFPUG CPM 4.1)