Migration of a Chosen Architectural Pattern to Service Oriented ...

Chapter 5. Guidelines 128Software Architecture DocumentationThe overview of the architecture of TRWAM project is presented in the figure5.16: Content (according to available documentation) of particular elements ofthe architecture is following:1. View – contains packages representing graphical part of the system. PackageAssets (SrodkiTrwale) is responsible for proper representation of assets onGraphical Usage Interface. Package Commons (Wspolne) contains classesresponsible for common parts of Graphical User Interface.2. Controller – here also two packages are available. Package Assets (SrodkiTrwale)contains classes associated with service of assets. Package Commons(Wspolne) contains classes common for the whole application like classesmanaging printing.3. Model – represents classes responsible for persistence of data in database.Package Assets (SrodkiTrwale) contains classes responsible for persistence ofassets. Package Commons (Wspolne) contains classes used by other classes.Package Data (Dane) contains classes persisted in database.4. javax.swing – this is a core package of Java language containing classesresponsible for displaying GUI.5. java.sql – this is a core package of Java language containing classes responsiblefor establishing connection to a database. The package allows sendingdata to previously connected database.6. javax.print – this is a core package of Java language. The package providesprint-relate functionality that allows discovering and selecting printers, setpage format and submit documents to selected printer.Rules and Limitations The rules and limitations presented in TRWAM projectare divided into two types:1. Business rules – document contain sixteen business rules. An example rule:An asset can be lent only if the manager of unit gave permission.2. Domain constrains – document presents only five domain constrains. Anexample constraint: System can use both PLN and Euro currency.GlossaryThe glossary defines basic vocabulary used to describe domain of the system.