《BS-6079-2-2000.pdf》由会员分享,可在线阅读,更多相关《BS-6079-2-2000.pdf(26页珍藏版)》请在三一文库上搜索。
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: Vocabulary Licensed Copy: sheffieldun sheffieldun, na, Tue Dec 05 01:17:17 GMT+00:00 2006, Uncontrolled Copy, (c) BSI This British Standard, having been prepared u
3、nder the direction of the Management Systems Sector Committee, was published under the authority of the Standards 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 fo
4、llowing BSI references relate to the work on this standard: Committee reference MS/2 Draft for comment 99/402648 DC ISBN 0 580 33148 2 BS 6079-2:2000 Amendments issued since publication Amd. No.DateComments 11015 Corrigendum No. 1 August 2000Change of font in column 1, rows 5 and 6, of Table 2 Corre
5、ction to 2.115 Committees responsible for this British Standard This British Standard was prepared by Technical 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 T
6、elecommunications plc Chartered Institute of Management Accountants Federation of the Electronics Industry Fellowship for Operational Research GAMBICA (BEAMA Ltd) Health and Safety Executive Highways Agency Institute of Quality Assurance Institution of Civil Engineers Institution of Incorporated Exe
7、cutive Engineers Institution of Mechanical Engineers Ministry of Defence Operational Research Society Royal Institution of Chartered Surveyors Society of British Aerospace Companies Ltd South Bank University Licensed Copy: sheffieldun sheffieldun, na, Tue Dec 05 01:17:17 GMT+00:00 2006, Uncontrolled
8、 Copy, (c) BSI BS 6079-2:2000 BSI 08-2000i Contents Page Committees responsibleInside front cover Forewordii Introduction1 1Scope1 2Project management terminology1 Annex A (informative) Recommended symbols used in network diagrams14 Annex B (informative) Line of balance terminology18 Annex C (inform
9、ative) List of acronyms commonly used in project management (PM)18 Bibliography21 Figure 1 Hierarchy of project terms1 Figure 2 Project management life cycle9 Figure A.1 Finish to start14 Figure A.2 Start to start14 Figure A.3 Finish to finish15 Figure A.4 Start to finish15 Figure A.5 AND16 Figure A
10、.6 Inclusive OR16 Figure A.7 Exclusive OR16 Figure A.8 AND17 Figure A.9 Inclusive OR17 Figure A.10 Exclusive OR17 Table 1 Project phases8 Table 2 Typical project phases8 Licensed Copy: sheffieldun sheffieldun, na, Tue Dec 05 01:17:17 GMT+00:00 2006, Uncontrolled Copy, (c) BSI ii BSI 08-2000 BS 6079-
11、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 facilitate co
12、mmunication 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 management t
13、echniques. 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 managem
14、ent 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 related pro
15、ject 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 illustrations,
16、 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 Standa
17、rds 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 notice dis
18、played in this document indicates when the document was last issued. Licensed Copy: sheffieldun sheffieldun, na, Tue Dec 05 01:17:17 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BSI 08-20001 BS 6079-2:2000 Introduction The vocabulary has been arranged alphabetically in the main body of this standard.
19、Where applicable informative reference has been made to other publications that give further guidance 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 acro
20、nyms. 1 Scope This standard defines the terms used in project management and network planning. It has 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 ima
21、ginary resource (2.139) introduced so that its availability and activity (2.5) requirement gives an extra means of control NOTEFor example, two jobs not being worked upon simultaneously in order to obviate an accident hazard. 2.2 acceptance criteria performance requirements and essential conditions
22、that have to be achieved before project (2.116) deliverables (2.46) are accepted 2.3 acceptance test 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 w
23、hich payment is due, but has not been made 2.5 activity job operation or process (2.113) consuming time and possibly other resources (2.139) NOTEThe position of activity (2.5) within the hierarchy of project (2.116) terms is shown in Figure 1. Project 2.116 Project life cycle 2.122 (Project process)
24、 Phase 2.107 (Stage) Task 2.170 (Work package) Activity 2.5 (Job) Figure 1 Hierarchy of project terms 2.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) symbol
25、ize the activities (2.5) 2.8 actual cost of work performed cumulative cost of work accrued on the project (2.116) in a specific period or up to a specific stage (2.165) NOTEFor some purposes cost may be measured in labour hours rather than money. 2.9 actual costs incurred costs (2.78) that are charg
26、ed to the project (2.116) budget (2.20) and for which payment has been made, or accrued Licensed Copy: sheffieldun sheffieldun, na, Tue Dec 05 01:17:17 GMT+00:00 2006, Uncontrolled Copy, (c) BSI 2 BSI 08-2000 BS 6079-2:2000 2.10 AND relationship logical relationship between two or more activities (2
27、.5) that converge on or diverge from an event (2.61) NOTEThe 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 (2.99) in a network NOTE 1It symbolizes an activity (2.5) in an activity-on-arrow network
28、(2.6). NOTE 2It 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) cost that is of a revenue nature and therefore charged as incurred to the profit and loss a
29、ccount NOTEAssociated 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 periods. 2.14 audit systematic retrospective examination of the whole, or part, of a project (2.11
30、6) or function to measure conformance with predetermined standards NOTEAudit (2.14) is usually qualified, for example financial audit, quality audit, design audit, project audit, health and safety audit. 2.15 automatic decision event decision event (2.44) where the decision depends only on the outco
31、me 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 (2.5) of a network are calculated 2.17 bar chart chart on which activities (2.5) and their dur
32、ations are represented by lines drawn to a common time scale NOTE 1A 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 2See also cascade chart (2.25). 2.18 baseline reference levels against which the project (2.116) is monitored
33、and controlled 2.19 branching logic conditional logic alternative paths (2.105) in a probabilistic network (2.112) 2.20 budget quantification of resources needed to achieve a task (2.170) by a set time, within which the task (2.170) owners are required to work NOTE A budget (2.20) consists of a fina
34、ncial 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), monitoring progress and taking appropriate action to achieve budgeted performance NOTEA budg
35、et (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 necessary to enable approval, authorization and policy making bodies to assess a project (2.116) pr
36、oposal 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 over a future series of periods NOTESee also revenue cost (2.148). 2.24 capital employed amount o
37、f 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 order of activities (2.5) is such that each activity (2.5) is dependent only on activities (2.5) h
38、igher in the list 2.26 cash flow cash receipts and payments in a specified period NOTESee also net cash flow (2.95). Licensed Copy: sheffieldun sheffieldun, na, Tue Dec 05 01:17:17 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BSI 08-20003 BS 6079-2:2000 2.27 change control process (2.113) that ensures
39、 potential changes to the deliverables (2.46) of a project (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 struct
40、ure (2.179) 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
41、raised nor paid 2.31 configuration functional and physical characteristics of a product as defined in technical documents and achieved in the product NOTEIn 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 modifie
42、d after authorization 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 NOTESee BS EN ISO 10007:1997 for guidance on configurat
43、ion management (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, pe
44、rson, activity (2.5) or project (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 cos
45、t variance 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) or project (2.116), initial and recurrent, and the benefits likely to arise fro
46、m the changed situation, initially and recurrently NOTEThe 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) or event (2.6
47、1) and can 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 NOTEThere may be more than one such path (2.105). 2.42 critical path analy
48、sis procedure 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) NOTEThe path (2.105) may be traversed more than once. 2.44 decision event state i
49、n the progress of a project (2.116) when a decision is required before the start of any succeeding activity (2.5) NOTEThe decision determines which of a number of alternative paths (2.105) is to be followed. Licensed Copy: sheffieldun sheffieldun, na, Tue Dec 05 01:17:17 GMT+00:00 2006, Uncontrolled Copy, (c) BSI 4 BSI 08-2000 BS 6079-2:2000 2.45 deliberate decision event decision event (2.44) where the decision is made as a result of the outcomes of the preceding activities (2.5) and possibly other information but which cannot be made aut
链接地址:https://www.31doc.com/p-3774598.html