| |
|
| Anticipate change in the system |
| Anticipation: |
To anticipate future changes and system enhancement we decided to
encapsulate each subsystem with minimum coupling possible and implement
the entire system in Java to allow maximum portability. Using Java to
allow eventual porting to the web/multiplatform. All subsystems are
designed to be as flexible as possible.
|
| |
Future Enhancement on
Controller and View Subsystems: |
May eventually encapsulate current subsystems in client/server
architecture to accomodate web services (e.g. Enclose the Controller
and View subsystems in a server. The server then provides the services
of the controller and view subsystems to the client.The server accesses
and manipulates the databases through the controller subsystem). �
Thus, both the Controller and View subsystems are designed with maximum
flexibility in extendibility.
|
| |
| Future Enhancement on Model Subsystems: |
The Model Subsystem is designed to be portable to any database provider.
The interface to the Model Subsystem will remain unchanged. Regardless
of the database provider the user will not have to learn any new
functionality.
|
| |
| Important Changes: |
- Some functionality may become obsolete in the transition to the�Web,
such as return video and pay late fees.
- Customer can rent and download movies from home.
- The movies will give out when a reach the due date and time. Thus
there would be no more return video and pay over to fees.
- As a result, the View Subsystem will not have the options for
"return video" and "pay late fees".
- The handlers for "return video" and "pay late fees"
in the Controller Subsystem will be change to provide other services.
|
| |
| Functionality for Ordinary and Exceptional cases |
| |
| How Start: |
- Power up main system (server), and the database system.
- Each employee must login in order to enter the main system (server).
- After logging in, the system will start at the main page.�����
|
| |
| Initialize: |
- Main system establishes the connection with the database system.
- Get initialization records from the database system and start at main Window.
|
| |
| Shutdown: |
- Stop all new transactions.
- Finish all current transactions.
- Save all transactions.
- Save all changes to the database system.
- Logout, and power down.
|
| |
| Corrupt data: |
- Display corrupt data error message.
- Provide option to return to main screen.
|
| |
| Software Error: |
- Display software error message.
- Provide user the option to restart system or end task.
|