book

Software Architecture and Design Illuminated

by Kai Qian, Xiang Fu, Lixin Tao, Chong-wei Xu

February 2009

Intermediate to advanced

388 pages

9h 1m

English

Jones & Bartlett Learning

Read now

Unlock full access

Cover Page
Title Page
Copyright Page
Contents
Preface
Chapter 1 - Introduction to Software Architecture
1.1 - Overview1.2 - Software Architecture: Bridging Requirements and Implementation1.3 - Architecture Styles1.4 - Quality Attributes1.5 - Software Architecture Design Guidelines1.6 - Summary1.7 - Self-Review Questions
Chapter 2 - Software Architecture Design Space
2.1 - Overview2.2 - Types of Software Structures2.2.1 - Software Static Structure2.2.2 - Software Runtime Structure2.2.3 - Software Management Structure2.3 - Software Elements2.4 - Software Connectors2.5 - An Agile Approach to Software Architecture Design2.6 - Summary2.7 - Self-Review Questions2.8 - Exercises2.9 - Design Exercises
Chapter 3 - Models for Software Architecture
3.1 - Overview3.2 - UML for Software Architecture3.2.1 - Structural Diagrams3.2.2 - Behavioral Diagrams3.3 - Architecture View Models3.3.1 - The Scenario View3.3.2 - The Logical or Conceptual View3.3.3 - The Development or Module View3.3.4 - The Process View3.3.5 - The Physical View3.3.6 - The User Interface View3.4 - Architecture Description Languages (ADL)3.5 - Summary3.6 - Self-Review Questions3.7 - Exercises3.8 - Design Exercises3.9 - Challenge Exercises
Chapter 4 - Object-Oriented Paradigm
4.1 - Overview4.2 - Introducing the Object-Oriented Paradigm4.2.1 - Classes and Objects4.2.2 - Relationships4.3 - OO Analysis4.3.1 - Step 1: Design of a UML use Case Diagram4.3.2 - Step 2: Develop an Analysis Class Diagram via Noun Extraction4.4 - Oo Design4.4.1 - Step 1: Identify Classes—CRC Card4.4.2 - Step 2: Construct an Interaction Diagram4.4.3 - Step 3: Build a State Machine Diagram4.4.4 - Step 4: Class Specification4.5 - Design Principles4.5.1 - Principle of Decoupling4.5.2 - Ensuring Cohesion4.5.3 - Open-Closed Principle4.6 - Summary4.7 - Self-Review Questions4.8 - Exercises4.9 - Design Exercises4.10 - Challenge Exercises
Chapter 5 - Data Flow Architectures
5.1 - Overview5.2 - Batch Sequential5.3 - Pipe and Filter Architecture5.4 - Process Control Architecture5.5 - Summary5.6 - Self-Review Questions5.7 - Exercises5.8 - Design Exercises5.9 - Challenge Exercises

Chapter 6 - Data-Centered Software Architecture
6.1 - Overview6.2 - Repository Architecture Style6.3 - Blackboard Architecture Style6.4 - Summary6.5 - Self-Review Questions6.6 - Exercises6.7 - Design Exercises6.8 - Challenge Exercise
Chapter 7 - Hierarchical Architecture
7.1 - Overview7.2 - Main-Subroutine7.3 - Master-Slave7.4 - Layered7.5 - Virtual Machine7.6 - Summary7.7 - Self-Review Questions7.8 - Exercises7.9 - Design Exercises7.10 - Challenge Exercises
Chapter 8 - Implicit Asynchronous Communication Software Architecture
8.1 - Overview8.2 - Nonbuffered Event-Based Implicit Invocations8.3 - Buffered Message-Based Software Architecture8.4 - Summary8.5 - Self-Review Questions8.6 - Exercises8.7 - Design Exercises8.8 - Challenge Exercise
Chapter 9 - Interaction-Oriented Software Architectures
9.1 - Overview9.2 - Model-View-Controller (MVC)9.2.1 - MVC-I9.2.2 - MVC-II9.3 - Presentation-Abstraction-Control (PAC)9.4 - Summary9.5 - Self-Review Questions9.6 - Exercises9.7 - Design Exercises9.8 - Challenge Exercises
Chapter 10 - Distributed Architecture
10.1 - Overview10.2 - Client-Server10.3 - Multi-tiers10.4 - Broker Architecture Style10.4.1 - Broker Implementation in the Common Object Request Broker Architecture (CORBA)10.4.2 - Message Broker Architecture10.5 - Service-Oriented Architecture (SOA)10.5.1 - SOA Implementation in Web Services10.5.2 - SOA Implementation for Grid Service Computing10.6 - Summary10.7 - Self-Review Questions10.8 - Exercises10.9 - Design Exercises10.10 - Challenge Exercise
Chapter 11 - Component-Based Software Architecture
11.1 - Overview11.2 - What is a Component?11.3 - Principles of Component-Based Design11.3.1 - Connections of Components11.3.2 - Component-Level Design Guidelines11.4 - Summary11.5 - Self-Review Questions11.6 - Exercises11.7 - Design Exercises11.8 - Challenge Exercises
Chapter 12 - Heterogeneous Architecture
12.1 - Overview12.2 - Methodology of Architecture Decision12.3 - Quality Attributes12.4 - Selection of Architecture Styles12.5 - Evaluation of Architecture Designs12.6 - Case Study: Online Computer Vendor12.6.1 - Overall Architecture Design of OCVS12.6.2 - Architecture Design of Order Processing Component12.6.3 - Architecture Design of Inventory Management12.6.4 - Architecture Design of Manufacture and Shipping Component12.7 - Summary12.8 - Self-Review Questions12.9 - Exercises12.10 - Design Exercises12.11 - Challenge Exercises
Chapter 13 - Architecture of User Interfaces
13.1 - Overview13.2 - Evolution of User Interfaces13.3 - Look and Feel (Syntax) of User Interfaces13.3.1 - Static Style of User Interfaces13.3.2 - Dynamic Style of User Interfaces13.3.3 - Customizable Style of User Interfaces13.3.4 - No User Interfaces13.4 - Usability (Semantics) of User Interfaces13.5 - Design Considerations of User Interfaces13.6 - Enabling Technology13.6.1 - Containers13.6.2 - Layout Managers13.6.3 - Major UI Components13.6.4 - Event Listeners13.6.5 - A Case Study13.7 - Direct Manipulation13.8 - Evaluation of User Interfaces13.9 - Summary13.10 - Self-Review Questions13.11 - Exercises13.12 - Challenge Exercises
Chapter 14 - Product Line Architectures
14.1 - Overview14.2 - Introduction and Motivation14.2.1 - Software Reuse and Product Lines14.2.2 - Methodologies, Processes, and Tools14.3 - Product Line Engineering: Design-for-Reuse14.4 - Product Development: Design-with-Reuse14.4.1 - Product Line Analysis: Domain Models14.4.2 - Product Line Design: Design-for-Commonality and Control-of-Variability14.4.3 - Product Line Implementation: Configuration Model and Componentbase14.4.4 - Heuristics14.4.5 - Software Technology for Systematic Reuse14.5 - Sample Product Line Analysis14.5.1 - Why: Mission and Strategic Goals14.5.2 - What: Product Families14.5.3 - How: Asset Base14.6 - Ultra-Large-Scale Systems14.7 - Summary14.8 - Self-Review Questions14.9 - Exercises14.10 - Design Exercises
Index

Content preview from Software Architecture and Design Illuminated

Product Line Architectures

Objectives of this Chapter

• Advance the concept of systematic reuse and its particular implementation using product lines

• Discuss design considerations for product line architectures and component bases

• Demonstrate the enabling technology

14.1 Overview

Today, organizations are emphasizing component-based development (CBD) to achieve the elusive goal of systematic reuse. The idea of systematic reuse has gained success in commercial products, creating a plethora of technological solutions to build software out of “reusable” components such as OMG's CORBA, Microsoft's COM and .NET, and Sun's JavaBeans, mainly ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 9780763754204

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages