1 540f07reviews9sep25 Pert and Reviews Reviews S&G Chapter 5.

Slides:



Advertisements
Similar presentations
Project Management Concepts
Advertisements

CP Chapter 4 Schedule Planning.
Gantt and PERT charts. Representing and Scheduling Project Plans Gantt Charts Useful for depicting simple projects or parts of large projects Show start.
Damian Gordon.  Static Testing is the testing of a component or system at a specification or implementation level without execution of the software.
Chapter 3 Managing the Information Systems Project
3-1 © Prentice Hall, 2004 Chapter 3: Managing the Object-Oriented Information Systems Project Object-Oriented Systems Analysis and Design Joey F. George,
Scheduling The Project  Scheduling Planning, budgeting and scheduling are all part of the same process Planning a project, developing a budget for it,
Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Tutorial 2 Project Management Activity Charts (PERT Charts)
CS3500 Software Engineering Project Management (1) In 1986 one well-known software engineer (Tom DeMarco) made the simple but important observation: “You.
Software Project Management Lecture # 11. Outline Quality Management ( chapter 26 - Pressman )  Software reviews  Formal Inspections & Technical Reviews.
MGMT 483 Week 8 Scheduling.
2 Project Management  Management of work to develop and implement an innovation or change in an existing organization Examples: –New buildings –Weapon.
1 reviews8 Software Reviews, Walkthroughs, and Inspections The standard technique to ensure quality in software development.
 Every stage from phase DESIGN in Software Development Process will have “design document” especially in analysis and design phases.  “Design document”
Importance of Project Schedules
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Chapter 3 Managing the Information Systems Project
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
1 © Bennett, McRobb and Farmer 2002, and De Montfort University 2002 Based on Chapter 21 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Project Plan The Development Plan The project plan is one of the first formal documents produced by the project team. It describes  How the project will.
Roberta Russell & Bernard W. Taylor, III
Lean Six Sigma: Process Improvement Tools and Techniques Donna C. Summers © 2011 Pearson Higher Education, Upper Saddle River, NJ All Rights Reserved.
Prepared by: Michael Palazzo
HIT241 - TIME MANAGEMENT Introduction
© 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 5 Slide 1 Chapter 3 Managing the Information Systems Project.
Chapter 3 : Managing the Information Systems Project.
PROJECT PLANNING. PLANNING Planning is essential and software development is no exception. Achieving success in software development requires planning.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 Chapter 5 Formulating Solutions: - Project and People Skills.
Galin, SQA from theory to implementation © Pearson Education Limited 2004 Review objectives Formal design reviews (FDRs) Participants Preparations The.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Copyright 2006 John Wiley & Sons, Inc. Beni Asllani University of Tennessee at Chattanooga Project Management Operations Management - 5 th Edition Chapter.
Project Management Project Planning Estimating Scheduling.
Chapter 8 Scheduling © 2012 John Wiley & Sons Inc.
BIS 360 – Lecture Two Ch. 3: Managing the IS Project.
Chapter 17 Project Tracking. Objectives Identify, develop, and use project management tools to track project progress: Schedules Gantt Charts Toll Gate.
CHAPTER 9 INSPECTIONS AS AN UP-FRONT QUALITY TECHNIQUE
1 Material Management Class Note # 6 Project Scheduling & Management Prof. Yuan-Shyi Peter Chiu Feb
University of Palestine software engineering department Testing of Software Systems Program Inspections, Walkthroughs, and Reviews instructor: Tasneem.
Chapter 8 Scheduling © 2012 John Wiley & Sons Inc.
CSCI 521 Final Exam Review. Why Establish a Standard Process? It is nearly impossible to have a high quality product without a high quality process. Standard.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
1 540f07cost10 Question of the Day u How important is it to be able to estimate the cost of a software project?
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
Chapter 3 Managing the Information Systems Project
Project Management Inspections and Reviews 1 February.
Project Management Organization Scheduling 31 January.
Project Time Management
Project Management Why do projects fail? Technical Reasons
Prof.Dr. Ahmet R. Özdural – Class Notes_06 - KMU417 Project Planning and Organization – Fall Semester.
Copyright 2006 John Wiley & Sons, Inc. Beni Asllani University of Tennessee at Chattanooga Project Management Operations Management - 5 th Edition Chapter.
Software Project Management Lecture # 12. Outline Quality Management ( chapter 26 - Pressman )  SQA  Who does it?  SQA Activities  Software reviews.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
IE 366 Chapter 6, Section 10 Project Planning and Scheduling.
Managing the Information Systems Project Cont’d
Management should be based on effective and thorough planning
deterministic Fixed and known in advance, representing a
CHAPTER 6 PROJECT TIME MANAGEMENT
Project Time Management
Reviews & Inspections ... there is no particular reason
PERT - The Program Evaluation and Review Technique
Applied Software Project Management
Review Techniques copyright © 1996, 2001, 2005 R. S
QA Reviews Lecture # 6.
AOA A style of project network diagram in which arrows
Importance of Project Schedules
CHAPTER 6 PROJECT TIME MANAGEMENT
Presentation transcript:

1 540f07reviews9sep25 Pert and Reviews Reviews S&G Chapter 5

2 540f07reviews9sep25 S&G Ch5 Reviews

3 540f07reviews9sep25 Types of reviews u Inspections u Deskchecks u Walkthroughs u Code reviews u Peer Programming

4 540f07reviews9sep25 Example Gannt Chart a1 a2 a3 a4 a5

5 540f07reviews9sep25 PERT Diagrams u Program Evaluation and Review Technique a1 a2 a3 a4 a5

6 540f07reviews9sep25 Critical Path u If there are N tasks with dependencies between the tasks, what set of tasks determines the minimum completion time for the whole project? u This is the critical path.

7 540f07reviews9sep25 Critical Path Algorithm (part 1) u For each node (until completion time of all nodes are calculated) »if the predecessors are completed, then take latest completions time and add required time for this node; »this is the completion time. u The node with the latest completion time determines the earliest completion time for project.

8 540f07reviews9sep25 Example

9 540f07reviews9sep25 Critical Path Algorithm (part 2) u Starting with the node with latest completion time, mark it as critical. u Select predecessor node with latest completion time, mark it as critical. u Continue until reaching start node.

10 540f07reviews9sep25 Example

11 540f07reviews9sep25 Critical Path Algorithm (part 3) u Slack time is the amount of time that a specific task can be delayed without changing the project delivery time u For each noncritical node starting with the last node, determine the earliest of the latest start times of the successor nodes. This is the latest completion time. Make the latest start time for the node to reflect this time.

12 540f07reviews9sep25 Example

13 540f07reviews9sep25 TTYP

14 540f07reviews9sep25 Software Reviews, Walkthroughs, and Inspections The standard technique to ensure quality in software development

15 540f07reviews9sep25 Peer Review u the primary function is to use the skill of a group of people to: – 1) identify needed improvements – 2) certify correctness – 3) encourage uniformity – 4) enforce subjective rules

16 540f07reviews9sep25 Management u secondary functions include: » 1) communication » 2) milestone » 3) visibility to management

17 540f07reviews9sep25 Progress u additional function (and not the least) is to force preparation of materials and specification of ideas.

18 540f07reviews9sep25 Review – two definitions u A formal, scheduled activity where a designer presents material about a design and a selected group of peers evaluates the technical aspects of the design. u The inclusive name for reviews, walkthroughs, and inspections

19 540f07reviews9sep25 Types of Reviews u Reviews – Requirement (SRR) – Design (PDR,CDR) u Walkthroughs u Inspections – Code – Document

20 540f07reviews9sep25 Walkthrough u A formal, scheduled activity where a designer presents a design and traces the values of sample data through the design and a selected group of peers evaluates the technical aspects of the design. u Pressman does not distinguish from other reviews

21 540f07reviews9sep25 Inspection u A formal, scheduled activity where a specialist checks a document for conformity with established standards (often corporate standards)

22 540f07reviews9sep REVIEWS u Professionalism – be prepared – be organized – present good image u Materials in advance u TA and Instructor serve as evaluators u Team is graded on quality of effort, professionalism, and following standards u Usually 50 minutes (except presentation 1)

23 540f07reviews9sep25 Procedures for Reviews u The evaluators prepare for the review by studying the prepared documents. u A formal report on the review is often required by management.

24 540f07reviews9sep25 Conduct of Reviews 1 schedule review 2 distribute materials 3 prepare 4 present 5 discuss 6 report

25 540f07reviews9sep25 Rules for Reviews – proper constructive attitude – proper preparation – proper environment – no management – participants should be participants – producers should determine time – distribute reports fast – record all issues in public

26 540f07reviews9sep25 Rules for Reviewers – prepare – be friendly – watch comments – one positive comment, one negative – raise issues, don't solve them – avoid style issues – stick to standards – stick to technical issues – make certain that everybody understands – do not evaluate producers

27 540f07reviews9sep25 Thursday, Sep 27 u Read S&G ch 3