The Utility of Model Problems
[Prev]
[Up]
[Top]
Model problems for software architecture should help us focus on specific
architectural issues. Such issues include
- Describing system organizations, and describing specific kinds of system
organization (architectural styles)
- Distinguishing among templates, instances, and invocations
- Distinguishing among different kinds of system organization -- not only
structural differences, but the implications of those differences
- Selecting among different architectural alternatives
- Using different models concurrently, or at different refinements of a
design; establishing consistency among such different views
- Defining families of systems
- Defining families, or styles, of architecture
- Describing dynamic behavior of systems with fixed structure and describing
dynamic changes in system structure
- Measuring, evaluating, or testing properties of systems such as overall
performance, reliability, or security
- Measuring, evalutaing, or testing properties of designs such as ease of
extension or subsetting
Different problems may, of course, be selected in response to different
issues. We have not tried to make the problems independent or orthogonal.
It's fine if they overlap, but as the set is refined, each should include a
description of the specific issues it helps to clarify.
[Prev]
[Up]
[Top]
Updated Halloween 95 by
Mary Shaw
Comments to maintainer