CMM in Practice: Processes for Executing Software Projects at Infosys / Edition 1

Paperback (Print)
Buy New
Buy New from BN.com
$57.13
Used and New from Other Sellers
Used and New from Other Sellers
from $1.99
Usually ships in 1-2 business days
(Save 97%)
Other sellers (Paperback)
  • All (21) from $1.99   
  • New (7) from $12.01   
  • Used (14) from $1.99   

Overview

The Capability Maturity Model (CMM) is a widely adopted set of guidelines for evaluating and improving an organization's software development processes. The CMM is a general framework, however, and provides no specific guidance for implementation; instead, each organization must relate CMM characteristics to its own processes. As a consequence, the need has emerged for comprehensive accounts of successful CMM implementations, as well as for detailed descriptions of how software projects are executed in those cases. Such real-world examples can serve as a valuable resource for managers and developers responsible for setting up the CMM and carrying out their own projects.

CMM in Practice comprises such a resource. Examining the various stages in the life cycle of a typical software project at Infosys Technologies, the book describes the technical and management processes used to initiate, plan, and execute the project. To enhance the discussion, an actual Infosys project is used as a running example throughout the book. The author, who was one of the main architects behind the quick transition from ISO to CMM at Infosys, shows how these working processes relate to the Key Process Areas of the CMM. He also illustrates how relatively simple and familiar approaches can be combined to raise an organization's software maturity level.

CMM in Practice covers these topics and more:

  • Requirements change management process
  • Process tailoring
  • Software metrics and statistical process control
  • Process database
  • Process capability baseline
  • Effort and schedule estimation
  • Quantitative quality management and defect estimation
  • Risk management and configuration management
  • Peer reviews and their quantitative control
  • Implementing reviews and the NAH syndrome
  • Data collection and analysis
  • Quantitative project monitoring and control
  • Milestone analysis
  • Audit process
  • Project closure analysis
Read More Show Less

Editorial Reviews

Booknews
The Capability Maturity Model (CMM), managed by the Software Engineering Institute at Carnegie Mellon U., is a widely adopted set of guidelines for software process improvement and assessment. In detailing the specifics for achieving the five levels of maturity within this framework, Jalote (computer science and engineering, Indian Institute of Technology, Kanpur) covers the technical and management steps used to initiate, plan, and execute projects via the life cycle of an actual project at level 4-rated Infosys Technologies. As one of the main architects behind the transition from ISO 9000 to CMM (details appended), the author shows how these processes relate to the Key Process Areas of the CMM. Annotation c. Book News, Inc., Portland, OR (booknews.com)
Read More Show Less

Product Details

  • ISBN-13: 9780201616262
  • Publisher: Addison-Wesley
  • Publication date: 10/28/1999
  • Series: SEI Software Engineering Series
  • Edition description: New Edition
  • Edition number: 1
  • Pages: 400
  • Product dimensions: 6.00 (w) x 8.90 (h) x 0.90 (d)

Meet the Author

Pankaj Jalote is Professor and Chairman of the Department of Computer Science and Engineering at the Indian Institute of Technology, Kanpur. He was formerly Assistant Professor in the Department of Computer Science at the University of Maryland and Vice President of Quality at Infosys Technologies, Ltd., in Bangalore, India. While at Infosys, he was one of the main architects behind Infosys’ move to high-maturity levels of the CMM. He is also the author of CMM in Practice: Processes for Executing Software Projects at Infosys (Addison-Wesley, 2000), in which he discusses the implementation of CMM in an organization.

0201616262AB07022002

Read More Show Less

Read an Excerpt

Worldwide, the demand for software is increasing at a rapid pace, with no end in sight for this growth in appetite. The growth has also spawned a dramatic increase in software development activity. In turn, this increased software development activity has sharpened the focus on the processes used for building software, collectively known as the software process. Although opinions differ on the nature and formality of the software process, there is now general agreement that use of proper processes is extremely important for an organization that seeks to deliver high-quality software and increase its own productivity.

The heightened importance of the software process has engendered a need for process improvement, which also requires methods for process analysis and assessment. One of the most extensive and influential software process improvement and assessment frameworks is the Capability Maturity Model (CMM) for software developed by the Software Engineering Institute (SEI) at Carnegie Mellon University. The CMM categorizes software process maturity into five levels: from level 1 (the lowest) to level 5 (the highest). For each level, the CMM specifies some key process areas (KPAs), which represent the areas on which an organization should focus if it wants to move to a particular level. Each KPA is associated with goals that represent the requirements to be satisfied by the process for that KPA. The KPAs for different maturity levels can be used for assessing the capability of the existing process, as well as for identifying the areas that need to be strengthened so as to move the process from a lower level of maturity to a higher level.

The CMM framework is quite general and not prescriptive. Although organizations can implement CMM in different ways, relating the characteristics mentioned in the CMM to real-life practices and processes can prove difficult. This book describes the set of processes used for executing a project at Infosys Technologies Ltd., a large software house headquartered in Bangalore, India. Infosys was formally assessed at CMM level 4 in December 1997 by two SEI-authorized lead assessors.

Rather than just explaining the various technical and management processes employed by Infosys, this book describes the processes as they appear at various stages in the life cycle of a project. Because the life cycle of a project includes both technical and management processes, this approach ensures that most processes affecting a project are explained. This approach is also one to which both practitioners and students can more easily relate. It does leave out the organization-level processes for supporting and managing the process activities. Some aspects of these processes have been described here, wherever their inclusion would not break the flow of the book. In addition, an article describing the management of the CMM framework implementation at Infosys is included as Appendix B.

The book includes 15 chapters. Chapter 1 gives a brief overview of the CMM and describes some organization-level support for processes at Infosys. The remaining chapters focus on project execution, and are organized into three parts. Part I (Chapters 2 and 3) deals with processes that are executed before the project formally commences. Part II (Chapters 4 through 10) deals with project planning activities. Part III (Chapters 11 through 15) examines project execution and termination. Most chapters focus on some key task in a project and have been kept as independent as possible of the other chapters.

It is not the intent of this book to provide extensive coverage of the literature or detailed explanations of the CMM. The main goal is to describe the processes of an organization that employs the CMM framework. The book also illustrates how simple and known approaches can be combined effectively to have a highly mature overall process. It does not suggest that Infosys's approach is optimal or better than someone else's or an ideal implementation of the CMM. Likewise, it does not recommend that these processes be used by others; that decidion is left for the readers.

The positive feedback I received on my earlier textbook, An Integrated Approach to Software Engineering (Springer Verlag, 1997), which had a case study running through the book, convinced me of one thing: In software engineering, it is invaluable to have real examples with real outputs and a complete example, if possible, when explaining concepts. This book employs the same approach. Most of the examples are real in that they have been picked from real projects, and one actual project—the weekly activity report (WAR) project—is used through much of the book to illustrate how different processes interrelate. Although the processes described are used at Infosys, any sensitive numbers (for example, on quality and productivity) included may have been sanitized to maintain the company's confidentiality.

This book should prove useful to all practitioners who are interested in the software process or the CMM framework. It should be immensely helpful to those practitioners who are trying to implement the CMM in their own organizations. To help ISO organizations in their effort to move to CMM, a general study describing possible gaps in an ISO organization with respect to different levels of the CMM has been provided in Appendix A. As the book discusses how projects are executed in a successful organization, it should also be of interest to professionals who are now managing software projects. For instructors and students, it can serve as a supplementary text for a project-oriented course on software engineering, as the book provides a good view of how software is developed in a business environment, along with a case study.

It is perhaps proper to explain my own involvement with Infosys. As Vice President (Quality) at Infosys, I was one of the main architects behind the company's successful transition from ISO to CMM level 4. Although Infosys supplied all of the material I requested, I take full responsibility for any mistakes, misrepresentations, and inaccuracies that may be present in the book. Such issues are bound to occur when one tries to describe the essence of an organization's process manual, along with a case study, in such a compact book. Any deviations in these descriptions from the actual processes of Infosys are entirely my responsibility, as I decided which portions of processes to include and in what manner.

Any comments or queries about the book are welcome, and can be sent to me at jalote@iitk.ac.in. For any information regarding Infosys, visit www.itlinfosys.com or send mail to public-relations@itlininfosys.com.

—Pankaj Jalote


Read More Show Less

Table of Contents

Preface.

1. Introduction.

Process-Based Approach for Project Execution.

Capability Maturity Model for Software.

Processes at Infosys.

Summary.

I. PROJECT INITIATION.

2. Proposals and Contracts.

Customer and Vendor Interaction.

The Proposal.

The Contract.

Summary.

3. Requirements Specification and Management.

Requirements Analysis and Specification.

Requirements Change Management.

Traceability Management.

Example: The WAR System.

Summary.

II. PROJECT PLANNING.

4. Process Definition and Tailoring.

Development Process.

Process Tailoring.

Summary.

5. Process Database and Process Capability Baseline.

Software Metrics and Process Management.

Process Database.

Process Capability Baseline.

Summary.

6. Effort Estimation and Scheduling.

Background Information for Estimation.

Bottom-Up Estimation.

Top-Down Estimation.

Scheduling.

Summary.

7. Quality Planning and Defect Estimation.

Quality Management.

Quantitative Quality Management Planning.

Summary.

8. Risk Management.

Background.

Risk Assessment.

Risk Control.

Examples.

Summary.

9. Project Management Plan.

Project Management Plan.

Example: Project Plan of WAR 2.0.

Summary.

10. Configuration Management.

Configuration Management Concepts.

Configuration Management Process.

Document Control.

Example: Configuration Management Plan of the WAR Project.

Summary.

III. PROJECT EXECUTION AND TERMINATION.

11. Life Cycle Execution.

High-Level Design.

Detailed Design.

Build.

System Testing.

Acceptance and Installation.

Summary.

12. Peer Review.

Review Process.

Data Collection.

Monitoring and Control.

Introduction of Reviews and the NAH Syndrome.

Summary.

13. Project Monitoring and Control.

Data Collection.

Project Tracking.

Quantitative Monitoring and Control.

Defect Analysis and Prevention.

Summary.

14. Project Audits.

Audit Process.

Audit Analysis.

Summary.

15. Project Closure.

Project Closure Analysis.

Archiving.

Closure Analysis Report for WAR 2.0.

Summary.

Appendix A. From ISO 9000 to CMM.

Appendix B. Managing the Software Process Improvement Project. 0201616262T04062001

Read More Show Less

Preface

Worldwide, the demand for software is increasing at a rapid pace, with no end in sight for this growth in appetite. The growth has also spawned a dramatic increase in software development activity. In turn, this increased software development activity has sharpened the focus on the processes used for building software, collectively known as the software process. Although opinions differ on the nature and formality of the software process, there is now general agreement that use of proper processes is extremely important for an organization that seeks to deliver high-quality software and increase its own productivity.

The heightened importance of the software process has engendered a need for process improvement, which also requires methods for process analysis and assessment. One of the most extensive and influential software process improvement and assessment frameworks is the Capability Maturity Model (CMM) for software developed by the Software Engineering Institute (SEI) at Carnegie Mellon University. The CMM categorizes software process maturity into five levels: from level 1 (the lowest) to level 5 (the highest). For each level, the CMM specifies some key process areas (KPAs), which represent the areas on which an organization should focus if it wants to move to a particular level. Each KPA is associated with goals that represent the requirements to be satisfied by the process for that KPA. The KPAs for different maturity levels can be used for assessing the capability of the existing process, as well as for identifying the areas that need to be strengthened so as to move the process from a lower level of maturity to a higher level.

The CMM framework is quite general and not prescriptive. Although organizations can implement CMM in different ways, relating the characteristics mentioned in the CMM to real-life practices and processes can prove difficult. This book describes the set of processes used for executing a project at Infosys Technologies Ltd., a large software house headquartered in Bangalore, India. Infosys was formally assessed at CMM level 4 in December 1997 by two SEI-authorized lead assessors.

Rather than just explaining the various technical and management processes employed by Infosys, this book describes the processes as they appear at various stages in the life cycle of a project. Because the life cycle of a project includes both technical and management processes, this approach ensures that most processes affecting a project are explained. This approach is also one to which both practitioners and students can more easily relate. It does leave out the organization-level processes for supporting and managing the process activities. Some aspects of these processes have been described here, wherever their inclusion would not break the flow of the book. In addition, an article describing the management of the CMM framework implementation at Infosys is included as Appendix B.

The book includes 15 chapters. Chapter 1 gives a brief overview of the CMM and describes some organization-level support for processes at Infosys. The remaining chapters focus on project execution, and are organized into three parts. Part I (Chapters 2 and 3) deals with processes that are executed before the project formally commences. Part II (Chapters 4 through 10) deals with project planning activities. Part III (Chapters 11 through 15) examines project execution and termination. Most chapters focus on some key task in a project and have been kept as independent as possible of the other chapters.

It is not the intent of this book to provide extensive coverage of the literature or detailed explanations of the CMM. The main goal is to describe the processes of an organization that employs the CMM framework. The book also illustrates how simple and known approaches can be combined effectively to have a highly mature overall process. It does not suggest that Infosys's approach is optimal or better than someone else's or an ideal implementation of the CMM. Likewise, it does not recommend that these processes be used by others; that decidion is left for the readers.

The positive feedback I received on my earlier textbook, An Integrated Approach to Software Engineering (Springer Verlag, 1997), which had a case study running through the book, convinced me of one thing: In software engineering, it is invaluable to have real examples with real outputs and a complete example, if possible, when explaining concepts. This book employs the same approach. Most of the examples are real in that they have been picked from real projects, and one actual project--the weekly activity report (WAR) project--is used through much of the book to illustrate how different processes interrelate. Although the processes described are used at Infosys, any sensitive numbers (for example, on quality and productivity) included may have been sanitized to maintain the company's confidentiality.

This book should prove useful to all practitioners who are interested in the software process or the CMM framework. It should be immensely helpful to those practitioners who are trying to implement the CMM in their own organizations. To help ISO organizations in their effort to move to CMM, a general study describing possible gaps in an ISO organization with respect to different levels of the CMM has been provided in Appendix A. As the book discusses how projects are executed in a successful organization, it should also be of interest to professionals who are now managing software projects. For instructors and students, it can serve as a supplementary text for a project-oriented course on software engineering, as the book provides a good view of how software is developed in a business environment, along with a case study.

It is perhaps proper to explain my own involvement with Infosys. As Vice President (Quality) at Infosys, I was one of the main architects behind the company's successful transition from ISO to CMM level 4. Although Infosys supplied all of the material I requested, I take full responsibility for any mistakes, misrepresentations, and inaccuracies that may be present in the book. Such issues are bound to occur when one tries to describe the essence of an organization's process manual, along with a case study, in such a compact book. Any deviations in these descriptions from the actual processes of Infosys are entirely my responsibility, as I decided which portions of processes to include and in what manner.

Any comments or queries about the book are welcome, and can be sent to me at jalote@iitk.ac.in. For any information regarding Infosys, visit www.itlinfosys.com or send mail to public-relations@itlininfosys.com.

--Pankaj Jalote

0201616262P04062001

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing 1 Customer Reviews
  • Anonymous

    Posted June 20, 2003

    Good book

    Good ways on how the author used the CMM to implement process improvement at Unisys but does not do much good to provide basic strategies for implementing.

    Was this review helpful? Yes  No   Report this review
Sort by: Showing 1 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)