Course Registration System

Supplementary Specification

Version 1.0

Revision History

Date

Version

Description

Author

21/Dec/98 Draft Initial release - draft S. Gamble
19/Feb/1999 Version 1.0 Incorporate review comments.

Add remote access requirement.

S. Gamble
 
 
 
 
 
 
 
 

Table of Contents

  1. Objectives
  2. Scope
  3. References
  4. Functionality
    1. System Error Logging
    2. Remote Access
  5. 5. Usability
    1. Windows Compliance
    2. Design for Ease-of-Use
    3. Online Help
  6. Reliability
    1. Availability
    2. Mean Time Between Failures
  7. Performance
    1. Simultaneous Users
    2. Database Access Response Time
    3. Transaction Response Time
  8. Supportability
    1. New Releases Downloadable
  9. Design Constraints
    1. Course Catalog Legacy System
    2. Billing System
    3. Platform Requirements
    4. Internet Browsers
    5. Java Compatibility

Supplementary Specification

  1. Objectives
  2. The purpose of this document is to define requirements of the Wylie course registration (C-Registration) system. This Supplementary Specification lists the requirements that are not readily captured in the use cases of the use-case model. The Supplementary Specifications and the use-case model together capture a complete set of requirements on the system.

  3. Scope
  4. This Supplementary Specification applies to the Wylie course registration system which will be developed by the Wylie College Information Systems (IT) department. The IT department will develop this client-server system to interface with the existing course catalog database.

    The C-Registration System will enable students to register for courses on-line. The C-Registration System allows professors to select their teaching courses and to maintain student grades.

    This specification defines the non-functional requirements of the system; such as reliability, usability, performance, and supportability as well as functional requirements that are common across a number of use cases. (The functional requirements are defined in the Use Case Specifications.)

  5. References

Applicable references are:

  1. System Business Case for the C-Registration System, WyIT388, DRAFT, 1998, Wylie College IT.
  2. Course Billing Interface Specification, WC93332, 1985, Wylie College Press.
  3. Course Catalog Database Specification, WC93422, 1985, Wylie College Press.
  4. Stakeholder Requests Document for the C-Registration System, WyIT389, V1.0, 1998, Wylie College IT.
  5. Vision Document of the C-Registration System, WyIT387, V1.0, 1998, Wylie College IT.
  6. Glossary for the C-Registration System, WyIT406, V2.0, 1999, Wylie College IT.
  7. Use Case Spec - Close Registration, WyIT403, V2.0, 1999, Wylie College IT.
  8. Use Case Spec Login, WyIT401, V2.0, 1999, Wylie College IT.
  9. Use Case Spec - Maintain Professor Info, WyIT407, Version 2.0, 1999, Wylie College IT.
  10. Use Case Spec - Register for Courses, WyIT402, Version 2.0, 1999, Wylie College IT.
  11. Use Case Spec - Select Courses to Teach, WyIT405, Version 2.0, 1999, Wylie College IT.
  12. Use Case Spec - Maintain Student Info, WyIT408, Version 2.0, 1999, Wylie College IT.
  13. Use Case Spec - Submit Grades, WyIT409, Version 2.0, 1999, Wylie College IT.
  14. Use Case Spec - View Report Card, WyIT410, Version 2.0, 1999, Wylie College IT.
  1. Functionality
  2. This section lists functional requirements that are common to more than one use case.

    1. System Error Logging
    2. All system errors shall be logged. Fatal system errors shall result in an orderly shutdown of the system.

      The system error messages shall include a text description of the error, the operating system error code (if applicable), the module detecting the error condition, a data stamp, and a time stamp. All system errors shall be retained in the Error Log Database.

    3. Remote Access

    All functionality shall be available remotely through an internet connection. This may require applications or controllers running on the remote computers.

  3. Usability
  4. This section lists all of those requirements that relate to, or affect, the usability of the system.

    1. Windows Compliance
    2. The desktop user-interface shall be Windows 95/98 compliant.

    3. Design for Ease-of-Use
    4. The user interface of the C-Registration System shall be designed for ease-of-use and shall be appropriate for a computer-literate user community with no additional training on the System.

    5. Online Help

    Each feature of the C-Registration System shall have built-in online help for the user. Online Help shall include step by step instructions on using the System. Online Help shall include definitions for terms and acronymns.

  5. Reliability
  6. This section lists all reliability requirements.

    1. Availability
    2. The C-Registration System shall be available 24 hours a day, 7 days a week. There shall be no more than 4% down time.

    3. Mean Time Between Failures

    Mean Time Between Failures shall exceed 300 hours.

  7. Performance
  8. The performance characteristics of the system are outlined in this section.

    1. Simultaneous Users
    2. The system shall support up to 2000 simultaneous users against the central database at any given time, and up to 500 simultaneous users against the local servers at any one time.

    3. Database Access Response Time
    4. The system shall provide access to the legacy course catalog database with no more than a 10 second latency.

    5. Transaction Response Time

    The system must be able to complete 80% of all transactions within 2 minutes.

  9. Supportability
  10. This section defines any requirements that will enhance the supportability or maintainability of the system being built.

    1. New Releases Downloadable

    Upgrades to the PC client portion of C-Registration shall be downloadable from the UNIX Server over the internet. This feature enables students to have easy access to system upgrades.

  11. Design Constraints
  12. This section lists any design constraints on the system being built.

    1. Course Catalog Legacy System
    2. The system shall integrate with existing legacy system (course catalog database) which operates on the College DEC VAX Main Frame.

    3. Billing System
    4. The C-Registration System shall interface with the existing Course Billing System which operates on the College DEC VAX Main Frame.

    5. Platform Requirements
    6. The client portion of the C-Registration System shall operate on any personal computer with a 486 processor or greater. The client portion shall require less than 20 MB disk space and 32 MB RAM.

      The server portion of the C-Registration System shall operate on the Wylie College UNIX server.

    7. Internet Browsers
    8. The web-based interface for the C-Registration System shall run in Netscape 4.0.4 and Internet Explorer 4.0 browsers.

    9. Java Compatibility

The web-based interface shall be compatible with the Java 1.1 VM runtime environment.

Display Rational Unified Process using frames

Copyright  1987 - 1999 Rational Software Corporation Rational Unified Process 5.5 (build 12)