Mythical-ManMonth-Lecture

Mythical-ManMonth-Lecture - EEL5881 software engineering I...

Info iconThis preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon
    EEL5881 software engineering I Mythical man-month lecture  Presented by Yi Luo
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
    acknowledge Most of the sides are taken from different  sources including: the slides of Dr. Robert W. Franceschini’s software life cycle class, EEL 6887, Spring 2007. The Mythical Man-Month: Essays on Software Engineering , 20th Anniversary Edition (Paperback), by Frederick P. Brooks (Author) Wikipedia http://en.wikipedia.org/wiki/The_Mythical_Man-Month
Background image of page 2
    About the book Author: Fred Brooks a book on software  project management central theme : "Adding  manpower to a late  software project makes it  later."  
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
    About the book The Bible of Software Engineering  everybody reads it but nobody does  anything about it!  Working in IBM, managing the development of OS/360 OS/360 was a great success, becoming the most important IBM mainframe operating system. mistakenly added more workers to a project falling behind schedule. mistakenly assert that one project, writing an Algol compiler, would require six months—regardless of the number of workers involved (It required longer).
Background image of page 4
    overview The Tar Pit The Mythical Man-Month The Surgical Team Conceptual Integrity The Second-system effect  Passing the word Why Did the Tower of Babel Fail? Summary and Other ideas
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
    The Tar Pit  [Brooks, Chapter 1] A program A programming product (generalization, testing, documentation, maintenance) A programming system (interfaces, system integration) A programming systems product x 3 x 3 We estimate as if building this… But we are building this
Background image of page 6
    What makes programming  fun? Brooks offers five reasons: Making things… …that others find useful. Making complex objects out of parts. Continuous learning because the task is  always different. Using tools and “materials” that do not  degrade.
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
    What causes problems? According to Brooks: Computers demand perfection. A person does not control the “circumstances” of  their work (goals, resources, information). Working out the bugs is just that – work. Working out the bugs takes an order of magnitude  longer than one expects. The resulting software seems to be obsolete  before it is released. However, this is more of a perception…
Background image of page 8
    The Mythical Man-Month [Brooks, Chapter 2] According to Brooks, failure to meet schedule  is the reason for most software project  failures.  Why? We don’t know how to estimate (overly optimistic). We confuse effort with progress.
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 10
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 08/25/2011 for the course EEL 5881 taught by Professor Staff during the Spring '09 term at University of Florida.

Page1 / 41

Mythical-ManMonth-Lecture - EEL5881 software engineering I...

This preview shows document pages 1 - 10. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online