2. TCS2411 Software Engineering1 Project Plan “What are you going to do in the project?”

3. TCS2411 Software Engineering2 Lecture Objectives zTo discuss the tasks in planning a project zTo describe the tools that can be used for developing a project plan zTo illustrate the use of graphical representations of project activities zTo understand the importance of the critical path in scheduling

4. TCS2411 Software Engineering3 Planning Meaning: “Organizing project in logical order and Identifying and defining work activities in a manner that help achieve project objectives”

5. TCS2411 Software Engineering4 Basic Reasons for Planning zTo element/reduce uncertainty zTo improve efficiency of the operation zTo provide better understanding zTo provide a basis for monitoring and controlling work

6. TCS2411 Software Engineering5 Project Planning and Control System Time/Cost/ Performance Tracking Goals/ Objectives Work Description and Instructions Management Decision- Making System Reports Network Scheduling Master/ Detailed Schedules Budgets

7. TCS2411 Software Engineering6 Planning Steps 1.Establish objectives 2.Develop a plan 3.Construct project planning diagram 4.Identify timing duration of each activity in planning diagram 5.Identify costs and labor/personnel associated with each activity

8. TCS2411 Software Engineering7 Establish Objectives zState objectives yProject start/end dates yBudgets yTechnical results zList milestones zMilestone: a scheduled event for which some person is held accountable and which is used to measure and control progress. zDesignate responsible personnel to meet objectives

9. TCS2411 Software Engineering8 Develop A Plan zList activities zDevelop Work Breakdown Structure (WBS): The WBS reflects the decomposition of a project into subtasks down to the level for effective planning and control. zDetermine relationships of activities yjob precedence/succession yconcurrent jobs

10. TCS2411 Software Engineering9 Work Breakdown Structure zBreak project tasks into successively finer levels: Program - Project - Task - Work Package - Work Unit zEach work unit yshort time span yspecific start & end point ybudgetable in terms of money, resources ycan be assigned an individual responsibility ycan be scheduled

11. TCS2411 Software Engineering10 Purpose of WBS zManageable zIndependent zIntegratable zMeasurable

12. TCS2411 Software Engineering11 WBS Example ABC Project ProgrammingDesignAnalysisDefinition Risk Analysis Feasibility Study Requirements Documentation... Level 1 Level 2 Level 3

13. TCS2411 Software Engineering12 WBS of a simple project Design Test plan Code Test Project Code A Code B Each activity has a duration and consumes resources. Each activity has a constraint(example: one must be finished before the other starts; so activities are executed in order).

14. TCS2411 Software Engineering13 Program Evaluation and Review Technique (PERT) diagram The numerical number represents the duration of each activity. PERT is mainly concerned with time of each activity and interrelations among activities. Design 15 Test plan 10 Test 15 Code A 18 Code B 18

15. TCS2411 Software Engineering14 Critical Path Method (CPM) zBy drawing a network diagram, you can figure out the critical path of your project. zThe critical path is the longest path through the network. If something falls behind schedule on the critical path, the whole project falls behind schedule unless time is made up elsewhere. zIt’s easier to adjust other activities (allocate more/less resources) when you know the interdependencies of activities

16. TCS2411 Software Engineering15 Construct Project Planning Diagram zDraw the logical sequence of activities zPrecedence Diagramming Method (PDM) yActivity on Node (AON) zArrow Diagramming Method (ADM) yActivity on Arrow (AOA)

17. TCS2411 Software Engineering16 Terms zActivity - A task or job which takes time & use up resources Represented by labeled arrowA zEvent - An instantaneous point representing the start or finish of an activity Represented by node zSlack time: indicates that the corresponding activity may consume more than its estimated time, or start later than the earliest possible start time, without affecting the total duration of the project. zCritical path: a path that has activities without any slack time 1

18. TCS2411 Software Engineering17 Activity-on-Arrow (AOA) Diagram G 1 25 3 4 6 B C A F E D Each activity has only one arrow associated with it.

19. TCS2411 Software Engineering18 Activity Precedence

20. TCS2411 Software Engineering19 Network Characteristics zConstruct from left to right zAny activity can have only one start node zNo two activities can have the same start and end node zDummy activities are used in AOA zStart the network by finding those activities that have no predecessors zCalculate activity times using probabilistic or deterministic means

21. TCS2411 Software Engineering20 Dummy Activity zRepresented by dotted arrow zUsed when relationships between activities require no work zApplied when ytwo activities start and end similarly ysucceeding activities have partial dependencies on predecessor activities

22. TCS2411 Software Engineering21 PERT and CPM PERT zR&D Development zOriginally focused on time only zUses probabilistic time estimates zAOA based zCritical path & slack CPM zConstruction zTime and Cost zUses deterministic time estimates zAON based zCritical path & slack zUsed in most software

23. TCS2411 Software Engineering22 GANTT Charts zHorizontal time representation of PERT/CPM, aka Timeline charts zSlack times shown as dashed lines zCritical path events are often milestones zInadequate for showing dependencies zPERT/CPM is required to control the schedule zCan be used as a scheduling mechanism.

24. TCS2411 Software Engineering23 Gantt Chart Example A D B C E F G time Milestone

25. TCS2411 Software Engineering24 Project Planning Summary Objectives Scope Specs Organizational Structure WBS Responsibility Chart Work Packages Networks Technical Criteria Project Plan Material & Manpower Schedules Documentation

26. TCS2411 Software Engineering25 Decision Tree Analysis zSoftware engineering managers are often faced with a make/buy decision to acquire a computer software. zThis decision can be solve by computing Decision Tree Analysis. zExample : System X, can be build (in- house developer), reuse, buy or contract (employees outside vendor).

27. TCS2411 Software Engineering26 The Make-Buy Decision

28. TCS2411 Software Engineering27 Computing Expected Cost (path probability) x (estimated path cost) (path probability) x (estimated path cost) i i For example, the expected cost to build is: expected cost = 0.30($380K)+0.70($450K) similarly, expected cost = $382K expected cost = $267K expected cost = $410K build reuse buy contr expected cost = = $429 K

29. TCS2411 Software Engineering28 References z“Software Engineering: A Practitioner’s Approach” 5th Ed. by Roger S. Pressman, Mc-Graw-Hill, 2001 z“Project Management: A Managerial Approach” by Jack R. Meredith & Samuel J. Mantel, Jr., John Wiley, 1989 z“Project Management: Principles and Practices” by M. Pete Spinner, Prentice-Hall, 1997 z“Goal Directed Project Management”, 2nd Edition, by Erling S. Andersen, Kristoffer V. Grude & Tor Haug, Kogan Page, 1995