Days of …

Just another rants and opinions weblog

Package Diagram Guidelines

  1. Create class package diagrams to logically organize your design.

  2. Create UML component diagrams to physically organize your design.

  3. Place inheriting packages below base packages.

  4. Vertically layer class package diagrams.

  5. Create use case package diagrams to organize your requirements.

  6. Include actors on use case package diagrams.

  7. Horizontally arrange use case package diagrams.

  8. Give packages simple, descriptive names.

  9. Make packages cohesive.

  10. Indicate architectural layers with stereotypes on packages.

  11. Avoid cyclic dependencies between packages.

  12. Reflect internal relationships in package dependencies.

]]>

One Response to Package Diagram Guidelines

  1. The Science of Packages

    Everyone knows about packages, but do you know of the science of packages? There are quite a few principles that deal with maintainability and reusability. Read on to learn about them, as explained by Robert C. Martin.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

blog comments powered by Disqus