CLIWS

Pronounced Clues.

CLIWS is a proactive software development practice, whereby each phase of development documented in waterfall has its own empowered decision maker.

CLIWS comes from the 4 practices:

• Cleanroom
• Lean
• Interactive
• Waterfall
  With the overlapping functionality of Sashimi.
  

  Cleanroom

Focuses on Software development based on formal methods and using statistically sound testing practices. These formal methods are detailed as Formal Specifications, Formal Development and Formal verification and Theorem Provers.

Specification - Formal methods may be used to give a description of the system to be developed, at whatever level(s) of detail desired.
Development - Once a formal specification has been developed, the specification may be used as a guide while the concrete system is developed (i.e. realized in software and/or hardware).
Verification - Once a formal specification has been developed, the specification may be used as the basis for proving properties of the specification (and hopefully by inference the developed system).

Lean

Think big, act small, fail fast; learn rapidly

Deliver as fast as possible
Empower the team
Eliminate waste

Interactive

Is an improvement upon standard waterfall practice.

Waterfall

Requirements

Design
Implementation or Development
Verification
Maintenance

Sashimi

Allows for the 5 phases of Waterfall to overlap. Allowing design to start while the requirements are going through finalization. As the design nears its initial proto-type presentation stage, the developers will start coding. And as a module finishes, the verification process starts comparing the functionality to the requirements.

44601 visitors. Built using 3F Wiki Engine Copyright © 2010 by 3F, LLC. All rights reserved, wordlwide.

SSL