Contents

Introduction .................................................................................................................................................. 3
UML DIAGRAMS ............................................................................................................................................ 4
CLASS DIAGRAM........................................................................................................................................ 4
DESCRIPTION............................................................................................................................................. 4
DESCRIPTION............................................................................................................................................. 7
USE CASE DIAGRAM .................................................................................................................................. 8
DESCRIPTION............................................................................................................................................. 9
SEQUENCE DIAGRAMS ............................................................................................................................ 10
DESCRIPTION........................................................................................................................................... 10
OBJECT ORIENTED CONCEPTS WE HAVE USED:.......................................................................................... 12
Design Patterns ........................................................................................................................................... 13
Template Design Pattern ........................................................................................................................ 13
Bridge Design Pattern ............................................................................................................................. 14
Façade Design Pattern ............................................................................................................................ 14
What Have we Learned ............................................................................................................................... 16
REFERENCES ................................................................................................................................................ 16

2 Virtual University Management System

Introduction
The main concept behind our project is to make a university environment accessible to every
commoner and this is being done by implementing a virtual university that would be the core hub
for every knowledge seeker out there and the best of all the different universities’ faulty in one
place.

Classes are being implemented so that students could get an admission in their degree of choice
and get their courses registered according to the current semesters they are enrolled in. The entire
student information ranging from their personal data to the courses registered and their result per
semesters would be accessible only to the respective student and the main administration.

Students are also being given the opportunity to explore and exploit the biggest online library
available. Books, notes, old FYP projects, resources and lectures for all genres of education
would be just one click away. Weekly updates on our newsletter would be uploaded regarding
every upcoming event, holiday and any change of routine. Students would also be given a shot at
entering the world of responsibilities by being offered different volunteer work and TAship
opportunities. Less fortunate individuals would also be granted scholarships and financial aids
and to ensure that the help being provided is to a truly deserving individual our administrative
team would conduct proper background checks. The greatest advantage being provided is that
students as well as instructors are not bounded by time. Students will be given a weekly hour
quota that they need to fulfill. Apart from this they can access their lecture at any time of the day.

3 Virtual University Management System

UML DIAGRAMS
CLASS DIAGRAM
FIGURE 1

DESCRIPTION
During the intermediate stage of working on our project, this is the class diagram that we
compiled. In here it can be seen that we have created 11 different classes that have been connect
within each other using different appropriate object oriented implementations. Now, starting off
with one of our main classes;

4 Virtual University Management System

Person
We are making person parent class which is inherited by all those classes who needs common
features of name, id, department and email. We are also inheriting login and set_basic_info. So,
our classes of faculty member and student are inheriting this class. We are also associating this
class with department class and resource hub as they are using some of its info

Moving on to the other classes that have been implemented in our class diagram:

Department
We have provided this class with attributes name, student list and course list and functions of
enroll. As, we are enrolling students in a particular department so the student class is aggregated
with department class. Electrical engineering, mechanical engineering and computer engineering
are the three departments that we are offering in our virtual university so they are all inheriting
department class. as we can see there exists “is- a” relationship between these departments and
department class so we are applying the object oriented concept of abstraction here. So
inheritance is the most appropriate way to connect these classes.

Course
Course is class that has the attributes of course code and course name and contains the functions
of get course details and set course details. This class is used by students to register course in
their particular department. So, we are connecting course class to department class using
multiplicity that many departments can have many courses.

Course Contents
This class contains the name of the course instructor and methods of online lectures,
set_instructor, get_instructor and take test. This class is inheriting course class.

Student
It is aggregating department class because every department has students. Student class is
associated with faculty member because of advisor.

Administration
Administration class is holding students records. It is responsible for registering a student,
storing the student’s data, administration test and publishing the newsletter. It also provides the
functions of fees and scholarship. In addition to this it also updates student details.

5 Virtual University Management System

 FIGURE 2

6 Virtual University Management System

DESCRIPTION
As we progressed with our work we made certain significant changes into our previous class diagram.
Figure 2 highlights all the changes and is the final class diagram describing our project and all our
implementations in detail. The classes being implanted here are:

Administration
In our previous class diagram we hadn’t connected administration class with any other classes.
But here we have used composition to connect our administration class with the university class
because here exists a very strict “consists of” or “has a” relationship. a university has
administration. If a university doesn’t exist administration won’t either. So the existence of
administration strictly depends upon the existence of university. The attributes and functions are
almost the same that were implemented in the previous class diagram.

Faculty
Faculty class is a composite of university class and it is making association of composition with
department class. here exists multiplicity that one university can have 1 to many faculties and 1
faculty can have 1 to many departments.

Person
This class has been changed that significantly, still student and faculty member classes are
inheriting this class but now student class is also inherited by undergraduate student class and
graduate student class which is making sense because all undergraduate and graduates are
students.

Student
Student class is associated with course and faculty member class. Student enrolls in a course and
student takes advises from faculty members.

Course
Course class is inherited by undergraduate and graduate course classes. Course class is composed
of course material class as we have shown in the previous class diagram. As an abstraction we
have associated course class with degree class with the function of require as degree requires
courses.

7 Virtual University Management System

USE CASE DIAGRAM

FIGURE 3

8 Virtual University Management System

DESCRIPTION
This diagram is a use case diagram. It describes the external relationship between our main
classes and the functions that they are performing. The boundary that separates these has been
defined as the virtual university. Student is connected with the use cases of take_admission,
register and enrolls, take lectures, take degree, course enrollment and quiz and exam. Pay
admission, use case is including scholarship use case as scholarships are also an option for
talented students.

In addition to this, we have made instructor an actor which is having the responsibility to upload
lectures for their particular course, to enroll a student for their course and to take quizzes and
exam.

Administration is the use case of getting admission, updating newsletter, pay admission and
register or enroll.

9 Virtual University Management System

SEQUENCE DIAGRAMS
SEQUENCE DIAGRAM FOR COURSE MANAGEMENT

FIGURE 4

DESCRIPTION
First student sends request to department class to take some particular class. Department class
then checks if the requesting student is valid one or not. If it is a valid student, it makes request

10 Virtual University Management System

course class to enroll that student and it validates that student. Course class then notifies the
instructor. Now if a student makes request to course for lectures, it asks an instructor for lectures
and instructor class then returns lectures to student class.

Now if a student wants to take exam of a course, instructor is the one who gives exam to student.
The student sends a response to instructor which is evaluated by instructor class and results are
stored in databases.

SEQUENCE DIAGRAM FOR ADMISIION AND REGISTRATION

FIGURE 5

11 Virtual University Management System

DESCRIPTION
In order to take admission in our virtual university student first has to apply for exam by sending
request to examiner which in turn makes a call to admission test. After the test this class stores
the result in database class and returns the reports to student class. Now student class sends
response to admission test and that response is again stored in database class. Examiner can also
access responses from databases class. After knowing the result student makes a request for
registration. We have used a condition of alt in our sequence diagram. If the student has passed
the test, examiner will register student in his database class.

OBJECT ORIENTED CONCEPTS WE HAVE USED:

Code to an interface
We are implementing the idea of code to an interface in our class diagrams. We have seen
various classes which are having same general characteristics in common so instead of defining
them in separately in different classes, we have preferred to use interface and then implementing
those interfaces within several classes.

Delegation over inheritance

Delegation is simply passing a duty off to someone/something else. Delegation can be an
alternative to inheritance.Delegation means that you use an object of another class as an instance
variable, and forward messages to the instance. We have tried to design various solutions
through this approach.

Encapsulate what varies

There are certain characteristics in our classes that won’t be addressed using interfaces or
inheritance so we have encapsulated what was varying which is a very important concept in
object oriented designs.

12 Virtual University Management System

Abstraction
With every step in our project, we came to realize better understandable and more feasible
solutions to our problems. So we have tried to implement our solutions in the best possible
manner and have achieved new levels of abstraction.

Design Patterns
The Following Design Patterns have been used in our project.

Template Design Pattern

There are two types of students MS students and BS students. There are many similarities in
their algorithms as both students pass through the same procedure of registering courses to taking
lectures and giving exams. The two algorithms are quite similar.

If we don’t apply the template pattern on these two type of students then each will have it’s own
and exact same operations which will be just code repetition. Implementing Template Design
Pattern removes this repetition of code.

13 Virtual University Management System

Bridge Design Pattern
Bridge Design Pattern focuses on delegation rather than inheritance. In our system, there are two
types of courses, one for graduate and undergraduate and further there are compulsory courses
and Elective Courses. If we just choose inheritance than this would create mess. Suppose that we
add exchange students or some other kind of students then the number of classes would increase
so we applied bridge design pattern to favor delegation. The varying classes identified are
courses types.

Façade Design Pattern

Our System is quite Complex and many different classes are dependent on each other means they
require some kind of information from other classes. Like Instructor needs to update courses and
Instructor also manages student records like taking exam from them and then calculating results
after checking those exams. So to reduce the complexity of the system we used Façade design
pattern.

14 Virtual University Management System

The Database is the façade class and it is connected to all subsystems like course, students,
instructor and the administration. They all need to update each other status and any class can
access or retrieve other class objects from database rather than going to long way to access the
objects.

15 Virtual University Management System

What Have we Learned
We learned that the design process requires a very good knowledge about object oriented
concepts. While designing this we went through different phases. Like we first learned about
how to draw sequence diagrams and what they really mean and same for all other kind of
diagrams. We learned that applying Design Pattern and OOD concepts can really lead to a nice
and simple solution and there were we few classes which were not easy to link and we
complicating the overall project but design pattern helped us simplify them.

REFERENCES
 https://en.wikipedia.org/wiki/Object-oriented_analysis_and_design

 Craig Larman, Applying UML and Pattern

 James Martin, Object Oriented Analysis and Design

16 Virtual University Management System