Requirements:

FeelGood.com

 

Functional Requirements

  1. The system shall support three types of users;  customers, content providers, and administrative users.
  2. The system shall allow a noncustomer to view a sample of material.
  3. The system shall allow a noncustomer to register on-line to become a customer for the service.
  4. Payment shall be made outside of the scope of the system using conventional monetary instruments, e.g., check or money order.
  5. The system shall provide a means for administrative users to activate an account for a new customer.
  6. The system shall provide a means for administrative users to deactivate an account for an existing customer for nonpayment.
  7. The system shall provide a means for administrative users to deactivate an account for an existing customer for other than nonpayment reasons and refund a partial balance sum to that customer.
  8. The system shall provide a mechanism for content provider users to enter new content items into the system, including descriptive parameters.
  9. The system shall provide a mechanism for administrative users and content providers to remove content items from the system.
  10. The system shall provide a selection mechanism to match stored content items to a customer's profile.
  11. The system shall provide a redundancy mechanism to record content items previously delivered to the customer and to eliminate delivery or previously delivered items..
  12. The system shall provide a mechanism to send content items to customers (e.g., via e-mail) on a predetermined schedule based on the selection and redundancy mechanism.
  13. The system shall provide a mechanism for customers to connect to the system and request a content item of a specified type, to be delivered by the same selection and redundancy mechanisms listed above.
  14. The system shall provide a mechanism for the customer to cancel his or her account at any item and request a refund.

Design Requirements

  1. The service shall be delivered to customers through the Internet and WWW.
  2. Customers shall be able to use older browsers (i.e., IE and Netscape 4.0 and later), a variety of e-mail applications, and dial-up modems over conventional phone lines operating at 28k and higher.
  3. The browser user interface shall be implemented as a "thin client" without requiring special plugins.
  4. The domain and storage system shall be implemented using IBM's HTTP, WebSphere, and DB2 enterprise-level systems.
  5. The service shall be available 24x7 with at least 98% up time.