Summary Checklist

  • Modules pertain to the way in which a system's software is decomposed into manageable units of functionality, which is one of the important forms of system structure.
  • Modules are related to one another by forms of is-part-of, depends-on, and is-a relations.
  • A module view provides a blueprint for the source code.
  • Expect to have at least one module view in your documentation package.
  • You should not depend on a module name to define the functional duties of the module: use the responsibility property.
  • Use an interface document to establish a module's role in the system.
  • Module views are commonly mapped to views of the component and connector viewtype. Module implementation units map to runtime components.

Documenting Software Architectures(c) Views and Beyond
Documenting Software Architectures: Views and Beyond
ISBN: 0201703726
EAN: 2147483647
Year: 2005
Pages: 152
Simiral book on Amazon © 2008-2017.
If you may any questions please contact us: