1、| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | BRITISH STANDARD BS 6079-2:2000 Incorporating Corr
2、igendum No. 1 ICS 01.040.03; 03.100.50 NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW Project management Part 2: VocabularyThis British Standard, having been prepared under the direction of the Management Systems Sector Committee, was published under the authority of the Stan
3、dards Committee and comes into effect on 15 March 2000 BSI 08-2000 BS 4335 first published August 1968 Second edition May 1972 Third edition April 1987 Published as BS 6079-2 March 2000 The following BSI references relate to the work on this standard: Committee reference MS/2 Draft for comment 99/40
4、2648 DC ISBN 0 580 33148 2 BS 6079-2:2000 Amendments issued since publication Amd. No. Date Comments 11015 Corrigendum No. 1 August 2000 Change of font in column 1, rows 5 and 6, of Table 2 Correction to 2.115 Committees responsible for this British Standard This British Standard was prepared by Tec
5、hnical Committee MS/2, Project management, upon which the following bodies were represented: Association of Project Managers BEAMA Ltd British Computer Society British Standards Society British Telecommunications plc Chartered Institute of Management Accountants Federation of the Electronics Industr
6、y Fellowship for Operational Research GAMBICA (BEAMA Ltd) Health and Safety Executive Highways Agency Institute of Quality Assurance Institution of Civil Engineers Institution of Incorporated Executive Engineers Institution of Mechanical Engineers Ministry of Defence Operational Research Society Roy
7、al Institution of Chartered Surveyors Society of British Aerospace Companies Ltd South Bank UniversityBS 6079-2:2000 BSI 08-2000 i Contents Page Committees responsible Inside front cover Foreword ii Introduction 1 1 Scope 1 2 Project management terminology 1 Annex A (informative) Recommended symbols
8、 used in network diagrams 14 Annex B (informative) Line of balance terminology 18 Annex C (informative) List of acronyms commonly used in project management (PM) 18 Bibliography 21 Figure 1 Hierarchy of project terms 1 Figure 2 Project management life cycle 9 Figure A.1 Finish to start 14 Figure A.2
9、 Start to start 14 Figure A.3 Finish to finish 15 Figure A.4 Start to finish 15 Figure A.5 AND 16 Figure A.6 Inclusive OR 16 Figure A.7 Exclusive OR 16 Figure A.8 AND 17 Figure A.9 Inclusive OR 17 Figure A.10 Exclusive OR 17 Table 1 Project phases 8 Table 2 Typical project phases 8ii BSI 08-2000 BS
10、6079-2:2000 Foreword The preparation of this British Standard was entrusted to Technical Committee MS/2, Project management. It is a revision of BS 4335:1987, which is withdrawn. The purpose of this British Standard is to standardize the terminology and symbols used in project management to facilita
11、te communication and the spread of knowledge of the subject. The changes made are in support of the other parts of BS 6079 which have extended the requirements for standardized terminology from the basic use in project network techniques to project management and its specialized use of other managem
12、ent techniques. Wherever possible the definitions given in BS 4335:1987 have been retained, although some have been deleted because they are no longer in use and others have been revised to reflect current usage or to improve clarity. No term has been included where its sense and usage in project ma
13、nagement are adequately defined in The Shorter Oxford English Dictionary. BS 6079 is now issued in three parts: BS 6079-1:2000, Project management Guide to project management; BS 6079-2:2000, Project management Vocabulary; BS 6079-3:2000, Project management Guide to the management of business relate
14、d project risk. Because the vocabulary now covers a much wider field it has been decided for ease of use to present the terms in alphabetic order (rather than grouped in separate specialist sections, as was the case in the 1987 edition). The three annexes to this standard contain graphical illustrat
15、ions, line of balance terminology and a list of commonly used acronyms respectively. The presentation of graphical illustrations in annex A is virtually the same as that in the 1987 edition. A British Standard does not purport to include all the necessary provisions of a contract. Users of British S
16、tandards are responsible for their correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations. Summary of pages This document comprises a front cover, an inside front cover, pages i and ii, pages 1 to 21 and a back cover. The BSI copyright notic
17、e displayed in this document indicates when the document was last issued. BSI 08-2000 1 BS 6079-2:2000 Introduction The vocabulary has been arranged alphabetically in the main body of this standard. Where applicable informative reference has been made to other publications that give further guidance
18、 on the project management and associated general management techniques defined herein. The annexes contain information on network symbols, Line of Balance terminology and a consolidated list of acronyms. 1 Scope This standard defines the terms used in project management and network planning. It has
19、 a broad relevance to projects in many industries, commerce and the public sector and was prepared in support of the other parts of BS 6079. 2 Project management terminology 2.1 abstract resource imaginary resource (2.139) introduced so that its availability and activity (2.5) requirement gives an e
20、xtra means of control NOTE For example, two jobs not being worked upon simultaneously in order to obviate an accident hazard. 2.2 acceptance criteria performance requirements and essential conditions that have to be achieved before project (2.116) deliverables (2.46) are accepted 2.3 acceptance test
21、 formal, predefined test conducted to determine the conformity of the deliverable (2.46) with the acceptance criteria (2.2) 2.4 accrued costs costs that are earmarked for the project (2.116) and for which payment is due, but has not been made 2.5 activity job operation or process (2.113) consuming t
22、ime and possibly other resources (2.139) NOTE The position of activity (2.5) within the hierarchy of project (2.116) terms is shown in Figure 1. Project 2.116 Projectlifecycle 2.122 (Projectprocess) Phase 2.107 (Stage) Task 2.170 (Workpackage) Activity 2.5 (Job) Figure 1 Hierarchy of project terms 2
23、.6 activity-on-arrow network arrow diagram network in which the arrows (2.11) symbolize the activities (2.5) 2.7 activity-on-node network precedence diagram network in which the nodes (2.99) symbolize the activities (2.5) 2.8 actual cost of work performed cumulative cost of work accrued on the proje
24、ct (2.116) in a specific period or up to a specific stage (2.165) NOTE For some purposes cost may be measured in labour hours rather than money. 2.9 actual costs incurred costs (2.78) that are charged to the project (2.116) budget (2.20) and for which payment has been made, or accrued2 BSI 08-2000 B
25、S 6079-2:2000 2.10 AND relationship logical relationship between two or more activities (2.5) that converge on or diverge from an event (2.61) NOTE The AND relationship (2.10) indicates that every one of the activities (2.5) has to be undertaken. 2.11 arrow directed connecting line between two nodes
26、 (2.99) in a network NOTE 1 It symbolizes an activity (2.5)i na n activity-on-arrow network (2.6). NOTE 2 It symbolizes a dependency (2.47) relationship in an activity-on-node network (2.7). 2.12 arrow diagram see activity-on-arrow network (2.6) 2.13 associated revenue that part of a project (2.116)
27、 cost that is of a revenue nature and therefore charged as incurred to the profit and loss account NOTE Associated revenue (2.13) differs from the capital element of the project (2.116) in that the capital element is taken as an asset to the balance sheet and depreciated over future accounting perio
28、ds. 2.14 audit systematic retrospective examination of the whole, or part, of a project (2.116) or function to measure conformance with predetermined standards NOTE Audit (2.14) is usually qualified, for example financial audit, quality audit, design audit, project audit, health and safety audit. 2.
29、15 automatic decision event decision event (2.44) where the decision depends only on the outcome of the preceding activities (2.5) and which can be programmed or made automatic 2.16 backward pass procedure whereby the latest event (2.61) times or the latest finish and start times for the activities
30、(2.5) of a network are calculated 2.17 bar chart chart on which activities (2.5) and their durations are represented by lines drawn to a common time scale NOTE 1 A Gantt chart (2.72) is a specific type of bar chart (2.17) and should not be used as a synonym for bar chart (2.17). NOTE 2 See also casc
31、ade chart (2.25). 2.18 baseline reference levels against which the project (2.116)i s monitored and controlled 2.19 branching logic conditional logic alternative paths (2.105)i naprobabilistic network (2.112) 2.20 budget quantification of resources needed to achieve a task (2.170) by a set time, wit
32、hin which the task (2.170) owners are required to work NOTE A budget (2.20) consists of a financial and/or quantitative statement, prepared and approved prior to a defined period, for the purpose of attaining a given objective for that period. 2.21 budgetary control system of creating budgets (2.20)
33、, monitoring progress and taking appropriate action to achieve budgeted performance NOTE A budget (2.20) should provide the information necessary to enable approval, authorization and policy making bodies to assess a project proposal and reach a rational decision. 2.22 business case information nece
34、ssary to enable approval, authorization and policy making bodies to assess a project (2.116) proposal and reach a reasoned decision 2.23 capital cost the carrying cost in a balance sheet of acquiring an asset and bringing it to the condition where it is capable of performing its intended function ov
35、er a future series of periods NOTE See also revenue cost (2.148). 2.24 capital employed amount of investment in an organization or project (2.116), normally the sum of fixed and current assets, less current liabilities at a particular date 2.25 cascade chart bar chart (2.17) on which the vertical or
36、der of activities (2.5) is such that each activity (2.5)i s dependent only on activities (2.5) higher in the list 2.26 cash flow cash receipts and payments in a specified period NOTE See also net cash flow (2.95). BSI 08-2000 3 BS 6079-2:2000 2.27 change control process (2.113) that ensures potentia
37、l changes to the deliverables (2.46)o faproject (2.116) or the sequence of work in a project (2.116), are recorded, evaluated, authorized and managed 2.28 child activity subordinate task (2.170) belonging to a parent activity (2.104) existing at a higher level in the work breakdown structure (2.179)
38、 2.29 commissioning advancement of an installation from the stage (2.165) of static completion to full working order and achievement of the specified operational requirements 2.30 committed costs costs that are legally committed even if delivery has not taken place, with invoices neither raised nor
39、paid 2.31 configuration functional and physical characteristics of a product as defined in technical documents and achieved in the product NOTE In a project (2.116) this should contain all items that can be identified as being relevant to the project (2.116) and that should only be modified after au
40、thorization by the relevant manager. 2.32 configuration management technical and administrative activities (2.5) concerned with the creation, maintenance and controlled change of configuration (2.31) throughout the life of the product NOTE See BS EN ISO 10007:1997 for guidance on configuration manag
41、ement (2.32), including specialist terminology. 2.33 contingency plan mitigation plan alternative course(s) of action devised to cope with project (2.116) risks (2.149) 2.34 cost breakdown structure hierarchical breakdown of a project (2.116) into cost elements 2.35 cost centre location, person, act
42、ivity (2.5)o rproject (2.116) in respect of which costs may be ascertained and related to cost units 2.36 cost code unique identity for a specified element of work 2.37 cost performance index a measure, expressed as a percentage or other ratio, of actual cost to budget (2.20)/plan 2.38 cost variance
43、 the difference (positive or negative) between the actual expenditure and the planned/budgeted expenditure 2.39 cost-benefit analysis analysis of the relationship between the costs of undertaking a task (2.170)o rproject (2.116), initial and recurrent, and the benefits likely to arise from the chang
44、ed situation, initially and recurrently NOTE The hard tangible readily measurable benefits may sometimes be accompanied by soft benefits which may be real but difficult to isolate, measure and value. 2.40 credited resource resource (2.139) that is created by an activity (2.5)o revent (2.61) and can
45、then be used by the project (2.116) 2.41 critical path sequence of activities (2.5) through a project network (2.129) from start to finish, the sum of whose durations determines the overall project (2.116) duration NOTE There may be more than one such path (2.105). 2.42 critical path analysis proced
46、ure for calculating the critical path (2.41) and floats (2.68) in a network 2.43 cycle path (2.105) that emanates from a decision event (2.44) and intentionally leads back to itself or to a prior event (2.61) NOTE The path (2.105) may be traversed more than once. 2.44 decision event state in the pro
47、gress of a project (2.116) when a decision is required before the start of any succeeding activity (2.5) NOTE The decision determines which of a number of alternative paths (2.105) is to be followed.4 BSI 08-2000 BS 6079-2:2000 2.45 deliberate decision event decision event (2.44) where the decision
48、is made as a result of the outcomes of the preceding activities (2.5) and possibly other information but which cannot be made automatically 2.46 deliverable end-product of a project (2.116) or the measurable results of intermediate activities (2.5) within the project organization (2.131) NOTE Delive
49、rables (2.46) may be in the form of hardware, software, services, processes (2.113), documents or any combination of these. 2.47 dependency precedence relationship restriction that one activity (2.5) has to precede, either in part or in total, another activity (2.5) 2.48 dependency arrow link arrow (2.11) used in an activity-on-node network (2.7) to represent the interrelationships of activities (2.5)i naproject (2.116) 2.49 deterministic network network containing paths (2.105), all of which have to be followed and whose du
