Topic
Software architecture
About: Software architecture is a research topic. Over the lifetime, 19929 publications have been published within this topic receiving 351123 citations.
Papers published on a yearly basis
1 / 2
Papers
Book•
1 Jan 1997TL;DR: This second edition of this book reflects the new developments in the field and new understanding of the important underpinnings of software architecture with new case studies and the new understanding both through new chapters and through additions to and elaboration of the existing chapters.
Abstract: From the Book:
Our goals for the first edition were threefold. First, we wanted to show through authentic case studies actual examples of software architectures solving real-world problems. Second, we wanted to establish and show the strong connection between an architecture and an organization's business goals. And third, we wanted to explain the importance of software architecture in achieving the quality goals for a system.
Our goals for this second edition are the same, but the passage of time since the writing of the first edition has brought new developments in the field and new understanding of the important underpinnings of software architecture. We reflect the new developments with new case studies and the new understanding both through new chapters and through additions to and elaboration of the existing chapters.
Architecture analysis, design, reconstruction, and documentation have all had major developments since the first edition. Architecture analysis has developed into a mature field with industrial-strength methods. This is reflected by a new chapter about the architecture tradeoff analysis method (ATAM). The ATAM has been adopted by industrial organizations as a technique for evaluating their software architectures.
Architecture design has also had major developments since the first edition. The capturing of quality requirements, the achievement of those requirements through small-scale and large-scale architectural approaches (tactics and patterns, respectively), and a design method that reflects knowledge of how to achieve qualities are all captured in various chapters. Three new chapters treat understanding quality requirements, achieving qualities, and theattribute driven design (ADD) method, respectively.
Architecture reconstruction or reverse engineering is an essential activity for capturing undocumented architectures. It can be used as a portion of a design project, an analysis project, or to provide input into a decision process to determine what to use as a basis for reconstructing an existing system. In the first edition, we briefly mentioned a tool set (Dali) and its uses in the re-engineering context; in in this edition the topic merits its own chapter.
Documenting software architectures is another topic that has matured considerably in the recent past. When the first edition was published, the Unified Modeling Language (UML) was just arriving on the scene. Now it is firmly entrenched, a reality reflected by all-new diagrams. But more important, an understanding of what kind of information to capture about an architecture, beyond what notation to use, has emerged. A new chapter covers architecture documentation.
The understanding of the application of software architecture to enable organizations to efficiently produce a variety of systems based on a single architecture is summarized in a totally rewritten chapter on software product lines. The chapter reinforces the link between architecture and an organization's business goals, as product lines, based around a software architecture, can enable order-of-magnitude improvements in cost, quality, and time to market.
In addition to the architectural developments, the technology for constructing distributed and Web-based systems has become prominent in today's economy. We reflect this trend by updating the World Wide Web chapter, by using Web-based examples for the ATAM chapter and the chapter on building systems from components, by replacing the CORBA case study with one on Enterprise JavaBeans (EJB), and by introducing a case study on a wireless EJB system designed to support wearable computers for maintenance technicians.
Finally, we have added a chapter that looks more closely at the financial aspects of architectures. There we introduce a method--the CBAM--for basing architectural decisions on economic criteria, in addition to the technical criteria that we had focused on previously.
As in the first edition, we use the architecture business cycle as a unifying motif and all of the case studies are described in terms of the quality goals that motivated the system design and how the architecture for the system achieves those quality goals.
In this edition, as in the first, we were very aware that our primary audience is practitioners, so we focus on presenting material that has been found useful in many industrial applications, as well as what we expect practice to be in the near future.
We hope that you enjoy reading it at least as much as we enjoyed writing it.
0321154959P12162002
6,072 citations
TL;DR: The development of a set of software applications that use the Data Model and its associated libraries, thus validating the approach and providing a pipeline for high‐throughput analysis of NMR data.
Abstract: To address data management and data exchange problems in the nuclear magnetic resonance (NMR) community, the Collaborative Computing Project for the NMR community (CCPN) created a "Data Model" that describes all the different types of information needed in an NMR structural study, from molecular structure and NMR parameters to coordinates. This paper describes the development of a set of software applications that use the Data Model and its associated libraries, thus validating the approach. These applications are freely available and provide a pipeline for high-throughput analysis of NMR data. Three programs work directly with the Data Model: CcpNmr Analysis, an entirely new analysis and interactive display program, the CcpNmr FormatConverter, which allows transfer of data from programs commonly used in NMR to and from the Data Model, and the CLOUDS software for automated structure calculation and assignment (Carnegie Mellon University), which was rewritten to interact directly with the Data Model. The ARIA 2.0 software for structure calculation (Institut Pasteur) and the QUEEN program for validation of restraints (University of Nijmegen) were extended to provide conversion of their data to the Data Model. During these developments the Data Model has been thoroughly tested and used, demonstrating that applications can successfully exchange data via the Data Model. The software architecture developed by CCPN is now ready for new developments, such as integration with additional software applications and extensions of the Data Model into other areas of research.
3,379 citations
Book•
1 Jan 1996TL;DR: Patterns.
Abstract: Patterns. Architectural Patterns. Design Patterns. Idioms. Pattern Systems. Patterns and Software Architecture. The Pattern Community. Where Will Patterns Go? Notations. Glossary. References. Index of Patterns.
2,988 citations
Book•
1 Jan 2006
TL;DR: Leading the way to the true service-oriented enterprise, Thomas Erl demystifies the complexities of the open WS-I standards with detailed practical discussions and case studies.
Abstract: "Service Oriented Architecture is a hot, but often misunderstood topic in IT today. Thomas articulately describes the concepts, specifications, and standards behind service orientation and Web Services. For enterprises adopting SOA, there is detailed advice for service-oriented analysis, planning, and design. This book is a must read!"i¾Alex Lynch, Principal Consultant, Microsoft Enterprise Services"One primary objective of applying SOA in design is to provide business value to the solutions we build. Understanding the right approach to analyzing, designing, and developing service-oriented solutions is critical. Thomas has done a great job of demystifying SOA in practical terms with his book."i¾Rick Weaver, IBM Senior Consulting Certified SW I/T Specialist"A pragmatic guide to SOA principles, strategy, and best practices that distills the hype into a general framework for approaching SOA adoption in complex enterprise environments." i¾Sameer Tyagi, Senior Staff Engineer, Sun Microsystems"A very timely and much needed contribution to a rapidly emerging field. Through clarifying the principles and nuances of this space, the author provides a comprehensive treatment of critical key aspects of SOA from analysis and planning to standards ranging from WS-specifications to BPEL. I'll be recommending this book to both clients and peers who are planning on embracing SOA principles."i¾Ravi Palepu, Senior Field Architect, Rogue Wave Software"Finally, an SOA book based on real implementation experience in production environments. Too many SOA books get lost in the technical details of Web Services standards, or simply repeat vendor hype. This book covers the really hard parts: the complex process of planning, designing and implementing service-oriented architectures that meet organizational goals. It is an essential companion to any software developer, architect, or project manager implementingi¾or thinking about implementingi¾a service-oriented architecture." i¾Priscilla Walmsley, Managing Director of Datypic"Thomas Erl's Service-Oriented Architecture: Concepts, Technology, and Design is as good an introduction to service-oriented architectures as one could wish for. In a single volume, it covers the entire topic, from theory to real-world use to technical details. The examples are superb and the writing is wonderfully clear." i¾Ronald Bourret, Author, "XML and Databases""Finally an SOA book which gets to the point with real world answers and examples. Erl guides you on a real world SOA journey. From architecture design to industry standards, this book is well written and can be easily referenced for everyday use. When embarking on your own service orientated adventures, this is the book you want in your bag." i¾Clark Sell, Vice President, CSell Incorporated"Organizations struggling to evolve existing service-oriented solutions beyond simple Web Services now have an expert resource available. Leading the way to the true service-oriented enterprise, Thomas Erl demystifies the complexities of the open WS-I standards with detailed practical discussions and case studies. Erl's depth and clarity makes this work a superb complement to his Field Guide." i¾Kevin P. Davis, PhD., Software Architect"This book is an excellent guide for architects, developers, and managers who are already working with or are considering developing Web Services or Service-Oriented Architecture solutions. The book is divided into four sections. In the first section the fundamental technologies of XML, Web Services and Service-Oriented Architectures are described in detail with attention given to emerging standards. The book is well written and very thorough in its coverage of the subject. I recommend this book highly to anyone interested in enterprise level service architectures."i¾Adam Hocek, President and CTO, Broadstrokes, Inc.Additional praise quotes are published at: www.soabooks.com/reviews.aspThe foremost "how-to" guide to SOAService-Oriented Architecture (SOA) is at the heart of a revolutionary computing platform that is being adopted world-wide and has earned the support of every major software provider. In Service-Oriented Architecture: Concepts, Technology, and Design, Thomas Erl presents the first end-to-end tutorial that provides step-by-step instructions for modeling and designing service-oriented solutions from the ground up.Erl uses more than 125 case study examples and over 300 diagrams to illuminate the most important facets of building SOA platforms: goals, obstacles, concepts, technologies, standards, delivery strategies, and processes for analysis and design.His book's broad coverage includes Detailed step-by-step processes for service-oriented analysis and service-oriented design An in-depth exploration of service-orientation as a distinct design paradigm, including a comparison to object-orientation A comprehensive study of SOA support in .NET and J2EE development and runtime platforms Descriptions of over a dozen key Web services technologies and WS-* specifications, including explanations of how they interrelate and how they are positioned within SOA The use of "In Plain English" sections, which describe complex concepts through non-technical analogies Guidelines for service-oriented business modeling and the creation of specialized service abstraction layers A study contrasting past architectures with SOA and reviewing current industry influences Project planning and the comparison of different SOA delivery strategies The goal of this book is to help you attain a solid understanding of what constitutes contemporary SOA along with step-by-step guidance for realizing its successful implementation.About the Web SitesErl's Service-Oriented Architecture books are supported by two Web sites. http://www.soabooks.com provides a variety of content resources and http://www.soaspecs.com supplies a descriptive portal to referenced specifications. i¾ © Copyright Pearson Education. All rights reserved.
2,668 citations
TL;DR: The 4+1 View Model organizes a description of a software architecture using five concurrent views, each of which addresses a specific set of concerns.
Abstract: The 4+1 View Model organizes a description of a software architecture using five concurrent views, each of which addresses a specific set of concerns. Architects capture their design decisions in four views and use the fifth view to illustrate and validate them. The logical view describes the design's object model when an object-oriented design method is used. To design an application that is very data driven, you can use an alternative approach to develop some other form of logical view, such as an entity-relationship diagram. The process view describes the design's concurrency and synchronization aspects. The physical view describes the mapping of the software onto the hardware and reflects its distributed aspect. The development view describes the software's static organization in its development environment. >
2,394 citations
Related Topics (5)
Performance Metrics
| Year | Papers |
|---|---|
| 2026 | 1 |
| 2025 | 26 |
| 2024 | 63 |
| 2023 | 71 |
| 2022 | 146 |
| 2021 | 400 |