(CMS)

COURSE MANAGEMENT
SYSTEM ON POST GRADUATE
PROGRAMME IN
MANAGEMENT

BY
TOSHAN SONTI
CSE-3B
16P71A05B6


1
CONTENTS
1. Introduction
2. Objectives
3. Scope & Limitations
4. Hardware & Software Requirements
5. Architecture
6. Process Model
7. Functional Requirements
8. Non Functional Requirements
9. Context Diagram
10. Data Flow Diagrams(DFD’s)
• DFD LEVEL - 0
• DFD LEVEL - 1
11. UML Diagrams
• Use-Case Diagrams
• Sequence Diagrams
• Class Diagrams
12. Test Cases

2
INTRODUCTION
A Post Graduate Programme in Management, also
known as Masters in Business Administration, is a very
special course for the people who are interested in
business management.This brings a scientific approach in
management. It mostly refers to management and
strategy. Any student or mid career professional can do
this course if interested. It provides a broad & focuses
only on planning and organising.

Mostly, the course is for a span of 2 years. But many

programmes are also for 1 year.There are many areas in
management to pursue, which will be a path to become
leaders, managers etc.

The programmes also consists of practical way of

projects in which students are given choice to be
specialised in a particular area to build a career around it.

3
OBJECTIVES
- Live projects and internships for students to
experience the challenges practically.
- MBA for under-graduates & other programmes for mid-
career professionals.
- To make the students think in an scientific way.
- Each student should be able to set a business &
identify key issues for it.

SCOPE AND LIMITATIONS

- Accreditations by many agencies that every student
get an opportunity to prove his mettle.
- Job depending on student skills and strategical
approach by taking placements.
- The limitation is no international certification and only
certification of university which we are affiliated with.

4
HARDWARE REQUIREMENTS
Processor: Pentium 4 or above.
RAM: 2GB.
HDD: 20GB or more.

SOFTWARE REQUIREMENTS
Operating System: Windows 10 or MAC.
Database: MySQL.
Server Deployment: Weblogic Server 10.
Framework: .NET Framework
Web Server: Apache

PROGRAMMING LANGUAGE & TOOLS

IDE: Eclipse.
User Interface: HTML, JavaScript.
Database: MySQL.

5
ARCHITECTURE

• A Web application architecture defines the interactions

between applications, middleware systems and
databases to ensure multiple applications can work
together.
• In this architecture, we have two programs running
concurrently:
- Code which lives in the browser and responds to
the user input(client side).
- Code which lives in the server and responds to the
http requests(server side).

• The server side code and language include is JAVA.

6
• The client side code and language include is HTML.

• Then, the user’s browser parses these codes.

• It is upto the web developer to decide what the code

in the server should do in relation to what the code on
the browser should do.

• Thus the client code can be seen and edited by the

user and has to only communicate through http
requests to the server and cannot access the server
directly.

• The imperative to have a good web application

architecture is because:
- It is blueprint for supporting future which may come
from increased demand, future interoperability and
enhanced reliability requirements.

• Through OOP , the organisational design of web

application architecture defines precisely on how an
application will function.

7
PROCESS MODEL
The process model for this project is spiral model.

The reason for using spiral model is:

• Provides potential for rapid development of increasingly
more complete versions of software.

• This model is a realistic approach to the development

of large scale systems and software.

• Uses prototyping as a risk reduction mechanism and

enables the developer to apply the prototyping
approach at any stage in the evolution of the product.

8
FUNCTIONAL REQUIREMENTS
TYPE OF USER FUNCTIONALITY DESCRIPTION
STUDENT LOGIN will logon to the
software
EXAM attends the exam,
check his result.
LIBRARY get membership,
view, rent& download
materials.
DASHBOARD view notifications.
CHAT BOX Discuss with Faculty.
FACULTY LOGIN logon to the
software.
EXAM conduct exams,
upload results.
LIBRARY upload materials,
videos.
CHAT BOX Discuss with
students.
CERTIFICATES issue certificates.
ADMIN LOGIN make changes in
accounts.
DASHBOARD updates the
dashboard

9
NON FUNCTIONAL REQUIREMENTS
PRIVACY:
The system shall protect the user’s privacy. Without the
permission of the user, the web application should not
display his/her details to the public on the web
application.

RELIABILITY:
The video quality should be clear and good .The audio
could be heard well. The video and audio of lectures
should be synchronised well.

RESPONSIVENESS:
The web application should take less
time to respond so
that the user should not feel uncomfortable waiting for
the output while using it.

AVAILABILITY:
Availability of the web application should be prior to the
user’s convenience so that the user can use it at any
time he is convenient. The web application should be
available 24/7. It should not get crashed.

10
USER FRIENDLINESS:
The web application should be user friendly so that the
user can easily access the website and go to his desired
page in a few clicks.

ACCESSIBILITY:

The system shall have high accessibility.

INTEROPERABILITY:
The system shall be highly interoperable so that the web
application can exchange information and make use of the
information with ease.

SCALABILITY:
Number of users at a time will mainly depend on the
number of registered students, server load, server
processing capacity and its memory. It should scale
maximum number of registered users. Highest priority will
be given to the members of the website like registered
students, faculty etc, to access the web application.

11
CONTEXT DIAGRAM
CHAT PLACEMENTS

DASHBOARD STUDENT

PAYMENT PGP CMS FACULTY

LOGIN ADMIN

EXAM
ONLINE
LIBRARY
CERTIFICATES

ADMIN:
• Creates and deletes accounts of the users.
• Change the passwords for the users.
• Website content changing like updating the dashboard,
updating new subjects of the course.

12
STUDENT:
• Every student registered to this course will get an
account and membership of online library.
• Change password of his/her account.
• Attends exam.
• Checks his result and status.
• View materials.
• Have access to the chat box for any doubts.

FACULTY:
• Have access to his/her account.
• Change password of his/her account.
• Conducts exam.
• Uploads materials, videos etc.
• Have access to the chat box to reply or clarify the
doubts of the students.

ONLINE LIBRARY:
• Every user has the access to the online library.
• Videos, ebooks, magazines, news, books, materials
related to the course will be available.

CERTIFICATES:
• After completion of the course or participation in
online exams or events, certificates will be given.

13
DASHBOARD:
• Notifications like News, updates, exam notices, results
will be displayed here.

CHAT BOX:
• Interaction between users and admin through online is
done here.
• Also interaction between student and faculty is done.

EXAM:
• Exams will be conducted through online links.
• Link will terminated after the completion of exam.
• Results will be displayed after the completion of exam.

PAYMENT:
• Any transaction of in-app purchases can be done here.

14
DATA FLOW DIAGRAMS(DFD)

DFD LEVEL 0:

DASHBOARD
Notifications

EXAM Link Login FACULTY

Result
Access
PGP CMS
Membership Access

LIBRARY Books,Links Login ADMIN

Login Access

STUDENT

15
DFD LEVEL 1:

EXAM FACULTY
DATABASE DATABASE

PGP CMS

LIBRARY ADMIN
DATABASE DATABASE

STUDENT
DATABASE

16
UML DIAGRAMS
To understand the system, one single diagram is not
sufficient and not enough to cover all the aspects of the
system.

So, we prepare different UML diagrams to understand

the system in a simple and better way and also to cover
all the aspects of the system.

The UML diagrams are generally made in a

incremental and iterative way.

The various kinds of UML diagrams we use are as

follows:

• Use Case Diagrams

• Sequence Diagrams

• Class Diagrams

17
USE CASE DIAGRAMS:
Use case diagrams are a set of use cases, actors and
their relationships. They represent the use case view of a
system. It also represents a particular functionality of a
system. They also describe the relationships among the
functionalities and their respective internal/external
controllers, who are als known as actors.

18
SEQUENCE DIAGRAMS
A sequence diagram is an interaction diagram. They
deals with sequences, which are the sequence of
messages flowing from one object to another. Sequence
diagram is used to visualise the sequence of calls in a
system to perform a specific functionality.

LOGIN:

Fig: Login operation done by Student and Faculty

19
EXAMS:

Fig: Exams operation done by Student and Faculty

20
LIBRARY:

Fig: Library operation done by Student and Faculty

21
CERTIFICATES:

Fig: Certificates operation done by Student and Faculty

22
COURSES:

Figure: View Course, Add Course & Status of the Course

operations done by Student.

23
CLASS DIAGRAMS
Class diagram is a static diagram. It represents the
static view of an application. Class diagram is not only
used for visualising, describing, and documenting different
aspects of a system but also for constructing executable
code of the software application.
Class diagram describes the attributes and operations
of a class and also the constraints imposed on the
system.
Class diagram shows a collection of classes,
interfaces, associations, collaborations, and constraints. It
is also known as a structural diagram.
Notations used:

CLASS
A class represents a relevant concept from the
domain, a set of persons, objects, or ideas that are
depicted in the IT system.

ATTRIBUTE
An attribute of a class represents a characteristic of
a class that is of interest for the user of the CMS
system.

24
OPERATIONS
An operation of a class represents the operations
performed by the class.

ASSOCIATION
An association represents a relationship between two
classes.

MULTIPLICITY
A multiplicity allows for statements about the number
of objects that are involved in an association.

25
The class diagram for this system is as follows:

Fig: Class Diagram for Course Management System

26
TEST CASES
REGISTER:
EXPECTED
S.NO TEST CASE RESULT
Open page for user to
If a user want to
1 enter his/her
register
information.

If user is already Display “Already

2
registered Registered”

If user misses any Should enter all the

3
field to enter fields with “*”

LOGIN:
EXPECTED
S.NO TEST CASE OUTPUT
Enter correct iD and
1 Login is successful
password

Access given by
2 Click login displaying user
profile

27
 EXPECTED
S.NO TEST CASE OUTPUT

3 Wrong iD Invalid iD is displayed

Wrong Password and Reset Password ? is

4 Correct iD Displayed

LIBRARY:
EXPECTED
S.NO TEST CASE OUTPUT

1 If user is a member Access to content.

Displays invalid
If user is not
2 access not
registered registered.

3 If user want to view Display content.

If user want Download link is

4 download displayed.

28
EXAMINATION:
EXPECTED
S.NO TEST CASE OUTPUT
Checks if any exam
1 If user is a student available and displays
the exam name.

If user chooses the Timer starts and

2 exam to attempt display questions.

Student submitting Takes the answers

3 the answer and displays the
before/on time date of results.
Student submitting Invalid Submission is
4 the answer displayed.
after time

29