CASE tools and CMM

1
CASE tools and CMM

• Kyle LeMarbe

2
Maturity Level 1 Initial Level

• No sound software engineering management
  practices are in place.
• Software is unpredictable and depends totally on
  current staff. If the staff changes then the
  process changes.

3
Maturity Level 2 Repeatable Level

• Basic project management practices are in place.
• Techniques are based on past project experience.
• Measurements are taken, a key first step in
  starting a software engineering process.
  (Tracking of costs and schedules)
• Problems are identified and are solved via
  immediate corrective actions.

4
Maturity Level 3 Defined Level

• Clearly defined set of software production
  practices are present. (Continual efforts to
  improve the process)
• Reviews are implemented to meet software quality
  goals.

5
Maturity Level 4 Managed Level

• Productivity and quality goals are set for
  projects.
• Productivity and quality are measured constantly
  and corrected when necessary.

6
Maturity Level 5 Optimizing Level

• Continual process improvement.
• Productivity and Quality is used to guide
  organization.

7
CASE Tools

• Analytical Tools
• Taxonomy
• Tools

8
CASE Tools at Low Maturity

• According to the author, should not be using
  advanced tools.
• Coding Tool
• E-mail Tool
• Pretty Printer
• Debugger

9
Disadvantages

• High level CASE tools cause unneeded confusion at
  lower CMM levels.
• Without structured methodology, performance is
  decreased.
• If training is not supplied, software is
  delivered late and users are less satisfied with
  the product in most cases.

10
CASE Tools at High Maturity

• Implementation of CASE environment including
  requirements, analysis, design, implementation,
  and post-delivery.
• Rational Rose
• Enterprise Architect
• BOUML

11
Advantages

• 50 Percent increase in productivity.
• Automated documentation.
• Integrated source development.
• Program is less prone to errors. (Fewer faults,
  and easier maintenance)

12
Disadvantages

• Employee training.
• Integrated environment costs.
• Downtime to implement changes.

13
References

• Stephen R. Schach, Object-Oriented Classical
  Software Engineering McGraw-Hill 2007
• http//en.wikipedia.org/wiki/List_of_UML_tools