1. 6/6/2016 1 SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering

2. 6/6/2016 2 Software Life Cycle Pre-projectProjectPost-project Documentation Coding & Debugging Detailed Analysis & Design Training kits Testing Requirement Definition Preliminary Analysis Evaluation: -Contents -Size -Risk Evaluation Production kits Change management Production Maintenance Training Status evaluation

3. 6/6/2016 3 Post-project Pre-Project Requirement Definition Preliminary Analysis Detailed Requirements Methodology Old metrics Resources Estimate Risks Model Requirements Activity list Project plan -Contents evaluation -Risk analysis -Estimation -Assignments -Contents evaluation -Risk analysis -Estimation -Assignments

4. 6/6/2016 4 Post-project Project Detailed analysis & design Training kit preparation Production kits Training kits Detailed requirements Model Project Plan Technical writing Manuals coverage Internal Documentation Refined project plan Refined estimates Source Production planning & kit preparation Executable Coding debugging Test planning Test input Test kit Project status Status evaluation Testing Test generation Project management Test output resources Test plan

5. 6/6/2016 5 project Training Version control & Configuration management Refined metrics Refined resources Refined methodology Estimate Metrics Evaluation & conclusion Post-Project Training kits Production kits Manuals Executable Maintenance Source Test kit Production New version Resources Methodology Change management

6. 6/6/2016 6 Software Life Cycle RequirementsAnalysisSpecificationCoding SystemTestIntegrationTestModuleTest

7. 6/6/2016 7 Requirements stage (Program Statement) Proposal stage Analysis Definition END Design stage (Draft Requirements Specification) (Requirements Specification) (Proposal) (Project Plans) Proposal and Project Planning Code stage Verification stage (Functional Description) (Design) (Code and Unit Test) (Documentation) (Technical Testing) (System Testing) Change to Requirements? Change Control Update all related documents, code, and tests to reflect the change Develop Proposal and Project Plans to fulfill project requirements Analyze requirements, categorize to expose incomplete areas, and prioritize by importance Gather initial requirements, clarify requirements for understanding Defined Requirements Update status with draft Approved Requirements Update status upon approval Committed Requirements Update status at commitment Designed Requirements Update status at design inspection Implemented Requirements Update status at code inspection Completed Requirements Update status at test completion Change affects Requirements Specification Change affects Proposal only

8. 6/6/2016 8 Commitments PlansReviewsRequirementsEstimatesQ. Assurance Tracking Configuration Management

9. 6/6/2016 9 REQUIREMENTS MANAGEMENT Definition Analysis Proposal and Project Planning Replanning needed? PROJECT PLANNING ESTIMATIONCOMMITMENT CONTROL PROJECT TRACKING PROJECT MANAGEMENT REVIEWS SOFTWARE QUALITY ASSURANCE Return to Commitment Point OR when Project is Complete Go to Delivery Point Initial Planning Create Estimates Review Estimates Commitment Negotiation Approval Form Commitment Point Commitment Tracking Compare Actuals to Plans Evaluate Status and Performance Requirements Status Tracking Status Meetings Project Reviews Commitment Reviews Annual SQA Plan Conduct Audits Postmortem Update Historical Database Requirements Change Control Replanning Additional Estimates New Commitment Negotiation Delivery Point No Yes

10. 6/6/2016 10 Requests from Customers, Marketing, or Engineering Defined Requirements Customer & Technical (mixed) Approved Requirements Customer & Technical (related) Committed Requirements Customer & Technical (& Project) (Project Requirements tracked in other Project Management Processes) Proposal & Project Planning Analysis Definition Designed Requirements Technical Implemented Requirements Technical Completed Requirements Customer & Technical Technical Requirements verified by technical testing Designed Requirements traced to code Technical Requirements Customer Requirements Technical Requirements traced to Design Customer Requirements verified by system testing REQUIREMENTS MANAGEMENT

11. 6/6/2016 11 Project Planning Phases Entrance Criteria: Inputs: Initial Planning Completion of Proposal Step - Market Analysis and Strategic Assessment Identification of: 1. Program/Projects 2. Functionality 3. Delivery Dates Gross Estimates of: 1. Size 2. Cost 3. Labor Project Planning Process Develop revisions to Project Plans Develop inputs to Project Plans Replanning Develop initial version Project Plans Exit Criteria: Approval and Commitment of Project Plans Outputs: Initial Version of: 1. Multi-Project Development Plan 2. Individual Project Plan 3. Quality Plan Entrance Criteria: Replanning indicated due to changes in: Project Status, Functionality, Staffing, Budget, etc. Exit Criteria: Approval and Commitment of Project Plans Project Planning Process Outputs: Revison of: 1. Multi-Project Development Plan 2. Individual Project Plan 3. Quality Plan Inputs: Changed Conditions Current version of Project Plans PROJECT PLANNING

12. 6/6/2016 12 Multi-Project Development Plan Propose Multi-Project Schedule Get estimated commitment dates Create Interdependencies Matrix Get estimated commitment dates Individual Project Plan Identify Constraints Functionality, Resource, and Schedule Constraints Update Multi-Project Schedule Update Plan to Reflect Approved Commitment Dates Create Integration Plan Identify Project Integration Milestones and Reviews Negotiate Commitment Approval Receive Approval or Renegotiate Constraints and Replan the Project Identify Tasks Work Breakdown Structure Create Quality Plan Estimate Work Effort Use Estimation Process for Size, Resource, and Schedule Estimates QualityPlan Check and Balance Compare Estimates to Constraints, Determine Alternatives or Contingency Plans Identify Milestones Use Project Review Guidelines to Schedule Milestones and Reviews Identify Processes and Procedures Identify Deliverables and Quality Records Identify Goals, Criteria, and Metrics PROJECT PLANNING

13. 6/6/2016 13 Multi-Project Development Plan Individual Project Plans Individual Project Plan Quality Plan covers interdependencies and integration only needed when a set of projects will be released together Quality Plan Multi-Project Master Schedule Interdependencies Matrix Integration Plans List of high-level schedule of all projects matrix of project interdepedencies integration plans/milestones of all projects list of pointers to project summaries and where to find them/who to contact Project Schedule Functionality Summary Staffing Summary schedule including tasks and staff resources list of major features and functionality total labor months and names of assigned staff covers tasks, resources, and schedule for a single project Interdependencies List Equipment/Materials Summary list of project’s interdependencies list of equipment/materials resource requirements pointer to (or section in project plan containing) the project’s Quality Plan Processes/Procedures List Deliverables/Quality Records Goals/Criteria/Metrics list of standard or special processes for this project list of all deliverables and quality records and their location goals and/or entrance and exit criteria for critical tasks, metrics to measure and determine product content and quality covers planning assumptions and configuration management and quality control information Other Assumptions & Risks other assumptions and risks to capture for review PROJECT PLANNING

14. 6/6/2016 14 Entrance Criteria: Inputs: Estimates required by Project Planning Process 1. Requirements and Tasks to Perform 2. Staffing or Schedule Constraints 3. Historical Project Data Profiles 4. Estimation Factors Checklist Data Estimation Process Exit Criteria: Estimation inputs and outputs recorded in Project Plans Outputs: Estimates for: 1. Size 2. Resource 3. Schedule ESTIMATION

15. 6/6/2016 15 Create Estimates Project Manager gathers input and calculates the estimate Estimation Process Steps Project Planning Process Identify Constraints Provides input constraints on staffing, schedule, and functionality Update Historical Project Data Profiles Gather data from completed projects to add to profiles for estimation base Negotiate Commitment Approval Receive Approval or Renegotiate Constraints and Replan the Project Update Project Plans with estimates for review and approval Collect Tracking Data Collect data for development phase Interdependent Process Steps Review Estimates Project Manager and Project Team review and revise inputs and estimates Project Tracking Process Changes require Project Plan revisions Project Complete ESTIMATION

16. 6/6/2016 16 Inputs Project Planning Process Negotiation Managers work with Director to get Commitment Approval Send Approval Form Department Manager sends form to Program Manager after Director signs Update Records Program Manager updates Commitment Control Records with Commitment Approval Form data ProcessOutputs 1. New Request, or 2. Change in Project Status that Affects Current Commitment Project Management Review Process Updated Records: 1. Commitment Change Record 2. Product Roadmap PROJECT PLANNING COMMITMENT CONTROL PROJECT TRACKING PROJECT MANAGEMENT REVIEWS

17. 6/6/2016 17 END Adjustments required? PROJECT COMPLETE? Obtain tracking requirements from project plan and agree to criteria for management escalation Obtain “planned” values from project plan Collect current “actual” values and compare to “planned” values Evaluate project performance and status relative to plan Report status and adjustments or proposals Project Planning Process Project Tracking Process Adjust project’s objectives, plan, or resources (including Commitment Control Process) Document and distribute revised plan YES NO PROJECT PLANNING PROJECT TRACKING

18. 6/6/2016 18 Report audit results at end-of-audit, end-of-month, end-of-phase Plan approved? Is it time for quarterly review? Obtain direction and priorities from Steering Committee and prepare annual SQA plan Develop detailed audit procedures and criteria, provide training Conduct audits Steering Committee Oversight Activities Audit Planning and Execution Activities Review SQA plans, non-compliance items; assign action items for non-compliance items Document and distribute new/revised plan YES NO Escalate to director Review and approve annual SQA plan Need to escalate to director? Need to revise SQA plan? YES NO YES SOFTWARE QUALITY ASSURANCE

19. 6/6/2016 19 new technologies CORBA Java HTML ODBC XML VBScript JavaScript Active-X ASP

20. 6/6/2016 20 Design a little... Implement a little... Test a little... Web Application Development