SE351 Roadmap. SE351a: Software Project & Process Management. W3.2: Software Development Lifecycles

Size: px

Start display at page:

Download "SE351 Roadmap. SE351a: Software Project & Process Management. W3.2: Software Development Lifecycles"

Morris Cross
5 years ago
Views:

1 SE351a: Software Project & Process Management W3.2: Software Development Lifecycles 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa SE351 Roadmap Introduction to Software Project Management Project Management Software Development Life Cycles Requirements Engineering Software Process & Project Metrics Software Project Planning Project Monitoring & Control Risk Management Software Quality Assurance 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 2

2 Outlines Software Lifecycles/Software Development Lifecycles Main Phases of SLC Major SLC Models ISO/IEC Software Lifecycle Process 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 3 The Objective is High quality Product Successful Development Process 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 4

Software Project Management Machine Process SDLC PMLC 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 5 PMLC Scope the Project State the problem or opportunity Establish the project goal Define the

3 Software Project Management Machine Process SDLC PMLC 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 5 PMLC Scope the Project State the problem or opportunity Establish the project goal Define the project objectives Identify the success criteria List assumptions, risks and obstacles Launch the Plan Recruit and organize project team Establish team operating rules Level project resources Schedule work packages Document work packages Project Close-Out Obtain client acceptance Install project deliverables Complete project documentation Complete post-implementation audit Issue final project report Develop Detailed Plans Identify project activities Estimate activity duration Determine resource requirements Construct & analyze project network Prepare the project proposal Monitor & Control Progress Establish progress reporting system Install change control process Define problem escalation process Monitor progress versus plan Revise project plan 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 6

4 Software Lifecycle: Main Phases 1. Requirements Analysis 2. Design 3. Implementation 4. Testing 5. Delivery/Deployment 6. Maintenance SDLC SLC 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 7 PMLC vs. SDLC Scope the Project Scope the Project Develop Detailed Plans Develop Detailed Plans Request Initiation Business Requirements Success Criteria Develop Requirements Establish Phase Review Schedule Launch the Plan Launch the Plan Identify the Development Team Build the System Monitor & Control Progress Monitor & Control Progress Monitor Progress Conduct Subsystem Test Conduct Acceptance Test Project Close-Out Project Close-Out Evaluate System Performance Conduct Post-Project Review 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 8

5 Cost vs. Phases 15% 6% 15% 18% 15% 21% 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 9 Software Development Lifecycle: Major Models Build It & Fix It Waterfall Rapid Prototyping Incremental Spiral Agile 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 10

6 Waterfall Model Requirements/ Specifications Verify Software Requirements Specification Design Verify Design Document Implementation Test Software System Integration Test Operations Manual Operations 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 11 Waterfall Model: Strengths Emphasis on early planning, client input, and design Emphasis on testing as an integral part of the lifecycle Document driven: per phase Emphasis on completion of one phase before moving on!! Weaknesses Sequential flow is not practical Depends on capturing and freezing requirements early in the lifecycle High blocking states No working version of the system until the end of the cycle Technical documents usually are not appropriate for communication 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 12

7 Rapid Prototyping Model Requirements/ Specifications Verify Develop Prototype Software Requirements Specification Design Verify Design Document Implementation Test Software System Integration Test Operations Manual Operations 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 13 Rapid Prototyping Strengths Avoids building systems to bad requirements Enable requirements and design to be communicated more clearly between Participants More requirements and design faults are caught early Weaknesses Lengthy requirements phase Need to throw away Temptation to release product early o the prototype may become the production system 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 14

8 The Incremental Model Breakdown design into builds Modules that can stand alone increment 1 analysis design code test delivery of 1st increment increment 2 analysis analysis design code code test delivery test of 2nd increment increment 3 analysis design code test delivery of 3rd increment 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 15 Spiral Model: Risk Management Determine risks involved in developing product Deal with risks in turn (resolve, minimize) Assessment Pushing limits of technology Assessing costs frequently 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 16

Spiral Model: A Simplified Version Planning Risk Analysis Evaluation Engineering 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 17 Spiral Model(Cont.) (Cont.

9 Spiral Model: A Simplified Version Planning Risk Analysis Evaluation Engineering 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 17 Spiral Model(Cont.) (Cont.) Strengths Emphasis on risk reduction techniques, o such as prototypes, COTS vs. In-house Assess cost-benefit Provides checkpoints for considering project cancellation Weaknesses Appropriate for large projects Full scale risk analysis requires training, skill, and considerable expense Internal (in-house) software 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 18

10 Agile Software Development Processes Are based on three key assumptions It is difficult to predict in advance o which requirements or customer priorities will change In many types of software o design and construction activities are interleaved (construction is used to prove the design) Analysis, design, and testing are not as predictable from a planning perspective as one might like them to be 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 19 Agile Software Development Processes Agile processes must be adapted incrementally to manage unpredictability It requires customer feedback o based on evaluation of delivered software increments (executable prototypes) over short time periods 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 20

11 Agile Software Development Encourages customer involvement and satisfaction incremental software delivery o o Stresses small project teams (software engineers & stakeholders) minimal software engineering work products continuous communication and collaboration (among developers and customers) on-time delivery of an operational software increment over analysis and design If applied effectively, it can deliver successful systems quickly 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 21 Extreme Programming (XP) Relies on object-oriented approach Key activities Planning o Design o Coding o Testing o o user stories created and ordered by customer value simple designs preferred, CRC cards and design prototypes are only work products, encourages use of re-factoring emphasizes on use of pairs programming to create story code, continuous integration and smoke testing is utilized unit tests created before coding are implemented using an automated testing framework to encourage use of regression testing, integration and validation testing done on daily basis, o acceptance tests focus on system features and functions viewable by the customer 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 22

12 XP-SDLC 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 23 Other Process Models Component assembly model reuse is a development objective Formal methods mathematical specification is to be developed Cleanroom software engineering emphasizes error detection before testing 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 24

13 ISO/IEC SLC Standard 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 25 ISO/IEC PURPOSE Establish a common framework for software lifecycle 1. To acquire, supply, develop, operate, and maintain software 2. To manage, control, and improve the framework 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 26

14 ISO12207 :Background International Organization for Standardization ISO ESTABLISHED: 1987 International Electrotechnical Commission IEC JTC1 Joint Technical Committee OBJECT: TO CARRY ON STANDARDIZATION WORK IN INFORMATION TECHNOLOGY SC1 - Vocabulary SC2 - Character sets & information coding SC6 - Telecommunications & information exchange between systems SC7 - Software engineering SC11 - Flexible magnetic media for digital data interchange SC14 - Representation of data elements SC15 - Labelling and file structure SC17 - Identification cards & related devices SC18 - Document processing and related communication SC21 - Information retrieval, transfer & management for OSI SC22 - Programming languages, their environments & systems software interfaces SC23 - Optical disk cartridges for information interchange SC24 - Computer graphics and image processing SC25 - Interconnection of information technology equipment SC26 - Microprocessor systems SC27 - IT security techniques SC28 - Office equipment SC29 - Coded representation of picture, audio and multimedia/hypermedia information 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 27 Background (Cont.) History: Proposed in June Working Drafts; 2 Committee Drafts Over 6 years and 17,000 person-hours Published 1 August 1995 Participants: Countries: Australia, Canada, Denmark, Finland, France, Germany, Ireland, Italy, Japan, Korea, Netherlands, Spain, Sweden, UK, USA 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 28

15 Relationship to System Areas SYSTEM ENGINEERING INFORMATION TECHNOLOGY CONVENTIONAL ENGINEERING ENGINEERING [12207] 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 29 Establishes Link With System Engineering Software treated as a part of the system System engineering activities are the foundation of software engineering Necessary system context provided Software activities placed under the context Software extracted from and integrated into the system Software engineering participates in system engineering 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 30

16 The Engineering View of ISO/IEC Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 31 DEVELOPMENT PROCESS SYSTEM ORGANIZATION SYSTEM HI X SI X MO SC SC SU SU SU SU HI- Hardware Item; SI- Software Item; MO- Manual Operations; SC- Software Component; SU- Software Unit; X- Other 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 32

17 A Management Complement ISO not a substitute for systematic, disciplined management Rather, ISO complements the management practices It provides a powerful and complete but flexible set of building blocks of a software lifecycle for a project and an organization to use as appropriate and effective 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 33 ISO12207 Concepts ISO describes 17 processes Each process is divided into "activities," and o the activities into "tasks," while placing requirements upon their execution 5 primary processes For major functions and primary parties 1. acquisition 2. supply 3. development 4. operation 5. maintenance 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 34

18 Primary Processes OPERATION 0 ACQUISITION SUPPLY DEVELOPMENT MAINTENANCE 0 DEVELOPMENT PLAN, DO, CHECK & ACT 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 35 ISO12207 Concepts(Cont.) (Cont.) 8 supporting processes For supporting other processes with a purpose 1. Documentation 2. Configuration Management 3. Quality Assurance 4. Verification 5. Validation 6. Joint Review 7. Audit 8. Problem Resolution 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 36

19 ISO Concepts(Cont.) 4 organizational processes For corporate level management and improvement 1. Management 2. Infrastructure 3. Improvement 4. Training Tailoring Processes To formalize tailoring of the standard o The intention for organizations is to tailor these 17 processes to fit the scope of their particular projects by deleting all inapplicable activities; and it defines compliance as the performance of those processes, activities, and tasks selected by tailoring 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 37 ISO Concepts Process Tree ACQUISITION SUPPLY DEVELOPMENT OPERATION MAINTENANCE PRIMARY Lifecycle SUPPORTING DOCUMENTATION CONFIGURATION MANAGEMENT QUALITY ASSURANCE VERIFICATION VALIDATION JOINT REVIEW AUDIT PROBLEM RESOLUTION ORGANIZATIONAL MANAGEMENT INFRASTRUCTURE IMPROVEMENT TRAINING TAILORING

20 Development Process FOR THE DEVELOPER (MODIFIER) OF PRODUCTS -May Perform or Support some System Engineering - Activities not necessarily in time order ACTIVITIES INTERNAL USE INVOKED PROCESSES OUTPUTS Development Process FOR THE DEVELOPER (MODIFIER) OF PRODUCTS -May Perform or Support some System Engineering - Activities not necessarily in time order ACTIVITIES INTERNAL USE INVOKED PROCESSES OUTPUTS 1. PROCESS IMPLEMENTATION 2. SYS. REQ. ANALYSIS 3. SYS. ARCH. DESIGN DOCUMENTATION C.M. PROBLEM RESOLUTION EVALUATIONS EVALUATIONS DEVELOPMENT PLANS & MODELS SYSTEM REQUIREMENTS SYS. ARCHITECTURE - HW, SW, MO 4. SOF. REQ. ANALYSIS EVALUATIONS ISO/IEC 9126 JT. REVIEWS REQUIREMENTS 5. SOF. ARCH. DESIGN EVALUATIONS JT. REVIEWS ARCHITECTURE 6. SOF. DET. DESIGN EVALUATIONS JT. REVIEWS DET. DESIGN 7. SOF. CODE/TEST EVALUATIONS CODE/DATABASE 8. SOF. INTEGRATION EVALUATIONS JT. REVIEWS INTEGRATED (SCIs) 9. SOF. QUALIF. TEST EVALUATIONS AUDITS DESIGN & CODE 10. SYS. INTEGRATION EVALUATIONS INTEGRATED 11. SYS. QUALIF. TEST EVALUATIONS AUDITS DESIGN & CODE 12. SOF. INSTALLATION 13. SOF. ACCPT. SUPPORT EVALUATIONS INSTALLATION PLAN INSTALLED SOFT. DELIVERABLE

21 Development Process FOR THE DEVELOPER (MODIFIER) OF PRODUCTS - May Perform or Support some System Engineering - Activities not necessarily in time order ACTIVITIES INTERNAL USE INVOKED PROCESSES OUTPUTS 4. SOF. REQ. ANALYSIS EVALUATIONS ISO/IEC 9126 JT. REVIEWS 5. SOF. ARCH. DESIGN EVALUATIONS JT. REVIEWS 6. SOF. DET. DESIGN EVALUATIONS JT. REVIEWS 7. SOF. CODE/TEST EVALUATIONS 8. SOF. INTEGRATION EVALUATIONS JT. REVIEWS REQUIREMENTS ARCHITECTURE DET. DESIGN CODE/DATABASE INTEGRATED 9. SOF. QUALIF. TEST EVALUATIONS AUDITS DESIGN & CODE 12. SOF. INSTALLATION EVALUATIONS 13. SOF. ACCPT. SUPPORT INSTALLATION PLAN INSTALLED SOFT. DELIVERABLE DEVELOPMENT PROCESS ACTIVITIES & TASKS 1. Process Implementation 3. System Architectural Design Define/Select lifecycle Model(s) Employ Regularly Doc, CM, & Prob. Res. Processes Select/Tailor internal Methods/Tools/ Develop, Doc., Execute plans May use non-deliverables - Avoid dependency of future operations & maintenance 2,3,10,11 System Activities Perform or support 4-9, 12,13 Software Activities Produce an Architecture of the system Identify HW, SW, & Manual Operations 5. Sfotware Architectural Design Produce an architecture of the SW system Identify components of the SW system 8. Software Integration 10. System Integration Integration in aggregates partition & Integration Paths may be different Perform

22 Operation Process For the Operator of a system contains software QUALITY LINES ACTIVITIES INTERNAL USE INVOKED PROCESSES OUTPUTS PROCESS IMPLEMENTATION PROBLEM RESOLUTION MAINTENANCE - OPERATION PLAN - OPERATION PROCEDURES OPERATIONAL TESTING INTERNAL TESTING & ENSURANCE RELEASED OPERATIONAL SYSTEM OPERATION FUNCTIONS PERFORMED USER SUPPORT - USER REQUESTS - PROBLEM RESOLUTIONS 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 43 OPERATION PROCESS ACTIVITIES & TASKS 1. PROCESS IMPLEMENTATION Develop Operational Plan Set Operational Standards Document & execute plan Establish procedures for/with problem resolutions Establish procedures for operational testing Establish procedures for interfacing with maintenance process Establish procedures for releasing products for operational use 2. OPERATIONAL TESTING Perform Operational testing for each release Release after criteria met Ensure code/database perform as planned 3. SYSTEM OPERATION Operate in environment 4. USER SUPPORT Proved assistance to users Forward user requests to maintenance as needed For temporary fixes, provide option to use it

23 Maintenance Process For the Maintainer of Software Product QUALITY FIXING HD ACTIVITIES INTERNAL USE INVOKED PROCESSES OUTPUTS PROCESS IMPLMENT. PROBLEM RESOLUTN. CM -MAINTENANCE PLANS/PROCS. PROB/MOD. ANALYSIS - PROB./MOD. ANAL/SOLN. MOD. IMPLEMENT. DEVELOPMENT MODIFIED MAINT. REVIEW/ ACCEPT. INTERNAL REVIEWS REVIEW RESULTS MIGRATION INTERNAL REVIEWS -MIGRATION PLANS/REPORTS - MIGRATED SYS. RETIREMENT - RETIREMENT PLANS - ARCHIVES 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 45 Maintenance Process Activities & Tasks 1. PROCESS IMPLEMENTATION 3. MODIFICATION IMPLEMENTATION 5. MIGRATION Develop, document and execute plan Establish procedures for problem reports and modifications requests Manage modifications Determine targets of modifications Use Development Process for mods. Supplement with testing to ensure modified and unmodified parts are correctly done Develop/document/ execute plan Notify users, etc. Do parallel operations Do post-operations for impact 2. PROBLEM/MODIFICATION ANALYSIS Analyze modifications for impacts Replicate/vefify problems Implement modifications Document and get approval 4. MAINTENANCE REVIEW/ACCEPTANCE Review with authorizing organization 6. RETIREMENT Develop/document/ execute plan Notify users, etc. Do parallel operations Provide for access to retired data/products

24 Organizational Process For an organization to manage and improve its process at corporate level 1 MANAGEMENT PROCESS PRIMARY PROCESS SUPPORTING PROCESS INFRASTRUCTURE PROCESS IMPROVEMENT PROCESS TRAINING PROCESS 1: Manage following management process 2: Establish infrastructure following infrastructure process 3: Improve following improvement process 4: Train personnel following training process NOTE: Management process is instantiated in primary & supporting processes, because they are managed differently 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 47 Indicators & Metrics PROCESS INDICATOR/METRIC ACQUISITION PROCESS MONITORING - Cost, Schedule, Technical SUPPLIER SELECTION - Capability, Past performance,... PROPOSAL EVALUATION - Technical, Cost, Schedule, Personnel,... AGREEMENT CHANGES - No., Rate, Impact,... ACCEPTANCE PROGRESS - Acceptance criteria, Conformance, Releasability,... JOINT ACTION ITEMS STATUS SUPPLY BID DECISION PROCESS MONITORING - Cost, Schedule, Technical PROBLEM STATUS - By Activity/Task/Source, Trend,... ACCEPTANCE PROGRESS - Acceptance criteria, Conformance, Releasability,... JOINT ACTION ITEMS STATUS

25 Indicators & Metrics(Cont.) (Cont.) Process DEVELOPMENT Indicator/Metric CHANGE STATUS: By Activity/Task, Source, Trend,... PROBLEM STATUS: BY Activity/Task, Source, Trend,... JOINT ACTION ITEMS STATUS TRACEABILITY: - Sys Reqs to Acquisition Needs - Sys Arch Design to Sys Reqs - Soft Reqs to Sys Reqs & Design - Soft Arch Design to Soft Reqs - Soft Det Design to Soft Reqs - Soft Unit to Soft Reqs & Design - Soft Design & Unit to Sys Reqs QUALITY CHARACTERISTICS [ISO/IEC 9126] - Functionality, Reliability, Usability, Efficiency, Maintainability, Portability - Plus their sub-characteristics REQs TESTABILITY STATUS TEST COVERAGE CONSISTENCY: INTERNAL & EXTERNAL CONFORMANCE TO EXPECTED RESULTS FEASIBILITY OF NEXT ACTIVITY FEASIBILITY OF OPERATIONS FEASIBILITY OF MAINTENANCE Indicators & Metrics(Cont.) (Cont.) Process Indicator/Metric OPERATION OPERATIONAL CHARACTERISTICS - Run time, Throughput, Availability, Responsiveness,... OPERATIONAL TESTING - Coverage, Releasability,... USER SUPPORT - Status of requests, support, releases,... MAINTENANCE STATUS: PROBLEM REPORTS & MODIFICATION REQUESTS - Measure of classification, size, criticality, closure,... - Impact on operations & maintenance TEST COVERAGE OF - Modified parts - Unmodified parts IMPACT ON UNMODIFIED PARTS MIGRATION PORTABILITY USER SUPPORT DURING MIGRATION POST-OPERATION IMPACT OF MIGRATION USER SUPPORT DURING RETIREMENT

26 ROLE? Primary Roles ACQUISITION ROLE SUPPLY ROLE OPERATING ROLE ACQUIRER SUPPLIER OPERATOR USER employ ACQUISITION PROCESS contract SUPPLY PROCESS employ employ OPERATION PROCESS employ employ employ S U P P O R T I N G ENGINEERING ROLE SUPPORTING ROLE DEVELOPER MAINTAINER EMPLOYER OF SUPPORTING PROCESSES use MAINTENANCE PROCESS use Documentation Configuration management Quality assurance Verification DEVELOPMENT PROCESS employ Validation Joint review Audit Problem resolution P R O C E S S E S ORGANIZATIONAL ROLE MANAGER ORGANIZATIONAL PROCESSES Management Infrastructure Improvement Training 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 51 Prototyping in Not listed as an activity of the Development Process - Treated as a method/technique for: - Performing studies, requirements analysis, design, etc. 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 52

27 Relationships to Quality Areas QUALITY MATURITY ISO 9002 QUALITY SYSTEM REQUIREMENTS SPICE/CMM QUALITY SYSTEM REQUIREMENTS Lifecycle PROCESSES REQUIREMENTS ISO/IEC Lifecycle Lifecycle PRACTICES 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 53

Chapter 1. Software Engineering Supporting Processes

Chapter 1. Software Engineering Supporting Processes Chapter 1 Software Engineering Supporting Processes 1. Introduction to IEEE/EIA Standard 12207.0-1996 IEEE/EIA Standard 12207.0-1996 establishes a common framework for software life cycle processes. The