In weniger als einer Minute können Sie mit dem Lesen von Discovering Real Business Requirements for Software Proje... auf Ihrem Kindle beginnen. Sie haben noch keinen Kindle? Hier kaufen.

An Ihren Kindle oder ein anderes Gerät senden

 
 
 

Kostenlos testen

Jetzt kostenlos reinlesen

An Ihren Kindle oder ein anderes Gerät senden

Lesen Sie Bücher auf Ihrem Computer oder auf anderen Mobilgeräten mit unseren GRATIS Kindle Lese-Apps.
Discovering Real Business Requirements for Software Project Success (Computing Library) (Computing Library S.)
 
 

Discovering Real Business Requirements for Software Project Success (Computing Library) (Computing Library S.) [Kindle Edition]

Robin F. Goldsmith

Digitaler Listenpreis: EUR 69,95 Was ist das?
Kindle-Preis: EUR 55,96 Inkl. MwSt. und kostenloser drahtloser Lieferung über Amazon Whispernet

Weitere Ausgaben

Amazon-Preis Neu ab Gebraucht ab
Kindle Edition EUR 55,96  
Gebundene Ausgabe EUR 78,99  

Produktbeschreibungen

Kurzbeschreibung

"While a number of books on the market deal with software requirements, this is the first resource to offer you a methodology for discovering and testing the real business requirements that software products must meet in order to provide value. The book provides you with practical techniques that help prevent the main causes of requirements creep, which in turn enhances software development success and satisfaction among the organizations that apply these approaches. Complementing discovery methods, you also learn more than 21 ways to test business requirements from the perspectives of assessing suitability of form, identifying overlooked requirements, and evaluating substance and content.

The powerful techniques and methods presented are applied to a real business case from a company recognized for world-class excellence. You are introduced to the innovative Problem Pyramidtm technique which helps you more reliably identify the real problem and requirements content. From an examination of key methods for gathering and understanding information about requirements, to seven guidelines for documenting and communicating requirements, while avoiding analysis paralysis, this book is a comprehensive, single source for uncovering the real business requirements for your software development projects."

Synopsis

Robin Goldsmith here explains why it is crucial to distinguish between business and technical requirements when developing new software, and provides a methodology for ensuring that business needs are met.

Produktinformation

  • Format: Kindle Edition
  • Dateigröße: 1434 KB
  • Seitenzahl der Print-Ausgabe: 241 Seiten
  • Verlag: Artec House (1. März 2004)
  • Verkauf durch: Amazon Media EU S.à r.l.
  • Sprache: Englisch
  • ASIN: B001REFS1E
  • Text-to-Speech (Vorlesemodus): Aktiviert

  •  Ist der Verkauf dieses Produkts für Sie nicht akzeptabel?

Mehr über den Autor

Robin F. Goldsmith
Entdecken Sie Bücher, lesen Sie über Autoren und mehr

Besuchen Sie die Seite von Robin F. Goldsmith auf Amazon

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.
 

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
10 von 10 Kunden fanden die folgende Rezension hilfreich
Testing Requirements is Part of Discovering Requirements 2. September 2004
Von Johanna Rothman - Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe
If you ever wanted to know if your requirements were accurate and complete, this book will help. As Robin says on p. 13, "...we're going to intermix discovery methods with techniques for testing the adequacy of requirements." Using his problem pyramid - which includes a way to measure the problem and the solution - Robin discusses several techniques to elicit and define requirements.

Robin defines 64 techniques to test requirements - throughout a project. For example, test method #17, "identify assumptions" is common sense that too few people remember. Test method #53 is "Defining acceptance criteria," a technique useful for any project if you want to know you've built what the customer wanted.

Between the problem pyramid emphasis on measurement and the various tests, the book can help you meet its promise of preventing too much requirements change throughout a project.
10 von 10 Kunden fanden die folgende Rezension hilfreich
This book will improve the quality of your products ! 17. Mai 2004
Von Joe Fisher - Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe
As a Software Developer and Consultant, I found this book to be a clear and practical guide that will be a valuable asset to all system development professionals.

I strongly recommend it to all systems professionals, and believe it is a MUST HAVE for systems analysts !

The book presents a step-by-step methodology that contrasts how things are "normally" done with how they should be done to achieve optimum results and satisfied customers.

In addition to analyzing why and how traditional approaches fail, the text provides a comprehensive checklist that can be followed to avoid common mistakes and improve the quality of the most significant aspect of develop: gathering and documenting requirements !

Presented in a easy-to-read format sprinkled with wry humor, you are likely to find it a more enjoyable read than most technical texts.

4 von 4 Kunden fanden die folgende Rezension hilfreich
Differentiates Identification of Business Problems from the Solution Alternatives 19. Dezember 2007
Von Paul L. - Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe
The 64 ways to test requirements are good and helpful, and you'll need to determine how many of these techniques (and with what rigor) could/should be applied to your project in your organizational context. The greatest benefit for me from reading this book was understanding the distinction Goldsmith makes between business problems and the solution design alternatives that might address them. I've witnessed problems on projects where this distinction was not understood, and I'm convinced that identifying the business problem(s) and business requirements first is critical before undertaking software requirements and solution alternatives.

Beliebte Markierungen

 (Was ist das?)
&quote;
difference between business and system requirements is not a matter of detail. &quote;
Markiert von 3 Kindle-Nutzern

Kunden diskutieren

Das Forum zu diesem Produkt
Diskussion Antworten Jüngster Beitrag
Noch keine Diskussionen

Fragen stellen, Meinungen austauschen, Einblicke gewinnen
Neue Diskussion starten
Thema:
Erster Beitrag:
Eingabe des Log-ins
 


Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
Alle Amazon-Diskussionen durchsuchen
   
Ähnliche Foren


Ähnliche Artikel finden


Anhand des Sachgebietes nach ähnlichen Produkten suchen: