Software Architecture in Practice Chapter 2: What Is Software Architecture? Why Is It Important?

9/1/2000


Click here to start


Table of Contents

Software Architecture in Practice Chapter 2: What Is Software Architecture? Why Is It Important?

Lecture Objectives

What Is Software Architecture?

Some Usual Descriptions of Architecture

What’s Wrong with “Components and Connectors?”

What’s Wrong with “Overall Structure?”

What’s Wrong with the Diagram?

The Definition of Software Architecture

Implications of Our Definition -1

Implications of Our Definition -2

Implications of Our Definition -3

Implications of Our Definition -4

Implications of Our Definition -5

Related Concepts

Reference Model

Architectural Style -1

Architectural Style -2

Reference Architecture -1

Reference Architecture -2

Reference Architecture -3

Why Is Architecture Important? (Technical Aspects)

Communication Vehicle

Result of Early Design Decisions -1

Result of Early Design Decisions -2

Result of Early Design Decisions -3

Result of Early Design Decisions -4

Result of Early Design Decisions -5

Result of Early Design Decisions -6

Result of Early Design Decisions -7

Reusable Model -1

Reusable Model -2

Reusable Model -3

Reusable Model -4

Reusable Model -5

Architectural Structures -1

Architectural Structures -2

Module Structure

Process Structure

Uses Structure

Calls Structure

Data Flow Structure

Class Structure

Physical Structure

What Are Structures Used For?

Architectural Structures Summary

Lecture Summary

Discussion Questions -1

Discussion Questions -2

Author: jtomal