Lean Architecture: for Agile Software Development et plus d'un million d'autres livres sont disponibles pour le Kindle d'Amazon. En savoir plus
EUR 29,60
  • 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
Lean Architecture: for Ag... a été ajouté à votre Panier
Amazon rachète votre
article EUR 12,35 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

Lean Architecture: for Agile Software Development (Anglais) Broché – 18 juin 2010


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 29,60
EUR 25,01 EUR 35,92
EUR 29,60 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.

Descriptions du produit

Revue de presse

′...a book of advice that is broad, enabling, and concrete.’ (Lean Magazine, January 2010).

Présentation de l'éditeur

More and more Agile projects are seeking architectural roots as they struggle with complexity and scale – and they′re seeking lightweight ways to do it Still seeking? In this book the authors help you to find your own path Taking cues from Lean development, they can help steer your project toward practices with longstanding track records Up–front architecture? Sure. You can deliver an architecture as code that compiles and that concretely guides development without bogging it down in a mass of documents and guesses about the implementation Documentation? Even a whiteboard diagram, or a CRC card, is documentation: the goal isn′t to avoid documentation, but to document just the right things in just the right amount Process? This all works within the frameworks of Scrum, XP, and other Agile approaches


Vendez cet article - Prix de rachat jusqu'à EUR 12,35
Vendez Lean Architecture: for Agile Software Development contre un chèque-cadeau d'une valeur pouvant aller jusqu'à EUR 12,35, 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é: 376 pages
  • Editeur : John Wiley & Sons (18 juin 2010)
  • Langue : Anglais
  • ISBN-10: 0470684208
  • ISBN-13: 978-0470684207
  • Dimensions du produit: 18,8 x 1,8 x 23,4 cm
  • Moyenne des commentaires client : 5.0 étoiles sur 5  Voir tous les commentaires (1 commentaire client)
  • Classement des meilleures ventes d'Amazon: 163.767 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 l'auteur

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

Dans ce livre (En savoir plus)
Parcourir les pages échantillon
Couverture | Copyright | Table des matières | Extrait | Index
Rechercher dans ce livre:

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 SALL le 26 août 2010
Format: Broché
A must have for anybody serious about software architecture.
This quote from the book will give you a hint as to what to expect : "Architecture is not meant to be cast in stone, but to be an overall guiding light that makes it difficult to create errors of form."

Enjoy!
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: 18 commentaires
17 internautes sur 21 ont trouvé ce commentaire utile 
A must read for all system developers 17 août 2010
Par Trygve Reenskaug - Publié sur Amazon.com
Format: Broché
This is a different book. Where most books expound a single theme such as Agile, Lean, or Scrum, "Lean Architecture for Agile Software Development" paints on a much broader canvas: Working with the end user, end user's mental model, user requirements, system architecture, and right down to actual code.

This is neither a beginner's "how to do it in ten easy lessons" nor is it a design method. It is a book written for the mature professional by two authors whose long experience has given them a deep understanding of what really matters in practical programming.

At a first glance, many methodologies appear as mere fads, but Coplien and Bjørnvig see through the fads and build on their real worth to create a thought-provoking and eminently practical book.

Three random jottings from my first reading:

* Architecture: "No matter how we care to define it, software architecture should support the enterprise value stream even to the extent that the source code itself should reflect the end user's mental model of the world."

* Lean secret: "...unite specialists together in one room: everybody, all together, from early on."

* Form and functionality: "System architecture should reflect the end user's mental model of the world. The model has two parts: The first part relates to the user's thought process when viewing the screen, and to what the system is: its form. The second part relates to what end users do - interacting with the system - and how the system should respond to user input. This is the system functionality. We work with users to elicit and develop these models and to capture them in code as early as possible."

The authors claim that an end user should have a picture in his head that enables him to see the commands that are meaningful in a given situation and to understand what they will do for him. This picture, Jim calls it the end user's mental model, it will be reflected into the actual code in well-built systems.

A few years ago, this reviewer introduced a new programming paradigm that he called Data, Context, and Interaction (DCI). The main feature of this paradigm is that it splits the code into two distinct parts. One part specifies system state; the other part specifies system behavior. Coplien and Bjørnvig use this paradigm to fill in the gap between architecture and code execution. To quote from the book:

* Key building blocks of object-oriented design: "Objects, which are end users' conceptualization of things in their business world; Classes, which provide simple, encapsulated access to the data that represents business information; Roles, which interact in a use case to achieve some business goal."

This book is a MUST read for all who want to understand the true nature of systems development.
11 internautes sur 14 ont trouvé ce commentaire utile 
Must Read for Architects in a Lean Organization. 7 septembre 2010
Par Steve Berczuk - Publié sur Amazon.com
Format: Broché
When I was a C++ programmer in the early 90's Coplien's Advanced C++ Programming Styles and Idioms was a source of interview material when looking for programmers. It's a good bet that this book may fill the same role for those looking to see if candidates for architect roles understand what it means to be an architect in a Lean or Agile Organization. This book dispels the myth that Agile and Architecture don't go together and explains the balance between Agile architecture and too much Big Up Front Design. This book emphasizes the importance of frequent collaboration between stakeholders in defining a good architecture and helps you to understand the importance of architecture to the success of agile projects. With code examples throughout, this book emphasizes that architecture and coding must go together. After describing some general principles of how architecture can add value to an agile project, the authors explain the Data Context, Interaction (DCI) architecture, which provides an framework for building lean architectures. My one minor complaint is that the transition between the general discussions of lean architecture and the focused discussion of DCI was a bit abrupt. But this was a minor distraction from an enjoyable and informative read. Rich with citations, places to go for more information, and historical context, this book will be useful for anyone who is struggling with how to build systems that need to support complicated user interactions (which could describe most non-trivial systems).
3 internautes sur 3 ont trouvé ce commentaire utile 
Different 20 octobre 2011
Par Stefan - Publié sur Amazon.com
Format: Broché
This book is an important contribution in its field. It is interesting, relevant and quite different. Not your typical software architecture book talking about connectors and components and the many classification of the possible combinations between the two. I warmly recommend the material as a fresh, original perspective on software architecture, use cases, requirements, coding. Not convincing enough for a four stars review? this is because I dislike the imperative cliché : "a must read" and also because I realized there is no "silver bullet" architecture book. I like the fact that Agile shows in a "normal" light, not that different from any common sense architecture where waste is not welcome, especially in documentation. Software has the unique feature of documenting itself, why try to duplicate that? In fact "Dispelling agile myths" is the title of a chapter.
It is refreshing to be reminded that OO is not only about subclassing and polymorphism, but one of its initial intent was having same mental (OO) model with your business partners.

I can see how it might not satisfy the most pragmatic programmers (and yes I am aware of the apparent contradiction: "lean and agile are for pragmatic developers!") Ample references are made to a topic carried on from an earlier book: Organizational Patterns, which is basically software architecture reflected in people interactions. Many techniques, habits, narratives, analogies or rules of thumb contribute to the originality of the material and the definition of the elusive features of software architecture.
8 internautes sur 10 ont trouvé ce commentaire utile 
Uses cases in code 3 novembre 2010
Par Marc Grue - Publié sur Amazon.com
Format: Broché
This first book covering the new DCI paradigm of programming is a must read for anyone interested in separating the more often changing behavioral parts of code related to use cases from the more slowly evolving structural parts of domain data.

A great practical description of how the use case evolves and translates directly into code, of how to reflect the end users mental model in code - making it much more readable for both programmers and domain experts. It goes into detail about how use case roles translates to Object Roles playing out their part of a use case algorithm and how they get injected into the domain objects to use their state. And we are presented with how the Context can set up the mapping of Roles to domain Objects in different flexible ways before firing off the trigger Interaction of the use case.

Apart from example code in C++ and Ruby through out the last chapters of the book, it also have a great appendix with coded DCI examples in Scala, Python, C#, Ruby and Squeak.

For anyone interested I can also recommend visiting the Google "object-composition" group where all the concepts are discussed and explored.
5 internautes sur 6 ont trouvé ce commentaire utile 
Wisdom from experience 25 janvier 2011
Par T. Anderson - Publié sur Amazon.com
Format: Broché Achat vérifié
I have the greatest respect for this author for the contributions he has made to the software development industry. This is a very good book to read to get his view of software development.

This book is a great read if you are an experienced developer. I do not recommend it to people new to the software development industry.

Do not pick this book up and think you are going to learn how to do software architecture. Personally I would have named the book "Thoughts on Lean". I found the book very interesting and found it to contain a lot of great advice, but it does not paint the complete picture of how to accomplish solid software architecture.

I like the DCI coverage, but would only use it if it can be documented better than what is shown in the book. Code is not enough documentation for me.

Personally I will apply the techniques in this book to modular level design and development. Over the years I have found that to be the place agile and lean development practices belong, not at the architecture level. Their programming techniques help to achieve a very modifiable architecture, which to me is the most import quality attribute you should strive for on any project of decent size.

Although my review comes off as a bit negative, the negativity is not a reflection of the quality of this book's wisdom. It is my personal bias against what the agile movement has done to the environments I am constantly finding myself cleaning up. Agile is perceived all to often as the easy road, when in fact it is a road only for the highly experienced and a select few.

All in all I recommend reading this book if you want to broaden your horizon. The personal insight the author provides into building software is worth the time.
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?