What is it possible and not possible to say about data flow by looking at a view in the module viewtype? What about control flow? What can you say about which modules interact with which other modules?
Which properties of a module might you think of as worthy of having special notational conventions to express them, and why? For example, you might want to color a commercial-off-the-shelf (COTS) module differently from modules developed in-house.
The depends-on relation among modules is very general. What specific types of dependencies might be reflected in a style in the module viewtype?
A primary property of a module is its set of responsibilities. How do a module's responsibilities differ from the requirements that it must satisfy?
When documenting a particular system, you might wish to combine modules into an aggregate, to market them as a combined package, for example. Would this package itself be a module? That is, are all aggregates of modules themselves modules?