Architectural Design & Patterns

According to Shaw & Garlan (1996), software architecture defines a system in terms of:

Architecture is concerned with which side of interfaces?

Which is NOT one of the three advantages of explicitly designing and documenting architecture?

In design by decomposition, the process is repeated until:

Architectural design is which stage of the software design process?

In the Pipe and Filter pattern, what is a 'filter'?

The Pipe and Filter architecture is described as NOT really suitable for:

A compiler processes source code through a fixed sequence of transformations where each stage's output feeds the next. Which architectural pattern best fits?

In a layered architecture, each layer relies on the services of:

Which three elements make up a Client-Server architecture?

Private implementation details of an element are considered part of the architecture.

Architectural patterns were first introduced in the 90s under the name 'architectural styles'.

Software design translates requirements into a 'blueprint' for constructing the software.

Non-functional requirements have little influence on the choice of architecture.

An architectural pattern should include information about when it is and is not useful.

In the Pipe and Filter pattern, the output of each element is the input of the next.

In MVC, the Model is responsible for displaying information to the user.

In the Repository architecture, components interact through the repository only.

Client-Server architecture can only be implemented across multiple physical computers.

In a layered architecture, changing a layer's interface affects only the adjacent layer.

Match each MVC component with its responsibility.

Match each Pipe and Filter term with its role.

Match each architectural pattern with its key idea.

Match each of the four common layers with its alternate name.

Match each advantage with the architecture that provides it.