Professional Documents
Culture Documents
Oop - Aug - 2016
Oop - Aug - 2016
Unit Code & Title : K/601/1295– Unit 19 - OBJECT ORIENTED PROGRAMMING (OOP)
Assessment Title & No’s : Student Registration System for Stafford University
Date of Submission:
2. This entire brief should be attached in first before you start answering.
4. All the assignments should print in A4 sized paper, and make sure to only use one side printing.
5. Allow 1” margin on each side of the paper. But on the left side you will need to leave room for
binging.
6. Ensure that your assignment is stapled or secured together in a binder of some sort and attach
the Softcopy (CD) of your final document, system on last page.
Important Points:
1. Check carefully the hand in date and the instructions given with the assignment. Late
submissions will not be accepted.
2. Ensure that you give yourself enough time to complete the assignment by the due date.
3. Don’t leave things such as printing to the last minute – excuses of this nature will not be
accepted for failure to hand in the work on time.
4. You must take responsibility for managing your own time effectively.
5. If you are unable to hand in your assignment on time and have valid reasons such as illness, you
may apply (in writing) for an extension.
6. Failure to achieve at least a PASS grade will result in a REFERRAL grade being given.
7. Non-submission of work without valid reasons will lead to an automatic REFERRAL. You will
then be asked to complete an alternative assignment.
8. Take great care that if you use other people’s work or ideas in your assignment, you properly
reference them, using the HARVARD referencing system, in you text and any bibliography,
otherwise you may be guilty of plagiarism.
I hereby, declare that I know what plagiarism entails, namely to use another’s work and to present it as
my own without attributing the sources in the correct way. I further understand what it means to copy
another’s work.
Date:.………………
The process of assigning Professors to courses and the registration of students is a frustration and time
consuming experience for SU.
After the Professors of SU have decided which courses they are going to teach for the semester, the
Registrar’s office enters the information into a computer system. A batch report is printed for Professors
indicating which courses they will teach. A course catalog is printed and distributed to the students.
Currently, the students fill out registration forms that indicate their choice in courses, and return the
completed forms to the Registrar’s office. The typical student load is four courses. The staff of the
Registrar’s office then enters the students’ forms into the computer. Once the students’ curriculum for
the semester has been entered, a batch job is run overnight to assign students to courses. Most of the
time student’s get their first choice; however, in those cases where there is a conflict, the Registrar’s
office talks with each student to get additional choices. Once all students have been successfully
assigned to courses, a hard copy of the students’ curriculum is send to the student’s for their
verification. Most student registrations are processed within a week, but some exceptional cases take
up to two weeks to solve.
At the beginning of each semester, students may request a course catalog containing a list of course
offerings for the coming semester. In addition, each student will indicate two alternative choices in case
a course offering become filled or cancelled. No course offering will have more than ten students or
fewer than three students. A course offering with fewer than three students will be canceled. Once the
registration process is completed for a student, the registration system sends information to the billing
system so that student can be billed for the semester.
Professors must be able to access the student registration system through their logins to indicate which
courses they will be teaching, and to see which students signed up for their course offerings.
For each semester, there is a period of time that students can change their schedule. Students must be
able to access the system during this time to add or drop courses.
The Registrar must create the curriculum and generate a catalog for the semester.
The Registrar must maintain all the information about courses, Professors and Students.
After the course selection process is completed, the Billing System must be supplied with billing
information
The Professor needs to use the system to select the courses to teach for a semester, and must
be able to receive a course roster from the system.
The Registrar is responsible for the generation of the course catalog for a semester, and for the
maintenance of all information about the curriculum, the students, and the Professors needed
by the system.
Based on the above information given, develop an object oriented software system using C#.NET
2. Identify the objects and data and file structures required to implement a given design. (LO 2.1)
3. Draw the Use Case Diagram, Class Diagram and Sequence Diagrams, ERD for the given scenario.
Use Case diagram should be supported with the Use Case narrations. (LO 2.2) (M 2.7)
a. The class diagram should indicate the relationships between classes (associations,
aggregation, compositions, generalizations etc.) (LO 3.2)
4. Implement the Object Oriented solution using C#.Net for the proposed Design using a suitable
IDE. (LO 3.1). Include onscreen help to assist the users of SU. (M 3.1)
5. Provide evidences of Implementation of object behaviors using control structures to meet the
design algorithm (LO 3.3)
6. Evaluate effective use of an Integrated Development Environment (IDE), Include important code
snippets (such as of system-specific algorithms) and screenshots of important user interfaces
(LO 3.4)
7. Prepare a test plan and test your solution according to the plan. The proposed plan should cover
all important functionality of the system. (LO 4.1)
8. Analyze actual test results against expected results and to overcome the discrepancies occurred.
(Note: Learner needs to give expected results in tabular form and screenshots of interfaces for
actual results with the conclusion) (LO 4.2) (D3.2)
9. Get independent feedback on your solution (use surveys, questioners, interviews or any other
feedback collecting method) and make recommendations and suggestions for improvements in
a separate conclusion/recommendations section. (LO 4.3) (D1.4)
10. Prepare onscreen help, a users’ guide and a technical documentation for the support and
maintenance of the software. (LO 4.4) (LO 4.5)
Comments: