Raymond Kehoe – författare

The ISO 9000-3 Guideline is meant to serve as a guide for the application of the ISO 9001 Standard to the development, supply, and maintenance of software. The Standard and Guideline are being used throughout the software industry as a benchmark for software product and process quality. As yet few software organizations meet the process quality required to meet the Standard, but increasingly the industry will seek to ensure that software organizations are certified under the Standard. This book presents senior managers, software project managers and software developers with a simple, concise, step-by-step explanation of the Guideline and a hands-on means to implement practices and procedures needed to meet the requirements of the ISO 9001 Standard and the ISO 9000-3 Guideline. The authors discuss the principles and practice of software engineering and provide templates of engineering documents to accompany the Guideline. As a result, this book will help software companies define their own software engineering processes to develop high quality software products.

Purpose The purpose of this book is to provide the reader with an understanding of the ISO 9000-3 guideline and how it applies to the specification, development, test, and maintenance of software. We will show that the basic practices and procedures that define software engineering and the ISO guideline are, for all intents and purposes, one and the same. We hope that the readers of this book will use the information found within not only to pass the certification audit but as a tool to be used to create the well-managed engineering environment needed to create reliable, well­ engineered products in a consistent manner. Audience This book is intended for senior software engineers, software managers, and non­ software managers within software organizations whose aim is to create an engi­ neering environment within their company or organization. In addition, individ­ uals outside the software organization who have responsibility for the specification of the software product and preparing their organization to take ownership of the developed product will find this book of great interest. Finally, those who must choose software companies to do business with or audit software companies to determine their ability to engineer and maintain a software product will find this book helpful. 2 Introduction Overview This book is made up of twenty-four chapters that can be grouped into four sections. Chapter 1 through Chapter 4 set the basis for the following chapters that deal directly with the guideline.