|
Documenting Software Architectures: Views and Beyond
By
Paul Clements, Felix Bachmann, Len Bass, David Garlan, James Ivers, Reed Little, Robert Nord, Judith Stafford
|
Table of Contents |
|
Chapter 2.
Styles of the Module Viewtype |
2.6 Discussion Questions
| 1: | Can you think of a system that cannot be described using a layered view? If a system is not layered, what would this say about its allowed-to-use relation?
|
| 2: | How does a UML class diagram relate to the styles given in this chapter? Does that diagram show decomposition, uses, generalization, or another combination? (Hint: We'll discuss this in some detail in Section 11.2.)
|
| 3: | We consciously chose the term generalization to avoid the multiple meanings that the term inheritance has acquired. Find two or three of these meanings, compare them, and discuss how they are both a kind of generalization. (Hint: You may wish to consult books by Booch and Rumbaugh, respectively.)
|
| 4: | Suppose that a portion of a system is generated with, for example, a user interface builder tool. Using one or more views in the module viewtype, how would you show the tool, the input to the tool�the user interface specification�and the output from the tool?
|
|
|
No comments:
Post a Comment