|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
| ||||||||||||||||||||||||
 Gutschein erhalten
Tauschen Sie jetzt The Art of Systems Architecting (Systems Engineering) gegen einen Amazon-Gutschein in Höhe von EUR 28,00 ein - einlösbar für Tausende von Artikeln bei Amazon.de. Entdecken Sie mehr eintauschbare Bücher im Bücher Trade-In Shop. Bitte beachten Sie die Teilnahmebedingungen.
 Jetzt für Amazon Student anmelden und um 20% erhöhten Eintauschwert sichern. |
Wird oft zusammen gekauft
Produktinformation
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
Ist der Verkauf dieses Produkts für Sie nicht akzeptabel? |
Mehr über die Autoren
Entdecken Sie Bücher, lesen Sie über Autoren und mehr
Produktbeschreibungen
Kurzbeschreibung
If engineering is the art and science of technical problem solving, systems architecting happens when you don't yet know what the problem is. The third edition of a highly respected bestseller, "The Art of Systems Architecting" provides in-depth coverage of the least understood part of systems design: moving from a vague concept and limited resources to a satisfactory and feasible system concept and an executable program. The book provides a practical, heuristic approach to the 'art' of systems architecting. It provides methods for embracing, and then taming, the growing complexity of modern systems. This Third Edition includes: five major case studies illustrating successful and unsuccessful practices; information on architecture frameworks as standards for architecture descriptions; new methods for integrating business strategy and architecture and the role of architecture as the technical embodiment of strategy; integration of process guidance for organizing and managing architecture projects; updates to the rapidly changing fields of software and systems-of-systems architecture; organization of heuristics around a simple and practical process model; and, a practical heuristic approach to the art of systems architecting extensively rewritten to reflect the latest developments, the text explains how to create a system from scratch, presenting invention/design rules together with clear explanations of how to use them. The author supplies practical guidelines for avoiding common systematic failures while implementing new mandates. He uses a heuristics-based approach that provides an organized attack on very ill-structured engineering problems. Examining architecture as more than a set of diagrams and documents, but as a set of decisions that either drive a system to success or doom it to failure, the book provides methods for integrating business strategy with technical architectural decision making.
Synopsis
The third edition of a highly respected bestseller, this book deals in depth with the least understood part of systems design: moving from a vague concept with limited resources to a satisfactory and feasible system and an executable program. Extensively rewritten to reflect the latest trends, this text addresses how to invent a system from scratch, presenting invention/design rules together with clear explanations of how to use them. The author supplies practical guidelines for avoiding common systematic failures while implementing new mandates. He organizes heuristics around a simple and practical process model and includes five major case studies of how successful and unsuccessful systems were architected.
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
Die hilfreichsten Kundenrezensionen
4 von 4 Kunden fanden die folgende Rezension hilfreich
Format:Gebundene Ausgabe
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.
4 von 4 Kunden fanden die folgende Rezension hilfreich
Format:Gebundene Ausgabe
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.
8 von 9 Kunden fanden die folgende Rezension hilfreich
Format: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?
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.
Möchten Sie weitere Rezensionen zu diesem Artikel anzeigen?
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
Kunden diskutieren
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
Lieblingslisten
Ähnliche Artikel finden
- Fremdsprachige Bücher > Architektur, Technik & Ingenieurswesen > Ingenieurwesen & Technik
- Fremdsprachige Bücher > Business, Karriere & Geld > Management & Führung > Projektmanagement
- Fremdsprachige Bücher > Computer & Internet > Hardware > Design & Architektur
- Fremdsprachige Bücher > Fachbücher > Technologie
Anhand des Sachgebietes nach ähnlichen Produkten suchen:
Ihr Kommentar
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
|
