Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Process and Method for Using Rational Code Review to Define a Programming Maturity Model Standard

IP.com Disclosure Number: IPCOM000035513D
Original Publication Date: 2005-Jan-21
Included in the Prior Art Database: 2005-Jan-21
Document File: 3 page(s) / 107K

Publishing Venue

IBM

Abstract

There is currently a CCM for Software (Levels 1-5) IBM Rational has a set of tools that can assist with the maturity level progress. This publication couples the CCM for Software with the current Rational Tool set, and describes the level in which to introduce certain tools

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 3

Process and Method for Using Rational Code Review to Define a Programming Maturity Model Standard

There is currently a CCM for Software (Levels 1-5) IBM Rational has a set of tools that can assist with the maturity level progress. This publication couples the CCM for Software with the Rational Tool set, and describes the level in which to introduce certain tools

CMM is organized into the five levels shown below. It prioritizes improvement actions for increasing software process maturity. A piece of the software process is the actual "coding" or "programming" function.

A piece of the software process is the actual "coding" or "programming" function of the organization. This subset function also goes through the same key areas of maturity process as shown in the figure below.

1

[This page contains 1 picture or other non-text object]

Page 2 of 3

The following Rational tool set can assist in the progress through these levels.

Level 5 Visual Modeling

Level 5 Visual Modeling

Testing from the Rose Modeling

Purify+/CodeReview

Testing from the Rose Modeling

Purify+/CodeReview

Level 4 Code coverage at the component/unit level

Level 4 Code coverage at the component/unit level

Better

Better

Level 3 Testability being introduced directly into code and design

Level 3 Testability being introduced directly into code and design

Component Tester, Functional Tester

Component Tester, Functional Tester

Level 2 Adhere to certain standards

Level 2 Adhere to certain standards

R2A/CodeReview

R2A/CodeReview

Level 1 Initial - chaos

Level 1 Initial - chaos

R2A/CodeReview

R2A/CodeReview

Below is a chart of where each tool set falls in the maturity model.a

2

[This page contains 2 pictures or other non-text objects]

Page 3 of 3

Lvl Characteristic for Software

Processes

Characteristic for the Code Itself Rational Tool used to move to next

Level

1 Adhoc, and occasionally chaotic

Few processes are defined

* No code or unit test reviews.
* During crisis, projects typically abandon planned procedures for design documentation, unit testing, etc.

Rational Code Review -- at the initial Quick View Level 1 setting.

Basic project management process are in place to track cost, schedule and functionality

2

* coding organizations adhere to coding practices
* an architecture profile or plan is in place
* Coding organizations include automated Unit...