Page History

__NOTOC__

• The system used as an example in this architecture document is an adapted version of the Adventure Builder Reference application, which was developed in the context of the Java BluePrints program at Sun Microsystems. However, the architecture documented here does not reflect exactly the implementation provided by Sun.
  • To make it a more interesting and realistic example of an SOA solution, we made several assumptions about the business context and requirements of the system.
  • We have also added a few elements and relations that don't exist in Sun's implementation, and omitted others.

...

• Any diagram shows one (of many) possible depiction of the design. If you have suggestions on how to improve any of the diagrams, please let us know.

• Each view has a context diagram subsection. The purpose of the context diagram is to show what is in scope and what is external to the system (or the part of the system shown in that view). Instead of a diagram, this subsection may contain:
  • a pointer to a context diagram in another view in case two views share the same context
  • "N/A" in case:
    • a context diagram is deemed unnecessary for that view (example)
    • the primary presentation already explicitly identifies the external elements via a color coding (example)
    • the primary presentation explicitly shows the boundary of the system (example)

...