Visual Models for Software Requirements et plus d'un million d'autres livres sont disponibles pour le Kindle d'Amazon. En savoir plus
EUR 22,10
  • Tous les prix incluent la TVA.
Il ne reste plus que 4 exemplaire(s) en stock (d'autres exemplaires sont en cours d'acheminement).
Expédié et vendu par Amazon.
Emballage cadeau disponible.
Quantité :1
Ajouter au panier
Amazon rachète votre
article EUR 6,12 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

Visual Models for Software Requirements (Anglais) Broché – 15 juillet 2012


Voir les 3 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 22,10
EUR 19,91 EUR 25,51

Offres spéciales et liens associés



Vendez cet article - Prix de rachat jusqu'à EUR 6,12
Vendez Visual Models for Software Requirements contre un chèque-cadeau d'une valeur pouvant aller jusqu'à EUR 6,12, 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


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 

Il n'y a pas encore de commentaires clients sur Amazon.fr
5 étoiles
4 étoiles
3 étoiles
2 étoiles
1 étoiles

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

Amazon.com: 12 commentaires
4 internautes sur 4 ont trouvé ce commentaire utile 
good practice but non standrad models 11 avril 2013
Par Jarek Zelinski - Publié sur Amazon.com
Format: Broché Achat vérifié
This book include good ideas, a lot of best practices but i don't understood why author totally ignored OMG standard modeling notations like a UML or BPMN ...remember that MSDN pages included a lot of articles with UML and BPMN models...
3 internautes sur 3 ont trouvé ce commentaire utile 
Helpful Guidance 19 octobre 2012
Par Ralph R. Young - Publié sur Amazon.com
Format: Broché
This useful book provides experienced-based guidance concerning how to use visual models to rigorously identify, capture, and validate software requirements. The authors provide a comprehensive language of visual models that has been used successfully on many real-world, large-scale projects. The book has many features - for example, exercises (and answers) to help you practice the application of the suggested techniques; guidance for the techniques concerning "When to Use", "When Not to Use", and "Common Mistakes"; a useful glossary; a detailed index; and appendices. The book is very readable and understandable. In my judgment, it will produce positive results for any reader who takes the time and effort to apply the advice.
3 internautes sur 3 ont trouvé ce commentaire utile 
Much Needed Adoption-Focused Resource 16 octobre 2012
Par Anne L Hartley - Publié sur Amazon.com
Format: Broché
The refreshing aspect of this book is that it embraces meaningful adoption -- not only by the practitioners creating the models but also for those who needs to consume and respond. In reality requirements practices remain surprisingly immature across most organizations, despite years of focus by the experts, standards organization, and industry leaders on better ways to define and communicate requirements that will address fundamental points of failure with projects. Eventhough we know better as a profession, the gap is still in sustained adoption of better ways of working. Sustained adoption of practices that deliver better requirements is ultimately dependent on leadership commitment, the capability of the requirements practitioner, the appropriateness of technique, and whether or not the consumers are prepared to consume.

Setting the usage context for each technique in "layman's terms" as reflected in this book is a great way to break down communication barriers to facilitate understanding, usage, and sustained adoption. Joy and Tony have given us an excellent tool that practitioners and consumers at all levels will find useful in helping their organization embrace and benefit from visual modeling. I am recommending this much needed resource to my clients and colleagues who are committed to Requirements practice improvements and the ultimate benefit to project outcomes!

Anne Hartley
Business/IT Transformation Consultant
AH Consulting LLC

BA Capability Champion and Practice Leader
27 internautes sur 38 ont trouvé ce commentaire utile 
Lacks Integrated Tooling Vision 4 septembre 2012
Par Kelvin D. Meeks - Publié sur Amazon.com
Format: Broché
Summary:

I'll start-off by saying that if you have no process or discipline in your organization's approach to documenting and capturing software requirements - there are a lot of good suggestions covered in this book. Also, if your approach to documenting software requirements lacks an appreciation for the business concerns - the Business Objectives modeling discussions in the book may be helpful and/or useful for your software engineering team. However, if your software requirements management processes are even moderately mature - and if already using Microsoft-centric tools to capture and manage software requirements - you will not find much that is new, novel, or of benefit in this book.

Positives:

An attempt to provide a comprehensive approach with an emphasis on business concerns
Coverage of the importance of Business Process modeling
Highlights the limitations of UML to capture business level concerns'
Focus on Business Objectives modeling
Discussion/coverage of Key Performance Indicator Models (KPIM)
'Feature Trees' [although, for any moderately complex effort, the choice of a visual modeling tool for drawing a Feature Tree - that lacks zoom/collapse capability of nodes - is problematic]
Inclusion of helpful links to references and additional resources at the end of each chapter.

Negatives:

Lack of integrating the Business Objectives modeling concepts with other mature software engineering models (e.g. Zachman Framework, Open Group TOGAF)
Microsoft-centric / bias in promoting tooling
Lack of any significant discussion of other possible software requirement tooling for visual modeling (i.e. non-Microsoft-centric tooling)
Lack of appreciation / coverage of how to minimize the manual maintenance of traceability across artifacts
Promoting a software requirements approach that relies on Sharepoint as a primary mechanism for publication/distribution is an abysmal experience as the size and duration of a project grows.
Link-rot: Over time, Sharepoint sites are renamed, restructured, reorganized. This results in an untenable maintenance effort for most organizations. Links embedded in MS Word, PowerPoint, Excel, and Visio documents are routinely broken - and identifying where to change all of the link references is also challenging..
Painful and labor intensive efforts to automate any generation of cross-references or matrices [when visual models and requirements are stored as MS Office documents across multiple SharePoint sites].

In choosing this book to review - I was hoping to find some new insights to capturing requirements - via visual models that might eliminate some of the 'pain' that most often is found to exists in the requirements management processes (and tooling) adopted by most large organizations. Since this book is written with a bias toward Microsoft(tm) technologies (e.g. SharePoint) - teams that attempt to adopt the suggested approach will eventually run into the same types of long-term problems and 'pain' that I have observed firsthand on many projects - across several different organizations.

At the end of the day - after having lived with the pain of an absence of integrated tooling for the capture and management of software requirements on too many projects - I must conclude that the authors lack of a integrated vision of tooling for visual software requirements management leads me to suggest avoiding this book for the majority of potential readers.

2012-12-09 Update:
As a poignant example of why the authors' suggestion is so laughable (that Sharepoint could be a viable tool for an enterprise to store requirement artifacts)...I offer yet-another-example of the joke that is Sharepoint. Tonight, I discovered the 260-character limitation for an URL in Sharepoint
2 internautes sur 2 ont trouvé ce commentaire utile 
Much needed for the industry! 25 octobre 2012
Par Angela Wick Garay - Publié sur Amazon.com
Format: Broché
This is a needed book for the industry!
There is something new to learn for everyone

If you are new to being a BA or new to structured modeling start with chapter 1, read through and do the exercises in chapters 2-24. If you are experienced with modeling, read chapter 1, then chapter 25, then the chapters in between as they drive your interest. Chapters 2- 24 are great to refresh and and learn even more about the models you may already use and some new ones to try out.

Chapter 1 is a great level setting of how business analysis for software development has changes over the years and why visuals are so important!

Chapters 2-24 are great for learning all about various models and how they make software projects successful. These chapters have great templates (also downloadable), examples and exercises to practice! My favorite is the Common Mistakes section for each model helping BAs self correct and identify when they are going down the wrong path.

Chapter 25 - Puts together which models to use when and on what types of projects, so helpful to planning for our projects!
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?