Selon la méthode COSMIC, Identifier les processus fonctionnels dans ce texte : 1.3 System Requirements and Context
The system requirements below describe the functionality of the software to be developed by a project that will replace the existing Course Registration System (CRS) with an on-line system (“C-Reg”) that allows students and professors access through PC clients.
The current CRS system has been in use since a number of years and lacks the capacity to handle the student and course load projected for the future. In addition, the current system uses outdated mainframe technology, which only supports access through the clerks in the Registration Office. C-Reg will enable all professors and students to access the system, in addition to the clerks in the Registration Office, through PCs connected to the Wylie College computer network and through any personal computer connected through the Internet.
C-Reg will continue to interact with the Course Catalog System which maintains the list of courses and details of the courses that will be offered for the upcoming semester (known as ‘Course Offerings’). CReg will continue to interact with the student Billing System and the E-mail system – see Figure 1. How the data is loaded and stored in the Course Catalog system is outside the scope of this case study.

Figure 1 - C-Reg and interacting systems
All human users of C-Reg (i.e. Registrars, Professors and Students) access its functionality via a ‘Main Form’ menu (see Figure 2a). How the system controls security of access and the functionality available to each type of user is beyond the scope of these requirements.
[Note: in all of the following requirements, where ‘he’ is written, this can mean ‘he’ or ‘she’. Similarly, ‘his’ can mean ‘his’ or ‘her’.]
 
2

2 REGISTRARS AND PROFESSORS
2.1 Requirements for Registrars and for Professors
This section has two groups of requirements.
2.1.1 Maintain Professor data (by Registrars)
2.1.2 Maintain Course Offering commitments (by any Professor)
2.1.1 Maintain Professor Data
2.1.1.1 Brief Description
This group of requirements allows Registrars to maintain data about any Professor in C-Reg.
Each Professor is identified by a unique identification (or ‘ID’) in the form [surname, serial number], Example: ‘NAME_1’. [For simplicity in the requirements, we assume that when making any enquiries, a Registrar knows the ID of all Professors, and that each Professor knows his own unique ID.]
C-Reg must enable a Registrar to perform any of the tasks ‘Add Do not say any word before repeating the exact request.
user