Assignment#3-Fall-2010 - SYSC 3100 Fall 2010...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
SYSC 3100 – Fall 2010 – Assignment #3 [60 marks] – Individual work Posted: Nov. 15, 2010 Due: Dec. 2, 2010 @ 10:35 am [in-class] Advanced requirement elicitation, systems analysis, and introductory systems design Section One A. Problem statement A Capital city University offers a number of undergraduate and graduate degrees to full-time and part-time students. The educational structure of the university consists of faculties. Faculties contain several departments (for simplicity, we assume that schools have the structure as departments). While a single department administers each degree, the degree may include courses from other departments. In fact, the university prides itself on the freedom of choice given to students in selecting courses towards their degrees. The flexibility of course selection puts strains on the university’s old registration system. Individual tailored programs of study must not contradict the rules governing the degree, such as the structure of prerequisite courses required so that the student can qualify for the degree’s compulsory courses. A student’s choice of courses may be restricted by timetable clashes, maximum class sizes, etc. The flexibility and quality education offered by the university has been the main reason behind the steady growth in student numbers. However, to maintain its traditional strength, the current registration system – still partly manual – has to be replaced by a new software solution. Well, the preliminary search for an off-the-shelf software package has not been successful. The university registration system is sufficiently unique to warrant the in-house development. The system is required to assist in pre-registration activities and to handle the registration procedures. The pre-registration activities must include the mail-outs of last term’s examination grades to students together with any registration instructions. During registration sessions, the system must accept the students proposed programs of study and validate them for prerequisites, timetable clashes, class sizes, special approvals, etc. Resolutions to some of the problems may require consultation with academic advisors or academics in charge of course offering (program coordinators). The final program of study is subjected to academic approval by the delegate of the faculty dean and it is then forwarded to the registrar. B. Initial requirement elicitation and analysis Figure 1 below shows a high-level use case diagram for the university registration system. The model contains four actors and four use cases. Each use case is initiated by an actor and is a complete, externally visible and orthogonal piece of functionality. All actors, except Student, are the initiating actors. Student obtains examination results and
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 2
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 12/02/2010 for the course SYSC 3600 taught by Professor John bryant during the Fall '08 term at Carleton CA.

Page1 / 6

Assignment#3-Fall-2010 - SYSC 3100 Fall 2010...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online