Relationship Between Classes Diagrams

Table of Contents

Page
Table Of Contents
I. Relationship Between Classes Diagrams / 2 - 4
1. Account Management / 3
2. Document Management / 4
II. Data Access Layer/Database Model / 5 - 6
1. DAL/DB Model Diagram / 6
III. Sequence Diagrams / 7 - 15
1. Account Management / 8 - 12
a. Login / 8
b. Create New Account / 9
c. Manage Account / 10
d. Manage User Account / 11
e. Logout / 12
2. Document Management / 13 - 15
a. Submit Document / 13
b. Evaluate Document / 14
c. Review Document / 15

Relationship Between Classes Diagrams

Notes

v The Relationship Between Classes diagrams are a clear model of the relationship between classes and some server-side entities in a given use case package.

v In the following diagrams, there is an abstracted "black box" in the business layer called the "Entity Manager Subsystem." The entity manager subsystem is a client-side (Java) package in the UnGraSP-IS Web application. This package includes the wrapper classes and Data Access Layer (DAL) classes, which are presented in the Data Access Layer portion of the following diagrams and in more detail in the Data Access Layer/Database Model diagram of this document.

v The DAL class names have "Proxy" appended to them because they are proxies that are used in remote procedure calls in GWT. Proxies hide the fact that the called method is not being executed on the same machine as the caller method. All methods of a given proxy are mapped to identically named methods on the Tomcat server, which may or may not interact with a database server. In the following diagrams, any entity, such as a database table or the server's file system, related to and positioned to the right of a DAL class implies that the DAL class is sending data over the Internet to the server-side service on the Web server, which handles the client's request and sends information back to the client.

Account Management

Document Management

Data Access Layer/Database Model

Notes

v Due to the shortcoming of Your Inc.'s use case definitions, and in order to maintain traceability despite being relatively easy to implement, not all of the DAL classes in the data access layer have complete CRUD operations.

Sequence Diagrams

Notes

v In the following sequence diagrams, there are two abstracted entities: Server and GWT Callback. The Server entity and the message originating from the DAL class to it represent the DAL class doing an asynchronousremote procedure call over the Internet to the Web server's service class. The method executed on the Web server matches the method called in the DAL class from the calling dispatcher. All proxies except DocUpload Proxy and Session Proxy map to services on the Web server that interact with a database server. The GWT Callback entity and the message originating from it represent the successful callback routine, the routine that is executed in the client-side dispatcher after the operation on the Web server successfully executes and possibly returns some data. The returned data is represented by the list of formal parameters in the method signature in the message originating from the GWT Callback entity to the given use case dispatcher.

v The following sequence diagrams do not show the initialization required for the client to use GWT's remote procedure calls and do not show the validation that the client requests from the server on each page load to assure that the user's session is still valid.

Account Management

Create New Account

Manage Account

Manage User Account

Logout

Document Management

Submit Document

Evaluate Document

Review Document