Lean Architecture: for Agile Software Development und über 1,5 Millionen weitere Bücher verfügbar für Amazon Kindle. Erfahren Sie mehr


oder
Loggen Sie sich ein, um 1-Click® einzuschalten.
oder
Mit kostenloser Probeteilnahme bei Amazon Prime. Melden Sie sich während des Bestellvorgangs an.
Jetzt eintauschen
und EUR 11,25 Gutschein erhalten
Eintausch
Alle Angebote
Möchten Sie verkaufen? Hier verkaufen
Der Artikel ist in folgender Variante leider nicht verfügbar
Keine Abbildung vorhanden für
Farbe:
Keine Abbildung vorhanden

 
Beginnen Sie mit dem Lesen von Lean Architecture: for Agile Software Development auf Ihrem Kindle in weniger als einer Minute.

Sie haben keinen Kindle? Hier kaufen oder eine gratis Kindle Lese-App herunterladen.

Lean Architecture: for Agile Software Development [Englisch] [Taschenbuch]

James O. Coplien , Gertrud Bjørnvig
3.5 von 5 Sternen  Alle Rezensionen anzeigen (2 Kundenrezensionen)
Preis: EUR 35,30 kostenlose Lieferung. Siehe Details.
  Alle Preisangaben inkl. MwSt.
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Nur noch 8 auf Lager (mehr ist unterwegs).
Verkauf und Versand durch Amazon. Geschenkverpackung verfügbar.
Lieferung bis Samstag, 23. August: Wählen Sie an der Kasse Morning-Express. Siehe Details.

Weitere Ausgaben

Amazon-Preis Neu ab Gebraucht ab
Kindle Edition EUR 25,96  
Taschenbuch EUR 35,30  

Kurzbeschreibung

18. Juni 2010
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

Hinweise und Aktionen

  • Studienbücher: Ob neu oder gebraucht, alle wichtigen Bücher für Ihr Studium finden Sie im großen Studium Special. Natürlich portofrei.


Wird oft zusammen gekauft

Lean Architecture: for Agile Software Development + Vorgehensmuster für Softwarearchitektur: Kombinierbare Praktiken in Zeiten von Agile und Lean
Preis für beide: EUR 70,29

Die ausgewählten Artikel zusammen kaufen

Kunden, die diesen Artikel gekauft haben, kauften auch


Produktinformation

  • Taschenbuch: 376 Seiten
  • Verlag: John Wiley & Sons; Auflage: 1. Auflage (18. Juni 2010)
  • Sprache: Englisch
  • ISBN-10: 0470684208
  • ISBN-13: 978-0470684207
  • Größe und/oder Gewicht: 23 x 19 x 2 cm
  • Durchschnittliche Kundenbewertung: 3.5 von 5 Sternen  Alle Rezensionen anzeigen (2 Kundenrezensionen)
  • Amazon Bestseller-Rang: Nr. 72.443 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
  • Komplettes Inhaltsverzeichnis ansehen

Mehr über den Autor

Entdecken Sie Bücher, lesen Sie über Autoren und mehr

Produktbeschreibungen

Pressestimmen

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

Buchrückseite

It's time for change - after 30 years, DCI has risen to complete the vision of object-oriented programming!
 
Aiming at no less than a paradigm shift, Lean Architecture uses a modern approach to software design, while embracing refreshing new insights of Lean and Agile. Giving a down-to-earth view of Agile requirements and the often-ignored relationship between requirements and architecture, this book goes beyond the fashionable idea of User Stories, and shows you how to employ Use Cases in a lightweight, incremental, Agile way. The authors detail the DCI (Data, Context and Interaction) architecture paradigm and show how DCI succeeds where object-oriented programming languages alone have failed to integrate software design with the end user's understanding of the overall business structure.
 
However, this is not a methodology book, but a book which focuses on code, with plenty of code examples. Topics covered include: Agile production, Stakeholder Engagement, Organizational issues, Scala/Python/Java implementation of the DCI account example, Qi4J and much more.
 
Renowned software architecture expert James Coplien and agile requirements expert Gertrud Bjørnvig share their expertise to give you concrete design advice that will help you:
* Create software that builds on your end-user mental models rather than design methodologies
* Write software that can directly be verified against behavioral requirements
* Organize - so that all your stakeholders support each other
* Support rapidly changing feature code in stable domain code to help embrace change
 

Lean Architecture casts a new light over important aspects of software development that have been marginalized or forgotten by the agile movement - it will help you find your own path.

Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?


In diesem Buch (Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Hier reinlesen und suchen:

Kundenrezensionen

4 Sterne
0
3 Sterne
0
1 Sterne
0
3.5 von 5 Sternen
3.5 von 5 Sternen
Die hilfreichsten Kundenrezensionen
1 von 1 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Use cases in code 3. November 2010
Von Marc Grue
Format:Taschenbuch
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.
War diese Rezension für Sie hilfreich?
2.0 von 5 Sternen A book about Lean that is full of Waste 19. August 2014
Format:Taschenbuch|Verifizierter Kauf
There are some bites of personal wisdom in this book. If you personally know the Author in some real world context, you can decide for yourself if you value His wisdom. Otherwise, based on His book alone, anyone else's wisdom might do just as well.

This expert on Lean has sprinkled His book with "deep and meaningful" quotes, placed prominently at the beginnings of important sections, that neither convey much meaning nor support his chain of reasoning. I call that Waste, not Lean. In fact, when asked about the actual meaning of His cherished quotes, the author explodes and shouts that His book is not even making any argument! Hence, questioning its contents value is "not conducive to learning". Well. Today's authoritarians like to hide behind new-age social responsibility waffle, and this Author is no exception.

Avoid this book. Sounds interesting when you read it casually, but deeper questioning will leave you vacuous. According to the Author Himself, He is not trying to make any particular argument for anything, so this book belongs to the realm of fiction or, rather, Waste. The various "thoughts" presented may be helpful... or maybe not.

But hey, everything definitely sounds good and leaves you with that warm, fuzzy feeling that lifts you above the concerns of mere reason, just like my last Zen retreat!
War diese Rezension für Sie hilfreich?
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com: 4.3 von 5 Sternen  15 Rezensionen
16 von 20 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen A must read for all system developers 17. August 2010
Von Trygve Reenskaug - Veröffentlicht auf Amazon.com
Format:Taschenbuch
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 von 14 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Must Read for Architects in a Lean Organization. 7. September 2010
Von Steve Berczuk - Veröffentlicht auf Amazon.com
Format:Taschenbuch
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).
8 von 10 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Uses cases in code 3. November 2010
Von Marc Grue - Veröffentlicht auf Amazon.com
Format:Taschenbuch
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.
3 von 3 Kunden fanden die folgende Rezension hilfreich
4.0 von 5 Sternen Different 20. Oktober 2011
Von Stefan - Veröffentlicht auf Amazon.com
Format:Taschenbuch
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.
2 von 2 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Plenty of "Aha!" moments 21. Juli 2011
Von Dave Isaacs - Veröffentlicht auf Amazon.com
Format:Taschenbuch
The authors provide plenty of "Aha!" moments, without trying to oversimplify the challenges of system design.

Just a few notable concepts from this book, which is full of many more great insights from these experienced system designers:
- How Lean and Agile approaches work together, so you can do up front work while avoiding a Big Up Front Design
- What the system "is" and what the system "does"
- Complex systems have multiple tops
- The important role of the team structure and team activities (beyond just the "coders") in realizing a viable solution
Waren diese Rezensionen hilfreich?   Wir wollen von Ihnen hören.
Kundenrezensionen suchen
Nur in den Rezensionen zu diesem Produkt suchen

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
 

Kundendiskussionen durchsuchen
Alle Amazon-Diskussionen durchsuchen
   


Ähnliche Artikel finden


Ihr Kommentar