Software Engineering
Table of Contents
Glass’ Law 3 Example 3
Boehm’s first law 3 Example 4
Boehm’s second law 4 Example 4
Davis’ law 5
Waterfall model 5
Spiral Model 7
Waterfall model with Glass’ Law 8
Waterfall model with Boehm’s First Law 9
Waterfall model with Boehm’s Second Law 9
Waterfall model with Davis Law 10
Spiral model with Glass Law 10
Spiral model with Boehm’s First Law 11
Spiral model with Boehm’s Second Law 11
Spiral model with Davis’ Law 11
Waterfall Model 12 Examples where this model suits 12 Examples where this model does not suit 12
Spiral Model 13 Examples where this model suits 13 Examples where this model does not suit 13
References 14
Bibliography 15
1. Describe each law in your own words. Illustrate with a practical example.
Glass’ Law
“Requirement deficiencies are the prime source of project failures.”
Any coherent and reasonable project must have some requirements that define what that project is supposed to do. The requirements are the basic steps in implementing a project. A requirement is an objective that must be met. There are several types of requirements such as price, performance and reliability objectives. Requirements are instructions describing what functions the project is supposed to provide, what characteristics the project is supposed to have, and what goals the project is supposed to meet. The shortage of requirements causes many problems in starting and implementing a project. This law states that this shortage of requirements is the main source in the failure of the project.
Example
Lack of defined requirements is one of the major reasons for a project to fail. An example project which failed due to lack of requirements is Passport Agency in UK. In this project, the requirements were not defined properly in the defining stage which led to computer problems in the summer of 1998 forcing thousands to cancel their holidays and costing taxpayers £12 million to fix.
Boehm’s first law
Glass’ Law 3 Example 3
Boehm’s first law 3 Example 4
Boehm’s second law 4 Example 4
Davis’ law 5
Waterfall model 5
Spiral Model 7
Waterfall model with Glass’ Law 8
Waterfall model with Boehm’s First Law 9
Waterfall model with Boehm’s Second Law 9
Waterfall model with Davis Law 10
Spiral model with Glass Law 10
Spiral model with Boehm’s First Law 11
Spiral model with Boehm’s Second Law 11
Spiral model with Davis’ Law 11
Waterfall Model 12 Examples where this model suits 12 Examples where this model does not suit 12
Spiral Model 13 Examples where this model suits 13 Examples where this model does not suit 13
References 14
Bibliography 15
1. Describe each law in your own words. Illustrate with a practical example.
Glass’ Law
“Requirement deficiencies are the prime source of project failures.”
Any coherent and reasonable project must have some requirements that define what that project is supposed to do. The requirements are the basic steps in implementing a project. A requirement is an objective that must be met. There are several types of requirements such as price, performance and reliability objectives. Requirements are instructions describing what functions the project is supposed to provide, what characteristics the project is supposed to have, and what goals the project is supposed to meet. The shortage of requirements causes many problems in starting and implementing a project. This law states that this shortage of requirements is the main source in the failure of the project.
Example
Lack of defined requirements is one of the major reasons for a project to fail. An example project which failed due to lack of requirements is Passport Agency in UK. In this project, the requirements were not defined properly in the defining stage which led to computer problems in the summer of 1998 forcing thousands to cancel their holidays and costing taxpayers £12 million to fix.
Boehm’s first law
References: Bibliography Angelfire: Prototyping, retrieved on 111th August, 2009, from http://alpalp1977.angelfire.com/unsal.pdf Bing, used on 10th, 11th, 12th, 13th August, 2009, from www.bing.com David Brown, 1998, Failed IT Projects, retrieved on 12th August, 2009, from, http://mailman.anu.edu.au/pipermail/link/1998-May/032964.html Google, retrieved on 10th, 11th, 12th and 13th August, 2009, from www.google.com Philosophe: Requirements and Specifications, retrieved on 11th August, 2009, from, http://philosophe.com/design/requirements/