GS Packages Standard

This page contains the design document for an enhancement or feature. The design should be considered a work in progress and may not represent the final design. As this is a collaborative design, contributions and participation from other developers and users is encouraged. Use the discussion page for providing comments and suggestions.

---

[edit] Notes on Packages

• Packages are simply a graphical grouping of functionality.
• They combine multiple Actors and Use Cases that have some comonalities.
• Packages can also be called Systems or Subsystems.
• Packages do not have to define internal associations between different Use Cases.

Example:

!!Replace graphic with GS example!!

• The actors in this diagram are:
  • WaitStaff
  • Patron
  • Cashier
  • Chef
• The combined Use Cases for all the actors are:
  • Order Food
  • Serve Food
  • Eat Food
  • Drink Wine
  • Pay For Food

Now, depending on how the developer was intending on implementing this in code, one could easily say that sense all the actors 'is a' Person, then they all need to 'Eat Food.' If this food is only the food served at this resteraunt, then perhaps all the actors do not have to 'Eat Food.' A simple Diagram like this has already helped to identify ambiguity in a design!

"Who needs Echelon when you've got web search engines?" - Marcus Sachs

All trademarks referenced herein are the properties of their respective owners. This site is not sponsored, endorsed, or run by the U.S. Government.