» » Practical Support for CMMI-SW Software Project Documentation Using IEEE Software Engineering Standards

Fb2 Practical Support for CMMI-SW Software Project Documentation Using IEEE Software Engineering Standards ePub

by John W. Walz,Susan K. Land

Category: Programming
Subcategory: Technologies and Computers
Author: John W. Walz,Susan K. Land
ISBN: 0471738492
ISBN13: 978-0471738497
Language: English
Publisher: Wiley-IEEE Computer Society Pr (November 11, 2005)
Pages: 360
Fb2 eBook: 1930 kb
ePub eBook: 1709 kb
Digital formats: lit mobi rtf lrf

Software process definition, documentation, and improvement shouldbe an integral part of every software ion

Software process definition, documentation, and improvement shouldbe an integral part of every software ion. This book addresses the specific ments in support of the CMMI-SW ® byproviding detailed documentation guidance in the form of: Detailed organizational policy examples. An Integrated set of over 20 deployable documenttemplates.

Software process definition, documentation, and improvement should be an integral part of every software engineering organization

Software process definition, documentation, and improvement should be an integral part of every software engineering organization. This book addresses the specific documentation requirements in support of the CMMI-SW® by providing detailed documentation guidance in the form of:, Detailed organizational policy examples. An Integrated set of over 20 deployable document templates. Examples of over 50 common work products required in support of assessment activities. Examples of organizational delineation of process documentation.

Susan K. Land (Author), John W. Walz (Author). ISBN-13: 978-0471768678. Organizations seeking to satisfy the documentation requirements associated with ISO 9001 will find invaluable support in Practical Support for ISO 9001 Software Project Documentation while aiming to enhance customer satisfaction and achieve continual improvement of its performance.

Furthermore, in large complex distributed systems and continuous running systems, the.

Start by marking Practical Support for CMMI-SW Software Project . John W. Walz (Goodreads Author).

Start by marking Practical Support for CMMI-SW Software Project Documentation Using IEEE Software Engineering Standards as Want to Read: Want to Read savin. This book addresses the specific documentation requirements in support of the CMMI-SW(R) by providing detailed documentation guidance in the form of: Detailed organizational policy examples. An Integrated set of over 20 deployable document temp Software process definition, documentation, and improvement should be an integral part of every software engineering organization. Land ; John W. Walz. 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 View more. Book Type: Wiley-IEEE Press. Pages: 500, Chapters 1-15. Topics: Computing and Processing.

4 Audience Software Project Managers Software Engineering Professionals Software Engineering Managers CMMI Organizations seeking to satisfy documentation requirements for Levels 2 & 3 of Capability Maturity Model Integrated for Software (CMMI -SW) 2006 John Walz 4 4. . 5 Overview Problem Statement Sftw Engr organizations face pressures and risks of missed deliveries and cost overruns Proposed Solution Organizations using CMMI -SW model, report significant reductions in missed deliveries.

Book Overview This book addresses the specific documentation requirements in support of the CMMI-SW? by providing detailed.

Software process definition, documentation, and improvement should be an integral part of every software engineering organization. This book addresses the specific documentation requirements in support of the CMMI-SW? by providing detailed documentation guidance in the form of: Detailed organizational policy examples.

Main Author: Land, Susan K. Other Authors: Walz, John W. Format

Practical support for CMMI-SW software project documentation : using IEEE software engineering standards /. Saved in: Main Author: Land, Susan K. Format: Book. Published: Hoboken, .

Software process definition, documentation, and improvement shouldbe an integral part of every software engineeringorganization.  This book addresses the specific documentationrequirements in support of the CMMI-SW® byproviding detailed documentation guidance in the form of:  Detailed organizational policy examples.An Integrated set of over 20 deployable documenttemplates.Examples of over 50 common work products required in support ofassessment activities.Examples of organizational delineation of processdocumentation. 

This book provides a set of IEEE Software EngineeringStandards-based templates that support the documentation requiredfor all activities associated with software development projects.The goal is to provide practical support for individualsresponsible for the development and documentation of softwareprocesses and procedures.  The objective is to present thereader with an integrated set of documents that support therequirements of the CMMI-SW® Levels 2 and 3. This book is meant to both complement and extend the informationprovided in JumpstartCMM®/CMMI® SoftwareProcess Improvement Using IEEE Software EngineeringStandards.  Jumpstart provides a detailed mappingof both the CMM® and the CMMI-SW®to the IEEE standards set and provides a logical basis for thematerial contained within this text.

 It is hoped that this book will provide specific supportfor organizations pursuing software process definition andimprovement.  For organizations that do not wish to pursueCMMI® accreditation, this document will show howthe application of IEEE Standards can facilitate the development ofsound software engineering practices. It also comes with aCD-Rom.

Comments to eBook Practical Support for CMMI-SW Software Project Documentation Using IEEE Software Engineering Standards
Androlhala
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).
Jaberini
My instructor @ BTC approved the book
Related to Practical Support for CMMI-SW Software Project Documentation Using IEEE Software Engineering Standards
Apache HTTP Server 2.2 Official Documentation - Volume I. Server Administration eBook
Fb2 Apache HTTP Server 2.2 Official Documentation - Volume I. Server Administration ePub
Perspectives on Software Documentation: Inquiries and Innovations (Baywood's Technical Communications Series (Unnumbered).) eBook
Fb2 Perspectives on Software Documentation: Inquiries and Innovations (Baywood's Technical Communications Series (Unnumbered).) ePub
Designing, Writing, and Producing Computer Documentation (Software Engineering Series) eBook
Fb2 Designing, Writing, and Producing Computer Documentation (Software Engineering Series) ePub
Bad Software: What To Do When Software Fails eBook
Fb2 Bad Software: What To Do When Software Fails ePub
Aspiration Based Decision Support Systems: Theory, Software and Applications (Lecture Notes in Economics Mathematical Systems) eBook
Fb2 Aspiration Based Decision Support Systems: Theory, Software and Applications (Lecture Notes in Economics  Mathematical Systems) ePub
Software Testing and Continuous Quality Improvement, Second Edition eBook
Fb2 Software Testing and Continuous Quality Improvement, Second Edition ePub
Documentation of Software Products: Recommendations for Producers and Users eBook
Fb2 Documentation of Software Products: Recommendations for Producers and Users ePub
Best Practices for the Formal Software Testing Process: A Menu of Testing Tasks eBook
Fb2 Best Practices for the Formal Software Testing Process: A Menu of Testing Tasks ePub
Developing Performance Support for Computer Systems: A Strategy for Maximizing Usability and Learnability eBook
Fb2 Developing Performance Support for Computer Systems: A Strategy for Maximizing Usability and Learnability ePub