First Dip in Enterprise System
its name is spaghetti monster, or enterprise system
This is a project I have done in RMIT University, which involves a lot of cooperation and interaction between multiple applications, which is so-called “Enterprise System”. The first part of the system is used to serve the University which relies on an old-fashioned system for student administration. As it usually happens in industry, requirements and/or values may change, so you should take this into account and design for flexibility. (This is an instruction in the project description, which is quite useful trying hard to figure out the blueprint.)
Another helpful tool when I was designing the restrictions in the data manipulation is thhe CRUD Management table:
| entities
|
STUDENT
(App 1*)[2] |
SUBJECT
(App 1* & 2) |
ENROLMENT
(App 1 & 2*) |
INVOICE
(App 3*) |
PAYMENT
(App 3*) |
|
| Application #1 SMA |
CRUD |
CRUD |
R |
—- |
—- |
|
| Application #2 EOL |
—- |
R |
CRUD |
—- |
—- |
|
| Application #3 FA |
—- |
—- |
—- |
CRUD |
C |
|
[1] Note: the initiator of the CRUD operations refer to the user’s behaviors in its main application, the propagations of the operations are not shown in this table, but in the business rules
[2] SUBJECT (App 1* & 2) means subject table exists in App #1 and #2, and App #1 is the primary application maintains the data;
Source Code:
deployment.rar: complied code and war/ear files
Table_Structures.rar: tables for applications
development.rar: source codes (NetBeans projects)
For the usage of the codes, please refer to the Project Manual for illustrated guides:
For code inspection and compiling:
Section 6 Developer Manual
For deployment:
Section 4 Deployment Guide
For running and using the system:
Section 5 User Manual
Recent Comments