Amazon cover image
Image from Amazon.com
Image from Google Jackets

Requirements engineering : a good practice guide / Ian Sommerville and Pete Sawyer.

By: Contributor(s): Material type: TextTextPublication details: Chichester, Eng. ; New York : Wiley, 1999.Description: xi, 391 p. : ill. ; 24 cmISBN:
  • 9780471974444
Subject(s): DDC classification:
  • 005.1   21
Contents:
Practical Process Improvement -- The Requirements Document -- Requirements Elicitation -- Requirements Analysis and Negotiation -- Describing Requirements -- System Modelling -- Requirements Validation -- Requirements Management -- Requirements Engineering for Critical Systems -- System Modelling with Structured Methods -- Formal Specification -- Viewpoints -- Index.
Summary: 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 organisatioSummary: This text shows how requirements should drive the software development cycle and reflect the needs of the system users. The "good practice" advice is written in a clear and jargon-free style, and information is presented in the form of FAQ
Tags from this library: No tags from this library for this title. Log in to add tags.
Star ratings
    Average rating: 0.0 (0 votes)
Holdings
Item type Current library Call number Copy number Status Date due Barcode
Books Books Main library General Stacks 005.1 / SO.R 1999 (Browse shelf(Opens below)) 1 Checked out 09/30/2021 003296

Includes bibliographical references and index.

Practical Process Improvement -- The Requirements Document -- Requirements Elicitation -- Requirements Analysis and Negotiation -- Describing Requirements -- System Modelling -- Requirements Validation -- Requirements Management -- Requirements Engineering for Critical Systems -- System Modelling with Structured Methods -- Formal Specification -- Viewpoints -- Index.

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 organisatio

This text shows how requirements should drive the software development cycle and reflect the needs of the system users. The "good practice" advice is written in a clear and jargon-free style, and information is presented in the form of FAQ

1

There are no comments on this title.

to post a comment.