The Cove Business Standards Discussion Forums More Free Files Forum Discussion Thread Post Attachments Listing Cove Discussion Forums Main Page
UL - Underwriters Laboratories - Health Sciences
Go Back   The Elsmar Cove Business Systems and Standards Discussion Forums > Common Quality Assurance Processes and Tools > Software Quality Assurance
Forum Username

Elsmar Cove Forum Visitor Notice(s)

Wooden Line

CMMI - Software 'Capability Maturity Model Integration' and Overlapping Waterfall

Elsmar XML RSS Feed
Elsmar Cove Forum RSS Feed

Monitor the Elsmar Forum
Sponsor Links

Courtesy Quick Links

Links that Cove visitors will find useful in your quest for knowledge:

International Standards Bodies - World Wide Standards Bodies

ASQ - American Society for Quality

International Standards Organization - ISO Standards and Information

International Quality Services

Marcelo Antunes'
SQR Consulting, and
Medical Devices Expert Forum

Bob Doering
Bob Doering's Blogs and,
Correct SPC - Precision Machining

Ajit Basrur
Claritas Consulting, LLC

NIST's Engineering Statistics Handbook

IRCA - International Register of Certified Auditors

SAE - Society of Automotive Engineers

Quality Digest

IEST - Institute of Environmental Sciences and Technology

Closed Thread
Thread Tools Search this Thread Rate Thread Content Display Modes
  Post Number #1  
Old 1st July 2000, 03:42 AM

Total Posts: n/a
Lurker CMMI - Software 'Capability Maturity Model Integration' and Overlapping Waterfall

Please explain about CMM ? IS that related to
Quality Assurance in Software industry ?

Sponsored Links
  Post Number #2  
Old 4th July 2000, 12:46 AM
Marc's Avatar

Total Posts: 25,226
Yin Yang Overlapping Waterfall Method

See Capability Maturity Model and this brief thread Overlapping Waterfall

This is a graphic of the Overlapping Waterfall method.
The waterfall model is a popular version of the systems development life cycle model for software engineering. Often considered the classic approach to the systems development life cycle, the waterfall model describes a development method that is linear and sequential. Waterfall development has distinct goals for each phase of development. Imagine a waterfall on the cliff of a steep mountain. Once the water has flowed over the edge of the cliff and has begun its journey down the side of the mountain, it cannot turn back. It is the same with waterfall development. Once a phase of development is completed, the development proceeds to the next phase and there is no turning back.

The advantage of waterfall development is that it allows for departmentalization and managerial control. A schedule can be set with deadlines for each stage of development and a product can proceed through the development process like a car in a carwash, and theoretically, be delivered on time. Development moves from concept, through design, implementation, testing, installation, troubleshooting, and ends up at operation and maintenance. Each phase of development proceeds in strict order, without any overlapping or iterative steps.

The disadvantage of waterfall development is that it does not allow for much reflection or revision. Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage. Alternatives to the waterfall model include joint application development (JAD), rapid application development (RAD), synch and stabilize, build and fix, and the spiral model.
The Standard Waterfall Model for Systems Development

The standard waterfall model for systems development is an approach that goes through the following steps:

1. Document System Concept
2. Identify System Requirements and Analyze Them
3. Break the System into Pieces (Architectural Design)
4. Design Each Piece (Detailed Design)
5. Code the System Components and Test Them Individually (Coding, Debugging, and Unit Testing)
6. Integrate the Pieces and Test the System (System Testing)
7. Deploy the System and Operate It

This model is widely used on large government systems, particularly by the Department of Defense (DOD).

As part of this standard approach, the party responsible for contracting out the system development (ESDIS for the ECS Contract) can call on a number of tools to help plan and document the system. ECS followed this planning approach, which means that early in the system development, ESDIS set up a standard set of documents for the contractor to supply, as well as a contractual schedule for the major pieces. The development process provided a number of design reviews, notably

* Conceptual Design Review
* Requirements Review
* Preliminary Design Review (PDR)
* Critical Design Review (CDR)

Until these reviews were completed, there would be little code developed. After the CDR, the contractor would code to the design.

The standard reference for estimating the cost of the system is the COnstructive COst MOdel (COCOMO) developed by Dr. Barry Boehm while he was at TRW [Boehm, B., 1981: Software Engineering Economics, Prentice-Hall]. This model relates the development time and workforce [man-months] to the "Source Lines of Code" (SLOC). Roughly, for an ECS type of system ECS, the workforce (and therefore cost) scales as the cube of the development time. There are simple versions of the model and much more complex ones. Generally, all of the relationships used to predict these relationships are statistical in nature: Dr. Boehm and other workers in software project cost estimation build a database of project schedules and costs and then regress those against SLOC estimates. The most recent version of Dr. Boehm's work is provided in [Boehm, B., et al., 2000: Software Cost Estimation with COCOMO II, Prentice-Hall.].

There have been a number of criticisms of the standard waterfall model, including

* Problems are not discovered until system testing.
* Requirements must be fixed before the system is designed - requirements evolution makes the development method unstable.
* Design and code work often turn up requirements inconsistencies, missing system components, and unexpected development needs.
* System performance cannot be tested until the system is almost coded; undercapacity may be difficult to correct.

The standard waterfall model is associated with the failure or cancellation of a number of large systems. It can also be very expensive. As a result, the software development community has experimented with a number of alternative approaches, including

* Spiral Design (Go through waterfalls, starting with a very rough notion of the system and becoming more detailed over time)
* Modified Waterfalls (Waterfalls with Overlapping Phases; Waterfall with Subprojects)
* Evolutionary Prototyping (Start with initial concept, design and implement an initial prototype, iterate as needed through prototype refinement until acceptable, complete and release the acceptable prototype)
* Staged Delivery (Go through Concept, Requirements Analysis, and Architectural Design - then implement the pieces, showing them to the customer as the components are completed - and go back to the previous steps if needed)
* Evolutionary Delivery (a cross between Evolutionary Prototyping and Staged Delivery)

These are discussed in considerable detail in [McConnell, S., 1996: Rapid Development, Taming Wild Software Schedules, Microsoft Press]. Commercial software projects often reduce the formality of the full waterfall model. In the last few years, a paradigm known as eXtreme Programming has emerged that emphasizes reducing the cost of software changes, developing test cases before coding, developing code using pairs of programmers, and putting most of the documentation into the code [Beck, K., 2000: Extreme Programming Explained, Embrace Change, Addison-Wesley].
Sponsored Links

Closed Thread

Lower Navigation Bar
Go Back   The Elsmar Cove Business Systems and Standards Discussion Forums > Common Quality Assurance Processes and Tools > Software Quality Assurance


Visitors Currently Viewing this Thread: 1 (0 Registered Visitors (Members) and 1 Unregistered Guest Visitors)
Thread Tools Search this Thread
Search this Thread:

Advanced Forum Search
Display Modes Rate Thread Content
Rate Thread Content:

Forum Posting Settings
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Similar Discussion Threads
Discussion Thread Title Thread Starter Forum Replies Last Post or Poll Vote
CMMI (Capability Maturity Model Integration) - questions ElectricallyBlonde Software Quality Assurance 5 18th June 2013 06:55 AM
CMMI (Capability Maturity Model Integration) - Ever heard CMMI? reynald Software Quality Assurance 5 26th February 2010 10:51 AM
How do I learn CMMI (Capability Maturity Model Integration)? someshvar Software Quality Assurance 4 29th August 2007 07:32 AM
Detail info on CMMI - Capability Maturity Model Integration for Software Amit Mishra Software Quality Assurance 15 2nd April 2007 05:42 AM
CMMI in Software - Capability Maturity Model Integration Marc Software Quality Assurance 20 20th August 2004 04:08 PM

The time now is 09:39 PM. All times are GMT -4.
Your time zone can be changed in your UserCP --> Options.


NOTE: This forum uses "Cookies"