《《cmmi培训资料五》ppt课件》由会员分享，可在线阅读，更多相关《《cmmi培训资料五》ppt课件（27页珍藏版）》请在金锄头文库上搜索。
1、CMMI介绍 （五）,CMMI Coordinator Team,October 07, 2004,PM Training (part 2),培训内容,SW development lifecycle SDLC Tailoring Product release DAR,SW development lifecycle,Waterfall,System feasibility Validation,Software Plans & Requirements Validation,Product Design Verification,Detailed Design Verification,C
2、ode Unit Test,Integration Product Verification,Implementation System Test,Operations & Maintenance Revalidation,This model is best suited when a set of high quality, stable user requirements exists. Its limitations stem from the fact that it requires complete knowledge of all requirements at early s
3、tages of the life cycle, commitment of all financial and other resources up front (with a low visibility until the product is ready) and lack of flexibility to accept change to requirements. The Waterfall Model is inappropriate for development situations where these factors may pose problem,SW devel
4、opment lifecycle,RAD Rapid Application Development,If a application can be modularized in a way that enables each major function to be completed in say, less than 3 months, it is a candidate for RAD. Each major function can be addressed by a separate RAD team and then integrated to form a whole appl
5、ication. If a system cannot be properly modularized, or if the technical risks are high,RAD is not suitable as a life cycle model.,Business Modeling,Data Modeling,Process Modeling,Application Generation,Testing & Delivery,Business Modeling,Data Modeling,Process Modeling,Application Generation,Testin
6、g & Delivery,Team1,Team2,SW development lifecycle,Incremental,The first increment is often a core product where the basic requirements are addressed, but many supplementary features remain undelivered. The core product is reviewed in detail by the customer and may be even used. As a result of the de
7、tailed review and / or use of the core product a plan is developed for the next increment. This is the best choice for projects that has high technical risks, and objective is achieved by breaking down the project organization and systems construction into manageable sub-projects.,Increment 1,Delive
8、ry of 1st Increment,Analysis,Design,Code,Test,Increment 2,Delivery of 2nd Increment,Analysis,Design,Code,Test,Increment 3,Delivery of 3rd Increment,Analysis,Design,Code,Test,SW development lifecycle,Prototyping,The analysts discuss with the customer the overall system objectives, identify whatever r
9、equirements are known, and outline areas where further definition is needed. On basis of the Gross Design a prototype is built which serve to obtain user feedback and refine the requirements of the software to be produced. Iteration occurs as the prototype is tuned to satisfy the needs of the custom
10、er and thus facilitate a better understanding of the customer requirements and thereby, modification and refinement of the system requirements.,Design,Coding,Testing,Installation,Maintenance,Project Initiated,Requirements gathering& refinements,Gross design,Building Prototype,Customer evaluation,Ref
11、ine prototype,Engineer product,Design of remaining portion of the System Construction of the whole software, or Construction the balance portion in case the Phase prototype is a functional prototype,Requirement Specifications (Requirement Analysis + Prototype Design + Prototype Construction + Custom
12、er Feedback + Refining Defining alternatives),SW development lifecycle,Spiral,This couples the iterative nature of the Prototyping Model with the controlled and systematic approach of the Waterfall Model. This model does not necessitate either a full knowledge of user requirements, or a full commitm
13、ent of funds for the entire development work at the beginning of the project. Like the Waterfall Model, the Spiral Model starts with a set of objectives that specify quality and costs associated with the reaching of goals.,SW development lifecycle,JAD (Joint Application Development) is a technique t
14、hat allows the development team, customer management and user groups to work together to build a product. This is more of a project management strategy and approach than a software process model, though the life cycle activities may differ in some cases while the JAD technique is adopted. Thus a pro
15、ject using JAD technique may use any of the life cycle models described above with the necessary tailoring of the life cycle model.,SW development lifecycle,Software Maintenance Lifecycle The lifecycle for any support project will normally involve understanding the system that is to be supported sys
16、tem study, and then providing support as when any issues are reported by the user (issues could include bugs, exceptions or minor changes) issue handling.,SDLC Tailoring,Entry Criteria,Requirements are clear; Draft project plan will be developed.,SDLC Tailoring,Inputs,MRD, System Requirement, and part of UC, UI etc. FB SDLC guideline FB Tailoring guideline,SDLC Tailoring,Activities,1 Depending on the requirements,the PM or DM will sel
