Architectual Design - Design Mechanisms
The following is a list of analysis mechanisms mapped to design mechanisms used to address non-function requirements. The relevant analysis mechanisms were identified based on the main functions required of the system. These mechanisms assume some details of the implementation environment, but are not tied to a specific implementation.
| Analysis Mechanism | Design Mechanism |
| Persistency | - All databases (database subsystems) will be use a OODBMS (Object Oriented Database Management System) - No legacy databases are needed |
| Distribution & Interprocess/Remote Process Communication | - RMI (Remote Method Invocation) necessary for client/server implementation |
| Redundancy | - Backup server/system to maintain backup of the data found in the databases - Backup server is mirror of primary server (updates data as the primary server is updated) - Backup server can become primary server if the primary server fails - Program can be used to re-update the primary server from the backup if failure occurs in the primary (or if it is taken down for maintenance) |
| Security | - Firewall to prevent access from external networks (Internet, etc.) - Login/Password required to access specific user account (individual user accounts are used, with the access level defined by the system administrator in the user database) (System administrator creates users) - User Database is encrypted to protect the login/password info of the users - Login procedure uses encryptions when communicating with user database - Login/Password is not stored in local memory once an attempt to login has been performed |
| Error Detection | - Logging program used to track and log errors - System Administrator notified when error occurs - Primary and Backup servers compare data during off-time to ensure synchronization of data (if data not synchronized, a report log will be created documenting the inconsistency in data) |
