238x Filetype PDF File size 0.61 MB Source: courses.acs.uwinnipeg.ca
This class- Chapter 14 and 15 Lecture 11 (Scheduling) Dr. Sheela Ramanna Applied Computer Science University of Winnipeg Introduction and Terminology Competencies and Definitions, SDLC Chap.1 and 3 Jan 7 Selecting SDLC -- Review of Process Models Chap. 4 Jan 12 Process Models Jan 14 Planning and Organization Project Teams and Roles --Team Selection Chap.6, 12, 29 Jan. 19 Project Planning and WBS – Proj.Proposal/Charter Chap.7 and 8 Jan. 21 Tasks, Activities -- Project Plan Creation +Review Chap. 9 Jan. 26 Quiz 1 Jan. 28 Software Sizing – Size Estimation Models Chap.10 Feb. 2 Software Sizing – Size Estimation Models Feb 4 Estimating Duration and Cost Chap. 11 Feb 9 Estimating Duration and Cost Feb.11 Reading Week Break Feb. 14-20 Problem Solving Class – Sizing and Estimation Feb. 23 Quiz 2 Feb. 25 Scheduling – PERT/CPM Scheduling Models Chap. 14 and 15 Mar. 2 Requirements Specification—Creating SSR Chap. 16 and 17 Mar. 4 Problem Solving Class -PERT Mar. 9 Risk Management – Quantitative Risk Assessment Chap. 18 Mar. 11 Software Metrics –Product and Process Metrics Chap. 21 Mar.16 Software Metrics Metrics Continued Chap. 21 Mar. 18 Problem Solving Class -Metrics Mar. 23 V&V- Testing strategies, test coverage and path Chap. 23 Mar. 25 measures Monitoring and Control Project Tracking and Control Chap. 25 Mar. 30 SQA and SCM Chap. 30, 31 April 1 Problem Solving (V&V) + Review April 6 Why a schedule It reflects all the relationships of activities as best understood by a team mapped into a real- world calendar and includes true productive working hours allows for inevitable uncertainty A planned schedule is “just” a team’s best guess of the future Number of ways to represent a schedule Table (non-graphical and is a list of activities with a start and finish date) GANTT (graphical and provides a good high-level view of the project schedule (phases/sub phases) PERT/CPM can be used for analysis of a schedule. Also called as networking diagrams that can be used to show precedence) Process for building a “real” schedule 1. Develop the WBS What activities must be done Who will do each one [What materials/supplies are required? How much will it cost] -- costing aspect 2. Identify activity dependencies What can be done first? What can be done next? Parallel activities 3. Develop a network diagram (PERT) from WBS and dependency information 4. Do CPM analysis computations (time) ED, ECT, LCT Is the total project durations acceptable? 5. Find and analyze critical path activities 6. Perform resource allocation 7. Convert the network to Gantt chart
no reviews yet
Please Login to review.