Möchten Sie verkaufen? Hier verkaufen
The Art of Systems Architecting, Second Edition
 
Größeres Bild
 

The Art of Systems Architecting, Second Edition [Gebundene Ausgabe]

Eberhardt Rechtin , Mark Maier
3.8 von 5 Sternen  Alle Rezensionen anzeigen (4 Kundenrezensionen)

Erhältlich bei diesen Anbietern.


Weitere Ausgaben

Amazon-Preis Neu ab Gebraucht ab
Kindle Edition EUR 56,25  
Gebundene Ausgabe EUR 60,99  
Gebundene Ausgabe, 28. Juni 2000 --  
Dieses Buch gibt es in einer neuen Auflage:
The Art of Systems Architecting (Systems Engineering) The Art of Systems Architecting (Systems Engineering) 3.8 von 5 Sternen (4)
EUR 87,99
Auf Lager.

Kunden, die diesen Artikel gekauft haben, kauften auch


Produktinformation


Mehr über die Autoren

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

Produktbeschreibungen

Pressestimmen

"The only way to develop this skill is to serve an apprenticeship with a proven practitioner. However, there are simply not enough gurus to go around, and I would recommend this book both for students of the discipline and as serious reading for experienced designers who wish to recognize and maintain their expertise." -E. James in Computing Millieux

Kurzbeschreibung

Today's architecting must handle systems of types unknown until very recently. New domains, including personal computers, intersatellite networks, health services, and joint service command and control are calling for new architectures-and for architects specializing in those domains. Since the original publication, of this bestselling text, these new and emerging fields have contributed architectural concepts and tools of their own to the relatively new formalism-and evolving profession-called Systems Architecting.The Art of Systems Architecting, Second Edition restates and extends into the future the classical architecting paradigm, incorporating the most broadly applicable of these contributions. It remains the most innovative, insightful treatment available to the discipline, providing both the academic and the industrial communities with the up-to-date tools, concepts, and techniques needed to conceive and build complex systems.

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


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

4 Rezensionen
5 Sterne:
 (2)
4 Sterne:
 (1)
3 Sterne:    (0)
2 Sterne:    (0)
1 Sterne:
 (1)
 
 
 
 
 
Durchschnittliche Kundenbewertung
3.8 von 5 Sternen (4 Kundenrezensionen)
 
 
 
 
Sagen Sie Ihre Meinung zu diesem Artikel:
Die hilfreichsten Kundenrezensionen

4 von 4 Kunden fanden die folgende Rezension hilfreich:
5.0 von 5 Sternen Wisdom Within, 3. Juli 1999
Von Ein Kunde
I am a professional software and systems architect. Also, I have designed, built, and teach an industrial course on architecting distributed object systems. Being a very active reader of the literature on software architecture, design patterns, and software development process, I can say: there is, in my opinion, no better book on the subject of the process of architecting and the realities of life as an architect. Herein lies wisdom. Grasp it.
Helfen Sie anderen Kunden bei der Suche nach den hilfreichsten Rezensionen 
War diese Rezension für Sie hilfreich? Ja Nein


4 von 4 Kunden fanden die folgende Rezension hilfreich:
4.0 von 5 Sternen You should read it to learn the heuristics, 30. März 1999
Von 
A. Hofman (Utrecht, The Netherlands) - Alle meine Rezensionen ansehen
(REAL NAME)   
The authors Rechtin and Maier first address the discussion of Architecting vs Engineering. Interesting. In Part 1 they focus on 4 architecting methodologies: Normative (solution based), Rational (method based), Participative (stakeholder based) and Heuristic (lessons learned). It's good to stress the importance of lessons learned and best practices, although worst practices are very important too. But is a methodology based on Heuristics a methodology? Chapter 2 describes heuristics as tools and this chapter is good to read. Part two of the book, four domains to use Systems Architecting, offers new insights by showing how systems are architected in "builder architected systems" (making products), manufacturing systems, social systems and software systems. Especially the chapter on social systems is good. Remember to ask yourself the 4 who's (who benefits, who pays, who provides and who loses) because these parties influence the acceptance of your system. Part three of the book focusses on models, modelling methodologies and design progression. Chapter 10, written by Brenda Forman, describes the Political proces. In my opinion the best chapter of the book. Every architect, every consultant (whatever kind of consultant) should read this chapter. Terrific heuristics ("Proof is a matter of having the votes", "the best engineering solutions are not necessarily the best political solutions") and good examples on something that a lot of IT professionals don't like: politics. But, as the book suggests: "You may well find the craziness of the political process distasteful - but it will not go away!" You can use the lessons of this chapter every day. Finally, Appendix A lists a lot of heuristics you can use. Recommended reading.
Helfen Sie anderen Kunden bei der Suche nach den hilfreichsten Rezensionen 
War diese Rezension für Sie hilfreich? Ja Nein


8 von 9 Kunden fanden die folgende Rezension hilfreich:
1.0 von 5 Sternen Who is this book for?, 19. März 2003
Rezension bezieht sich auf: The Art of Systems Architecting, Second Edition (Gebundene Ausgabe)
Who do the authors write for? The experienced architect or the novice?
On p. 175f, they write: "The power of the Chapter 2 heuristics come by cataloging heuristics which apply in many domains, giving them generality ... However, the general heuristic relies on an experienced system-level architect to select the ones appropriate ... A catalog of general heuristics is of much less use to the novice; indeed, an uninformed selection among them could be dangerous."
In this book I haven't found one heuristic which was new to me. Run-of-the-mill stuff every experienced software developer knows. On the other hand not for the novice, as the authors say. So who do the authors write for?

Moreover, I found this book hard to read:
- The typesetting is terrible.
- Headings are undistinguishable. You don't know where you are.
- Very rarely, you stumble over a picture. Then it says nothing. E.g. regard figure 1.1 on page 9, and read the explanation. The story is simple, it tells you nothing, you learn nothing, and you get a picture to understand it even better.
- There is a lot of hot air in this book, and it's annoying to have to read that nonsense. E.g., on page 27: "An initial collection of about 100 heuristics was soon surpassed by contributions from over 200 students, reaching nearly 1000 heuristics within 6 years. Many, of course, were variations on single, central ideas". Yes, I would have expected this. It's OK to tell me, though. But then the sentence continues "just as there are many variations of hammers, saws, and screwdrivers". Well ... thank you.

Helfen Sie anderen Kunden bei der Suche nach den hilfreichsten Rezensionen 
War diese Rezension für Sie hilfreich? Ja Nein

Sagen Sie Ihre Meinung zu diesem Artikel: Eigene Rezension erstellen
 
 
Die neuesten Kundenrezensionen


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
 


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


Lieblingslisten


Ähnliche Artikel finden


Anhand des Sachgebietes nach ähnlichen Produkten suchen:


Ihr Kommentar