CSE-332 Software Design Methods The Mythical Man-Month 박성우 POSTECH October 20, 2015.

Slides:



Advertisements
Similar presentations
Ch.1 Introduction to Software Engineering The Evolution 1.1 The Evolving Role of Software 1/15 In the early days: User Computer Software = Place a sequence.
Advertisements

EEL5881 software engineering I Mythical man-month lecture
Effort metrics: Man-month. Mythical Man Month – the book Brooks lead development of OS/360 and reflected on the problems experienced in the project. The.
Robert Lockyer.
Project Management Information Systems and Management.
Lecture 2 Team Coordination 1 ICS 126 Team Coordination Team Formation and Organization Group Management Meeting Techniques Large software systems require.
brought to you by: jeremy miller brought to you by: jeremy miller.
CIS-74 Computer Software Quality Assurance Systematic Software Testing Chapter 1: An Overview of the Testing Process.
The Mythical Man-Month By: Zac Lippard CS 470. What is the “Man-Month”? This is the idea that men and months are interchangeable between each other. This.
Software Engineering Teams Group 3 presents: Teamwork is the ability to work together toward a common vision. The ability to direct individual accomplishments.
OPEN DEVELOPMENT, AGILE, XP AND SCRUM © University of LiverpoolCOMP 319slide 1.
The Surgical Team A different kind of team build By Chris Bradney A different kind of team build By Chris Bradney.
Informatics 43 – April 21, Things to know Midterm on Thursday – Closed book, closed notes, bring pen/pencil – Questions available on web site (updated)
Informatics 43 – May 12, Restatement of Goals for Testing Want to verify software’s correctness  Need to test  Need to decide on test cases 
Chapter 1: Key Points Program = Useful to the programmer in the garage Programming Product = Useful to anyone Programming System Component = Part of a.
University of Southern California Center for Systems and Software Engineering ©USC-CSSE1 3/18/08 (Systems and) Software Process Dynamics Ray Madachy USC.
CS351 © 2003 Ray S. Babcock Cost Estimation ● I've got Bad News and Bad News!
CS CS 5150 Software Engineering Lecture 27 People 2.
CS189A/172 - Winter 2008 Lecture 5: Project Management.
The Mythical Man-Month Due Today: Code & Coding Standards Due Next Class: Quiz #3; see webpage Mythical Man-Month I Bio Break Mythical Man-Month II Questions.
Team Models Two early philosophies –Decentralized/democratic –Centralized/autocratic Variation –Controlled Decentralized
CSE Software Design and Engineering Jonathan M. Smith
Mythical Man Month Fred Brooks, Why are software projects late? Estimating techniques are poorly developedEstimating techniques are poorly developed.
SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION © University of LiverpoolCOMP 319slide 1.
CSE 230: Introduction to Software Engineering Topics covered: Introduction.
SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION © University of LiverpoolCOMP 319slide 1.
Cost Estimation Van Vliet, chapter 7 Glenn D. Blank.
Information System Economics Software Project Cost Estimation.
ITEC 370 Lecture 15 Implementation. Review Questions? Draft of design document on F Brief 3-5 minute work update on F (will continue except for mid-term)
Why is software engineering worth studying?  Demand for software is growing dramatically  Software costs are growing per system  Many projects have.
6-January-2003cse Introduction © 2003 University of Washington1 Introduction CSE 403, Winter 2003 Software Engineering
CSC 354 – Software Engineering, Spring 2013, Week 2 Mythical Man-Month Ch. 1-5 Tar Pit, Mythical Man-Month, Surgical Team, Aristocracy / Democracy & System.
The Mythical Man-Month the MYTH behind the REAL
Slide TMMM.1/28 The Mythical Man-Months. Slide TMMM.2/28 Overview Fred Brooks and OS/360 The Mythical Man-Month What has and has not changed? No Silver.
By Justin hendrix. Chapter 1: The Tar Pit Chapter one is about making a good project that won’t get stuck in the “tar pit.” That is it must be flexible.
Slide 1 Teams l Most products are too large to be completed by a single software professional with the given time constraints l You will work within a.
©Ian Sommerville 2000 Slide 1 Project management l Organising, planning and scheduling software projects l Objectives To introduce software project management.
Managing Resources Program Evaluation and Review Technique (PERT) Production Process.
Project Schedules Chapter 4 Applied Software Project Management, Stellman & Greene See also:
CMSC 345 Fall 2000 Software Design and Development.
Mythical Man Month By Ryan Ruzich.  More software projects have gone awry for lack calendar time than all other reasons combined.
Software Engineering At Glance. Why We Need Software Engineering? The aim of software engineering is to solve the software crisis Software is delivered.
CSE SW Project Management / Module 15 - Introduction to Effort Estimation Copyright © , Dennis J. Frailey, All Rights Reserved CSE7315M15.
Software Engineer Basic IntroductionJob ClassificationCompetenciesJob OverviewJob content.
Student Startup Sequence Verify network connection Rotate to Landscape mode Start Presenter 2.0 Maximize Application Role->Student Connect->Classroom 1.
Chapter Three The Surgical Team. The Problem Large Group – 10:1 productivity and 5:1 program speed and space management. – Negative aspect Sheer number.
Chapter Eighteen Proposition of the Mythical Man Month: True or False?
CSE 403 Lecture 25 Scheduling and Planning a Large Project Reading: The Mythical Man-Month, Ch. 2, by F. Brooks slides created by Marty Stepp
CSE403 Software Engineering Autumn 2001 Project Management Gary Kimura and Will Portnoy Lecture #10 October 18, 2000.
PI2134 Software Engineering IT Telkom.  Software definition  Characteristic of software  Software myths  Software Engineering definition  Generic.
1 / 28 CS 425/625 Software Engineering Managing People Based on Chapter 22 of the textbook [Somm00] Ian Sommerville, Software Engineering, 6 th Ed., Addison-Wesley,
CSE403 Software Engineering Autumn 2000 Project Management Gary Kimura Lecture #10 October 16, 2000.
CS 501: Software Engineering Fall 1999 Lecture 20 Management III Managing People.
Copyright , Dennis J. Frailey CSE7315 – Software Project Management CSE7315 M15 - Version 9.01 SMU CSE 7315 Planning and Managing a Software Project.
The Surgical Team Jacob Harper. The Problem Good Programmer vs Poor Programmer  10 times more productive 200 man project  25 manager, 175 programmers.
Software Engineering, COMP201 Slide 1 Software Engineering CSE470.
Estimation Questions How do you estimate? What are you going to estimate? Where do you start?
Project Management A Practical Approach Sridhar Pandurangiah Director - Engineering Sridhar Pandurangiah Director - Engineering.
Why is software engineering worth studying?
Software Project Management
Informatics 43 – May 10, 2016.
THE MYTHICAL MAN-MONTH
Informatics 43 – April 19, 2016.
© Ian Davis 2017 Spring (c) Ian Davis.
Informatics 43 Discussion 13 May, 2016
Nuggets from The Mythical Man-Month Fred Brooks University of North Carolina at Chapel Hill ONR_Updated.
Cost Estimation I've got Bad News and Bad News!.
Cost Estimation Van Vliet, chapter 7 Glenn D. Blank.
CSE 403 Scheduling These lecture slides are copyright (C) Marty Stepp, 2007, with significant content taken from slides written by Valentin Razmov. They.
Presentation transcript:

CSE-332 Software Design Methods The Mythical Man-Month 박성우 POSTECH October 20, 2015

The Mythical Man-Month Book on software engineering and project management Book on the human elements of software engineering “The Bible of Software Engineering” Everybody quotes it. Some people read it. A few people go by it.

Mythical Man-Month All programmers are optimist. “all will go well” For a large programming effort, the probability becomes vanishingly small. The man-month as a unit for measuring the size of a job? a dangerous and deceptive myth valid only when there is no communication among workers communication = training + intercommunication

Brooks’s Law “Adding manpower to a late software project makes it later.” The number of months of a project depends on its sequential constraint. We can derive schedules using fewer men and more months. We cannot derive schedules using more men and fewer months. Most software projects have gone awry for lack of calendar time.

Productivity Variations Measured performance of a group of experienced programmers Ratios between best and worst performances: 10:1 on productivity measurements 5:1 on program speed and space measurements A $20,000/year programmer may well be 10 times as productive as a $10,000/year programmer.

As Few Minds As Possible One wants a system to be built by as few minds as possible. If a 200-man project has 25 managers who are the most competent, then fire the 175 troops and put the managers back to programming! The Ideal of the small sharp team, which by common consensus shouldn’t exceed 10 people. But we want to use considerable manpower. Goal: Few minds are involved in design and construction, yet many hands are brought to bear.

Surgical Team Surgeon: chief programmer defines specifications needs great talent, ten years of experience, considerable knowledge unilaterally settles all differences of judgments Copilot: alter ego of the surgeon, but less experienced knows all the code intimately researches alternative design strategies insurance against disaster to the surgeon Toolsmith: see to the tools needed or wanted by his surgeon Tester: devises test cases and test data Administrator, Editor, Secretaries, Program clerks, Language lawyer

10-man Programming Team Surgeon Copilot Toolsmith Tester Administrator Editor