Internet Engineering
Jan Nikodem, Ph.D.
Software Engineering Management of Software Project
Software Engineering Lecture 4 Software bloat is a term used to describe the tendency of newer computer programs to have; • a larger installation footprint, • many unnecessary features that are not used by end users
Wikipedia
3/22 Software bloat is a term used to describe the tendency of newer computer programs which
• generally use more system resources than necessary, while offering little or no benefit to its users.
Wikipedia
4/22 Software bloat Wirth's law (computing adage) Software is getting slower more rapidly than hardware becomes faster.
Nationality; Swiss, electronic engineer, computer scientist ETH Zürich, University of California, Berkeley, Stanford University University of Zurich. Xerox PARC. Niklaus Emil Wirth 1934
5/22 Software bloat may be a symptom of the second-system effect, refers to the tendency, when following on from a relatively small, elegant, and successful system, to design the successor as an elephantine, feature-laden monstrosity.
The Mythical Man-Month
Nationality; USA, applied mathematics Copyright owned by SD&M (www.sdm.de) IBM, University of North Carolina at Chapel Hill Fred Brooks 1931
6/22 Software bloat
Version Year Memory Processor Hard disk Windows 95 1995 4 MB 25 MHz 50 MB Windows 98 1998 16 MB 66 MHz 200 MB Windows 2000 2000 32 MB 133 MHz 650 MB Windows XP 2001 64 MB 233 MHz 1.5 GB Windows Vista 2007 512 MB 800 MHz 15 GB Windows 7 2009 1 GB 1 GHz 16 GB Wikipedia
7/22 Pareto’s principle (80/20 rule)
In 1906, Italian economist Vilfredo Pareto described the unequal distribution of wealth in his country, observing that twenty percent of the people owned eighty percent of the wealth.
Vilfredo Pareto 1848-1923 8/22 Management of software project It is most important that top management be quality-minded. In the absence of sincere manifestation of interest at the top, little will happen below.
Nationality; USA electrical engineer, quality guru, quality management, lawyer, University of Minnesota, Bell Laboratories, AT&T, Western Electric, New York University. Joseph M. Juran 1904-2008
9/22 Management of software project
The vital few and the useful many. The 80/20 Rule means that in anything a few (20%) are vital and many (80%) are useful only.
Nationality; USA electrical engineer, quality guru, quality management, lawyer, University of Minnesota, Bell Laboratories, AT&T, Western Electric, New York University. Joseph M. Juran 1904-2008
10/22 Pareto Principle as a daily reminder (1)
Pareto Principle reminds to focus on the 20% of matters. Of the things you do during your day, only 20% really matter.
Those 20% produce 80% of your results. Identify and focus on those things. Joseph M. Juran 1904-2008
11/22 Pareto Principle as a daily reminder (2)
When the fire drills of the day begin to sap your time, remind yourself of the 20% you need to focus on. If something in the schedule has to slip, if something isn't going to be done, make sure it's not part of that 20%. Joseph M. Juran 1904-2008
12/22 The vital few and the useful many
Project Managers know that 20% of the work (the first 10% and the last 10%) consume 80% of your time and resources.
Nationality; USA electrical engineer, quality guru, quality management, lawyer, University of Minnesota, Bell Laboratories, AT&T, Western Electric, New York University. Joseph M. Juran 1904-2008
13/22 Management of software project Don't just "work smart", ”work smart” on the right things .
The daily reminder: Focus your time and energy on the 20% of you work that is really important. Joseph M. Juran 1904-2008
14/22 Management reality (1) • Escalation aspect- some projects have escalating commitment to a failing course of action.
• Runway IT projects - that seem to take on a life of their own, represent a type of IT failure that can cost companies millions of dollars
M. Keil, R. Mixon, T. Saarinen, V. Tuunainen, Understanding runaway information technology project :… Journal of Managemen,1994 - portal.acm.org
15/22 Management reality (2)
Runway IT projects
16/22 Management reality (3)
Escalating commitment
17/22 Management myths (1) Writing code is the major part of creating a software product .
!
Table 1: Percentages of time spent in different stages of software development for several NASA projects. (adapted from Boehm 1981).
18/22 Management myths (2) We can solve schedule problems by adding more programmers . „Nine women can not make ! a baby in one month“.
F. P. Brooks
19/22 Management myths (2) We can solve schedule problems by adding more programmers . „Adding manpower to a late ! software project makes it later”.
F. P. Brooks
20/22 Readings
• Niklaus Wirth, A Brief History of Software Engineering IEEE Annals of the History of Computing - Volume 30, Number 3, July-September 2008, pp. 32-39, DOI: 10.1353/ahc.0.0021
• M. Keil, R. Mixon, T. Saarinen, V. Tuunainen, Understanding runaway information technology project :… Journal of Management,1994 - portal.acm.org
21/22 Useful links
• technology management
• Juran - Documentary An Immigrant's Gift
• E.W.Dijkstra Archive: Home page
• Fred Brooks - Wikipedia, the free encyclopedia
22/22