A Study of CMM Level 5 Projects(2011)

Note: Please Scroll Down to See the Download Link.

ABSTRACT:

The Capability Maturity Model is a software development processes with the goal of developing high quality software within budget and planned cycle time. In this project there are two major contributions. One is identify the key project factor such as software size that determine software project development outcome for CMM level 5 projects, Another  one is benchmark for effort, quality and cycle time based on CMM level 5 project data. Cycle time may be compressed at the cost of quality; Quality may be achieved at the cost of increases testing effort. To find the software quality, effort and cycle time we are using three constraints such as I) Literature review, II) Research model, design and methodology, III) Data analysis and results. The cycle time for software development, which depends on two factors one is planned development time another one is actual development time. Software development effort as the total effort beginning with the end of the requirements specification stage until the end of customer acceptance testing.

Developing software to meet functional needs with acceptable levels of quality, within budget, and on schedule, is a goal pursued by every software development organization. Many organizations are adopting the best practices in software development, such as those based on Capability Maturity Model . CMM has been one of the most popular efforts in enhancing software quality and reducing development costs. Although development effort, software quality, and cycle time have been studied in prior research on software estimation most of the published results are based on data sets that are now considered dated, due to various technological innovations such as the use of object-oriented languages, middleware, and newer tools and due to increased adoption of best practices in software development, that is, those based on CMM. there is a need to reexamine relationships between software project development outcomes and various factors identified from prior literature. Conventional wisdom suggests that there are conflicting influences on software development effort, quality, and cycle time: Cycle time may be compressed at the cost of quality, experienced professionals may improve quality but at increased costs, quality may be achieved at the cost of increased testing effort, larger team size may reduce development time while raising total costs, process maturity may improve quality but at high cost, and so forth. Research suggests that one of the most important consequences of improved processes is superior conformance quality. The reduction in variability is likely to be most pronounced in development organizations at CMM level 5, which is the highest level of process maturity. Its results, therefore, may not be generalizable outside the environment where they were calibrated. Valuable insights can be gained from a study that focuses exclusively on CMM level 5 software development projects. In this paper, we make two major contributions. First, we identify key project factors such as software size that determine software project development outcomes for CMM level 5 projects. Second, we provide benchmarks for effort, quality, and cycle time based on CMM level 5 project data. Our results suggest that estimation models based on CMM level 5 data are portable across multiple CMM level 5 organizations.

Overview

Objective:

Software development processes with the goal of developing high quality software within budget and planned cycle time.  Cycle time may be compressed at the cost of quality,                 

Scope of the project:

The main scope of the project is measuring the effectiveness of these techniques for reducing rate of software defects produce failures. The quality of software will be found based on the quality, cycle time, effort, product size, product complexity and schedule pressure Developing software to meet functional needs with acceptable levels of quality, within budget, and on schedule, is a goal pursued by every software development organization. Many organizations are adopting the best practices in software development, such as those based on Capability Maturity Model . CMM has been one of the most popular efforts in enhancing software quality and reducing development costs. Although development effort, software quality, and cycle time have been studied in prior research on software estimation most of the published results are based on data sets that are now considered dated. Due to various technological innovations such as the use of object-oriented languages, middleware, and newer tools and due to increased adoption of best practices in software development, that is, those based on CMM. There is a need to reexamine relationships between software project development outcomes and various factors identified from prior literature. Conventional wisdom suggests that there are conflicting influences on software development effort, quality, and cycle time: Cycle time may be compressed at the cost of quality, experienced professionals may improve quality but at increased costs, quality may be achieved at the cost of increased testing effort, larger team size may reduce development time while raising total costs, process maturity may improve quality but at high cost, and so forth. Research suggests that one of the most important consequences of improved processes is superior conformance quality. The reduction in variability is likely to be most pronounced in development organizations at CMM level 5, which is the highest level of process maturity. Its results, therefore, may not be generalizable outside the environment where they were calibrated. Valuable insights can be gained from a study that focuses exclusively on CMM level 5 software development projects. In this paper, we make two major contributions. First, we identify key project factors such as software size that determine software project development outcomes for CMM level 5 projects. Second, we provide benchmarks for effort, quality, and cycle time based on CMM level 5 project data. Our results suggest that estimation models based on CMM level 5 data are portable across multiple CMM level 5 organizations.

Existing System

In existing system they are find  the  some drawbacks in that quality of software. Those are in quality, cycle time, effort, product size, and product complexity.

Proposed System

In proposed system the quality of software will be found based on the quality, cycle time, effort, product size, product complexity and schedule pressure.

Modules and its Description

1.    Effort

2.    Quality

3.    Cycle Time

4.    Testing

Effort

Effort is often regarded as a surrogate for software development cost since personnel cost is the dominant cost in software development. In this module we have used COCOMO algorithm. This algorithm use the number of source lines of code (SLOC) as the basis for effort estimation. Effort is a function of system size combined with production rate that is how much work someone can complete in a given time.

Quality

Product size (SIZE) can be measured using lines of codes or using FPs .In this step we are using Function Point count to measure the quality of the software. A function point is a measure of program size that is based on the system’s number and complexity of inputs, outputs, queries, files, and program interfaces. We List major elements of system and then Determine the total number of each element. Specify complexity index of each component (low, med., high).

Cycle Time

Cycle time is an important outcome variable because software projects are often carried out under strict delivery schedules. When planned schedules are longer than the minimum cost-effective schedule, they do not raise development costs. This is because, under ideal circumstances, projects can be completed using fewer developers than the optimal staffing strength. The number of lines of code has been reported to be a significant predictor of construction time.

Testing

This module is involving entire application to be verified and get the for test cases.

Software/ Hardware Requirements

Hardware Requirements

         SYSTEM                    : Pentium IV 2.4 GHz

         HARD DISK              : 40 GB

         RAM                           : 512MB

Software Requirements

         Operating system     : Windows XP Professional

         Technology               : Microsoft Visual Studio .Net 2008

         Coding Language   : C#

         Backend                    : SQL Server 2005

Click here to download A Study of CMM Level 5 Projects(2011) source code