- Gebundene Ausgabe: 286 Seiten
- Verlag: Springer; Auflage: 2006 (20. April 2006)
- Sprache: Englisch
- ISBN-10: 3540287132
- ISBN-13: 978-3540287131
- Größe und/oder Gewicht: 23,4 x 1,8 x 15,6 cm
- Durchschnittliche Kundenbewertung: 3 Kundenrezensionen
Nr. 679.940 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
- Nr. 1053 in Fremdsprachige Bücher > Business, Karriere & Geld > Industriezweige & Berufe > MIS
- Nr. 3004 in Fremdsprachige Bücher > Computer & Internet > Programmieren > Software-Design & Entwicklung > Softwareentwicklung
- Nr. 20610 in Fremdsprachige Bücher > Business, Karriere & Geld > Management & Führung
- Komplettes Inhaltsverzeichnis ansehen
Essential Software Architecture (Englisch) Gebundene Ausgabe – 15. Februar 2006
Kunden, die diesen Artikel gekauft haben, kauften auch
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Wenn Sie dieses Produkt verkaufen, möchten Sie über Seller Support Updates vorschlagen?
"Ian's book helps us to head in the right direction through the various techniques and approaches... An essential guide to computer science students as well as developers and IT professionals who aspire to become an IT architect". (Anna Liu, Architect Advisor, Microsoft Australia)
"All in all, Essential Software Architecture is head and shoulders above other books on the subject that I've read." (Gregory Wilson, Dr. Dobbs Journal)
"Gorton has produced a well-done, thorough work. Writing such a book on software architecture is a daunting task. (...) Very few texts on this subject have been able to achieve the delicate balance between generality and specificity. Essential Software Architecture does this." (Shantanu Bhattacharya, Siemens Information Systems Ltd., India, for ACM Reviews)
Job titles like "Technical Architect" and "Chief Architect" nowadays abound in the software industry, yet many people suspect that "architecture" is one of the most overused and least understood terms in professional software development.Gorton's book helps resolve this predicament. It concisely describes the essential elements of knowledge and key skills required to be a software architect. The explanations encompass the essentials of architecture thinking, practices, and supporting technologies. They range from a general understanding of software structure and quality attributes, through technical issues like middleware components and documentation techniques, to emerging technologies like model-driven architecture, software product lines, aspect-oriented design, service-oriented architectures, and the Semantic Web, all of which will influence future software system architectures.All approaches are illustrated by an ongoing real-world example. So if you work as an architect or senior designer (or want to someday), or if you are a student in software engineering, here is a valuable and yet approachable source of knowledge.'Ian's book helps us to head in the right direction through the various techniques and approaches...An essential guide to computer science students as well as developers and IT professionals who aspire to become an IT architect' - (Anna Liu, Architect Advisor, Microsoft Australia). Alle Produktbeschreibungen
Derzeit tritt ein Problem beim Filtern der Rezensionen auf. Bitte versuchen Sie es später noch einmal.
As an introductory textbook it is very useful for (to be) ICT professionals and students.
Hinzu kommt der leicht lesbare und immer unterhaltsame Stil des Autors, der aber nie schlampig oder oberflächlich ist.
Daher eine klare 5-Sterne-Empfehlung!
Die hilfreichsten Kundenrezensionen auf Amazon.com
The core chapters of the book are the first 6 chapters, which provided a strong foundation of knowledge. Chapter 1 introduces the topic by discussing architecture definition, abstraction, views and non-functional requirements plus others. Chapter 2 introduces the study study utilized throughout the book. I got alot out of chapters 3 & 4. Chapter 3 discusses software quality attributes that an architecture should take into consideration. Quality attribute are characteristics of an architecture design rather than capability. Quality attributes are such items as scalability, modifiability, security, performance, portability, etc. Chapter 4 discusses architecture design patterns and technologies applicable to architecture design. Chapter 5 discusses development cycle for defining your software architecture. Chapter 6 discusses how to document the architecture design.
I thought chapter 6 was a bit light in discussing architecture documentation. In the course where this book was the textbook, there was much time spent discussing views and viewpoints. I think chapter 6 should have delved deeper into the view discussion.
I thought the author did an excellent job with this book. There are many different types of software architectures that can be built. Therefore, readers would becoming various technological perspectives in reading this book. I felt he discussed the topics in the chapters in a way that was applicable to this wide audience.
I feel that this is an incredibly useful resource for those who have to design systems from the "ground up". It has several best practices and examples of where things can go wrong.
I feel this is well worth a read.