ImageVerifierCode 换一换
格式:PDF , 页数:24 ,大小:1.37MB ,
资源ID:586812      下载积分:10000 积分
快捷下载
登录下载
邮箱/手机:
温馨提示:
如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
如填写123,账号就是123,密码也是123。
特别说明:
请自助下载,系统不会自动发送文件的哦; 如果您已付费,想二次下载,请登录后访问:我的下载记录
支付方式: 支付宝扫码支付 微信扫码支付   
注意:如需开发票,请勿充值!
验证码:   换一换

加入VIP,免费下载
 

温馨提示:由于个人手机设置不同,如果发现不能下载,请复制以下地址【http://www.mydoc123.com/d-586812.html】到电脑端继续下载(重复下载不扣费)。

已注册用户请登录:
账号:
密码:
验证码:   换一换
  忘记密码?
三方登录: 微信登录  

下载须知

1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。
2: 试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。
3: 文件的所有权益归上传用户所有。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 本站仅提供交流平台,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

版权提示 | 免责声明

本文(BS ISO 27026-2011 Space systems Programme management Breakdown of project management structures《航空航天系统 程序管理 项目管理架构的故障》.pdf)为本站会员(赵齐羽)主动上传,麦多课文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文库(发送邮件至master@mydoc123.com或直接QQ联系客服),我们立即给予删除!

BS ISO 27026-2011 Space systems Programme management Breakdown of project management structures《航空航天系统 程序管理 项目管理架构的故障》.pdf

1、BSI Standards PublicationBS ISO 27026:2011Space systems Programmemanagement Breakdown ofproject management structuresIncorporating corrigendum September 2015BS ISO 27026:2011 BRITISH STANDARDNational forewordThis British Standard is the UK implementation of ISO 27026:2011. The UK participation in it

2、s preparation was entrusted by TechnicalCommittee ACE/68, Space systems and operations, to SubcommitteeA list of organizations represented on this subcommittee can be obtained on request to its secretary.This publication does not purport to include all the necessary provisions of a contract. Users a

3、re responsible for its correct application.ISBN 978 0 580 91515 4 ICS 49.140 Compliance with a British Standard cannot confer immunity from legal obligations.This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 March 2011.Amendments/corrigenda

4、issued since publicationDate T e x t a f f e c t e d30 September 2015 Implementation of ISO corrected text 1 May2011: Annexes A, B, C, D and E corrected The British Standards Institution 2015. Published by BSI StandardsLimited 2015ACE/68/-/5, Space systems and operations - Programme management. Refe

5、rence numberISO 27026:2011(E)ISO 2011INTERNATIONAL STANDARD ISO27026First edition2011-02-15Corrected version2011-05-01Space systems Programme management Breakdown of project management structures Systmes spatiaux Management de programme lments de structures de gestion de projet ISO 27026:2011(E) PDF

6、 disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, par

7、ties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative

8、 to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. COPYRIGHT

9、 PROTECTED DOCUMENT ISO 2011 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or I

10、SOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO 2011 All rights reservedBS ISO 27026:2011ISO 27026:2011(E) ISO 2011 All rights

11、reserved iiiContents Page Foreword iv Introductionvi 1 Scope1 2 Normative references1 3 Terms, definitions and abbreviated terms1 3.1 Terms and definitions .1 3.2 Abbreviated terms .2 4 Overview of project breakdown structures 2 4.1 General .2 4.2 Relationship of project breakdown structures.2 4.3 P

12、urpose of project breakdown structures3 4.4 Tailoring4 5 Processes and requirements of project breakdown structures.4 5.1 General .4 5.2 Specification tree.4 5.3 Function tree5 5.4 Product tree .5 5.5 Work breakdown structure.6 5.6 Cost breakdown structure6 5.7 Business agreement breakdown structure

13、.7 5.8 Organizational breakdown structure.7 Annex A (informative) Specification tree8 Annex B (informative) Function tree .9 Annex C (informative) Product tree.10 Annex D (informative) Work breakdown structure 11 Annex E (informative) Cost breakdown structure .12 BS ISO 27026:2011ISO 27026:2011(E) i

14、v ISO 2011 All rights reservedForeword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interes

15、ted in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical C

16、ommission (IEC) on all matters of electrotechnical standardization. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of technical committees is to prepare International Standards. Draft International Standards adopted by the tech

17、nical committees are circulated to the member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO

18、shall not be held responsible for identifying any or all such patent rights. ISO 27026 was prepared by Technical Committee ISO/TC 20, Aircraft and space vehicles, Subcommittee SC 14, Space systems and operations. This corrected version of ISO 27026:2011 incorporates the following corrections plus ot

19、her minor editorial modifications. Annex A: Figure A.1 has replaced Figure C.1. In new Figure C.1: PL component: PL.1.1.1.1 PL component: PL.1.1.1.1 has been changed to: PL component: PL.1.1.1.1 PL component: PL.1.1.1.2 and PA component: PA.1.1.1.1 PA component: PA.1.1.1.1 has been changed to PA com

20、ponent: PA.1.1.1.1 PA component: PA.1.1.1.2 In the Note, “specification” has been changed to “product”. Annex B: Figure B.1 has replaced Figure A.1. BS ISO 27026:2011ISO 27026:2011(E) ISO 2011 All rights reserved vIn the new Figure A.1, “function” has been changed to “specification”. Annex C: Figure

21、 C.1 has replaced Figure B.1. In the new Figure B.1, “PA subfunction” on the left side has been changed to “PL subfunction” and “PA sub-subfunction” has been changed to “PL sub-subfunction”. In the Note, “product” has been changed to “function”. Annex D: PL component WBS item: PL.1.1.1.1 PL componen

22、t WBS item: PL.1.1.1.1 has been changed to: PL component WBS item: PL.1.1.1.1 PL component WBS item: PL.1.1.1.2 and PA component WBS item: PA.1.1.1.1 PA component WBS item: PA.1.1.1.1 has been changed to: PA component WBS item: PA.1.1.1.1 PA component WBS item: PA.1.1.1.2 Annex E: PL component CBS i

23、tem: PL.1.1.1.1 PL component CBS item: PL.1.1.1.1 has been changed to: PL component CBS item: PL.1.1.1.1 PL component CBS item: PL.1.1.1.2 and PA component CBS item: PA.1.1.1.1 PA component CBS item: PA.1.1.1.1 has been changed to: PA component CBS item: PA.1.1.1.1 PA component CBS item: PA.1.1.1.2

24、BS ISO 27026:2011ISO 27026:2011(E) vi ISO 2011 All rights reservedIntroduction Space programmes, and the space systems developed by them, are complex, incorporate many different technologies, and can last for many years progressing through several different stages from conception to disposal or othe

25、r disposition. When a space programme advances from one stage to another, substantial changes in the breakdown of project management structures, hereinafter collectively called project breakdown structures, of the programme and the type and amount of resources required can occur; a programme is ofte

26、n composed of one or more projects. In addition, there can be attendant risks to either the success of the project or to the well-being of project equipment or to personnel. Well-regulated project breakdown structures can be an important factor in ensuring that all factors are ready for these change

27、s through controlled changes to the project breakdown structures that form a framework for the project in each of the several different stages, and assist in ensuring that the risks are well understood and accepted. Use of this International Standard as a basis for the framework of activities compri

28、sing the project, the necessary resources, controls, inputs, outputs, and results is intended to enhance communications between different organizations that participate in a project, and can assist in reducing costs and schedule of performing the project in each stage. BS ISO 27026:2011INTERNATIONAL

29、 STANDARD ISO 27026:2011(E) ISO 2011 All rights reserved 1Space systems Programme management Breakdown of project management structures 1 Scope This International Standard specifies processes, requirements and recommendations for the breakdown of project management structures, collectively called pr

30、oject breakdown structures, in terms of the various specification (i.e. requirements), functional, product, work, cost, business and organizational breakdown structures that are established and implemented to contribute to the success of a space programme, which is often composed of one or more proj

31、ects. It is intended to complement and supplement similar project breakdown structure processes, requirements and recommendations contained within ISO 14300-1, which serves as a higher tier International Standard for this International Standard and for such other space systems and operations Interna

32、tional Standards that require formal project breakdown structures. This International Standard specifies the various types of project breakdown structures and gives processes, requirements and guidance concerning the composition of these breakdown structures. This International Standard is applicabl

33、e to project breakdown structures for a project, including at the top level of a programme, i.e. level 0, as indicated in ISO 14300-1. It is intended to be used either by an independent developer as a partial basis for programme processes or as a basis for an agreement between a supplier and a custo

34、mer. This International Standard also provides descriptions of the kinds of project breakdown structures that are commonly useful in contributing to the success of a space project. Other project breakdown structures not described in this International Standard also often contribute to the success of

35、 a space project. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO 1430

36、0-1, Space systems Programme management Part 1: Structuring of a project ISO 9000, Quality management systems Fundamentals and vocabulary 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions For the purposes of this document, the terms and definitions given in ISO 9000 and the follow

37、ing apply. 3.1.1 breakdown structure framework for efficiently controlling some aspect of the activities of a programme or project BS ISO 27026:2011ISO 27026:2011(E) 2 ISO 2011 All rights reserved3.1.2 programme strategic set of coordinated and controlled activities that has a defined architecture a

38、nd/or technical approach, requirements, funding level and a management organization that often initiates and directs one or more projects 3.1.3 project portion of a programme consisting of a set of coordinated and controlled activities, undertaken to achieve an objective(s) of the programme conformi

39、ng to specific programme requirements, including constraints of time, cost and other resources 3.2 Abbreviated terms The following abbreviated terms apply. Abbreviated term Meaning CBS Cost breakdown structure OBS Organizational breakdown structure WBS Work breakdown structure WP Work package 4 Over

40、view of project breakdown structures 4.1 General 4.1.1 There are generally several types of project breakdown structures that are generated to provide a framework for efficiently controlling the programme, or its projects, and producing the product agreed to between the customer and the supplier. Ge

41、nerally, the project breakdown structures have the organizational framework of a tree. 4.1.2 A project breakdown structures tree as used in this International Standard is an arrangement of related items or elements characterized by having a top level node, or summit, that is broken down into lower l

42、evel elements or nodes until the lowest level elements are determined; the lowest level is usually based upon some degree of reasonableness or of diminishing returns of further breakdown. A tree is generally constructed for project breakdown structures because the lower level elements are more easil

43、y managed. In a project breakdown structures tree, a hierarchical relationship exists between elements at the same level of breakdown to the next higher related node element above; in addition, elements at the same level of breakdown often have interfaces with other items at the same level. 4.1.3 Th

44、e project breakdown structures described in this clause and in Clause 5 are expressed in terms of a business agreement or contract between a supplier and a customer, where the project breakdown structures would be based upon the suppliers workshare. However, the same principles, processes and requir

45、ements for project breakdown structures can be used by an independent developer, in which case the project breakdown structures would be for the complete system product that might be developed entirely by the independent developer, or by the independent developer and subcontracted suppliers. 4.2 Rel

46、ationship of project breakdown structures 4.2.1 In the context of ISO 14300-1, the various project breakdown structures within a programme or project originate with the level 0 customers set of requirements. Based upon the business agreement and from the customers requirements, a level 1 supplier de

47、velops a set of specifications, each containing requirements, that satisfies the level 0 customers requirements. The specifications are organized in a hierarchical BS ISO 27026:2011ISO 27026:2011(E) ISO 2011 All rights reserved 3specification tree, with lower level specifications containing requirem

48、ents that flow down from higher level specifications. 4.2.2 From the requirements contained in the specification tree, a function tree shall be generally generated. The functions determine what shall be performed by the level 1 suppliers workshare portion of the system, which could be the complete s

49、ystem; the functional requirements in the specification tree specify how well the requirements shall be performed. The specification and functional trees shall be used to generate the design elements of the system product, which is arranged as a product tree. The development of the specification, and hence requirements, tree, is an iterative process with the development of the function tree and the product tree to develop lower levels of each of the trees. Depending upon the situation, the requirements within the specifica

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1