Requirements Engineering: A Good Practice Guide [Englisch] [Taschenbuch]

Defining what the customer wants is often a difficult aspect of creating successful software. However, Ian Sommerville and Pete Sawyer handle the topic with intelligence and depth in Requirements Engineering: A Good Practice Guide. The authors provide practical advice on how to make sure you deliver quality software that the customer wants and needs, all within budget.

The text first outlines what requirements engineering is and how it fits into the software engineering process. The authors then use a question-and-answer approach, short chapters, and highlighted tips to show how to define and develop a process for creating reliable software in your organization. Sommerville and Sawyer consider some ad hoc ways to improve your customer requirements documents and some more rigorous approaches, such as ISO 9000 standards for software engineering and formal specifications (where the correctness of software can be proved mathematically). Requirements Engineering can be a little dry, but it covers a vital area of software design that can benefit almost all developers.

"A marvellous book.a unique focus on what practising engineers need to do." Watts Humphrey, Software Engineering Institute, USA Requirements Engineering A good practice guide Find more RE resources at this web support site http://www.comp.lancs.ac.uk/computing/resources/re-gpg/ Visit our Web page! http://www.wiley.com/ compbooks/ Requirements engineering is the process of discovering, documenting and managing the requirements for a computer-based system. The goal of requirements engineering is to produce a set of system requirements which, as far as possible, is complete, consistent, relevant and reflects what the customer actually wants. Although this ideal is probably unattainable, the use of a systematic approach based on engineering principles leads to better requirements than the informal approach which is still commonly used. This book presents a set of guidelines which reflect the best practice in requirements engineering. Based on the authors' experience in research and in software and systems development, these guidelines explain in an easy-to-understand way how you can improve your requirements engineering processes. The guidelines are applicable for any type of application and, in general, apply to both systems and software engineering. The guidelines here range from simple 'common sense' to those which propose the introduction of complex new methods. The guidelines and process improvement schemes have been organised so that you can pick and choose according to your problems, goals and available budget. There are few dependencies between guidelines so you can introduce them in any order in your organisation. Guidelines presented in the book
* are consistent with ISO 9000 and CMM
* are ranked with cost/benefit analysis
* give implementation advice
* can be combined and applied to suit your organisation's needs
* are supported by a web page pointing to RE tools and resources

"A marvellous book.a unique focus on what practising engineers need to do." Watts Humphrey, Software Engineering Institute, USA Requirements Engineering A good practice guide Find more RE resources at this web support site http://www comp.lancs.ac.uk/computing/resources/re-gpg/ Visit our Web page! http://www wiley.com/ compbooks/ Requirements engineering is the process of discovering, documenting and managing the requirements for a computer-based system. The goal of requirements engineering is to produce a set of system requirements which, as far as possible, is complete, consistent, relevant and reflects what the customer actually wants. Although this ideal is probably unattainable, the use of a systematic approach based on engineering principles leads to better requirements than the informal approach which is still commonly used. This book presents a set of guidelines which reflect the best practice in requirements engineering. Based on the authors' experience in research and in software and systems development, these guidelines explain in an easy-to-understand way how you can improve your requirements engineering processes.

The guidelines are applicable for any type of application and, in general, apply to both systems and software engineering. The guidelines here range from simple 'common sense' to those which propose the introduction of complex new methods. The guidelines and process improvement schemes have been organised so that you can pick and choose according to your problems, goals and available budget. There are few dependencies between guidelines so you can introduce them in any order in your organisation. Guidelines presented in the book are consistent with ISO 9000 and CMM are ranked with cost/benefit analysis give implementation advice can be combined and applied to suit your organisation's needs are supported by a web page pointing to RE tools and resources

Sci Tech News, Sept 1997
Presents guidelines which reflect good practice in requirements engineering, based on the authors' experience in research and in software and systems development. The guidelines range from common sense tips to complex new methods, and can be used in any order which suits the reader's problems, goals and budget. Guidlelines are consistent with ISO 9000 and CMM, are ranked with cost and benefit analysis, include implementation advice, and can be combined and applied to suit an organization's needs.

"A marvellous book.a unique focus on what practising engineers need to do." Watts Humphrey, Software Engineering Institute, USA Requirements Engineering A good practice guide Find more RE resources at this web support site http://www.comp.lancs.ac.uk/computing/resources/re-gpg/ Visit our Web page! http://www.wiley.com/ compbooks/ Requirements engineering is the process of discovering, documenting and managing the requirements for a computer-based system. The goal of requirements engineering is to produce a set of system requirements which, as far as possible, is complete, consistent, relevant and reflects what the customer actually wants. Although this ideal is probably unattainable, the use of a systematic approach based on engineering principles leads to better requirements than the informal approach which is still commonly used. This book presents a set of guidelines which reflect the best practice in requirements engineering. Based on the authors' experience in research and in software and systems development, these guidelines explain in an easy-to-understand way how you can improve your requirements engineering processes. The guidelines are applicable for any type of application and, in general, apply to both systems and software engineering. The guidelines here range from simple 'common sense' to those which propose the introduction of complex new methods. The guidelines and process improvement schemes have been organised so that you can pick and choose according to your problems, goals and available budget. There are few dependencies between guidelines so you can introduce them in any order in your organisation. Guidelines presented in the book
* are consistent with ISO 9000 and CMM
* are ranked with cost/benefit analysis
* give implementation advice
* can be combined and applied to suit your organisation's needs
* are supported by a web page pointing to RE tools and resources