skip to main content
Skip header Section
CMM in practice: processes for executing software projects at InfosysOctober 1999
  • Author:
  • Pankaj Jalote
Publisher:
  • Addison-Wesley Longman Publishing Co., Inc.
  • 75 Arlington Street, Suite 300 Boston, MA
  • United States
ISBN:978-0-201-61626-2
Published:01 October 1999
Pages:
372
Skip Bibliometrics Section
Bibliometrics
Abstract

No abstract available.

Cited By

  1. Pardo C, Pino F, Garca F, Piattini M and Baldassarre M (2012). An ontology for the harmonization of multiple standards and models, Computer Standards & Interfaces, 34:1, (48-59), Online publication date: 1-Jan-2012.
  2. Baldassarre M, Caivano D, Pino F, Piattini M and Visaggio G A strategy for painless harmonization of quality standards Proceedings of the 11th international conference on Product-Focused Software Process Improvement, (395-408)
  3. Liu G and Wang W Research an educational software defect prediction model based on SVM Proceedings of the Entertainment for education, and 5th international conference on E-learning and games, (215-222)
  4. Agrawal M and Chari K (2007). Software Effort, Quality, and Cycle Time, IEEE Transactions on Software Engineering, 33:3, (145-156), Online publication date: 1-Mar-2007.
  5. Jäntti M, Miettinen A, Pylkkänen N and Kainulainen T Improving the problem management process from knowledge management perspective Proceedings of the 8th international conference on Product-Focused Software Process Improvement, (389-401)
  6. Wang Q, Jiang N, Gou L, Che M and Zhang R Practical experiences of cost/schedule measure through earned value management and statistical process control Proceedings of the 2006 international conference on Software Process Simulation and Modeling, (348-354)
  7. Jäntti M, Toroi T and Eerola A Difficulties in establishing a defect management process Proceedings of the 7th international conference on Product-Focused Software Process Improvement, (142-150)
  8. Haapio T and Ahonen J A case study on the success of introducing general non-construction activities for project management and planning improvement Proceedings of the 7th international conference on Product-Focused Software Process Improvement, (151-165)
  9. Jäntti M and Kinnunen K Improving the software problem management process Proceedings of the 13th European conference on Software Process Improvement, (40-49)
  10. Jalote P and Jain G (2006). Assigning tasks in a 24-h software development model, Journal of Systems and Software, 79:7, (904-911), Online publication date: 1-Jul-2006.
  11. Yoo C, Yoon J, Lee B, Lee C, Lee J, Hyun S and Wu C (2006). A unified model for the implementation of both ISO 9001, Journal of Systems and Software, 79:7, (954-961), Online publication date: 1-Jul-2006.
  12. Jedlitschka A, Hamann D, Göhlert T and Schröder A Adapting PROFES for use in an agile process Proceedings of the 6th international conference on Product Focused Software Process Improvement, (502-516)
  13. Jalote P and Saxena A (2002). Optimum Control Limits for Employing Statistical Process Control in Software Process, IEEE Transactions on Software Engineering, 28:12, (1126-1134), Online publication date: 1-Dec-2002.
  14. ACM
    (2019). Estimating software projects, ACM SIGSOFT Software Engineering Notes, 26:4, (60-67), Online publication date: 1-Jul-2001.
  15. ACM
    Jalote P Moving from ISO9000 to higher levels of the CMM (tutorial session) Proceedings of the 22nd international conference on Software engineering
Contributors
  • Indraprastha Institute of Information Technology, Delhi

Recommendations

Reviews

Donald Rajinder Chand

The Software Engineering Institute (SEI)'s approach to software process improvement based on the Capability Maturity Model (CMM) is recognized as a major contribution to the field of software engineering: it has furthered both the theoretical underpinnings and the practice of software development. Despite its validated and substantiated success in the aerospace industry and among Department of Defense subcontractors, the SEI approach has been slow in diffusing in the information systems (IS) arena. The view of the SEI approach in the IS community is that the underlying software development model is not applicable to the task of applications development in IS shops. By describing the CMM-based processes for executing software projects at Infosys, a highly successful systems development company that has been assessed at maturity level 4 in the SEI maturity framework, this book provides concrete evidence that CMM is relevant to IS. Jalote divides the software development processes at Infosys into three parts: project initiation, project planning, and project execution and termination. In the project initiation part, the book focuses on the business activity of proposals and contracts and on a key software development area, namely, requirements specification and management. In the project planning part, it discusses the basic planning activity of effort estimation and scheduling, and the process management areas of process definition and tailoring, process database and process capability baseline, and quality planning and defect estimation. Project planning also includes the key process areas (KPAs) of risk management, project management planning, and configuration management. The project execution and termination part addresses the software development areas of life cycle execution and the KPAs of peer review and project monitoring and control. It also includes the business activities of project audits and project closure. The focus of each chapter is on how a specific KPA or business activity is performed at Infosys. Each chapter begins with a brief overview of the KPA or business activity; describes the processes used at Infosys for that purpose; and ends with useful templates, examples, and sample documents. The Weekly Activity Report system project is used as a case study to illustrate the processes employed in a project. There is plenty of literature that describes and explains CMM and the SEI process, but there is a shortage of useful information about how to implement the KPAs in different software development settings in terms of what to measure and how to measure it. This book is a small step in overcoming this shortage. More significantly, it provides information that IS organizations can adapt to improve their systems development. I have been teaching a graduate elective on managing systems development in an IS curriculum for the past four years, and have used Watts Humphrey's Managing the software process [1] as a text. This semester I complemented my lectures with templates and samples provided in this book, and found that Humphrey's material became more meaningful and relevant to the IS professionals enrolled in my class. This book is a useful supplement to the typical primary text in software engineering, software process management, or project management courses.

Access critical reviews of Computing literature here

Become a reviewer for Computing Reviews.