Parts in blue are directives to students.

Parts in yellow are my answers (not necessarily correct).

Supplementary Specification

Revision History

Version	Date	Description	Author
Inception Draft	July 16, 2003	To be refined during Elaboration.	Mathews
Inception Draft	July 17, 2003	Revised for web constraint.	Mathews
Elaboration	August 21, 2003	Revised after first iteration experience.	Mathews

Introduction

This document is the repository of all Registration System requirements not captured in the use cases.

Functionality

<fill in>

Logging and Error Handling

Log all errors to persistent storage.

Security

All usage requires user authentication.

A web-based solution in a public lab raises security issues that must be dealt with (clearing the cache, for example).

Usability

<fill in>

Human Factors

Interfaces should conform to web-accessibility guidelines detailed by the university (see Information in Domains of Interest).

The interface should be intuitive and responsive.

Reliability

<fill in>

Recoverability

Information should be left in a consistent state after every transaction.

Performance

<fill in>

Potentially thousands of students could use the system at the same time. The system should be responsive under high loads.

Supportability

<fill in>

Adaptability

-

Configurability

The University has many varieties of computer platforms and browsers that must be supported. See Implementation Constraints.

Implementation Constraints

<fill in>

The system must be accessible from a large number of clients.

The system must be accessible over the web from existing University computer labs. The major browsers that must be supported are:

· Internet Explorer 5.x and later

· Netscape 6.x and later

· Mozilla 1.x and later

· Safari 1.x and later

Purchased Components

<fill in>

Free Open Source Components

<fill in>

The following might be useful for a Java-based solution:

· JLog

· JUnit

Interfaces

<fill in>

-

Domain (Business) Rules

ID	Rule	Changeability	Source
RULE1	A student may not alter another student’s schedule.	Low	University policy
RULE2	Advisors and registrar staff may alter a student's schedule.	Low	University policy
RULE3	Some courses may not have a meeting time or place.	Low	Registrar
RULE4	Students can register for variable credit classes, pass/fail, or R credit.	Low	Registrar
RULE5	Courses are designated by major and a number.	Low	Registrar
RULE6	Courses are cancelled if a minimum enrollment is not met.	Low	Department policy
RULE7	Department must offer classes before Registrar deadline	Low	Registrar

Legal Issues

<fill in>

Use of open source software is recommended as long as licensing issues can be resolved.

Information in Domains of Interest

Course Catalog

The Registrar maintains a course catalog every two years. The course catalog contains course descriptions and prerequisites. This information is separate from the system under discussion.

Prerequisites

Students should fulfill various requirements before taking a course. These requirements usually include taking a previous course or courses, but may also involve the year in school, their major, etc.... These are generally presented as a guideline, so the System under discussion will not be responsible for checking prerequisites.

Meeting Times and Places

Some courses, such as internships and research, do not have a set meeting time or place. The Registrar designates the time and place as “arranged”.

Variations in Credit

<Note: finish describing credit variations>

Some courses are taken for alternate credit, such as pass/fail. The Department offering the course designates these courses.

Students may request to take a class pass/fail. The Registrar records this at the request of the Student, Professor, and Department.

Various courses such as internships and cooperative learning experiences are designated the R credit (for required). The R credit does not add credits (it has no quantity).

Project based courses, such as research, are open for a variable number of credits set by the Student.

Course Designations

Courses are designated by the major + a 3 digit number. Generally, a 100 level class is at a freshmen level, a 200 level class is at a sophomore level, and so on. For example, CprE 308 would be a junior level class in computer engineering. Course designations are set for each catalog. Thereafter, departments use them to inform the Registrar of course offerings.

Web-Accessibility Guidelines

The University has supplied the following link to use when designing web interfaces: http://www.iastate.edu/guide/access/