These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20051WVU LDCSEECS 430Project Scheduling and Trackingcopyright © 1996, 2001, 2005R.S. Pressman & Associates, Inc.For University Use OnlyMay be reproduced ONLY for student use at the university levelwhen used in conjunction with Software Engineering: A Practitioner's Approach.Any other reproduction or use is expressly prohibited.These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20052Why Are Projects Late? an unrealistic deadline established by someone outside the software development group changing customer requirements that are not reflected in schedule changes; an honest underestimate of the amount of effort and/or the number of resources that will be required to do the job; predictable and/or unpredictable risks that were not considered when the project commenced; technical difficulties that could not have been foreseen in advance; human difficulties that could not have been foreseen in advance; miscommunication among project staff that results in delays; a failure by project management to recognize that the project isfalling behind schedule and a lack of action to correct the problemThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20053Scheduling Principles compartmentalization—define distinct tasks interdependency—indicate task interrelationship  effort validation—be sure resources are available defined responsibilities—people must be assigned defined outcomes—each task must have an output defined milestones—review for qualityThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20054Effort and Delivery TimeEffort CostImpossible regiontdEdTmin = 0.75TdtoEoEa = m ( td4/ta4)development timeEa = effort in person-months td = nominal delivery time for schedule to = optimal development time (in terms of cost) ta = actual delivery time desired These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20055Effort Allocation40-50%30-40% “front end” activities customer communication analysis design review and modification construction activities coding or code generation testing and installation unit, integration white-box, black box regression 15-20%These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20056Defining Task Sets determine type of project assess the degree of rigor required identify adaptation criteria select appropriate software engineering tasksThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20057Task Set Refinement1.1 Concept scoping determines the overall scope of the project.Task definition: Task 1.1 Concept Scoping 1.1.1 Identify need, benefits and potential customers;1.1.2 Define desired output/control and input events that drive the application;Begin Task 1.1.21.1.2.1 FTR: Review written description of needFTR indicates that a formal technical review (Chapter 26) is to be conducted.1.1.2.2 Derive a list of customer visible outputs/inputs1.1.2.3 FTR: Review outputs/inputs with customer and revise as required;endtask Task 1.1.21.1.3 Define the functionality/behavior for each major function;Begin Task 1.1.31.1.3.1 FTR: Review output and input data objects derived in task 1.1.2;1.1.3.2 Derive a model of functions/behaviors;1.1.3.3 FTR: Review functions/behaviors with customer and revise as required;endtask Task 1.1.31.1.4 Isolate those elements of the technology to be implemented in software; 1.1.5 Research availability of existing software;1.1.6 Define technical feasibility;1.1.7 Make quick estimate of size;1.1.8 Create a Scope Definition;endTask definition: Task 1.1is refined toThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20058Define a Task NetworkI.1ConceptscopingI.3aTech. RiskAssessmentI.3bTech. RiskAssessmentI.3cTech. RiskAssessmentThree I.3 tasks areapplied in parallel to3 different conceptfunctionsThree I.3 tasks areapplied in parallel to3 different conceptfunctionsI.4Proof ofConceptI.5aConceptImplement.I.5bConceptImplement.I.5cConceptImplement.I.2ConceptplanningI.6CustomerReactionIntegratea, b, cThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20059Timeline ChartsTasksWeek 1Week 2Week 3Week 4Week nTask 1Task 2Task 3Task 4Task 5Task 6Task 7Task 8Task 9Task 10Task 11Task 12These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 200510Use Automated Tools toDerive a Timeline ChartI.1.1 Identify need and benefits Meet with customers Identify needs and project constraints Establish product statement Milestone: product statement definedI.1.2 Define desired output/control/input (OCI) Scope keyboard functions Scope voice input functions Scope modes of interaction Scope document diagnostics Scope other WP functions Document OCI FTR: Review OCI with customer Revise OCI as required; Milestone; OCI definedI.1.3 Define the functionality/behavior Define keyboard functions Define voice input