CS 160: Software Engineering October 20 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak www.cs.sjsu.edu/~mak.

Slides:



Advertisements
Similar presentations
Project Management Concepts
Advertisements

Gantt Chart.
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,
© 2005 by Prentice Hall Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Scheduling The Project  Scheduling Planning, budgeting and scheduling are all part of the same process Planning a project, developing a budget for it,
© 2008 by Prentice Hall 3-1 ITCS311 Systems Analysis and Design Dr. Taher Homeed Feb 2010 Department of Computer Science College of IT University of Bahrain.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
CS3773 Software Engineering Lecture 8 Software Planning and Estimation.
2 Project Management  Management of work to develop and implement an innovation or change in an existing organization Examples: –New buildings –Weapon.
Project Management.
Project management A whistle-stop tour Toot!. Places to see Overview Project design in detail Task analysis example Design documentation examples Terminus.
COMP2001 HNC Project. Project Characteristics A project must have: clear objectives planning & control resources assurance of quality.
S N R E University of Michigan Announcements 1. 1.Pick project treasurer All treasurers have group meeting with Mary M. in SNRE business office soon.
Project Management 30 January. Odds and ends Tournament on the webweb In the newsnews.
Chapter 3 Managing the Information Systems Project
CS Techniques Supporting Project Management (Part 4) Bilgisayar Mühendisliği Bölümü – Bilkent Üniversitesi – Fall 2009 Dr.Çağatay ÜNDEĞER Instructor.
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.
CS 153: Concepts of Compiler Design October 27 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak
Project Scheduling & Budgeting CEE 402 Engineers Without Frontiers Lecture 6 February 26, 2003.
Managing Project Scheduling. What is Project Scheduling? The process of: – defining project activities – determining their sequence – estimating their.
MS-Project tutorial Phongphan Danphitsanuphan CSSE – Computer Science Dept University of Southern California.
GANTT Charts. What is a GANTT chart? A Gantt chart is a type of bar chart that illustrates a project schedule. Gantt charts illustrate the start and finish.
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.
© 2005 by Prentice Hall 3-1 Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Fourth Edition.
PROJECT PLANNING. PLANNING Planning is essential and software development is no exception. Achieving success in software development requires planning.
Open Workbench By Wilmer Arellano Spring Statement Of Work (SOW) A statement of work (SOW) is a document used in the Project Development Life Cycle.
Year 11 Info Tech Project Management Overview. Project management overview identifying tasks, resources, people and time scheduling tasks, resources,
Copyright 2006 John Wiley & Sons, Inc. Beni Asllani University of Tennessee at Chattanooga Project Management Operations Management - 5 th Edition Chapter.
EGNR 300 Project Management Planning & Scheduling ENGR 300 Dept. of Computer Science and Engineering University of Bridgeport,
Week 6: Project Management E1102 – Design Fundamental Using Advanced Computer Technologies Spring 2010.
Lecture 3 Scheduling CSCI – 3350 Software Engineering II Fall 2014 Bill Pine.
CS 235: User Interface Design October 15 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak
Software Project Management
Ch. 41 Project control. Ch. 42 Work Breakdown Structure WBS describes a break down of project goal into intermediate goals Each in turn broken down in.
WEEK 4 Introduction to Project Management. Agenda Phase 2: Planning ◦ Communication Plan ◦ Scheduling Preparation  Build an AON Diagram  Determine Critical.
Project Management Formal Methods. How do you monitor a project?
CS 235: User Interface Design September 22 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak
Geog 469 GIS Workshop Project Management.
CS 160: Software Engineering October 15 Class Meeting
PLANNING ENGINEERING AND PROJECT MANAGEMENT
PRJ566 Project Planning & Management Work Breakdown Structure.
Program Evaluation and Review Technique
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design.
PRJ566 Project Planning & Management Dependencies, Network Diagrams & Critical Path.
CS 160: Software Engineering December 10 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
Chapter 3 Managing the Information Systems Project
Project Management Organization Scheduling 31 January.
A Recipe for Preparing a Schedule that Works Ulla Merz prepared for MPUG phone: (303)
CON 2001 Construction Methods Tool #1 - Construction Scheduling Presented by Elia Twigg, P.E. (Prof. Ralph V. Locurcio, P.E.)
CS 235: User Interface Design March 17 Class Meeting Department of Computer Science San Jose State University Spring 2015 Instructor: Ron Mak
CS 157B: Database Management Systems II April 22 Class Meeting Department of Computer Science San Jose State University Spring 2013 Instructor: Ron Mak.
Copyright 2006 John Wiley & Sons, Inc. Beni Asllani University of Tennessee at Chattanooga Project Management Operations Management - 5 th Edition Chapter.
CS 160 and CMPE/SE 131 Software Engineering March 22 Class Meeting Department of Computer Science Department of Computer Engineering San José State University.
IT-301 Project Management I: Unit 4: Cost Management.
CS 160 and CMPE/SE 131 Software Engineering May 12 Class Meeting Department of Computer Science Department of Computer Engineering San José State University.
SOW / Open Workbench By Wilmer Arellano Spring 2008.
CS 160 and CMPE/SE 131 Software Engineering March 24 Class Meeting Department of Computer Science Department of Computer Engineering San José State University.
Project Management Planning and Scheduling. “Failing to plan is planning to fail” by J. Hinze, Construction Planning and Scheduling Planning: “what” is.
Project Planning Ing. Athanasios Podaras, Ph.D Faculty of Economics Department of Informatics Technical University of Liberec.
Managing the Information Systems Project Cont’d
Chapter 3 Managing the Information Systems Project
CE 332 – Construction Engineering and Management
Business System Development
Chapter 3 Managing the Information Systems Project
Gantt Chart.
CMPE/SE 131 Software Engineering March 23 Class Meeting
Presentation transcript:

CS 160: Software Engineering October 20 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak

Computer Science Dept. Fall 2014: October 20 CS 160: Software Engineering © R. Mak Tesla Motors Headquarters Visit  Palo Alto  Friday afternoon, November 14  See Piazza for details! 2

Computer Science Dept. Fall 2014: October 20 CS 160: Software Engineering © R. Mak 3 “Good” Estimates  Estimates don’t need to be perfectly accurate as much as they need to be useful. “A good estimate is an estimate that provides a clear enough view of the project reality to allow the project leadership to make good decisions about how to control the project to hit its targets.” Steve McConnell, Software Estimation

Computer Science Dept. Fall 2014: October 20 CS 160: Software Engineering © R. Mak 4 Work Breakdown Structure (WBS)  A decomposition of a complex project into a hierarchical set of tasks and subtasks.  Can be shown in outline form or as a tree. Project Subtask 1.1 Subtask 1.2 Subtask 2.1Subtask 3.1 Subtask 3.2 Subtask 3.3 Task 1Task 2Task 3

Computer Science Dept. Fall 2014: October 20 CS 160: Software Engineering © R. Mak 5 WBS Example: Building a House  Architectural design Create draft of architecture Prepare construction documents  Interior design Pre-design Select furniture Plan equipment  Construction phase Build foundation Build ground floor Build second second floor Build roof Complete wiring and plumbing  Decoration phase Walls Furniture

Computer Science Dept. Fall 2014: October 20 CS 160: Software Engineering © R. Mak 6 Project Schedule  Often represented as Gantt charts. Named after Henry Gantt, who developed them in  Enter the work breakdown structure.  Estimate the time requirement for each task (task duration).  Set task dependencies.  Assign task resources.

Computer Science Dept. Fall 2014: October 20 CS 160: Software Engineering © R. Mak 7 Project Schedule, cont’d  Once estimates are put into a schedule, they become commitments.  However, schedules can change (i.e., slip)... up to a point!

Computer Science Dept. Fall 2014: October 20 CS 160: Software Engineering © R. Mak 8 Example Gantt Chart WBSTime Resources Dependencies Milestones Progress

Computer Science Dept. Fall 2014: October 20 CS 160: Software Engineering © R. Mak 9 Gantt Chart Demo  Download and install GanttProject from  Demo Task creation Task dependencies Resources

Computer Science Dept. Fall 2014: October 20 CS 160: Software Engineering © R. Mak Assignment #4  Create a project schedule as a Gantt chart for your team.  Due Monday, October

Computer Science Dept. Fall 2014: October 20 CS 160: Software Engineering © R. Mak 11 Critical Path  Identify the critical path of a schedule. The longest path of tasks The “long pole in the tent”  The critical path determines the shortest possible time to complete the project.  Any delay in the critical path directly delays the completion of the overall project.

Computer Science Dept. Fall 2014: October 20 CS 160: Software Engineering © R. Mak 12 PERT Chart  Project Evaluation and Review Technique  Represent the schedule as an acyclic graph of tasks.  Demo PERT chart Critical path

Feedback: Privacy Policy Feedback
Do Not Sell My Personal Information
About project: SlidePlayer Terms of Service

© 2024 SlidePlayer.com Inc. All rights reserved.