|
Research
Failure Cases
Glossary
Reading
Room
|
Glossary
- Successful
project
The project is completed on time and on budget, with all features and
functions as specified. [Johnson 2001 - Standish Report].
- Challenged
project
The project is completed and operational, but over budget, late, and
with fewer features and functions that initially specified. [Johnson
2001 - Standish Report].
- Failed
project
The project is cancelled before completion, never implemented, or scrapped
following installation. [Based on: Johnson 2001 - Standish Report].
- Terminal
failure of a product
A failure that renders a system permanently unusable.
- Runaway
Project
A term coined by the consultancy KPMG to identify mainly IT projects
which resist termination. Typified by a constantly changing specification
and absorption of much extra resource and cost in a desperate effort
to get the project finished. https://www.pmforum.org/library/glossary/PMG_R05.htm#Runaway%20Project
- Failure
The inability of a system to perform its required functions within specified
performance requirements. (IEEE 610.12-1990).
- Hazard
A potentially unsafe condition. (EUROCONTROL: Air Navigation System
Safety Assessment Methodology. SAF.ET1.ST03.1000-MAN-01-00)
- Risk
The combination of the probability, or frequency of occurrence of defined
hazard and the magnitude of the consequences of the occurrence. (EUROCONTROL:
Air Navigation System Safety Assessment Methodology. SAF.ET1.ST03.1000-MAN-01-00)
- Safety
Freedom from unacceptable risk. (EUROCONTROL: Air Navigation System
Safety Assessment Methodology. SAF.ET1.ST03.1000-MAN-01-00)
PMBOK
- Activity
An element of work performed during the course of a project. An activity
normally has an expected duration, an expected cost, and expected resource
requirements. Activities can be subdivided into tasks.
- Constraints
Applicable restrictions that will affect the performance of the project.
Any factor that affects when activity can be scheduled.
- Duration
(DU)
The number of work periods (not including holidays or other non-working
periods) required to complete an activity or other project element.
Usually expressed as workdays or workweeks. Sometimes incorrectly equated
with elapsed time.
- Component
A unit of composition with contractually specified interfaces and explicit
context dependencies only. Context dependencies are specified by stating
the required interfaces and the acceptable execution platforms. A software
component can be deployed independently and is subject to composition
by third parties. (Allen, Szyperski)
- Component-based
development (CBD)
The creation, integration, and re-use of components of program code,
each of which has a common interface for use by multiple systems. [The
Free Online Dictionary of Computing: https://foldoc.doc.ic.ac.uk/
]
- Domain
An area of knowledge or activity characterised by a family of related
systems. (RUP)
- Neighbourhood
A well-defined set of interrelated business processes, business types,
applications, time scales, and boundary notes. (OOSPICE)
- Activity
Any step taken or function performed, both mental and physical, towards
achieving some objective. (Zahran)
- Practice
a software engineering or management activity that contributes to the
creation of the output (work products) of a process or enhances the
capability of a process. (15504)
- Process
A set of interrelated activities, which transform inputs into outputs.
(12207)
- Process
Outcome
An achievable result of the successful achievement of the process purpose.
(12207)
- Process
Purpose
The high level objective of performing the process and the likely outcomes
of effective implementation of the process. (12207)
- Work
Product
An artifact associated with the execution of a practice (e.g. a test
case, a requirement specification, code, or work breakdown structure).
The existence of the work product indicates that the practice is performed.
(Zahran)
|
