《软件项目计划管理.ppt》由会员分享，可在线阅读，更多相关《软件项目计划管理.ppt（70页珍藏版）》请在金锄头文库上搜索。
1、2003.01.10,SOFTWARE ENGINEERING,授课安排,系统工程 软件项目计划 软件需求分析 软件设计 编程 软件测试 软件维护 面向对象方法、软件复用和构件技术等,2003.01.10,SOFTWARE ENGINEERING,软件项目管理,软件工程管理是对软件项目的开发管理，是对整个软件生存期的所有活动进行管理。任何工程的成败，都与管理的好坏密切相关，软件工程更不例外。尤其是软件产品的特殊性，软件工程的管理对于保证软件产品的质量也具有极为重要的作用。 任何技术先进的大型项目的开发如果没有一套科学的管理方法和严格的组织领导，是不可能取得成功的 。,2003.01.10,SO
2、FTWARE ENGINEERING,软件项目管理,4P：人员(People)、产品(product)、过程(Process)和项目(Rroject)。 将人员组织起来以有效地完成工作； 和客户及其他共利益者很好地沟通，以便了解产品的目标和范围，方案和限制等； 选择合适于人员和产品的过程； 估算工作量和工作时间，制定项目计划，包括：定义工作产品，建立质量检查点以及确定一些机制以监控计划所规定的工作。,2003.01.10,SOFTWARE ENGINEERING,软件项目管理,要让软件项目失败很容易，只要符合下列条件之一即可：（1）项目经理对软件一无所知；（2）技术负责人对编程不感兴趣；（3）
3、真正编写代码的程序员是临时雇用的。 如果上述三个条件同时具备，就请放心失败好了。 让我们少幻想自己是比尔盖茨，先当好程序员和程序经理再说。,2003.01.10,SOFTWARE ENGINEERING,The Definition Phase,System Engineering,Software project planning,Software requirements analysis,Software scope,Refined,2003.01.10,SOFTWARE ENGINEERING,Software Project Planning 软件项目计划,软件项目计划包括五项主要活
4、动：估算、进度安排、风险分析、质量管理计划和变更管理计划。 很多技术人员宁愿从事技术工作，而不愿花费时间制定计划。很多管理者也对计划的效果没有信心，所以很多软件项目就经常不制定计划。,2003.01.10,SOFTWARE ENGINEERING,Software Project Planning 软件项目计划,在可行性分析之后，项目计划与质量管理将贯穿需求分析、系统设计、程序设计、测试、维护等软件工程环节。 项目计划是要提供一份合理的进程表，让所有开发人员任务明确、步调一致，最终共同准时地完成项目。项目计划是要付诸实施的，不象喊政治口号。软件的项目计划重在“准确”而非“快速”。,2003.0
5、1.10,SOFTWARE ENGINEERING,Software Project Planning 软件项目计划,在做软件的项目计划时，应屏弃一切浮夸作风。只有“知已知彼”才能做出合理的项目计划。这里“知彼”是指要了解项目的规模、难度与时间限制。“知已”是指要了解有多少可用资源，如可调用的软件人员有几个？他们的水平如何？软硬件设施如何？等,2003.01.10,SOFTWARE ENGINEERING,软件项目计划,如有进行系统定义，则“系统规格说明书”的功能描述和约束所有有关软件的信息几乎都是可用的，否则计划人员必须起系统分析员的作用。,确定软件的作用范围 资源需求估计 工作量和成本估计
6、 进度安排(里程碑),系统规格 说明书,=软件计划,不确定性,2003.01.10,SOFTWARE ENGINEERING,Software Scope（范围）,The first activity in software project planning is the determination of software scope.Function and perform-ance allocated to software during system engineering should be assessed to establish a project scope that is u
7、nambiguous and understandable at management and technical levels.,2003.01.10,SOFTWARE ENGINEERING,Software Scope,Software scope describes function, performance,constraints,interfaces,and reliability. Functions described in the statement of scope are evaluated and in some cases refined to provide mor
8、e detail prior to the beginning of estimation.Because both cost and schedule estimates are functionally oriented,some degree of decomposition is often useful.,2003.01.10,SOFTWARE ENGINEERING,Software Scope,The most commonly used technique to bridge the communication gap between the customer and deve
9、loper and to get the communication process started is to conduct a preliminary meeting or interview. The analyst start by asking “context free questions.”,2003.01.10,SOFTWARE ENGINEERING,Project Planning Objectives,The objective of software project planning is to provide a framework that enables the
10、 manager to make reasonable estimates of resources,cast, and schedule.These estimates are made within a limited time frame at the beginning of a software project and should be updated regularly as the project progresses. In addition, estimates should attempt to define “best case” and “worst case” sc
11、enarios so that project outcomes can be bounded.,2003.01.10,SOFTWARE ENGINEERING,Software Project Planning,The software project planner must estimate three things before a project begin:how long it will take,how much effort will be required, and how many people will be involved.In addition,the plann
12、er must predict the resources (software and hardware) that will be required and the risk involved.,2003.01.10,SOFTWARE ENGINEERING,Estimating（估算）,The estimating is as much art as it is science. A leading executive was once asked what single characteristic was most important when selecting a project
13、manager.His response: “a person with the ability to know what will go wrong before it actually does.”We might add: “and the courage to estimate when the future is cloudy.”,2003.01.10,SOFTWARE ENGINEERING,Estimating,Estimation of resources,cost,and schedule for a software development effort requires
14、experience,access to good historical information,and the courage to commit to quantitative measures when qualitative data are all that exist.,2003.01.10,SOFTWARE ENGINEERING,Estimating Risk（风险）,Project complexity Project size The degree of structural uncertainty The availability of historical inform
15、ation If project scope is poorly understood or project requirements are subject to change,uncertainty and risk become dangerously high.,2003.01.10,SOFTWARE ENGINEERING,Software Project Estimation,In the early days of computing,software costs comprised a small percentage of overall computer-based sys
16、tem cost.An order of magnitude error in estimates of software cost had relatively little impact. Software cost and effort estimation will never be an exact science.,2003.01.10,SOFTWARE ENGINEERING,Software Project Estimation,To achieve reliable cost and effort estimates, a number of options arise: Delay estimation until late in the project. Base estimates on similar projects that have already been completed. Use relatively simple “decomposition techniques” to generate project cost and effort
