- Amazon Student members save an additional 10% on Textbooks with promo code TEXTBOOK10. Enter code TEXTBOOK10 at checkout. Here's how (restrictions apply)
Practical Support for CMMI-SW Software Project Documentation Using IEEE Software Engineering Standards Paperback – Nov 11 2005
Special Offers and Product Promotions
No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.
To get the free app, enter your e-mail address or mobile phone number.
"...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)
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
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Most Helpful Customer Reviews on Amazon.com (beta)
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).
Look for similar items by category
- Books > Computers & Technology > Computer Science > Software Engineering > Information Systems
- Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
- Books > Computers & Technology > Project Management > PMP Exam
- Books > Computers & Technology > Software
- Books > Professional & Technical > Engineering > Telecommunications
- Books > Qualifying Textbooks - Fall 2007 > Computers & Internet
- Books > Qualifying Textbooks - Fall 2007 > Engineering
- Books > Qualifying Textbooks - Fall 2007 > Humanities
- Books > Qualifying Textbooks - Fall 2007 > Science
- Books > Science & Math
- Books > Textbooks > Computer Science & Information Systems > Software Design & Engineering
- Books > Textbooks > Engineering