Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives Review

Average Reviews:

(More customer reviews)Are you looking to buy Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives? Here is the right place to find the great deals. we can offer discounts of up to 90% on Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives ReviewWhen it comes to the systems or software architecture, I subscribe to Tom Demarco's definition: "An architecture is a framework for the disciplined introduction of change." (http://www.systemsguild.com/GuildSite/TDM/Architecture.html). And while most of the job postings matching "architect" these days talk about the need for writing and testing code, there is a growing awareness in the industry that in order to build a resilient enterprise system an organization must look beyond design patterns and coding idioms. In addition to the technical challenges, building large enterprise system requires effort of many professionals during an extended period of time. This brings other non-technical risks into the picture.
This is one of the better books covering many issues that comprise System Architecture discipline in the light of their personal experience. The authors introduce us to an approach for partitioning architecture using Viewpoints (behavioral characteristics, e.g. Functional, Information, Concurrency, Development, Deployment, Operational) and Perspectives (nonfunctional aspects, e.g. Security, Performance and Scalability, Availability and Resilience, Evolution).
The first half of the book describes the discipline of Application Software Architecture, the second half contains two catalogs, one for Viewpoints and the other for Perspectives. Both catalogs describe concerns, artifacts (models), problems and pitfalls when focusing on a viewpoint or perspective.
I would qualify this book as a companion and reference for a beginner through intermediate level. It gives an excellent overview of what a system architect has to go through day in and day out to achieve success. The book contains a wealth of advice on what to pay and not pay attention to in any particular stage of the architectural development. The authors clearly speak from personal experience. Their examples are always to the point, although a bit sketchy with respect to details on techniques and artifacts and how to develop and use them. Considering the site of the volume, the authors did an excellent job balancing width and depth of coverage: trying to cover such a vast discipline in detail in a 500+-page book is not possible.Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives Overview
Software Systems Architecture is a practitioner-oriented guide to designing and implementing effective architectures for information systems. It is both a readily accessible introduction to software architecture and an invaluable handbook of well-established best practices. It shows why the role of the architect is central to any successful information-systems development project, and, by presenting a set of architectural viewpoints and perspectives, provides specific direction for improving your own and your organization's approach to software systems architecture.

With this book you will learn how to

Design an architecture that reflects and balances the different needs of its stakeholders
Communicate the architecture to stakeholders and demonstrate that it has met their requirements
Focus on architecturally significant aspects of design, including frequently overlooked areas such as performance,resilience, and location
Use scenarios and patterns to drive the creation and validation of your architecture
Document your architecture as a set of related views
Use perspectives to ensure that your architecture exhibits important qualities such as performance, scalability, and security

The architectural viewpoints and perspectives presented in the book also provide a valuable long-term reference source for new and experienced architects alike.

Whether you are an aspiring or practicing software architect, you will find yourself referring repeatedly to the practical advice in this book throughout the lifecycle of your projects.

A supporting Web site containing further information can be found at www.viewpoints-and-perspectives.info


Want to learn more information about Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Enterprise Architecture: Creating Value by Informed Governance (The Enterprise Engineering Series) Review

Average Reviews:

(More customer reviews)Are you looking to buy Enterprise Architecture: Creating Value by Informed Governance (The Enterprise Engineering Series)? Here is the right place to find the great deals. we can offer discounts of up to 90% on Enterprise Architecture: Creating Value by Informed Governance (The Enterprise Engineering Series). Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Enterprise Architecture: Creating Value by Informed Governance (The Enterprise Engineering Series) ReviewAfter reading Architecture Principles and Enterprise Architecture at Work I decided I would also read this book and Enterprise Governance and Enterprise Engineering as well. I am starting Enterprise Governance and Enterprise Engineering now. This series is great!!! I recommend every Enterprise Architect buy the series.
This book was the first of the series. It is only 145 pages long, but it is packed full of valuable information.
This book puts Enterprise Architecture into context. It gives a complete picture of Enterprise Architecture.
It starts with a great chapter on why Enterprise Architecture is needed and then has chapters on Positioning Enterprise Architecture, The Results of Enterprise Architecting, The Process of Enterprise Architecting, and The Enterprise Architect.
One of my favorite parts of the book is the description the book gives to the Enterprise Architect role. Anyone looking to hire or become an Enterprise Architect should read this chapter. It covers basic job descriptions, competencies (e.g. dedication, authenticity, integrity, negotiation, openness, stability, etc.), responsibilities, and personality types.
One of the things I didn't like about the book is that there is no index. This seems to be the case for the smaller Springer book, so I can't ding the authors for that.
This is a well rounded introduction to Enterprise Architecture. It covers all the basics in depth and also provides a really nice example to show you the results of Enterprise Architecting.
All in all I highly recommend this book for anyone involved in anyway with Enterprise Architecture. It will provide you a clear picture of what it involves.

Enterprise Architecture: Creating Value by Informed Governance (The Enterprise Engineering Series) OverviewTwenty years after the first publications and books on enterprise architecture, the domain is evolving from a technology-driven towards a more business-driven approach, thus empowering decision makers to adapt and transform an enterprise in order to keep up with changing business needs. At the same time the discipline of enterprise architecting has matured, leading to a better understanding of the profession of an enterprise architect.With this book, the authors aim to provide an overview of enterprise architecture including the process of creating, applying and maintaining it, thus taking into account the perspectives of CxOs, business managers, enterprise architects, solution architects, designers and engineers. They explore the results that are produced as part of an enterprise architecture, the process by which these are produced, and the role the architect plays in this process. As such, they do not describe a specific method for developing an enterprise (IT) architecture, nor do they define a specific modeling language for enterprise architecture, rather they offer the reader a fundamental way of thinking about enterprise architecture, which will enable him to select and apply the right approach, architecture framework and tools that meet the objective and context of the architecture work at hand. This approach is emphasized by discussion statements at the end of each chapter, sparking thoughts about benefits, shortcomings, and future research directions.Covering both theoretical foundations and practical use, and written in close collaboration between industry professionals and academic lecturers, Enterprise Architecture thus offers an ideal introduction for students in areas like business information systems or management science, as well as guidance and background for professionals seeking a more thorough understanding of their field of work.

Want to learn more information about Enterprise Architecture: Creating Value by Informed Governance (The Enterprise Engineering Series)?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

SOA-Based Enterprise Integration: A Step-by-Step Guide to Services-based Application Review

Average Reviews:

(More customer reviews)Are you looking to buy SOA-Based Enterprise Integration: A Step-by-Step Guide to Services-based Application? Here is the right place to find the great deals. we can offer discounts of up to 90% on SOA-Based Enterprise Integration: A Step-by-Step Guide to Services-based Application. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

SOA-Based Enterprise Integration: A Step-by-Step Guide to Services-based Application ReviewWhen I first looked at this book (after opening the package from Amazon), I thought it would be perfect... it's not a hefty 1000-page cookbook... and seemed like it would be just the perfect level of detail to rein in the broad topics into something coherent. In fact, the book does a decent job with the overall picture, but has some major flaws in style, presentation, and bias that renders it a groggy, often un-informing, experience. I stuck with it, because I had no alternative at hand, and a tight timeframe, so I can speak as a reviewer that has actually read the book.
The Good: This book contains a decent overview of SOA components and does tie them together in a good overall picture.
The Bad (part I): This book was written by an IBM Senior Architect. The technical editor for the book is an IBM Architect. The forward was written by an IBM Fellow. The back cover contains endorsements from two IBMers, one of which is the VP for WebSphere Marketing. Much of the book contains unbiased information on industry standards. However, much of the rest of the book is an over-the-top promotion of IBM products. For example, the capstone of this work is the chapter on Enterprise Service Bus. This chapter reads like glossy marketing literature for IBM products at best and like an informertial at worst. That chapter is only 30 pages long, but uses the word "WebSphere" 24 times by my count. Conversely, the non-IBM Weblogic is mentioned exactly 0 times in the same chapter, and rarely throughout the rest of the book. This book calls IBM's WESB "the prime example" of an application server based ESB and goes on to list, in bulletized form, its "features and advantages". In another section, the author states, "IBM offers the most complete product lines in this area."
The Bad (part II): This book is poorly presented. It can't decide if it is a 40,000 ft overview or a detailed description of various technologies. For example, SOAP is covered in 22 short pages. That's obviously not enough for anything more than an explanation of what it is, how it is used, why it's good, and a few examples. Yet the author tries to dive into the structure of a SOAP message to the point of who-cares detail for a book like this. In the 22 pages covering SOAP, for example, the author states FIVE TIMES that if the header element is present, it must precede the body element.
In addition, the author uses a highly verbose and repetitive style. It often seems that about 20% of the book is either telling you what it's going to tell you or telling you what it's already told you. The book could have contained the same amount of useful information in about 200 pages. This overly verbose and repetitive style gives the book a sense that the author, a PhD, does not know how to communicate effectively with lesser intellects and frequently overshoots his simplification. The result is that the work often, but inconsistently, reads a bit like a "for dummies" type of book.SOA-Based Enterprise Integration: A Step-by-Step Guide to Services-based Application Overview
Foreword by Ray Harishankar, IBM Fellow
"There are many books on the market on the topic of SOA and SOA's business and technology value.This book focuses on one of the key technical values of SOA and does an excellent job of describing SOA-based application integration by clarifying the relationship and patterns of SOA with other integration technologies in a distributed computing environment." Sandra Carter, IBM Vice President for SOA, BPM, and WebSphere Marketing
"Services Oriented Architectures present many challenges today in the integration of existing systems and new systems, along with many times, old legacy mainframe applications.This book successfully addresses many of the complexities we see in the integration of SOA and mainframe legacy applications, presenting options and approaches to integrate the applications with the rest of the enterprise.The author takes a clearly defined pattern-based approach discussing the advantages, tools and methods.Readers will benefit from the insights in this book whether they play the architect role or a developer role on a SOA project."Sue Miller-Sylvia, IBM Fellow and Application Development Service Area Leader

Want to learn more information about SOA-Based Enterprise Integration: A Step-by-Step Guide to Services-based Application?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Web Service Contract Design and Versioning for SOA Review

Average Reviews:

(More customer reviews)Are you looking to buy Web Service Contract Design and Versioning for SOA? Here is the right place to find the great deals. we can offer discounts of up to 90% on Web Service Contract Design and Versioning for SOA. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Web Service Contract Design and Versioning for SOA ReviewI just wanted to let other Kindle owners in the IT profession know that the content of this book is as good as the other reviews indicate, but you should buy the paper edition rather than the Kindle edition.
Most of the xml in the Kindle edition is unreadable, due to its being truncated at the left margin, and sometimes at the bottom of the page, as well. Some of the sidebar content has the same problem.
All in all, there's just too much content missing from the Kindle edition. With the hard copy being just ten dollars more, it's the better choice.Web Service Contract Design and Versioning for SOA OverviewThe Ultimate Guide for Designing and Governing Web Service ContractsFor Web services to succeed as part of SOA, they require balanced, effective technical contracts that enable services to be evolved and repeatedly reused for years to come. Now, a team of industry experts presents the first end-to-end guide to designing and governing Web service contracts. Writing for developers, architects, governance specialists, and other IT professionals, the authors cover the following areas:Understanding Web Service Contract Technologies Initial chapters and ongoing supplementary content help even the most inexperienced professional get up to speed on how all of the different technologies and design considerations relate to the creation of Web service contracts. For example, a visual anatomy of a Web service contract documented from logical and physical perspectives is provided, along with a chapter dedicated to describing namespaces in plain English. The book is further equipped with numerous case study examples and many illustrations.Fundamental and Advanced WSDLTutorial coverage of WSDL 1.1 and 2.0 and detailed descriptions of their differences is followed by numerous advanced WSDL topics and design techniques, including extreme loose coupling, modularization options, use of extensibility elements, asynchrony, message dispatch, service instance identification, non-SOAP HTTP binding, and WS-BPEL extensions. Also explained is how WSDL definitions are shaped by key SOA design patterns.Fundamental and Advanced XML SchemaXML Schema basics are covered within the context of Web services and SOA, after which advanced XML Schema chapters delve into a variety of specialized message design considerations and techniques, including the use of wildcards, reusability of schemas and schema fragments, type inheritance and composition, CRUD-style message design, and combining industry and custom schemas.Fundamental and Advanced WS-PolicyTopics, such as Policy Expression Structure, Composite Policies, Operator Composition Rules, and Policy Attachment establish a foundation upon which more advanced topics, such as policy reusability and centralization, nested, parameterized, and ignorable assertions are covered, along with an exploration of creating concurrent policy-enabled contracts and designing custom policy assertions and vocabularies.Fundamental Message Design with SOAPA broad range of message design-related topics are covered, including SOAP message structures, SOAP nodes and roles, SOAP faults, designing custom SOAP headers and working with industry-standard SOAP headers.Advanced Message Design with WS-AddressingThe art of message design is taken to a new level with in-depth descriptions of WS-Addressing endpoint references (EPRs) and MAP headers and an exploration of how they are applied via SOA design patterns. Also covered are WSDL binding considerations, related MEP rules, WS-Addressing policy assertions, and detailed coverage of how WS-Addressing relates to SOAP Action values.Advanced Message Design with MTOM, and SwADeveloping SOAP messages capable of transporting large documents or binary content is explored with a documentation of the MTOM packaging and serialization framework (including MTOM-related policy assertions), together with the SOAP with Attachments (SwA) standard and the related WS-I Attachments Profile.Versioning Techniques and StrategiesFundamental versioning theory starts off a series of chapters that dive into a variety of versioning techniques based on proven SOA design patterns including backward and forward compatibility, version identification strategies, service termination, policy versioning, validation by projection, concurrency control, partial understanding, and versioning with and without wildcards.Web Service Contracts and SOAThe constant focus of this book is on the design and versioning of Web service contracts in support of SOA and service-orientation. Relevant SOA design principles and design patterns are periodically discussed to demonstrate how specific Web service technologies can be applied and further optimized. Furthermore, several of the advanced chapters provide expert techniques for designing Web service contracts while taking SOA governance considerations into account.About the Web Siteswww.soabooks.com supplements this book with a variety of resources, including a diagram symbol legend, glossary, supplementary articles, and source code available for download.www.soaspecs.com provides further support by establishing a descriptive portal to XML and Web services specifications referenced in all of Erl's Service-Oriented Architecture books.

Want to learn more information about Web Service Contract Design and Versioning for SOA?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Touch of Class: Learning to Program Well with Objects and Contracts Review

Average Reviews:

(More customer reviews)Are you looking to buy Touch of Class: Learning to Program Well with Objects and Contracts? Here is the right place to find the great deals. we can offer discounts of up to 90% on Touch of Class: Learning to Program Well with Objects and Contracts. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Touch of Class: Learning to Program Well with Objects and Contracts ReviewFrom the man who invented eiffel. An excellent introduction to software development the right way. Examples and the software development environment is available as a free download. The approach used in this book is useful for the beginner as well as an experienced programmer. Software runs on Linux, Mac OS x,
and Windows.Touch of Class: Learning to Program Well with Objects and Contracts OverviewFrom object technology pioneer and ETH Zurich professor Bertrand Meyer, winner of the Jolt award and the ACM Software System Award, a revolutionary textbook that makes learning programming fun and rewarding. Meyer builds his presentation on a rich object-oriented software system supporting graphics and multimedia, which students can use to produce impressive applications from day one, then understand inside out as they learn new programming techniques. Unique to Touch of Class is a combination of a practical, hands-on approach to programming with the introduction of sound theoretical support focused on helping students learn the construction of high quality software. The use of full color brings exciting programming concepts to life.Among the useful features of the book is the use of Design by Contract, critical to software quality and providing a gentle introduction to formal methods. Will give students a major advantage by teaching professional-level techniques in a literate, relaxed and humorous way.

Want to learn more information about Touch of Class: Learning to Program Well with Objects and Contracts?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Pattern-Oriented Software Architecture Volume 4: A Pattern Language for Distributed Computing (v. 4) Review

Average Reviews:

(More customer reviews)Are you looking to buy Pattern-Oriented Software Architecture Volume 4: A Pattern Language for Distributed Computing (v. 4)? Here is the right place to find the great deals. we can offer discounts of up to 90% on Pattern-Oriented Software Architecture Volume 4: A Pattern Language for Distributed Computing (v. 4). Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Pattern-Oriented Software Architecture Volume 4: A Pattern Language for Distributed Computing (v. 4) ReviewI don't have much to add over T. Anderson's review, but wanted to weigh in with a 5-star vote as a practicing distributed-systems architect. In particular I'm irritated by the one-star review from the person who obviously didn't understand what he/she was buying.
This is as close as you're going to get to a one-stop "encyclopedia" of patterns relevant to distributed computing (and other areas as well). I own most of the architecture/design patterns books, but this is the one I'll go to first for ideas, study, and use as a reference.
As for content, the catalogue of patterns is more comprehensive than any other volume I'm aware of and it is well organized. Each chapter describes a group of patterns that address recurrent vertical and horizontal architectural problem spaces. Each group is briefly introduced and described in the context of that. These introductions are pithy, on-target, and along with the complete pattern descriptions almost constitute a good introduction to distributed computing in general.
Most patterns are described in two pages in a format that has been well-honed over time for usefulness and comprehensibility. You find out where and when each pattern is likely to be useful, what motivates it, how it works, pros and cons, and what other patterns might be used with it.
The cross-referencing between patterns both within this book and in other sources is extensive and one of its most valuable features. The authors provide you with 114 pattern descriptions cross-referenced with "over 150" from other sources. That's a pretty extensive language!
Lots of spelling errors and such, but nothing that should confuse anyone.
This book is NOT a true encyclopedia, and you will want or need some of the core volumes that cover the "over 150" patterns that are referenced but not described here. The most notable are:
Patterns of Enterprise Application Architecture (The Addison-Wesley Signature Series)
Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions (The Addison-Wesley Signature Series)
Remoting Patterns: Foundations of Enterprise, Internet and Realtime Distributed Object Middleware (Wiley Software Patterns Series)
Most, if not all, of the material in Pattern-Oriented Software Architecture Volume 2: Patterns for Concurrent and Networked Objects is covered in Volume 4. If you don't have that book you might want it for deeper discussion of some of the patterns. On the other hand, the current volume contains important updates to a couple of patterns in the earlier volume.
If you're new to patterns, please avoid Design Patterns: Elements of Reusable Object-Oriented Software (Addison-Wesley Professional Computing Series), also known as the "GoF" (Gang of Four) book. It is a classic and the authors deserve their "props" for introducing design patterns to the broader development community, but it is the worst-written and most misleading book I've ever read on patterns. (In fairness to the authors, it was the "grand-daddy" of them all and perhaps they can be excused for not having the intervening 12 years of experience in pattern documentation to help them.)
I've heard good things about Head First Design Patterns (Head First) and Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition) from people who have read the GoF book, so you might try that. I haven't read either myself.
If you're familiar with patterns and want perhaps the most comprehensive and useful single pattern book to date, especially if you're involved with the architecture of distributed systems, buy this!
It is not for beginners or those looking for boilerplate code!
Pattern-Oriented Software Architecture Volume 4: A Pattern Language for Distributed Computing (v. 4) OverviewThe eagerly awaited Pattern-Oriented Software Architecture (POSA) Volume 4 is about a pattern language for distributed computing.
The authors will guide you through the best practices and introduce you to key areas of building distributed software systems. POSA 4 connects many stand-alone patterns, pattern collections and pattern languages from the existing body of literature found in the POSA series. Such patterns relate to and are useful for distributed computing to a single language.
The panel of experts provides you with a consistent and coherent holistic view on the craft of building distributed systems.
Includes a foreword by Martin Fowler
A must read for practitioners who want practical advice to develop a comprehensive language integrating patterns from key literature.


Want to learn more information about Pattern-Oriented Software Architecture Volume 4: A Pattern Language for Distributed Computing (v. 4)?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Security for Web Services and Service-Oriented Architectures Review

Average Reviews:

(More customer reviews)Are you looking to buy Security for Web Services and Service-Oriented Architectures? Here is the right place to find the great deals. we can offer discounts of up to 90% on Security for Web Services and Service-Oriented Architectures. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Security for Web Services and Service-Oriented Architectures ReviewThe review is based only on the first three chapters that I have managed to read so far.
1. The premise of the book is pretty valuable. There is need for updated literature that takes web services security out of the standards world and makes it more approachable. On that count, I laud the initiative.
2. The book, however, suffers from several significant issues:
a. The proof-reading, for a book that purports to be a reference on the topic, is abysmal. Consider this snippet on page 35 related to threat modeling: "even though the security functions provided by the middleware are becoming more and more reach and complete,...". Any technical editor should have picked up the multiple mistakes in this sentence. Unfortunately, such mistakes abound in the book.
b. In trying to emphasize theory, the book often comes across as dry and irrelevant. For example, table 3.2 related to STRIDE Categories and the surrounding explanation on page 32, while being factually complete, seem like they belong to a Microsoft Press book. At the level the book aims for, what's important is not an explanation of STRIDE (why wouldn't I read Howard's or Swiderski's books for that?) but how that relates to Web services. Explaining the STRIDE concepts as related to a fictional Web Service might have been much more useful.
c.Some of the technical terms used in the book are downright incorrect. For example, on page 35, in the same paragraph as #2(a), the authors talk of "RBAC-based authorization mechanisms". RBAC itself stands for Role Based Access Control. What does it mean for an authorization mechanism to be RBAC-based?
d. If this book is to be useful at all, the figures need to be seriously improved. They are miniature, complex and hardly span a quarter of a page. In short, they are barely decipherable and there's a lot of text referring to such figures that becomes disconnected.
With all this said, I still give the book 3 stars because there is at least some method to the approach and it's much better than reading a bunch of W3C or OASIS standards. Not to mention the fact that chapter 3 refers to CAPEC that I had, in part, contributed attack patterns to :-)
I would definitely wish for the editors at Springer to take a serious look at the language and technical terminology and make figures more understandable. The book has a lot of promise and it would be a shame if such matters were to obscure that.Security for Web Services and Service-Oriented Architectures OverviewWeb services based on the eXtensible Markup Language (XML), the Simple Object Access Protocol (SOAP), and related standards, and deployed in Service-Oriented Architectures (SOA), are the key to Web-based interoperability for applications within and across organizations. It is crucial that the security of services and their interactions with users is ensured if Web services technology is to live up to its promise. However, the very features that make it attractive - such as greater and ubiquitous access to data and other resources, dynamic application configuration and reconfiguration through workflows, and relative autonomy - conflict with conventional security models and mechanisms.Elisa Bertino and her coauthors provide a comprehensive guide to security for Web services and SOA. They cover in detail all recent standards that address Web service security, including XML Encryption, XML Signature, WS-Security, and WS-SecureConversation, as well as recent research on access control for simple and conversation-based Web services, advanced digital identity management techniques, and access control for Web-based workflows. They explain how these implement means for identification, authentication, and authorization with respect to security aspects such as integrity, confidentiality, and availability.This book will serve practitioners as a comprehensive critical reference on Web service standards, with illustrative examples and analyses of critical issues; researchers will use it as a state-of-the-art overview of ongoing research and innovative new directions; and graduate students will use it as a textbook on advanced topics in computer and system security.

Want to learn more information about Security for Web Services and Service-Oriented Architectures?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Design for Trustworthy Software: Tools, Techniques, and Methodology of Developing Robust Software Review

Average Reviews:

(More customer reviews)Are you looking to buy Design for Trustworthy Software: Tools, Techniques, and Methodology of Developing Robust Software? Here is the right place to find the great deals. we can offer discounts of up to 90% on Design for Trustworthy Software: Tools, Techniques, and Methodology of Developing Robust Software. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Design for Trustworthy Software: Tools, Techniques, and Methodology of Developing Robust Software ReviewThis thoroughly researched book begins with an excellent summary of the state of software development methodologies. It provides a useful description of the important strategies, life-cycle models, and process improvement methodologies. The theme of the book comes from applying Taguchi Methods to software development. This approach to trustworthy software shifts effort "upstream" from testing to design: Build software right in the first place rather than waiting for a huge quality assurance department (or worse yet, customers) to find the bugs for you. Several chapters provide detail on how to apply these principles to large scale software systems.
The authors have pulled together material from an impressive set of resources into one, admittedly lengthy, book. The shear number of methodologies (including corresponding acronyms!) contained in this volume is staggering. The chapter endnotes document these sources and web references give many pointers for additional information. They also include several case studies written by practioners who have used the methodologies described in the book.Design for Trustworthy Software: Tools, Techniques, and Methodology of Developing Robust Software Overview ASQ 2007 CROSBY MEDAL WINNER!

An Integrated Technology for Delivering Better Software—Cheaper and Faster!

This book presents an integrated technology, Design for Trustworthy Software (DFTS), to address software quality issues upstream such that the goal of software quality becomes that of preventing bugs in implementation rather than finding and eliminating them during and after implementation. The thrust of the technology is that major quality deployments take place before a single line of code is written!

This customer-oriented integrated technology can help deliver breakthrough results in cost, quality, and delivery schedule thus meeting and exceeding customer expectations. The authors describe the principles behind the technology as well as their applications to actual software design problems. They present illustrative case studies covering various aspects of DFTS technology including CoSQ, AHP, TRIZ, FMEA, QFD, and Taguchi Methods and provide ample questions and exercises to test the readers understanding of the material in addition to detailed examples of the applications of the technology.

The book can be used to impart organization-wide learning including training for DFTS Black Belts and Master Black Belts. It helps you gain rapid mastery, so you can deploy DFTS Technology quickly and successfully.
Learn how to

• Plan, build, maintain, and improve your trustworthy software development system
• Adapt best practices of quality, leadership, learning, and management for the unique software development milieu
• Listen to the customer's voice, then guide user expectations to realizable, reliable software products
• Refocus on customer-centered issues such as reliability, dependability, availability, and upgradeability
• Encourage greater design creativity and innovation
• Validate, verify, test, evaluate, integrate, and maintain software for trustworthiness
• Analyze the financial impact of software quality
• Prepare your leadership and infrastructure for DFTS

Design for Trustworthy Software will help you improve quality whether you develop in-house, outsource, consult, or provide support. It offers breakthrough solutions for the entire spectrum of software and quality professionals—from developers to project leaders, chief software architects to customers.

The American Society for Quality (ASQ) is the world's leading authority on quality which provides a community that advances learning, quality improvement, and knowledge exchange to improve business results, and to create better workplaces and communities worldwide. The Crosby Medal is presented to the individual who has authored a distinguished book contributing significantly to the extension of the philosophy and application of the principles, methods, or techniques of quality management.


Bijay K. Jayaswal, CEO of Agilenty Consulting Group, has held senior executive positions and consulted on quality and strategy for 25 years. His expertise includes value engineering, process improvement, and product development. He has directed MBA and Advanced Management programs, and helped to introduce enterprise-wide reengineering and Six Sigma initiatives.

Dr. Peter C. Patton, Chairman of Agilenty Consulting Group, is Professor of Quantitative Methods and Computer Science at the University of St. Thomas. He served as CIO of the University of Pennsylvania and CTO at Lawson Software, and has been involved with software development since 1955.


Want to learn more information about Design for Trustworthy Software: Tools, Techniques, and Methodology of Developing Robust Software?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Building Reliable Component-Based Software Systems Review

Average Reviews:

(More customer reviews)Are you looking to buy Building Reliable Component-Based Software Systems? Here is the right place to find the great deals. we can offer discounts of up to 90% on Building Reliable Component-Based Software Systems. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Building Reliable Component-Based Software Systems ReviewOh no, another book with a misleading title...
It should have been called "Building ***snip*** Component-Based Software Systems". See the difference ? The only reason I chose to read it was that magic "Reliable" word, and now what do we have ?
So, magic mirror, please tell us who should read this book ?
Quote:
"Experienced developers will find useful technical details ... while inexperienced developers can learn about the principles ... the book is [also] aproppriate as a course book ... for graduate ... or undergraduate students."
I for one am an experienced developer, now where are my technical details ?
Before I continue, please keep in mind that my opinion is biased by the word "Reliable" in the title. The book hardly says a word about reliability, for God's sake.
The book is a compilation of assorted chapters written by different European researchers. Researchers more than practioners that is. Basically the book hardly says anything you wouldn't know if you have ever put your hands on OOP.
First chapters come to components from different perspective each, but most remain introductory. Component is this, interface is that, environment is also concerned... Components are good (but too complex to say anything else)...
Many of the non-trivial conclusions are highly controversial. Example, chapter 3, "Architecting Component-Based Systems". The authors take 3 "architectures", namely "Pipes and filters", "Blackboard" and "Object-oriented", give each a half a page discussion, and come to the conclusion that out of the three the "Pipes and filters" is the most secure (!). Excuse me, but this is absurd.
Various discussions, ex. semantical integrity (limited with design-by-contract), roles, failure injections, product lines were reasonably interesting.
Chapters 11, 12 touch the Koala platform developed at Philips and used internally for their TVs and stuff. Ch. 12 was interesting to read, and is the only one that comes close to the promised "technical details". It's counterpart, ch. 11 is burdened with controversial conclusions, ex. "For example, the use of Windows results in applications based on message loops, which may not be the best architecture in all cases" or "A company that sells a software package can only survive if it has many customers".
The rest of the chapters is dedicated to using components in real-time systems and describing several case-studies. What do they say ? Using components is real-time is more complex than ever... It's difficult to introduce common approaches where machine power is limited... Real-time is special... Well, what do you know.
I won't discuss case studies which take last several chapters. They are various, some too aerial, some not, but they certainly say little new. Emulating a RTOS on top of Windows NT by means of a hi-res timer and cooperative user-level multithreading ? Tag-your-stuff-and-put-it-in-Active-Directory kind of system ? COM-like something which is not quite COM ? It's not RELIABLE.
The writing style is far less than perfect. Look, I understand that the book is written by a bunch of European professors, moreover, I'm not a native English speaker myself, but !
How shall a reader cope with something like: "There is that system, it has two parts to it - BOM and BOF. BOM does this, BOF does that." ? Oh, BOM it is, huh ? Thank you very much, it's all clear to me now. I mean, if you describe a system which is obviously transparent to you, why not make it easy for reader to understand ?
Also fun is repeating same things multiple times within a chapter. Like "Foo is bar, but biz is not baz. ... 2 pages ... Foo is bar, but biz is not baz." First time you encounter this, it's like "wait a minute, I've just seen exactly same thing... flip... flip... oh... what a heck ?". Again, I agree that one big book is better than one small book, but it's somehow disturbing.
I also didn't understand having a UML diagram with Name being a separate entity linked to all other entities on the stage. I always thought that Name should be an attribute.
And on and on it goes...
Therefore 3 out of 5, may be less, may be more for students.Building Reliable Component-Based Software Systems OverviewCBSE (component-based software engineering) is the emerging discipline of the development of software components and systems incorporating such components. This resource provides a practical guide to building reliable component-based software systems. It aims to give software-development professionals the guidance they need to effectively manage complex software through the integration of pre-existing components. Moreover, the book discusses the benefits and risks to be considered when developing components and systems using components. This hands-on reference describes technical and non-technical aspects of systems development using components and component development. It focuses on real-time systems, employing case studies using component-based approaches in the development of industrial automation systems. This book should be of interest to: software developers; project managers; researchers; and professors and students interested in component software engineering.

Want to learn more information about Building Reliable Component-Based Software Systems?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Building Software: A Practitioner's Guide (Applied Software Engineering Series) Review

Average Reviews:

(More customer reviews)Are you looking to buy Building Software: A Practitioner's Guide (Applied Software Engineering Series)? Here is the right place to find the great deals. we can offer discounts of up to 90% on Building Software: A Practitioner's Guide (Applied Software Engineering Series). Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Building Software: A Practitioner's Guide (Applied Software Engineering Series) ReviewSaran & Krishnamurthy have managed to accomplish in this work a singularly new and valuable insight: that of bringing to the "art" of designing robust and valid software systems perspectives from the larger body of work and thought around the areas of general (not software specific) systems design, media ecology, even philosophy - that have long existed but (for reasons unknown) never till now been leveraged to add value to the software system's architect/ manager's arsenal of tools and knowledge. Particularly interesting are their inclusion of Ashby's Law of Requisite Variety and quotes from McLuhan's seminal work "Understanding Media" and their contextualization of these to the building of software systems.
In addition, another thing I greatly appreciate in this volume is the candid documentation of learning and thoughts from what is the authors' clearly hands-on experience in architecting and managing engineering lifecycles of complex software systems. They rightly point out that while failures and execution challenges have long been shared across and analyzed in industries other than software and consequently mitigated, that has not been the case for the area of software systems design. They attempt to fill this gap.
It is apparent that the authors clearly understand the challenges faced by techno management and business stakeholders that have long hampered efficiency and execution. They candidly and rightly acknowledge that "the map is not the territory". Rather than offer another complex and elaborate lifecycle management framework, they take the approach of offering a simple "SEE" model that is general enough to be implemented under business constraints. The comments are straightforward and made in context of the environment and business challenges, dynamics of the software industry today (especially applications development) - for instance there is a fairly comprehensive discussion of "insourcing" vs. "outsourcing" as strategic choices and outsourcing business models.
All in all, I recommend this volume, especially since it takes the practical approach of not offering a canned solution to building better software touted as a silver bullet - because none exists - and places emphasis instead on fostering thought and reflection through a number of insights, learning from hard experience, nuggets of wisdom and a general thought and planning model. After 15 years of building and managing the development of complex software systems, it's not often now that I come across a whole lot really "new" or "valuable" (to me) in works of such nature... But because of the observations I made above- I was pleased to discover that this book was a worthwhile exception!
Building Software: A Practitioner's Guide (Applied Software Engineering Series) OverviewNovel in its approach to software design, development, and management, Building Software: A Practitioner's Guide shows you how to successfully build and manage a system. The approach the authors recommend is a simple, effective framework known as Solution Engineering Execution (SEE). Through SEE, you create a successful solution by following a highly organized, well-planned process. This process makes you view the solution from a holistic, systematic perspective. Developing a successful system requires that you are able to address technology matters related to architecture, design, selection, integration, and security. Building Software: A Practitioner's Guide offers insight into how to make software reliable and how to ensure it meets customer and organizational needs. Using the above approach you are able to:Find a good solution to the problem at handFocus on engineering the solution wellAddress all aspects of delivery associated with the solution The book provides insightful examples of cross-domain and legacy solutions that allow you to overcome common software concerns such as requirement issues, change control, quality and schedule management, and internal and external communication problems.

Want to learn more information about Building Software: A Practitioner's Guide (Applied Software Engineering Series)?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Applied Software Product Line Engineering Review

Average Reviews:

(More customer reviews)Are you looking to buy Applied Software Product Line Engineering? Here is the right place to find the great deals. we can offer discounts of up to 90% on Applied Software Product Line Engineering. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Applied Software Product Line Engineering ReviewThe authors of this book represent an all-star lineup of the best of the best in the Software Product Line Engineering (SPLE) field. They do a great job of providing a snapshot of the current SPLE best practices in the industry today.
Each chapter is written by a different author, or team of authors. This leads to some different perspectives on SPLE. This works for this type of book, but it does provide a conflict in the points of view taken in certain chapters. If you have experience with SPLE this shouldn't be an issue because you will already understand what those different views are, but for someone with little or no experience this could cause confusion. I found none of the points of view wrong, just different. Different domains require, and provide for, different approaches.
I recommend this book to those that are experienced as a guide to the evolution of the topics covered, and to the beginner I would use it as a road map of topics you should learn more about in order to get the full understanding behind each chapter. Each chapter provides an excellent reference section.
I would suggest also reading the following books. They provide more information about the material covered in some of the chapters.
"Software Product Lines: Practices and Patterns" is mentioned several places in the book. It is key to getting a more in-depth look at the 29 practice areas and the patterns that help to apply them.
"Designing Software Product Lines with UML: From Use Cases to Pattern-Based Software Architectures" goes in-depth into the use of Product Line UML based Software engineering (PLUS). UML and PLUS are mentioned several places in the book. PLUS is what I use when I build a software product line. I have created a UML stereotype in SPARX EA which you can download. Just google "UML STATIC MODELING IN PRODUCT LINE ENGINEERING (PLE) with SPARX EA".
The table of contents is below.
ORGANIZATIONAL AND MANAGERIAL ISSUES
Software Product Line Engineering: Overview and Future Directions
A Roadmap for Software Product Line Adoption
New Methods behind a New Generation of Software Product Line Successes
Evaluating Product Family Development Using the Balanced Scorecard Approach
Product Management for Software Product Lines: An Overview
METHODOLOGIES AND PROCESSES
A Systems Product Line Approach
Adoption of Software Product Lines to Develop Autonomic Pervasive Systems
Development of a Software Product Line for Validation
Environments
Building a Family of Compilers
Formal Verification and Software Product Lines
TECHNICAL ISSUES
Multiple-View Requirements Models for Software Product Line Engineering
Managing Flexibility and Variability: A Road to Competitive Advantage
Feature Oriented Analysis and Design for Dynamically
Reconfigurable Product Lines
Separating Application and Security Concerns in Modeling
Software Product Lines
Architecture as Language
INDUSTRY EXPERIENCES AND CASE STUDIES
Management and Financial Controls of a Software Product Line Adoption
Efficient Scoping with CaVE: A Case Study
Model-Driven, Aspect-Oriented Product Line Engineering: An Industrial Case Study
Evaluation of Design Options in Embedded Automotive Product Lines
Product Line in the Business Process Management Domain
I found the material covered to all be of great value. There are a lot of great case studies through out the book beyond the section of chapters that cover case studies. They help to take the practices covered from theory to reality.
My biggest pain point with this book is the index. It is just down right sad. I am not going to ding the book for something technical the editors missed. I have been very tempted to grab an electronic version to make up for its weakness', although I have not seen one for sale.
All in all if you are involved with Software Product Line Engineering at all, this is a mandatory read. Software Product Line Engineering is an evolving field and this book brings us up to date on the evolution of the field.
Applied Software Product Line Engineering OverviewOver the last decade, software product line engineering (SPLE) has emerged as one of the most promising software development paradigms for increasing productivity in IT-related industries. Detailing the various aspects of SPLE implementation in different domains, Applied Software Product Line Engineering documents best practices with regard to system development. Expert contributors from academia and industry come together and focus on core asset development, product development, and management, addressing the process, technical, and organizational issues needed to meet the growing demand for information. They detail the adoption and diffusion of SPLE as a primary software development paradigm and also address technical and managerial issues in software product line engineering. Providing an authoritative perspective of the latest research and practice in SLPE, the text:Presents in-depth discussions and many industry / case studies Covers applications in various domains including automotive, business process management, and defenseOrganized according to the organizational, process, and technical aspects of software product lines within an organizationProvides the expertise of a distinguished panel of global contributorsEver-increasing global competition coupled with a fragile world economy means that the pressure is on for software engineers and software process improvement professionals to find ways to meet the needs of expanding markets-with greater efficiency and effectiveness. This book arms readers with the insight needed to harness the power of SPLE to increase productivity, reduce time to market, and to handle the growing diversity in the quickly evolving global marketplace.

Want to learn more information about Applied Software Product Line Engineering?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Documenting Software Architectures: Views and Beyond (2nd Edition) Review

Average Reviews:

(More customer reviews)Are you looking to buy Documenting Software Architectures: Views and Beyond (2nd Edition)? Here is the right place to find the great deals. we can offer discounts of up to 90% on Documenting Software Architectures: Views and Beyond (2nd Edition). Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Documenting Software Architectures: Views and Beyond (2nd Edition) ReviewSoftware architecture really is unlike any other aspect of its design. The architecture has deeper meaning and larger scale than any other aspect, and can't be discussed in the same ways.
This book opens that discussion. Among the "architecture" books I've read lately, this is the only one to offer concrete advice on describing, presenting, and analyzing archtiectural features of a system. It identifies a number of documentation types and variations. It also identifies a number of different readers - developers, future architects, users, etc. - and addresses their different documentation needs.
The authors use a little UML, but not a lot. For one thing, standard UML works at too low a level for architectural discussion. Classes, and even hierarchies of class inheritance are such fine-grained entities that architecture gernerally won't address them. Instead, the authors offer a number of diagramming styles of their own. For once, I agree with the need for non-standard notation.
Even so, I think they under-utilize the existing standards in favor of their own terminology and notation. They could have used a UML profile for lots of the discussion. It would have had to be a new profile, however, not just a force-fit of the real-time profile. They also under-used the existing architecture standards (IEEE/ANSI, DoD, NASA, and more) in favor of their own discussion. Maybe their approach can be used in any of those frameworks, but that should have been more explicit.
I see only one major flaw in this book, the assumption that a software system's architecture describes the program delivered to a customer. That's way too narrow. A large system includes things like test harnesses, debug instrumentation, application-specific QA tools, and user documentation of many kinds. Those can be major undertakings of their own. They are intimately tied to the delivered software, and may constrain the actual product.
On the postivie side, this book offer an extensive real-world case study. That probably doubles the book's value, by putting a concrete face on the otherwise abstract discussion.
There are two ways to use this book: you can agree with it, or think about it and disagree with it. If you really think about it, though, you get it's full value whether you agree or not.
In other words, you can't lose by reading this book.Documenting Software Architectures: Views and Beyond (2nd Edition) Overview"This new edition is brighter, shinier, more complete, more pragmatic, more focused than the previous one, and I wouldn't have thought it possible to improve on the original. As the field of software architecture has grown over these past decades, there is much more to be said, much more that we know, and much more that we can reflect upon of what's worked and what hasn't—and the authors here do all that, and more." —From the Foreword by Grady Booch, IBM Fellow

Software architecture—the conceptual glue that holds every phase of a project together for its many stakeholders—is widely recognized as a critical element in modern software development. Practitioners have increasingly discovered that close attention to a software system's architecture pays valuable dividends. Without an architecture that is appropriate for the problem being solved, a project will stumble along or, most likely, fail. Even with a superb architecture, if that architecture is not well understood or well communicated the project is unlikely to succeed.
Documenting Software Architectures, Second Edition, provides the most complete and current guidance, independent of language or notation, on how to capture an architecture in a commonly understandable form. Drawing on their extensive experience, the authors first help you decide what information to document, and then, with guidelines and examples (in various notations, including UML), show you how to express an architecture so that others can successfully build, use, and maintain a system from it. The book features rules for sound documentation, the goals and strategies of documentation, architectural views and styles, documentation for software interfaces and software behavior, and templates for capturing and organizing information to generate a coherent package. New and improved in this second edition:


Coverage of architectural styles such as service-oriented architectures, multi-tier architectures, and data models
Guidance for documentation in an Agile development environment
Deeper treatment of documentation of rationale, reflecting best industrial practices
Improved templates, reflecting years of use and feedback, and more documentation layout options
A new, comprehensive example (available online), featuring documentation of a Web-based service-oriented system
Reference guides for three important architecture documentation languages: UML, AADL, and SySML


Want to learn more information about Documenting Software Architectures: Views and Beyond (2nd Edition)?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Pattern-Oriented Software Architecture Volume 2: Patterns for Concurrent and Networked Objects Review

Average Reviews:

(More customer reviews)Are you looking to buy Pattern-Oriented Software Architecture Volume 2: Patterns for Concurrent and Networked Objects? Here is the right place to find the great deals. we can offer discounts of up to 90% on Pattern-Oriented Software Architecture Volume 2: Patterns for Concurrent and Networked Objects. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Pattern-Oriented Software Architecture Volume 2: Patterns for Concurrent and Networked Objects ReviewThe book consists of three sections: a short introduction that outlines the problem space, a section containing a large collection of patterns, and a short final section that talks about weaving patterns into a pattern language and offers a few speculations as to the future of patterns.
The first section is quite short, but covers the problem space nicely and provides the motivation for what follows. The presentation is greatly helped by a case study for applying patterns to a concurrent web server; this illustrates how individual patterns can be used to solve particular problems and provides a practical perspective for how to make use of what is in the remainder of the book.
The second section constitutes the majority of the book and describes a large collection of network and concurrency patterns. Here is where the real meat of the book can be found, with 17 different patterns plus variants. There is something for everyone here, such as interceptor, reactor, acceptor-connector, etc. The patterns are presented clearly, with ample UML diagrams to support the extensive explanations. What I liked particularly is that the presentation is both complete and fair. For example, the double-checked locking pattern isn't just presented as a panacea for singleton initialization. Instead, you get explicit warnings about memory coherency issues, together with examples for how to deal with them, so you don't go and implement something and then wonder why it doesn't work...
The final section of the book shows how to connect patterns into a pattern language, such that each pattern nicely fits into a larger architectural whole. There is also some speculation as to where patterns might be headed next. (According to the authors, we are nowhere near having exhausted the topic.)
Overall, I was really impressed with this book. The text provides extensive references to existing literature, so if you are interested in learning about a particular topic in more detail, you'll find plenty of material for further reading. And there is an index that actually works (which is a rarity these days).
While the language is lucid, the book is probably not something you want to read in a single sitting. Instead, it's the sort of book you browse through, picking up interesting things as you go, and then referring back to them when you need more detail. (I read the book over a number of weeks, digesting a chapter at a time when it suited me.)
Overall, I highly recommend this book. While much of the content has been published previously, it's difficult to find elsewhere and not as up to date. Here, you get everything in one place, presented in a form that works both for learning and as a reference.
If you are interested in programming distributed systems, don't miss this--there is no other book that covers the ground anywhere near as well!Pattern-Oriented Software Architecture Volume 2: Patterns for Concurrent and Networked Objects OverviewDesigning application and middleware software to run in concurrent and networked environments is a significant challenge to software developers. The patterns catalogued in this second volume of Pattern-Oriented Software Architectures (POSA) form the basis of a pattern language that addresses issues associated with concurrency and networking.The book presents 17 interrelated patterns ranging from idioms through architectural designs. They cover core elements of building concurrent and network systems: service access and configuration, event handling, synchronization,and concurrency. All patterns present extensive examples and known uses in multiple programming languages, including C++, C, and Java.The book can be used to tackle specific software development problems or read from cover to cover to provide a fundamental understanding of the best practices for constructing concurrent and networked applications and middleware.About the AuthorsThis book has been written by the award winning team responsible for the first POSA volume "A System of Patterns", joined in this volume by Douglas C. Schmidt from University of California, Irvine (UCI), USA.Visit our Web Page

Want to learn more information about Pattern-Oriented Software Architecture Volume 2: Patterns for Concurrent and Networked Objects?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Architecting Software Intensive Systems: A Practitioners Guide Review

Average Reviews:

(More customer reviews)Are you looking to buy Architecting Software Intensive Systems: A Practitioners Guide? Here is the right place to find the great deals. we can offer discounts of up to 90% on Architecting Software Intensive Systems: A Practitioners Guide. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Architecting Software Intensive Systems: A Practitioners Guide ReviewThis book does an excellent job of introducing the reader to the soft skills needed to succeed as a software architect.
The book starts by covering the architectural lifecycle. It discusses chaos, dissemination, adaptation, harvest, and sunset. It also discusses external influences that affect the lifecycle such as stakeholders, business models, marketplace, technological environment, and organizational structure.
The book continues on by putting software architecture into context. It shows how it's related to enterprise architecture, system architecture, and detailed software design and the constraints that they place on each other.
The author covers how to interact with stakeholders and manage the architectural drivers that each group of stakeholders places on the architecture. It covers high-level functionality, quality attribute requirements, technical constraints, and business constraints.
This section also covers architectural structures which include structure and perspective, structures and systematic properties, styles and patterns of reasoning framework tactics and quality attributes. The work of an architect is covered in this section and documenting the architectural design which covers UML, technical writing guidance, and document structures.
Section 2 covers the Architectural Centric Design Method (ACDM). The author goes into great detail covering all eight stages. They include Discovering the Architectural Drivers, Establishing Project Scope, Create/Refine the Architecture, Evaluate the Architecture Design, The Go/No -- Go Decision, Experimentation, Production Planning, and Production.
The last section covers transitioning design practices, processes, and methods as well as other design considerations including legacy, designed by selection, and maintenance. The author then covers using the ACDM with software development frameworks which include Waterfall, Extreme Programming, SCRUM, Team Software Process, and RUP and CMMI.
I highly recommend this book to anyone considering getting into software architecture. The book is for architecting software intensive systems but many of the practices found in the book can be applied to building applications. An example of what I mean by applications is Web applications, RIAs, or thick client applications that are not delivered as bundled software releases or any system that is not hardware intensive.
The author does a great job pulling in industry-standard processes that are already in place for example SEI's ATAM and how to apply tactics to quality attributes. This is one of the best architecture books that cover the soft skills necessary to achieve success.Architecting Software Intensive Systems: A Practitioners Guide OverviewArchitectural design is a crucial first step in developing complex software intensive systems. Early design decisions establish the structures necessary for achieving broad systemic properties. However, today's organizations lack synergy between software their development processes and technological methodologies. Providing a thorough treatment of the latest theory and best practices, Architecting Software Intensive Systems: A Practitioner's Guide explains:How and when to design architecturesHow to weave architecture design processes into existing development processesWhat to do with architecture design artifacts once createdThe first section establishes key concepts in architectural design for software intensive systems, including architectural drivers, structures, and fundamental guidance for architectural design. The book goes on to describe the industry tested Architecture Centric Design Method. Each stage of the method is explained and the book provides all of the supporting templates and checklists. The last section discusses practical matters, including how to adopt disciplined architectural design practices into existing organizational development processes. With the principled understanding of design provided by this book, architects can temper their visceral instinct to react and be better prepared to address a broader range of design problems regardless of business context or their domain experience.

Want to learn more information about Architecting Software Intensive Systems: A Practitioners Guide?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Just Enough Software Architecture: A Risk-Driven Approach Review

Average Reviews:

(More customer reviews)Are you looking to buy Just Enough Software Architecture: A Risk-Driven Approach? Here is the right place to find the great deals. we can offer discounts of up to 90% on Just Enough Software Architecture: A Risk-Driven Approach. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Just Enough Software Architecture: A Risk-Driven Approach ReviewThis a broad and deep book on all things software architecture except the architecting process (for process, one recommended read is "Process Software Architecting" by Eeles/Cripps). Several readerships will benefit from "Just Enough Software Architecture":
- As an experienced IT architect, I do not necessarily agree with everything in the book (this does not come as a surprise, as architects have opinions). That said, I certainly learned a lot that I can apply immediately on my projects and some of the more provocative statements challenge me to leave my comfort zone (or at least consider doing so).
- Junior architects can use the book both as a tutorial and as a reference when/while growing in their profession.
- Developers with a "who needs architects" mindset (hopefully) will understand architects and modelers much better after having read this book, and appreciate the value of archtecture.
Things I liked in particular:
- Overall vision and message of pragmatism sent
- The risk-driven approach increases chances to get accepted both in agile development and in more traditional architecture communities
- There is a lot of practical advice e.g. in Chapters 10, 11 and 15
- The author is in command of a large body of relevant related work (both industra and academia) and puts them in perspective adequately
- Editorial quality: structure, figures, command of the English language (some words and expressions a bit be hard to comprehend for non-native speaker)
Some room for improvements (2nd edition?):
- Not all metaphors and analogies work internationally, e.g. not all IT people are sports fans that follow baseball or know what a rookie is
- The connection between parts 1 and 2 could be a bit stronger, even if loose coupling generally is a good thing; e.g., some more backward references
In summary, I'd say Just Enough Software Architecture is a highly recommended read for every architect in touch with development reality and every developer with a desire to build complex systems that will stand the test of time.Just Enough Software Architecture: A Risk-Driven Approach OverviewThis is a practical guide for software developers, and different than other software architecture books. Here's why:
It teaches risk-driven architecting. There is no need for meticulous designs when risks are small, nor any excuse for sloppy designs when risks threaten your success. This book describes a way to do just enough architecture. It avoids the one-size-fits-all process tar pit with advice on how to tune your design effort based on the risks you face.
It democratizes architecture. This book seeks to make architecture relevant to all software developers. Developers need to understand how to use constraints as guiderails that ensure desired outcomes, and how seemingly small changes can affect a system's properties.
It cultivates declarative knowledge. There is a difference between being able to hit a ball and knowing why you are able to hit it, what psychologists refer to as procedural knowledge versus declarative knowledge. This book will make you more aware of what you have been doing and provide names for the concepts.
It emphasizes the engineering. This book focuses on the technical parts of software development and what developers do to ensure the system works not job titles or processes. It shows you how to build models and analyze architectures so that you can make principled design tradeoffs. It describes the techniques software designers use to reason about medium to large sized problems and points out where you can learn specialized techniques in more detail.
It provides practical advice. Software design decisions influence the architecture and vice versa. The approach in this book embraces drill-down/pop-up behavior by describing models that have various levels of abstraction, from architecture to data structure design.

Want to learn more information about Just Enough Software Architecture: A Risk-Driven Approach?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...

Pattern Oriented Software Architecture Volume 5: On Patterns and Pattern Languages Review

Average Reviews:

(More customer reviews)Are you looking to buy Pattern Oriented Software Architecture Volume 5: On Patterns and Pattern Languages? Here is the right place to find the great deals. we can offer discounts of up to 90% on Pattern Oriented Software Architecture Volume 5: On Patterns and Pattern Languages. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Pattern Oriented Software Architecture Volume 5: On Patterns and Pattern Languages ReviewWe knew something about patterns and the relationships between patterns, but, this book addresses the concept of pattern language more deeply by classifying and naming those relationships, such as Complements, Compounds, and Sequences. These idea are covered in part II of the book, after talking about single patterns in part I, which I think we know more about it from the literature.
The most interesting part, from my point of view, is part III, which relates the concepts of pattern language to the well-known jargon in theory of automation. I like the analogy of patterns as words and pattern sequences as sentences, and I think we can borrow some idea of compilers to build tools that help designers that are using a pattern language. This is what I'm working as my research right now.
Finally, the book could be more compact, specially for the first two parts. But, considering the fact that the authors wanted to wrap up their ideas presented in the previous four volumes, it had to be wordy.Pattern Oriented Software Architecture Volume 5: On Patterns and Pattern Languages Overview
Software patterns have revolutionized the way developers think about how software is designed, built, and documented, and this unique book offers an in-depth look of what patterns are, what they are not, and how to use them successfully
The only book to attempt to develop a comprehensive language that integrates patterns from key literature, it also serves as a reference manual for all pattern-oriented software architecture (POSA) patterns
Addresses the question of what a pattern language is and compares various pattern paradigms
Developers and programmers operating in an object-oriented environment will find this book to be an invaluable resource


Want to learn more information about Pattern Oriented Software Architecture Volume 5: On Patterns and Pattern Languages?

>> Click Here to See All Customer Reviews & Ratings Now

Read More...