Overview
- Authors:
-
-
Raymond Kehoe
-
San Jose, USA
-
Alka Jarvis
-
Palo Alto, USA
Access this book
Other ways to access
Table of contents (25 chapters)
-
Front Matter
Pages i-xiii
-
- Raymond Kehoe, Alka Jarvis
Pages 1-2
-
- Raymond Kehoe, Alka Jarvis
Pages 3-5
-
- Raymond Kehoe, Alka Jarvis
Pages 7-17
-
- Raymond Kehoe, Alka Jarvis
Pages 19-24
-
- Raymond Kehoe, Alka Jarvis
Pages 25-36
-
- Raymond Kehoe, Alka Jarvis
Pages 37-43
-
- Raymond Kehoe, Alka Jarvis
Pages 45-50
-
- Raymond Kehoe, Alka Jarvis
Pages 51-57
-
- Raymond Kehoe, Alka Jarvis
Pages 59-66
-
- Raymond Kehoe, Alka Jarvis
Pages 67-70
-
- Raymond Kehoe, Alka Jarvis
Pages 71-85
-
- Raymond Kehoe, Alka Jarvis
Pages 87-91
-
- Raymond Kehoe, Alka Jarvis
Pages 93-102
-
- Raymond Kehoe, Alka Jarvis
Pages 103-110
-
- Raymond Kehoe, Alka Jarvis
Pages 111-120
-
- Raymond Kehoe, Alka Jarvis
Pages 121-131
-
- Raymond Kehoe, Alka Jarvis
Pages 133-138
-
- Raymond Kehoe, Alka Jarvis
Pages 139-141
-
- Raymond Kehoe, Alka Jarvis
Pages 143-147
About this book
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.
Authors and Affiliations
-
San Jose, USA
Raymond Kehoe
-
Palo Alto, USA
Alka Jarvis