1 / 16

CEN 4021 Software Engineering II

CEN 4021 Software Engineering II. Software Project Planning ( P OMA) Task Scheduling. Instructor: Masoud Sadjadi http://www.cs.fiu.edu/~sadjadi/ sadjadi@cs.fiu.edu. Acknowledgements. Dr. Onyeka Ezenwoye Dr. Peter Clarke. Agenda. Software Project Planning ( P OMA) Task Scheduling.

gosselin
Download Presentation

CEN 4021 Software Engineering II

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CEN 4021 Software Engineering II • Software Project Planning (POMA) • Task Scheduling Instructor: Masoud Sadjadi http://www.cs.fiu.edu/~sadjadi/ sadjadi@cs.fiu.edu

  2. Acknowledgements • Dr. Onyeka Ezenwoye • Dr. Peter Clarke

  3. Agenda • Software Project Planning (POMA) • Task Scheduling

  4. Task Sequence and Effort representation • All tasks share at least two basic characteristics • Require effort in terms of person-days required to complete each task • A specified order for processing the task

  5. Task sequence/effort table Total effort required: 40 person-days

  6. Graphical representation of tasks from previous table Task B 5 9 Task A Task D 11 Task E 8 End 9 7 Task C Critical Task Critical Path Non-critical Task Total project time: 35 days Non-critical Path

  7. Critical versus Non-Critical Paths Critical path • The path that takes the most time to complete. Critical task (critical activity) • A task that resides on the critical path. Non-critical path • Any path that is not a critical path and thus takes less effort to complete than the critical path. Non-critical task (non-critical activity) • Any activity that resides on a non-critical path and not a critical path. These tasks may accept some delay in completion.

  8. Critical Path Method (CPM) “The critical path method analyses the precedence of activities to predict the total project duration. The method calculates which sequence activities (path) has the least amount of flexibility” • Quality Software Project Management, Futrell et. al.

  9. Task Scheduling • Forward-pass scheduling • Early start time (ES) and early finish (EF) • Backward-pass scheduling • Late start (LS) and Late finish (LF) • Slack time

  10. Forward-pass scheduling 9 9 14 9 16 16 27 27 35

  11. Backward-pass scheduling 9 0 11 16 9 16 16 27 27 35

  12. Slack time • Total slack time of an activity • The difference in start time between a non-critical task’s late start time and its early start time or its late finish time and early finish time. Total slack time of a task = LS - ES Or Total slack time of a task = LF – EF e.g., Activity B: LS – ES (11 - 9) or LF – EF (16 - 14) => 2 • Total slack time • The maximum allowable delay for all non-critical activities.

  13. Program Evaluation and Review Technique (PERT) • An estimating technique • assumes each activity duration is subject to a range estimates • uses weighting method to arrive at a specific duration.

  14. Program Evaluation and Review Technique (PERT) Expected estimate (EE) = [O + P + (4 x A)] / 6 Where O = most optimistic estimate P = most pessimistic estimate A = most likely estimate

  15. Program Evaluation and Review Technique (PERT) Expected Project time (EPT) • Sum of expected estimates of the critical tasks. EPT = Σ(EE of all critical task)

  16. CPM vs PERT • Scheduling a lot of activities with 3 estimates computationally messy • many people argue 3 estimates are not much more accurate than 1 estimate • Most project management scheduling software use CPM

More Related