About: Architectural pattern is a research topic. Over the lifetime, 4118 publications have been published within this topic receiving 113612 citations.
TL;DR: The book is an introduction to the idea of design patterns in software engineering, and a catalog of twenty-three common patterns, which most experienced OOP designers will find out they've known about patterns all along.
Abstract: The book is an introduction to the idea of design patterns in software engineering, and a catalog of twenty-three common patterns. The nice thing is, most experienced OOP designers will find out they've known about patterns all along. It's just that they've never considered them as such, or tried to centralize the idea behind a given pattern so that it will be easily reusable.
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.
TL;DR: This paper provides an introduction to the emerging field of software architecture by considering a number of common architectural styles upon which many systems are currently based and showing how different styles can be combined in a single design.
Abstract: As the size of software systems increases, the algorithms and data structures of the computation no longer constitute the major design problems. When systems are constructed from many components, the organization of the overall system -- the software architecture -- presents a new set of design problems. This level of design has been addressed in a number of ways including informal diagrams and descriptive terms, module interconnection languages, templates and frameworks for systems that serve the needs of specific domains, and formal models of component integration mechanisms. In this paper we provide an introduction to the emerging field of software architecture. We begin by considering a number of common architectural styles upon which many systems are currently based and show how different styles can be combined in a single design. Then we present six case studies to illustrate how architectural representations can improve our understanding of complex software systems. Finally, we survey some of the outstanding problems in the field, and consider a few of the promising research directions.
TL;DR: This chapter discusses Software Architecture and Product Lines and the design of Software Architectures and its transformation into Family-Based System Development.
Abstract: 1. Software Architecture and Product Lines. I. THE DESIGNING OF SOFTWARE ARCHITECTURES. 2. Design of Software Architectures. 3. Software Architectural Design: Case Studies. 4. Functionality-Based Architectural Design. 5. Assessing Software Architectures. 6. Transformation of Software Architectures. II. SOFTWARE PRODUCT LINES. 7. Software Product Lines: An Introduction. 8. Software Product Lines: Case Studies. 9. Designing a Product-Line Architecture. 10. Developing Components: Traditional. 11. Developing Components: Object-Oriented Frameworks. 12. Family-Based System Development. 13. Evolving Product-Line Assets. 14. Organizing for Software Product Lines. 15. Industrial Experiences. References. Index.