|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
Wird oft zusammen gekauft
Produktinformation
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
Ist der Verkauf dieses Produkts für Sie nicht akzeptabel? |
Mehr über die Autoren
Entdecken Sie Bücher, lesen Sie über Autoren und mehr
Produktbeschreibungen
Kurzbeschreibung
-- Teaches readers to get agreement on what users want before attempting to create solutions.
-- Instruction on how to organize requirements into a single message that developers can understand.
-- Supported with practical exercises that facilitate the learning process.
Writing Better Requirements specifically focuses on how to uncover and clearly express requirements for software and systems. Loosely defined, requirements represent the required uses of a system as defined by the ultimate end user. By gathering requirements, systems builders can better learn what features need to be included, before design and coding begin. The authors write from the perspective that users own requirements, therefore users must be able to understand them. This elementary perspective yields a straightforward, easily-digested approach. Requirements are treated as simple pieces of text, supported by operational scenarios and informal diagrams. Each chapter in this book introduces a stage in the requirements process. Key terms are defined informally, explained thoroughly, and illustrated with examples. Each chapter is also supported by exercises that help the reader hone their requirements writing skills.
Synopsis
Well-written requirements are crucial to systems of all kinds. This text explains and demonstrates exactly what requirements are for, and how to write them. It provides practical techniques and defines key terms, explaining and illustrating to develop the skills of good requirements writing.
In diesem Buch
(Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Tags(Was ist das?)Bei einem Tag handelt es sich um ein Schlagwort, das zum Produkt passt.
Tags erleichtern allen Kunden die Suche und die Sortierung ihrer Lieblingsprodukte. |
Eine digitale Version dieses Buchs im Kindle-Shop verkaufen
Wenn Sie ein Verleger oder Autor sind und die digitalen Rechte an einem Buch haben, können Sie die digitale Version des Buchs in unserem Kindle-Shop verkaufen.
Weitere Informationen
Kundenrezensionen
Es gibt noch keine Kundenrezensionen auf Amazon.de
5 Sterne
4 Sterne
3 Sterne
2 Sterne
1 Sterne
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:
6 Rezensionen
28 von 29 Kunden fanden die folgende Rezension hilfreich
I love this book!
30. März 2007
Format:Taschenbuch
It's a short and to the point book on what requirements should contain; it's like a cliff-notes version of other requirements gathering books. We ordered one for our whole team and made it required reading! For anyone who doesn't have the time nor the patience to weed through 300 pages to get to the point, this is the book for you.
10 von 10 Kunden fanden die folgende Rezension hilfreich
The Book Provides Practical Advice
31. Mai 2008
Format:Taschenbuch|Von Amazon bestätigter Kauf
It is rare when you come across a project management book that is easy to read, short and full of valuable information but Writing Better Requirements meets this criteria. I like simple and to the point!
The Book Provides Practical Advice
The book provides good practical advice on writing requirements. Alexander and Stevens follow their own advice for writing requirements in the book by using simple words that contribute to the books readability. The book is written in a manner that will not intimidate non-technical personnel so it may given to the entire project team, including customers and users. (Wait... I just had a novel idea...we should teach our customers and users how to write requirements.)
Here are five of many valuable tips from Writing Better Requirements
1. Perspective on the requirements effort. The authors state approximately 5% of the project effort and up to 25% of the schedule duration should be put on project requirements.
2. Guidance on structuring requirements. Improper structuring is identified as a primary cause of poor requirements. The structuring discussion includes a useful table that documents problems and solutions for structuring requirements. For, example, the authors characterize one problem as Some requirements can be applied simultaneously or in any order and provide the common sense solution of Mark whether sections in the structure are sequences, parallels or alternatives. Overall the authors provide some good alternatives to challenges on how to effectively structure requirements.
3. Plenty of exercises. Another valuable aspect of this book are the exercises provided after a lot of the sections in the book. The exercises provided are well thought out and solutions are included at the end of the book. In addition to the exercises examples are provided to clarify and reinforce key points.
4. Guidelines on conducting a requirements workshop. Important guidelines on how to conduct a requirements workshop are discussed including room lay out and facilitation tips. The book has a good glossary of terms.
5. Lists of other sources of requirements. The book includes a nice list of other sources of requirements. One of these sources that is often overlooked is problem reports from the previous system. The authors state these problem reports can often be turned around into requirements. This is a powerful method to ensure improvement of the future system.
Writing Better Requirements should be a part of every project managers library. I give it 5 of 5 stars! Make your life easier and give it as a holiday gift for your users and customers.
Dr. James T. Brown PMP PE CSP
Author - The Handbook of Program Management
The Book Provides Practical Advice
The book provides good practical advice on writing requirements. Alexander and Stevens follow their own advice for writing requirements in the book by using simple words that contribute to the books readability. The book is written in a manner that will not intimidate non-technical personnel so it may given to the entire project team, including customers and users. (Wait... I just had a novel idea...we should teach our customers and users how to write requirements.)
Here are five of many valuable tips from Writing Better Requirements
1. Perspective on the requirements effort. The authors state approximately 5% of the project effort and up to 25% of the schedule duration should be put on project requirements.
2. Guidance on structuring requirements. Improper structuring is identified as a primary cause of poor requirements. The structuring discussion includes a useful table that documents problems and solutions for structuring requirements. For, example, the authors characterize one problem as Some requirements can be applied simultaneously or in any order and provide the common sense solution of Mark whether sections in the structure are sequences, parallels or alternatives. Overall the authors provide some good alternatives to challenges on how to effectively structure requirements.
3. Plenty of exercises. Another valuable aspect of this book are the exercises provided after a lot of the sections in the book. The exercises provided are well thought out and solutions are included at the end of the book. In addition to the exercises examples are provided to clarify and reinforce key points.
4. Guidelines on conducting a requirements workshop. Important guidelines on how to conduct a requirements workshop are discussed including room lay out and facilitation tips. The book has a good glossary of terms.
5. Lists of other sources of requirements. The book includes a nice list of other sources of requirements. One of these sources that is often overlooked is problem reports from the previous system. The authors state these problem reports can often be turned around into requirements. This is a powerful method to ensure improvement of the future system.
Writing Better Requirements should be a part of every project managers library. I give it 5 of 5 stars! Make your life easier and give it as a holiday gift for your users and customers.
Dr. James T. Brown PMP PE CSP
Author - The Handbook of Program Management
4 von 4 Kunden fanden die folgende Rezension hilfreich
Vance Hilderman's Review of "Better Requirements"
31. März 2010
Format:Taschenbuch|Von Amazon bestätigter Kauf
I found this book to be very helpful in developing an overall process sense of requirements development. This book provided an excellent synopsis of "why" good requirements are important and what the pitfalls are when such is lacking. The examples were both relevant and descriptive. As an overall initial treatise on requirements, this book was terrific. As such, the focus is perhaps more upon managers and leaders of teams, rather than the actual developer of detailed requirements. Ideally there would be a follow-on companion volume with greater detail to better aid the actual developer of requirements including checklists and several case studies, as well as more detailed examples. But I completely recommend this book. Vance Hilderman, March 2010.
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
Kunden diskutieren
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
Lieblingslisten
Ähnliche Artikel finden
Anhand des Sachgebietes nach ähnlichen Produkten suchen:
Ihr Kommentar
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
|
