For your second assignment, you will need to produce a requirements specification document for a system which will allow the CECS Records office to maintain the list of faculty advisor assignments to students.
The current process (which I will describe in class) is far too cumbersome to make changes in real-time (students graduate before a change in advisor can be effected). In a nutshell, the system needs to be able to edit a local copy of the master faculty advisor - CIS student assignments. Students are allowed to change advisors at any time. Students and staff are allowed to review faculty research interests to facilitate advisor selection. If a student has no preference, he or she is assigned to the faculty member with the fewest student advisees. Faculty and staff can print lists of advisees by advisor. Students can check the list to see who is assigned as their faculty advisor. Advisor assignments are exported 4 to 6 times a year to Banner system. A web interface is desirable.
I would prefer that you work as groups of 2 or 3. I would like your group use object-oriented analysis techniques. If you really believe that you cannot use object-oriented analysis techniques, you may use one of the classic methodologies discussed in the text. As always, I will need a written statement describing what each member of your group contributed to this assignment.
Your group is required to develop a complete object- oriented analysis model for your project. Your group does not need to construct an object-oriented design of this system or plan to implement their design using some object- oriented programming language.
Your specification document is due three weeks from today. Your group should use the headings suggested in the Pressman template located at www.rspa.com/docs/Reqmspec.html. These headings include introduction, information description, usage scenario(s), data model description, functional model description, behavioral model description, limitations/restrictions/constraints and validation criteria. You will need to include an E-R diagram, a finite state model, and a data flow diagram or class hierarchy as part of your document.
Assigned: 10-15-01
Due date: 11-05-01