Design+Considerations

Please limit posts on this page to insights, constraints, and observations that you believe should be considered by the design team while the project is being conceptualized and programmed. Modules that you'd like to see included in the system should be described on the **Features & Capabilities** page, not this one.

1. The design should be modular, with provision for components that can included or not on a given faculty member's home page, depending on that faculty member's design preference. (Peters)

2. The modules should be movable so that a faculty member can arrange selected components as desired. (Peters) (b) User session state should be stored and recalled on future visits (Bundrick)

3. Ideally the architecture of the system should be portable, so the system might be shared with (marketed to) other institutions. (Peters)

4. System should be scalable (Bundrick)

5. It needs to be platform-independent(kennedy)

6. It must be as fast as using those systems natively (kennedy)

7. It must be simple to use (kennedy)

8. It must be maintainable both in data and in code (kennedy)

9. It must be a production-scale system. (kennedy)

10. Security measures should be in place to prevent code exploits (Bundrick)

11. Some data may also require encryption. (Bundrick)

12 Some code may have to talk to different databases, db abstraction layer may need to be utilized. (Bundrick)