Presentation is loading. Please wait.

Presentation is loading. Please wait.

CS 160 and CMPE/SE 131 Software Engineering March 24 Class Meeting Department of Computer Science Department of Computer Engineering San José State University.

Published byDennis Scott Modified over 8 years ago

Similar presentations

Presentation on theme: "CS 160 and CMPE/SE 131 Software Engineering March 24 Class Meeting Department of Computer Science Department of Computer Engineering San José State University."— Presentation transcript:

1 CS 160 and CMPE/SE 131 Software Engineering March 24 Class Meeting Department of Computer Science Department of Computer Engineering San José State University Spring 2016 Instructor: Ron Mak www.cs.sjsu.edu/~mak

2 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak Please send me your PowerPoint slides … … from your conceptual design review so I can post them to the class website. Send me your marketing brochure if you haven’t already done so. 2

3 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak 3 Project Team Design Reviews  Present and defend key aspects of your design. CS 160: 15 minutes per team. CmpE 131: 12 minutes per team.  Use PowerPoint slides Turn in your slides after your presentation.  Briefly discuss your overall design.  Show and explain the design of your most important or core classes. UML class diagrams and/or sequence diagrams.

4 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak 4 Project Team Design Reviews, cont’d  Briefly discuss your database design. ER diagram Relational schema diagram (optional)  Questions and answers at the end.  Audience: Very technical Other development engineer Technical managers Expect “deep” questions from the audience!

5 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak Project Team Design Reviews, cont’d  Presentation schedule, CS 160-01  Tuesday, April 5 Ruby Baby Softneers TBA Underground Railsroad  Thursday, April 7 Big Trains Code-Ninjas NoName Revy 5

6 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak Project Team Design Reviews, cont’d  Presentation schedule, CS 160-02  Tuesday, April 5 Spartans on Rails SpartanSE The A Team The Directors  Thursday, April 7 Face Green Hacking Bad Mak & Cheese 6

7 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak Project Team Design Reviews, cont’d  Presentation schedule, CMPE 131-01 7  Tuesday, April 5 NoName4 Piramides Rubber Ducks RubyLand Sour Patch Kids Unispace  Thursday, April 7 ARMY Codiggers Cupid’s Minions Fabulous Gains JAMH

8 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”  Excerpts from “10 Deadly Sins of Software Estimation” by Steve McConnell http://www.ewh.ieee.org/r5/central_texas/austin_cs/p resentations/2004.08.26.pdf http://www.ewh.ieee.org/r5/central_texas/austin_cs/p resentations/2004.08.26.pdf 8

9 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”, cont’d 9

10 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”, cont’d 10

11 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”, cont’d 11

12 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”, cont’d 12

13 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”, cont’d 13

14 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”, cont’d 14

15 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”, cont’d 15

16 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”, cont’d 16

17 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”, cont’d 17

18 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”, cont’d 18

19 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”, cont’d 19

20 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”, cont’d 20

21 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”, cont’d 21

22 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”, cont’d 22

23 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”, cont’d 23

24 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”, cont’d 24

25 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”, cont’d 25

26 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak “Sins of Software Estimation”, cont’d 26

27 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak Sins of Software Estimation, cont’d 27

28 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak 28 “Good” Estimates  Estimates don’t need to be perfectly accurate as much as they need to be useful.  Once estimates are put into a schedule, they become commitments. “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

29 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak Example Project Schedule: Gantt Chart 29 Critical path

30 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak Example Project Schedule: PERT Chart 30

31 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak Example Project Schedule: Resources Chart 31

32 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak 32 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

33 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak 33 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 floor Build roof Complete wiring and plumbing  Decoration phase Walls Furniture

34 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak 34 Project Schedule  Often represented as Gantt charts. Named after Henry Gantt, who developed them in 1917.  Enter the work breakdown structure.  Estimate the time requirement for each task (task duration).  Set task dependencies.  Assign task resources.

35 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak 35 Example Gantt Chart WBSTime Resources Dependencies Milestones Progress

36 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak 36 Gantt Chart Demo  Download and install GanttProject from http://ganttproject.biz/ http://ganttproject.biz/ Watch the introductory video. Similar to (the very expensive) Microsoft Project.  Demo Task creation Task dependencies Resources

37 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak 37 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. Demo

38 Computer Science Dept. Spring 2016: March 24 CS 160 and CMPE/SE 131: Software Engineering © R. Mak 38 PERT Chart  Project Evaluation and Review Technique  Represent the schedule as an acyclic graph of tasks. Demo

Download ppt "CS 160 and CMPE/SE 131 Software Engineering March 24 Class Meeting Department of Computer Science Department of Computer Engineering San José State University."

Similar presentations

Project Management Concepts

Project Management Concepts
Chapter 3 Managing the Information Systems Project

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,

3-1 © Prentice Hall, 2004 Chapter 3: Managing the Object-Oriented Information Systems Project Object-Oriented Systems Analysis and Design Joey F. George,
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.

Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.

Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
© 2005 by Prentice Hall Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.

© 2005 by Prentice Hall Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
© 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.

© 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.

Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
CS3773 Software Engineering Lecture 8 Software Planning and Estimation.

CS3773 Software Engineering Lecture 8 Software Planning and Estimation.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.

Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Project Management.

Project Management.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.

Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Project management A whistle-stop tour Toot!. Places to see Overview Project design in detail Task analysis example Design documentation examples Terminus.

Project management A whistle-stop tour Toot!. Places to see Overview Project design in detail Task analysis example Design documentation examples Terminus.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.

Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
COMP2001 HNC Project. Project Characteristics A project must have: clear objectives planning & control resources assurance of quality.

COMP2001 HNC Project. Project Characteristics A project must have: clear objectives planning & control resources assurance of quality.
Chapter 3 Managing the Information Systems Project

Chapter 3 Managing the Information Systems Project
CS-413 1 Techniques Supporting Project Management (Part 4) Bilgisayar Mühendisliği Bölümü – Bilkent Üniversitesi – Fall 2009 Dr.Çağatay ÜNDEĞER Instructor.

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 Management and Scheduling

Project Management and Scheduling
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.

CS 160: Software Engineering October 20 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak
Managing Project Scheduling. What is Project Scheduling? The process of: – defining project activities – determining their sequence – estimating their.

Managing Project Scheduling. What is Project Scheduling? The process of: – defining project activities – determining their sequence – estimating their.

Similar presentations

Ads by Google