Software Requirements (3rd Edition) et plus d'un million d'autres livres sont disponibles pour le Kindle d'Amazon. En savoir plus
  • Tous les prix incluent la TVA.
Il ne reste plus que 10 exemplaire(s) en stock (d'autres exemplaires sont en cours d'acheminement).
Expédié et vendu par Amazon.
Emballage cadeau disponible.
Quantité :1
Software Requirements a été ajouté à votre Panier
+ EUR 2,99 (livraison)
D'occasion: Très bon | Détails
Vendu par momox fr
État: D'occasion: Très bon
Commentaire: En Stock.
Amazon rachète votre
article EUR 12,74 en chèque-cadeau.
Vous l'avez déjà ?
Repliez vers l'arrière Repliez vers l'avant
Ecoutez Lecture en cours... Interrompu   Vous écoutez un extrait de l'édition audio Audible
En savoir plus
Voir les 2 images

Software Requirements (Anglais) Broché – 15 août 2013


Voir les 2 formats et éditions Masquer les autres formats et éditions
Prix Amazon Neuf à partir de Occasion à partir de
Format Kindle
"Veuillez réessayer"
Broché
"Veuillez réessayer"
EUR 32,54
EUR 28,94 EUR 27,98
EUR 32,54 Livraison à EUR 0,01. Il ne reste plus que 10 exemplaire(s) en stock (d'autres exemplaires sont en cours d'acheminement). Expédié et vendu par Amazon. Emballage cadeau disponible.

Produits fréquemment achetés ensemble

Software Requirements + Writing Effective Use Cases
Prix pour les deux : EUR 89,25

Acheter les articles sélectionnés ensemble

Descriptions du produit

Biographie de l'auteur

Joy Beatty, a leader in the software requirements community, has trained thousands of business analysts and helped major organizations build business-analysis centers of excellence. She is coauthor of Visual Models for Software Requirements.



Vendez cet article - Prix de rachat jusqu'à EUR 12,74
Vendez Software Requirements contre un chèque-cadeau d'une valeur pouvant aller jusqu'à EUR 12,74, que vous pourrez ensuite utiliser sur tout le site Amazon.fr. Les valeurs de rachat peuvent varier (voir les critères d'éligibilité des produits). En savoir plus sur notre programme de reprise Amazon Rachète.

Détails sur le produit

  • Broché: 672 pages
  • Editeur : Microsoft Press; Édition : 3 (15 août 2013)
  • Langue : Anglais
  • ISBN-10: 0735679665
  • ISBN-13: 978-0735679665
  • Dimensions du produit: 18,5 x 3,8 x 22,6 cm
  • Moyenne des commentaires client : 5.0 étoiles sur 5  Voir tous les commentaires (1 commentaire client)
  • Classement des meilleures ventes d'Amazon: 44.645 en Livres anglais et étrangers (Voir les 100 premiers en Livres anglais et étrangers)
  • Table des matières complète
  •  Souhaitez-vous compléter ou améliorer les informations sur ce produit ? Ou faire modifier les images?


En savoir plus sur les auteurs

Découvrez des livres, informez-vous sur les écrivains, lisez des blogs d'auteurs et bien plus encore.

Commentaires en ligne

5.0 étoiles sur 5
5 étoiles
1
4 étoiles
0
3 étoiles
0
2 étoiles
0
1 étoiles
0
Voir le commentaire client
Partagez votre opinion avec les autres clients

Commentaires client les plus utiles

Par E. DENIS le 26 décembre 2014
Format: Format Kindle Achat vérifié
Je suis tombé par hasard sur une référence à ce livre dans un forum spécialisé de Business Analysts. Bonne pioche, il est très lisible, bien plus digeste qu'un BABOK.
Remarque sur ce commentaire Avez-vous trouvé ce commentaire utile ? Oui Non Commentaire en cours d'envoi...
Merci pour votre commentaire. Si ce commentaire est inapproprié, dites-le nous.
Désolé, nous n'avons pas réussi à enregistrer votre vote. Veuillez réessayer

Commentaires client les plus utiles sur Amazon.com (beta)

Amazon.com: 46 commentaires
11 internautes sur 11 ont trouvé ce commentaire utile 
An invaluable reference guide for all roles involved in software development 23 septembre 2013
Par TinaHeidenreich - Publié sur Amazon.com
Format: Broché
I became a business analyst in 2004 and a co-worker suggested that I read Karl Wieger's books, Software Requirements, 2nd Edition and More About Software Requirements Thorny Issues and Practical Advice. That was the BEST professional advice I've ever received. The books have been integral in helping me to understand the many different skill sets, techniques, and best practices required to do a great job as an analyst.

So when I heard that Karl and Joy were co-writing the 3rd Edition of Software Requirements I was elated! The information provided in the new book is current, easy to understand, and so very relevant. Real-life examples and humor have been weaved throughout the book which makes it a very interesting read.

I recommend this book as an essential reference guide for anyone involved in software development, not just analysts. All roles should know about business analysis as it relates to system design and software development. This will be a book that you will refer to time after time.
4 internautes sur 4 ont trouvé ce commentaire utile 
A great reference guide with valuable nudges and insights to advance your craft! 7 janvier 2014
Par Yaaqub Mohamed (Yamo) - Publié sur Amazon.com
Format: Format Kindle
I have been an avid reader and fan of Karl’s software development related books ever since my university days and now as a lead practitioner and trainer, I continue to find more value in his work. I had the honor of interviewing both Karl and Joy to learn about some behind-the-scenes information on how this new edition was updated. I was pleased to learn about their due diligence to ensure they’ve left no stone unturned to bring forward the latest and greatest in software requirements engineering.

The organization of the book, the emphasis on the role of a business analyst, and an in-depth requirements discovery and development roadmap are some of the key strengths of this edition. The first part sets the context and introduces a few best practices for requirements engineering. This is essential, and in my view applicable to all roles involved in software development.

Part II of the book covers the requirements development process, best practices in-depth for both waterfall and agile projects. As you read through this section, you will realize that the best practices are truly methodology agnostic, and imperative regardless of the business analysis approach.

One of the big challenges of a requirements practitioner is how to tailor the requirements discovery and development process for different projects, and Part III of the book precisely addresses this facet. This was something that always wished that a book would contain as I continue to work on different kinds of projects as a lead business analysis practitioner.

I was also pleased to see an entire section of the book devoted to requirements management aspect (Part IV). There is succinct and usable information that covers processes, best practices and tools that are invaluable for effective requirements management.

The last part looks at the requirements process improvement that can be useful for Requirements CoEs (Center of Excellence) or practice groups within organizations.

With comprehensive coverage of the requirements development processes, best practices and tools, this is a must-have book in your reference library; to both upgrade your knowledge and also advance your craft as a business analysis or requirements engineering practitioner.
4 internautes sur 4 ont trouvé ce commentaire utile 
The Gold Standard got even better! 18 décembre 2013
Par Joyce Statz - Publié sur Amazon.com
Format: Broché
Over the years, when a novice business analyst (or someone with experience handling requirements) has asked me for a good reference, I’ve sent them to Karl Wiegers’ books. This third edition of Software Requirements is the gold standard I’ll now be recommending. Karl and Joy have done an excellent job of enriching the already-great material from the prior version, giving readers an understanding of why solid requirements are needed and illustrating practical techniques for developing and managing requirements. In addition to commonplace stories illustrating the concepts, they provide clear and useful examples of all the techniques. Practical, complete examples are essential to understanding methods an analyst hasn’t used before; like many of the subject matter experts we encounter, we “know it when we see it!”

The book is written in a flow that helps an analyst see what needs to be done from the point when an idea is first considered, to when it becomes the subject of a project, all the way through the project completion. Not all techniques work well with all types of projects, though, so the book includes sections describing adaptations of the material discussed and the specific needs of particular types of projects. They cover agile, enhancement and replacement, packaged solution, outsourced, business process automation, business analytics, and embedded and real-time projects.

While it’s a healthy-sized tome at more than 600 pages, the book is well organized and specific topics are easy to access individually. Most business analysts would benefit from reading it cover to cover, though, at least once!
6 internautes sur 7 ont trouvé ce commentaire utile 
Required reading for project managers, but don't forget the coffee 3 avril 2014
Par Ivy - Publié sur Amazon.com
Format: Broché Commentaire client Vine pour produit gratuit ( De quoi s'agit-il? )
There are a great many friendlier, funnier, more engaging software requirements books on the market. There are very few books as comprehensive and concise as this one. Yes, concise. I know it's huge. It just covers that much information.

It provides an analysis of stakeholders and functional vs nonfunctional requirements that was surprisingly informative. We throw those terms around all the time, but rarely consider a formal definition. This book looks at a variety of options, and the one you choose will guide your thinking throughout requirements analysis and harvsting.

It covers everything you need to establish your requirements for the waterfall method, though it features substantial information on agile. If you are new to agile, and need ideas on how to gather the backlog, or if you've been using a while but don't feel the backlog is as complete as it should be, grab this book and a notepad. It covers a host of sources that are easy to overlook

It is very, very dry reading, which is the only reason it is four stars and not five. I found it hard to stay focused once in a while, and needed a caffeine boost to keep going. There is an attempt in the beginning to be humorous, but that is quickly lost. It is a little poorly organized. The topic sentence does not always guide the reader to the topic under discussion. You'll need to reset your focus a few times during the book, but it's worth it. The first two editions are often considered required reading for project managers, and the third lives up to that august reputation.
1 internautes sur 1 ont trouvé ce commentaire utile 
Readable and encyclopedic 25 octobre 2013
Par Abe Taha - Publié sur Amazon.com
Format: Broché
One of the areas often overlooked when writing software systems is thoroughly understanding what needs to be developed. Specifically who are the users that are going to interact with the system, what are they trying to accomplish with the software, and how is the system expected to behave under normal and error conditions. In short, developing software requirements and specifications before the software is written.

"Software Requirements 3" addresses these questions, with clear answers and advice in a rather longish format of roughly 673 pages.

The book starts with a story about the importance of software requirements: a case of an employee who changed her last name without getting married, and the accounting software's inability to handle the change, with the repercussions that the employee will not get paid until the the "bug" is fixed. The book mentions that this is not an atypical situation, and that
... errors introduced during requirements activities account for 40 to 50 percent of all defects found in a software product
The book proceeds to explain how to prevent problems like these from happening in the future, through explaining the mechanics of requirements gathering starting with defining who the customer is, and who the decision makers are, followed by a tour of the requirement gathering process, including requirements elicitations, and appropriate documentation. The book advocates readable, concise, and precise requirements documentation, and ample use of imagery to explain difficult concepts.

The book offers advice on how to reduce development risk, through frequent customer checkpoints as things are developed, to minimize the mismatch between customer expectations, and what developers build. The book also advocates building prototypes to illustrate concepts, and drive conversations to minimize the gap between what's being build, and what customers expect.

The book addresses the often ignored fact that requirements frequently change during the development process, and offers a full chapter on handling these changes, and tools for managing the changes.

The book is geared toward the business analyst, but software engineers would benefit greatly from reading it. And despite the book's length, the authors' writing style is approachable, and it was a pleasure to read.
Ces commentaires ont-ils été utiles ? Dites-le-nous


Commentaires

Souhaitez-vous compléter ou améliorer les informations sur ce produit ? Ou faire modifier les images?