Auto boutiques-francophones Simple and secure cloud storage SmartSaver Cyber Monday Deals Week in Home & Kitchen Kindle Black Friday Deals Week in Music SGG Countdown to Cyber Monday in Lawn & Garden
Only 1 left in stock (more on the way).
Ships from and sold by Gift-wrap available.
Practical Support for CMM... has been added to your Cart
+ CDN$ 6.49 shipping
Used: Good | Details
Sold by Daily-Deal-
Condition: Used: Good
Comment: This Book is in Good Condition. Used Copy With Light Amount of Wear. 100% Guaranteed.
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See all 2 images

Practical Support for CMMI-SW Software Project Documentation Using IEEE Software Engineering Standards Paperback – Nov 11 2005

See all formats and editions Hide other formats and editions
Amazon Price
New from Used from
"Please retry"
CDN$ 148.99
CDN$ 126.00 CDN$ 43.24

Cyber Monday Deals Week in Books

No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.

  • Apple
  • Android
  • Windows Phone
  • Android

To get the free app, enter your e-mail address or mobile phone number.

Product Details

  • Paperback: 360 pages
  • Publisher: Wiley-IEEE Computer Society Pr; 1 edition (Nov. 11 2005)
  • Language: English
  • ISBN-10: 0471738492
  • ISBN-13: 978-0471738497
  • Product Dimensions: 17.8 x 1.8 x 25.4 cm
  • Shipping Weight: 658 g
  • Amazon Bestsellers Rank: #3,076,590 in Books (See Top 100 in Books)
  •  Would you like to update product info, give feedback on images, or tell us about a lower price?

  • See Complete Table of Contents

Product Description


"...a useful bridge into the world of IEEE software engineering standards..." (Software Quality Professional, September 2006)

From the Back Cover

An essential guide to CMMI®-SW documentation

The CMMI®-SW, a compendium of recommended requirements for software engineering, promotes the continuous evolution of improved software and system engineering processes. Organizations seeking to satisfy documentation requirements of CMMI®-SW Levels 2 and 3 will find invaluable support in this clear and systematic text.

Beginning with a comprehensive summary of CMMI®-SW, the authors present detailed guidance on the implementation of these industry standards, including how to define and train a process team, set goals, fix timelines, baseline and implement processes, and perform gap analysis and self-auditing procedures. In addition, they describe common procedural pitfalls and how to avoid them.

Practical Support for CMMI®-SW Software Project Documentation offers:

  • Detailed organizational policy examples
  • An integrated set of over twenty deployable document templates
  • Examples of over fifty common work products required in support of assessment activities

A companion to Jumpstart CMM®/CMMI® Software Process Improvement, this in-depth reference will expedite the design and development of process and product documentation. Even organizations not pursuing CMMI® accreditation will learn how the application of IEEE standards can facilitate the development of sound software engineering practices.

See all Product Description

Inside This Book

(Learn More)
First Sentence
Moving an organization from the chaotic environment of free-form development toward a more controlled and documented process can be overwhelming to those tasked to make it happen. Read the first page
Explore More
Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Search inside this book:

Customer Reviews

There are no customer reviews yet on
5 star
4 star
3 star
2 star
1 star

Most Helpful Customer Reviews on (beta) 1 review
1 of 1 people found the following review helpful
Helpful for Starting a SEPG team and reaching CMMI-ML-3 Dec 29 2008
By Mark A. Lucas - Published on
Format: Paperback Verified Purchase
I am in a very large organization that is making all of our projects (at the least) CMMI Maturity level-3 compliant. We have Level-5 software factories (offshore centers), some Level-4 programs/projects, and 1,000s of Level-3 compliant (internally appraised) projects.
However, we have "custom" project management document templates that still rely tremendously on the author's (project manager) previous experience writing these references or LUCK (b/c a lower level grunt is actually writing the document!).
The IEEE project management documents (project management approach, risk and issue management plan, change management plan, etc.) are not perfect, but they ARE based on hundreds of project experiences and years or experience and input from 100s of IEEE member organizations.
This book provides the table of contents from the IEEE documents but Not 100% of the text (you have to spend a few $100usd to be a IEEE member to get the actual templates).
BUT, if you are starting a SEPG (software engineering process group) or Quality Management System (QMS) team dont waste time trying to create your templates from scratch. Step-1, get this book and create the ourline of the documents, step-2 harvest the best examples from your projects and insert the best sample sections into the templates.
Remember that 60-80% of these documents are essentially "boiler-plate" that apply to most of your projects, or projects of a certain type.
I RECOMEND that you fill in your templates with as much of the "boilerplate" as possible and make these management documents as close to "fill in the blank" as possible. Using the IEEE standards as a baseline for the structure and content will help you significantly.

CAVEATS: IEEE standards, like way too many I.T. documents, includes the Glossary section in the beginning of the document. Although this may be helpful to define key words before they are encountered, I find the least obtrusive location for the Glossary is as an Appendix. This is not only a common location for documents in many many other fields, it encourages the glossary to be as small or large as it needs to be, rather than drowning the reader with terms they may already know in the beginning of the document.
DITTO for large Tables and Diagrams. I suggest they are located either in the Appendix or as a separate external file that is maintained separately (and is easily referenced by several documents - something dificult to do if they are buried in a single document).