Project Title Date: 20, Dec, 2018

Supervised By :
Mr. Zaheed Ahmad
Lecturer
University Of Kotli AJ&K

Name Registration No.

Ahsan Shabbir 2014-UKT-0002

Ahsan Ajaz 2014-UKT-0020
Tuba Waris 2014-UKT-0026
Introduction
Design
Class Model
Class Diagram
Mapping of Class Diagram
Database Diagram
Interaction Model
Use Case Diagram
Sequence Diagrams
Activity Diagrams
Implementation
Testing
Conclusions & Future Extension
 CMS stands for Campus Management System
 CMS encompasses all facilities such as Online admission, Merit
List, Student Enrollment, Course Registration and Fee
Management etc.
 In this application we use Object-Oriented Modeling Techniques (OMT).
 UML have many diagrams and different types of system models.
Class Model
Class Diagram
Mapping of Class Diagram
Database Diagram
We have used class model for defining static structure of CMS
 Person
-name
-fatherName RegistratOfficeAdmin
-cnic -username
-address -password
-phoneNo 1
+registerDepartment()
-photo ad * +registerFaculty()
-dateOfBirth +postAd()
-state -adNo
1 *
-district -lastDate
-tehsial -entryTestDate
-city -fee AddmissionScehdule
-domicile -fdtionalFee
-listNo
+crudOpertion() -lastDate
ReqClass Programm
-displayDate
-class -ProgramName
+setAdmissonSchedule()
-subject +crudOpertion() +updateAdmisstionSchedule()
-reqMarks
Applicant
1 +crudOpertion()
-catageory * 1
-ammount
-year 1
1
-date 1 EntryTestReport
-status -obtainMarke
+apply() 1 acadmicRecord -totalMark
+updateInformation() -avg
+deleteInformation() * -class
-listNo
+login() -subject
-status
+logout() -obtainMark
-totalMark +crudOpertion()
+crudOpertionl()
1
Teacher
0.1 * -postion
-regNo
-qalification
Course
+takeAttendance()
-courseCode +login()
-courseName +logout()
-lab +checkAttendance()
Student -crh +uploadResult()
-rollNo -proId
-regNo TimeTable
+crudOpertion()
+registration() -roomNo 1
CouserRegistration
+update() -day
-semester 1 -time
+delete()
-date -date
+manageRegisterCourse()
+checkAttendance() +crudOpertion() +crudOpertion()
+genrateFeeChallan()
Department
1
* * -depName *
-userName Attendance
-password -status
* -date
+addDepartment()
+registerCourse() +takeAttendance() *
+verifyStudent() +checkAttendance()
1 +genrateMeritList()
+registerTeacher()
+manageTimeTabel() 1
Session Faculty
+manageCourse()
1 -crudOpertion
-session 1
+crudOpertion() * +registerFaculty()
* FeeSchedule
-tuitionfee
-other
-self

Class Diagram
-lastDate *
-semester
+manageFeeschedule()
 Person
Person
-name
-fatherName RegistratOfficeAdmin

Id name fatherName cnic address phone photo dateOfBirth -cnic

-address
1
-username
-password
-phoneNo +registerDepartment()
-photo ad * +registerFaculty()
-dateOfBirth +postAd()
-state -adNo
1 *
-district -lastDate
-tehsial -entryTestDate
-city -fee AddmissionScehdule
-domicile -fdtionalFee
-listNo
+crudOpertion() -lastDate
ReqClass Programm
-displayDate
-class -ProgramName
+setAdmissonSchedule()
-subject +crudOpertion() +updateAdmisstionSchedule()
-reqMarks
Applicant

Teacher
1 +crudOpertion()
-catageory * 1
-ammount
-year 1
pId position regNo qualificatio depId
1
-date 1 EntryTestReport
-status -obtainMarke
(reference n (reference +apply()
+updateInformation()
1
*
acadmicRecord
-class
-totalMark
-avg
+deleteInformation()
Person) Department)
-listNo
+login() -subject
-status
+logout() -obtainMark
-totalMark +crudOpertion()
+crudOpertionl()
1

Apply
Teacher
0.1 * -postion
-regNo
-qalification
Id proId personId Catego year Date Course
-courseCode
+takeAttendance()
+login()
(reference (reference ry Student
-courseName
-lab
+logout()
+checkAttendance()
-crh
Programme) Program)
+uploadResult()
-rollNo -proId
-regNo TimeTable
+crudOpertion()
+registration() -roomNo 1
CouserRegistration
+update() -day
-semester 1 -time
+delete()
-date -date
+manageRegisterCourse()
+checkAttendance() +crudOpertion() +crudOpertion()

Student
+genrateFeeChallan()
Department
1
* * -depName *
-userName Attendance
-password
rollNo ApplicationId regNo SessionId catageory
-status
* -date
+addDepartment()
+registerCourse() +takeAttendance() *
(reference (reference 1
+verifyStudent()
+genrateMeritList()
+checkAttendance()

Application) Session)
+registerTeacher()
+manageTimeTabel() 1
Session Faculty
+manageCourse()
1 -crudOpertion
-session 1
+crudOpertion() * +registerFaculty()
* FeeSchedule
-tuitionfee
-other
-self
-lastDate *
-semester
+manageFeeschedule()
Database Diagram
Interaction models:
 Use case diagrams
 Sequence diagrams
 Activity diagrams
Use Case Diagram Consist Of Two Things:

Actor
Use Cases
 Use Case For CMS

Upload Result Manage Program

Manage Admision ad
Take Attendance

Manage Department

Check Attendance Registrar office

logout

Teacher

Login

Verify Student

Manage Merit list

Apply for
Addmission Manage Teachers

Register Course
Manage fee
Schedules
Student
Check attendance

Manage Courses

Check Result

Manage Timetable
Print result card
«extends» Department

Verify Result

Verify Result

DMC
Reports
<<include>>

Examination Admin Update result <<include>> Result Card

login

logout
 :User
:GUI :Database

RequestForAddDagreeProgram()
Display form

Enter data
SendData

Added
SuccessfulySaved

Sequence Diagram for Add Degree Program

:User
:User Interface :Database

login
Verify user

Valid user
Display Dashboard

add qualification
send data

saved qualification
successfully saved

apply for program

request for check criteria for degree program

seccessfully applied

display challan form

Sequence Diagram for Applying Admission

 Login

[no]

[yes]

verify student genrate merit list Register Teacher Add Course set fee schedule Allocate Time Table Verify result

logout

Activity Diagram for Department

 Login

[no]

[yes]

apply for addmision

Apply for another program Genrate challan form Send failure notice

Activity Diagram for Admission

 Development Tools: Visual Studio 2012, MS SQL Server 2016
 Programming Language: C #,Asp.net ,HTML ,CSS , JQuery
Test Case ID: 01

Test Case Name: Log in

Test Case Description: This test case will examine the login process of a user.

Dependency or Prerequisite: Database connection is required.

User should have a proper user name and password provided by the Admin
,Department,Student ,Teacher and User with an active status.

Expected Input: Valid User Name and Password.

Expected flow of Events: User enters information and click on “Log In” button.

Alternate flow of Events: System is shut down, leaves some mandatory details missing or quits the system.

Actual Results: User successfully logs in and can use system functions accordingly.

Expected Results: Log in is carried successfully.

Actor: Admin,Department, Teacher ,Student

Bugs, Errors: None

Estimated time: Less than 1 second.

Test Case ID: 02

Test Case Name: Admission ad Generate

Test Case Description: This case examines the process of generate the admission ad for new admission.

Dependency or Prerequisite: Database connection is required

There should be at least one existing admin with active status who can add the all
necessary record.
The existing admin has successfully logged in to the ad panel.

Expected Input: Ad schedule, Register department, Add Required classics , Merit list schedule

Actual Results: Add show in the form of Report.

Expected Results: Genrateded Add

Actor: Registrar Admin

Bugs, Errors: None

Estimated time: Less than 1 second.

Test Case ID: 03

Test Case Name: Apply for Admission

Test Case Description: This case examines the process of apply for admission.

Dependency or Prerequisite: Database connection is required.

The new user must register using email ,Name and phone no.

Expected Input: Personal Information , Academic Information , Program Information

that who apply.

Expected flow of Events: User first register then the user name and password are send his
mobile phone then the user complete his personal information and
academic information after this process the user apply for program. .

Alternate flow of Events: If the user not registered and not login then the user cannot apply
the program.

Actual Results: After apply the program the system will generate the bank challan .

Expected Results: Successfully

Actor: User

Bugs, Errors: None

Estimated time: Less than 1 second.

It has been a great pleasure for us to work on this project. And this project
proved good for us since it taught us many things. CMS is need of the
University Of Kotli and thus we are privileged to work on it.
The proposed system is built successfully and it performs according to the
requirements specified in the requirements specification document. System is
satisfactorily tested with example data, it provides intended results. It is
found to be bug free as per the testing standards that are implemented.