- 1、本文档共29页,可阅读全部内容。
- 2、原创力文档(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。
- 3、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载。
- 4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
查看更多
微软产品生命周期模型
* * * * * * * * * * * The Product Cycle Model (PCM) is Microsoft’s way of developing products and services. It includes phases for planning, design, implementation, stabilization, and release. The Product Cycle Model is an iterative process, during which plans are continually reassessed and refined. It is not a structure with prescriptive steps that are etched in steel; rather, it is a structure of processes that many teams adapt for their own unique product or service, customer base, and schedule. For example, a project that takes three years to complete is different than a project that takes nine months; a product or service that is sold on a CD is different than a service that is sold over the Web; and the first version (also known as v1) of a product or service is different than an update of an existing product or service. In each of these instances, the project will have slightly different needs and the Product Cycle Model will be slightly modified to accommodate those needs. * * * 市场机会:产品有没有价值 相关文档(需求,竞争分析) * 不是从开发角度(如:容不容易实现,代码眩不眩) * 前期的市场宣传 * 功能是否符合:测试人员和开发人员的互动,寻找产品缺陷,发布BETa版,收集外部人员的意见 功能上需要修改的话,需要开会决定增加或删减 * 构建网站,发布一些消息,技术论坛,bug报告, 发布会,交给生产部门(rtm) rtw Rto(运维) * User scenarios: a sequence of events used to define a product requirements from a user’s point of view * * The Product Cycle Model is an iterative, not linear, process. As a team develops a product or service, it makes plans that are made based on assumptions. At various points within each phase of the Product Cycle Model, the team reassesses these assumptions, and, if necessary, changes plans or the design. For instance, the features that are finalized during the design phase sometimes effect the decisions made during the planning phase. These discrepancies are sorted out before the features are coded during the implementation phase. During the implementation phase, customer problems and the proposed solutions are reassessed to ensure that the approach is still applicable. If changes are requir
文档评论(0)