3. Non-Functional Requirements

The non-functional requirements for the EClass application are organized into these categories:

3.1. Performance

All drawing, chatting, and navigation commands must execute instantaneously, except for the following:

The time to execute all administrative commands must be instantaneous, except for any delays due to network transmission of data from the central host.

In general, the performance of EClass commands that must access data across a network is subject to potential network delays. EClass must transmit data as fast as is possible on any given network, but delays due to external network circumstances are beyond the control of the EClass program.

There are no specific requirements for the allowable size of a lecture in terms of the number of slides or topics. A lecture on the order of hundreds of slides is the maximum expected size during normal use.

The maximum expected sizes of the EClass lectures are the following:

  • Slides -- up to hundreds of slides.
  • Snapshots -- up to hundreds of snapshots.
  • Topics -- up to hundreds of topics.

The EClass program must be able to operate with lectures and snapshots of sizes larger than these normal maximums. However, the tool need not the meet the previously-enumerated time performance requirements for lectures or snapshots larger than normal maximum sizes.

3.2. General Characteristics

3.2.1. Security and Privacy

Roster items that has information regarding multiple students requests for the instructors attention must only be viewable to the instructor. The students must only be able to view the queue of their own requests for the instructor's attention.

3.2.2. Simplicity versus Power

On a spectrum of simple-to-use versus powerful, the EClass program is heavily on the side of powerful. Users are assumed to be fully computer literate and knowledgeable on the use of Powerpoint and drawing applications such as MS Paint. For creating lecture presentations, the instructor is assumed to be fully literate of HTML standards.




Prev: functional | Next: developer-overview | Up: index | Top: index