《幻灯片注释lect02》由会员分享，可在线阅读，更多相关《幻灯片注释lect02（45页珍藏版）》请在金锄头文库上搜索。
1、Software Project Management,Lecture 2 Software Development Models,Software project management,2,Overview,Introduction Technical plan Software process models Selecting process model,Software project management,3,Definitions,Software Process the set of activities, methods, and practices that are used
2、in the production and evolution of software Software Process Model one specific embodiment具体化 of a software process architecture (Humphrey 1990),Software project management,4,Why Modelling?,To provide a common understanding To locate any inconsistencies, redundancies and omissions To reflect the dev
3、elopment goals and provide early evaluation To assist development team to understand any special situation,Software project management,5,Project Analysis,Methodologies Object-Oriented Development (OOD) Structured System Analysis and Design Method (SSADM) Jackson Structured Programming (JSP) Technolo
4、gies application-building environment knowledge-based system tools,Software project management,6,Project Characteristics,data oriented or control oriented system? general package or application specific? a particular type of system for which specific tools have been developed? safety-critical system
5、? nature of the hardware/software environment?,Software project management,7,Project Risks,Product uncertainty Process uncertainty Resource uncertainty,Software project management,8,Considerations for Project Approach,Control systems Information systems General applications Specialized techniques Ha
6、rdware environment Safety-critical systems Imprecise requirements,Software project management,9,Technical Plan,Contents Constraints Approach Implementation Implications,Software project management,10,Technical Plan - Constraints,Character of the system to be developed Risks and uncertainties of the
7、project User requirements concerning implementation,Software project management,11,Technical Plan - Approach,Selected methodology or process model Development methods Required software tools Target hardware/software environment,Software project management,12,Technical Plan - Implementation,Developme
8、nt environment Maintenance environment Training,Software project management,13,Technical Plan - Implications,Project products and activities effect on schedule duration and overall project effort Financial report used to produce costings,Software project management,14,Software Process Models,Waterfa
9、ll Model V Model Spiral Model Prototyping Model,Software project management,15,Software Process Models (contd),Phased Development Model incremental development model Iterative反复的 development model Operational Specification Model Transformation转化 Model,Software project management,16,Waterfall Model,R
10、equirement Analysis,System Design,Coding,Testing,Maintenance,Software project management,17,Waterfall Model (contd),classical one-shot approach effective control limited scope of iteration long cycle time not suitable for system of high uncertainty,Software project management,18,V Model,Requirements
11、 Analysis,System Design,Program Design,Coding,Unit and Integration Testing,System Testing,Maintenance,User Acceptance Testing,Software project management,19,V Model (contd),Additional validation process introduced Relate testing to analysis and design Loop back in case of discrepancy差异,Software proj
12、ect management,20,Spiral Model (adapted from Boehm 1987),Plan next phases,Determine objectives, alternatives and constraints,Evaluate alternatives; identify and resolve risks,Develop and verify next-level product,Requirements plan,Development plan,Integration and Test plan,Concept of operation,Risk
13、analysis,Risk analysis,Risk analysis,Prototype,Prototype,Prototype,Software requirements,Requirements validation,System product design,Design validation,Acceptance test,Integration and Test,Unit testing,Coding,Detailed design,Cumulative cost,Progress through steps,Software project management,21,Spir
14、al Model (contd),Evolutionary approach Iterative development combined with risk management Risk analysis results in “go, no-go” decision,Software project management,22,Spiral Model (contd),Four major activities Planning Risk analysis Engineering Customer evaluation,Software project management,23,Pro
15、totyping Model,Goals meet users requirements in early stage reduce risk and uncertainty,Software project management,24,Classification of Prototype,Throw-away After users agree the requirements of the system, the prototype will be discarded. Evolutionary Modifications are based on the existing protot
16、ype. Incremental Functions will be arranged and built accordingly.,Software project management,25,Prototyping Model,Build prototype,User satisfaction,YES,NO,User feedback,Software project management,26,Benefits of Prototyping,Learning by doing Improved communication Improved user involvement Clarification of partially-known requirements,Software project management,27,Prototyping Sequences,Requirements gathering Quick design Prototype construction Customer evaluation Refinement Loop back to quick design for fine tuning Product engineering,
