- Paperback: 608 pages
- Publisher: Addison-Wesley Professional; 1 edition (Dec 17 2001)
- Language: English
- ISBN-10: 0201745704
- ISBN-13: 978-0201745702
- Product Dimensions: 23.7 x 18.4 x 3.1 cm
- Shipping Weight: 1.1 Kg
- Average Customer Review: 5.0 out of 5 stars See all reviews (3 customer reviews)
- Amazon Bestsellers Rank: #396,368 in Books (See Top 100 in Books)
- See Complete Table of Contents
|
||||||||||||||||||
|
||||||||||||||||||
|
||||||||||||||||||
Product Details |
Product Description
From Amazon
Suitable for most any IT professional who wants to build better software, Software Requirements: Styles and Techniques offers a surprisingly readable textbook-style treatment of software engineering's numerous attempts to get it right with defining requirements. Surveying almost every conceivable style of defining requirements, yet remaining thoroughly practical, this book can let your organisation do more with its requirements documents, which is a good step to creating software that succeeds better with your users.
Though everyone in software design knows about requirements, actual examples have usually remained shrouded in secrecy whether out of concerns over intellectual property or client confidentiality. One considerable strength of this title is that the author has seen many good and bad requirements documents and come up with several complete samples for a Danish shipyard and two hospital systems that can be published here.
Reading Software Requirements will likely convince you that you can do better with your requirements documents. Though there is no one "best" way, certain types of requirements work for certain situations better than others. This text can help you choose. Certain to be required reading for serious software analysts, this title can also benefit virtually anyone who works with software design documents. Its clear presentation style, remarkably devoid of jargon, helps make this book a great resource for a wide range of readers, with or without a background in traditional software engineering. --Richard Dragan
Book Description
Most IT systems fail to meet expectations. They don't meet business goals and don't support users efficiently. Why? Because the requirements didn't address the right issues. Writing a good requirements specification doesn't take more time. This book shows how it is done - many times faster and many times smarter.
This book covers many aspects of requirements.
Styles- Traditional and more cost/effective ways of expressing requirements.
Techniques- Ways of gathering, verifying, and maintaining requirements; ways of getting commitment from the stakeholders and support - yet limit - innovation; ways of ensuring that you meet your business goals.
It discusses the styles and techniques useful for different project types, for instance software developed specifically for the customer, software bought off-the shelf and adapted for the customer (COTS), and software developed for a broad market.
The book illustrates everything through real-life examples. It also deals with difficult requirements, for instance how to specify ease-of-use, how to specify very complex computations, and how to deal with 200 reports that the old system has, and the new system may or may not need.
The book shows two complete, real-life specifications and large parts of several others. It also has exercises and figures for presentation.
This book covers many aspects of requirements.
Styles- Traditional and more cost/effective ways of expressing requirements.
Techniques- Ways of gathering, verifying, and maintaining requirements; ways of getting commitment from the stakeholders and support - yet limit - innovation; ways of ensuring that you meet your business goals.
It discusses the styles and techniques useful for different project types, for instance software developed specifically for the customer, software bought off-the shelf and adapted for the customer (COTS), and software developed for a broad market.
The book illustrates everything through real-life examples. It also deals with difficult requirements, for instance how to specify ease-of-use, how to specify very complex computations, and how to deal with 200 reports that the old system has, and the new system may or may not need.
The book shows two complete, real-life specifications and large parts of several others. It also has exercises and figures for presentation.
Inside This Book
(Learn More)
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organize and find favorite items. |
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most helpful customer reviews
1 of 1 people found the following review helpful
5.0 out of 5 stars
Original book,! Distinctive approach for requirements.,
By Radouane OUDRHIRI (London United Kingdom) - See all my reviews
This review is from: Software Requirements: Styles & Techniques (Paperback)
Very original book; a rich source of knowledge and reflection. The approach is quite distinctive; it combines industrial and academic experience. We feel from the examples presented in the book and their conceptualisation that the author went through a long and painful (but fruitful) learning process of requirements engineering.The author presents various techniques and models, and he stresses that there is no RIGHT model for all situations. He also discusses practical issues/problems, with a balance between pragmatism and perfection. The book discusses the types of projects, contracts and appropriate requirement elicitation/engineering techniques to be considered. One of the rare books, that discuss seriously Quality Requirements, not from the surface and not just by listing them from standards, but in details with practical examples, especially usability. I highly recommend this book for anyone who deals with requirements! Practitioners, students and teachers.
5.0 out of 5 stars
A very good book on requierements,
By
This review is from: Software Requirements: Styles & Techniques (Paperback)
Many books I read talk about requirement analysis living the previuos steps (exlicitation and documentation) to the reader.This books presents, in a very pleasant way, the different forms we have to describe requirements in a SOW or a SRS. It compares differents style and gives very good advices. A must to have.
5.0 out of 5 stars
Excellent material,
This review is from: Software Requirements: Styles & Techniques (Paperback)
If you've ever worked/will work with getting requirements in a software project, you can't go wrong with this book. Taking you first through the basics, Lauesen then goes on to discuss the different techniques of specifying requirements under different conditions. Man, this is gonna save your bacon one of these days... :)
Share your thoughts with other customers: Create your own review
Want to see more reviews on this item?
|
|
Listmania!
Look for similar items by category
- Books > Computers & Internet > Computer Science > Software Engineering > Design Tools & Techniques
- Books > Computers & Internet > Programming > Software Design, Testing & Engineering > Software Development
- Books > Computers & Internet > Software
- Books > Qualifying Textbooks - Fall 2007 > Computers & Internet
Look for similar items by subject
Feedback
Would you like to update product info or give feedback on images?
|
