CMU CS 15-675 Architectures for Software Systems Spring 1997

Problem Types and Problem Frames

Garlan & Shaw Questions on Readings for Lecture 3

Due: Monday, January 20, 1997

The papers:

[Jac95]: Software Requirements and Specifications, sections: Polya, Phenomena, Problem Context, Domains, Application Domain, Machine, Problem Frames, Domain Interactions, Context Diagrams, Frame Diagrams, Simple IS Frame, Simple Control Frame, Connection Frame, Workpiece Frame, JSP Frame

[Pol73]: How to Solve It, pp.xvi-xvii, 33-36

[Rec92]: The Art of Systems Architecting

Hints:

These readings help you think about the kind of problem you are solving; this is a precursor of selecting an architecture to solve it. They have two common themes: (1) It is essential to discriminate among different kinds of problems and solutions, and hence to make informed choices among solution strategies. (2) The most important design decisions deal with overall system structure--not with, for example, programming details.

You may find it helpful to read the sections of Jac95 in roughly the order given.

Pay attention to the kind of information the authors regard as most important. Also pay attention to the specific problem and solution structures they identify and the methodological implications. During the semester, we will often ask you to identify the problem frame of the problem for which you are proposing an architecture.

Questions:

1. What two kinds of problems does Polya identify?

2. What are the principal parts of a problem frame?

3. What is the most significant difference between the real world domain of the simple IS frame and the controlled domain of the simple control frame?

4. What are four methods commonly used by architects? Which is particularly characteristic?

Email the Current Maintainer

Modified: 01/21/97