Thesis

University Clearance Workflow
Asif Iqbal
Toqeer Hussain
Supervised by:
Mr. Shahzad Rizwan
Department of Computer Science
COMSATS INSTITUTE OF INFORMATION TECHNOLOGY

ATTOCK PAKISTAN
SPRING 2015
NUMBER OF
MEMBERS
PROJECT ID
TITLE
SUPERVISOR NAME
Mr. Shahzad Rizwan
MEMBER NAME
REG. NO.
EMAIL ADDRESS
Asif Iqbal
CIIT/FA11-BCS-074/ATK
mr.asif.comsats@gmail.com
Toqeer Hussain
CIIT/FA11-BCS-049/ATK
Toqeer69@gmail.com
CHECKLIST:
Number of pages in this report
We have enclosed the soft-copy of this document along-with the codes
and scripts created by myself/ourselves
YES / NO
Our supervisor has attested the attached document
YES / NO
We confirm to state that this project is free from any type of

plagiarism and misuse of copyrighted material
YES / NO
MEMBERS SIGNATURES
Supervisors Signature
Note 1: This paper must be signed by your supervisor
Note 2: The soft-copies of your project report, source codes, schematics, and executables should be delivered in a CD
This work, entitled University Clearance Workflow has been

approved for the award of
Bachelor in Computer Science
Date: 05-06-2015
External Examiner:
Head of Department:
Department of Computer Science
COMSATS INSTITUTE OF INFORMATION TECHNOLOGY

ATTOCK PAKISTAN
Declaration
No portion of the work referred to in the dissertation has been submitted in support
of an application for another degree or qualification of this or any other
university/institute or other institution of learning.
MEMBERS SIGNATURES
Acknowledgements
We would like to thank our parents who kept backing us up all the times both
financially and morally. We are thankful to them for their prayers.
We would also like to thank Mr. Shahzad Rizwan for his guidance and
encouraging us to work hard. His critical comments on this work have certainly
made me think of new ideas and techniques in the fields of software
development.
We are grateful to the ALLAH Almighty who provides all the resources of every
kind to us, so that we make their proper use for the benefit of mankind. May He
keep providing us with all the resources, and the guidance to keep helping the
humanity.
Abstract
University Clearance Work-flow is a web based application that is applicable when the
student passes his/her Course work and is eligible to apply for the clearance of his/her
degree which can be utilize anywhere for the purpose of Clearing the course-work form
department, hostel, library, fee and degree-section .
Web based application facilitates users to apply for the Clearance of Final Clearance for
the under-taking the degree protocol.
This system is designed and developed for the purpose of helping the students who are
eligible to apply for the Clearance. The system is developed for the clearance of the
students that are integrated modules capable to clear the steps that are required in order to
make clearance for getting the Degree from university.
Project in Brief
ProjectTitle:
The system is designed and developed for the purpose of easing the students that
Objective:
are Eligible to apply for clearance
Asif Iqbal
Undertaken By:
Toqeer Hussain
Supervised By:
Mr.Shahzad Rizwan
Date Started:
October, 2014
Date Completed:
May, 2015
PHP (WordPress)
Tools, Technologies
and Language:
Platform Used:
MySQL 2012
Microsoft Visio 2013
Windows 8Professional 64-bit
SystemUsed:
Corei3, 2.4 GHz, RAM: 6 GB
Table of Contents
Contents
University Clearance Workflow........................................................................................................... 1
........................................................................................................................................................ 1
Declaration...................................................................................................................................... 4
Acknowledgements......................................................................................................................... 5
Abstract........................................................................................................................................... 6
CHAPTER 1.................................................................................................................................... 9
Introduction..................................................................................................................................... 9
1.1
Introduction.................................................................................................................... 10
1.2
Need of the Project........................................................................................................ 10
1.3
Problem Statement........................................................................................................ 10
1.4
Existing System............................................................................................................. 11
1.5
Proposed System.......................................................................................................... 11
1.5.1
1.6
Benefits of proposed system......................................................................................11

Scope of the project....................................................................................................... 12
CHAPTER 2.................................................................................................................................. 13
System Analysis............................................................................................................................ 13
1.7
System Analysis............................................................................................................ 14
1.7.1
Functional Requirements...........................................................................................14
1.7.2
Non Functional Requirements...................................................................................14
1.8
Use Case Diagram........................................................................................................ 16
1.9
Use Case in Detail......................................................................................................... 17
1.9.1
Login.......................................................................................................................... 17
1.9.2
Student Registration.................................................................................................. 17
1.9.3
Resend Request........................................................................................................ 17
8
1.9.4
Forgot Password....................................................................................................... 17
1.9.5
Manage Department Clearance.................................................................................17
1.9.6
Manage Fee Clearance............................................................................................. 17
1.9.7
Manage Hostel Clearance......................................................................................... 17
1.9.8
Manage Library Clearance........................................................................................ 18
1.9.9
Manage Degree Clearance.......................................................................................18
1.10
Use Case Description.................................................................................................... 18
1.10.1
Manage Users....................................................................................................... 18
Scenario 1: Add New User......................................................................................................... 18

Scenario 2: Search User............................................................................................................ 20
1.10.2
Login...................................................................................................................... 20
1.10.3
Forgot Password................................................................................................... 21
1.10.4
Register................................................................................................................. 22
1.10.5
Manage Library Clearance....................................................................................23
Scenario 1: Clearance Application.............................................................................................23

Scenario 2: Reject Application................................................................................................... 24
Scenario 3: Process Application................................................................................................ 25
Scenario 4: Pending Application................................................................................................26
1.10.6
Manage Network Administration............................................................................26

Scenario 2:
Reject Application............................................................................................... 27

1.10.7
Manage Hostel Clearance.....................................................................................30

Scenario 2:

1.10.8
Manage Account Section.......................................................................................33

Scenario 2:

1.10.9
Manage Examination Section................................................................................36

9
Scenario 2:

1.10.10
Manage Head of Department................................................................................39

Scenario 2:

CHAPTER 3.................................................................................................................................. 43
System Design.............................................................................................................................. 43
1.11
Sequence Diagram........................................................................................................ 44
1.12
System Sequence Diagrams......................................................................................... 44
1.12.1
Login...................................................................................................................... 44
1.12.2
Student Registration.............................................................................................. 46
1.12.3
Resend Request.................................................................................................... 47
1.12.4
Clerk Registration.................................................................................................. 48
1.12.5
Clear Student Request..........................................................................................49
1.12.6
Reject Student Request......................................................................................... 50
1.12.7
Forward Student Request......................................................................................51
1.12.8
Manage Network Administrator..............................................................................52
1.12.9
Manage Processed Applications............................................................................53
1.12.10
Manage Pending Applications...............................................................................53
1.12.11
Manage Hostel Clearance.....................................................................................54
1.12.12
Manage Accounts Clearance.................................................................................55
1.12.13
Manage Examination Clearance............................................................................56
1.12.14
1.13
Domain Model............................................................................................................... 58
1.14
Activity Diagram............................................................................................................ 59
1.15
Class Diagram............................................................................................................... 60
1.16
ERD Diagram................................................................................................................ 61
CHAPTER 4.................................................................................................................................. 62
Implementation.............................................................................................................................. 62
1.17
Implementation.............................................................................................................. 63
1.18
Tools and Technologies.................................................................................................63
1.18.1
ASP.NET................................................................................................................ 63
10
4.2.2 SQL SEVER 2012......................................................................................................... 63

4.2.3 Microsoft Visual Studio 2013......................................................................................... 64
CHAPTER 5.................................................................................................................................. 65
Testing........................................................................................................................................... 65
1.19
System Testing.............................................................................................................. 66
1.20
Testing Strategies.......................................................................................................... 66
1.20.1
Unit Testing............................................................................................................ 66
1.20.2
Integration Testing................................................................................................. 66
1.20.3
System Testing...................................................................................................... 67
1.21
Test Plan........................................................................................................................ 67
1.21.1
Objectives.............................................................................................................. 67
1.21.2
Software Test Environment....................................................................................67
1.23
Test Cases..................................................................................................................... 68
1.23.1
Login...................................................................................................................... 68
1.23.2
Register................................................................................................................. 68
1.23.3
Retrieve User......................................................................................................... 70
1.23.4
Update User.......................................................................................................... 71
1.23.5
Forgot Password................................................................................................... 72
1.23.6
Manage Library Clearance....................................................................................73
1.23.7
Manage Process Application.................................................................................74
1.23.8
Manage Pending Application.................................................................................75
1.23.9
Manage Network Administration............................................................................76
1.23.10
1.23.11
1.23.12
Manage Hostel Section..........................................................................................79
1.23.13
1.23.14
1.23.15
Manage Accounts Section.....................................................................................82
1.23.16
1.23.17
1.23.18
Manage Examination Section................................................................................85
1.23.19
1.23.20
1.23.21
1.23.22

11
1.23.23
CHAPTER 6.................................................................................................................................. 91
Conclusion.................................................................................................................................... 91
1.24
Conclusion..................................................................................................................... 92
12
CHAPTER 1
Introduction
13
Chapter 1
Introduction
1.1 Introduction
University Clearance Gateway is a web based Application. The main purpose of
this system is to facilitate the students that are eligible to get their degree cleared. There is
no automated system that is applicable to handle the different modules related to the
degree clearance. In this system different modules are integrated with each other in order
to handle the clearance for the students.
Redundancy chances will be much less.
Ambiguity.
Time will be saved
The system is designed and developed for the purpose of helping the students
that are eligible for instantiating their clearance process and want to get the degree
clearance done by this protocol.
1.2 Need of the Project

The existing system is manual. The student eligible to acquire the degree go
through different departments manually to get the clearance done. In this way the students
get way big struggle and is very difficult to acquire the degree. The system is not
automated and student goes through manually to concern departments and wastes a lot of
time also. Redundancy and ambiguity chance is much possible in this situation.
In this system we will also facilitate the student as well as the administration in
order to go through the clearance.
Time will be saved much with this application and students will not get frustrated in
order to get their degree.
1.3 Problem Statement

A student is supposed to visit 5 hostels, 2 libraries, fee section, security department
and his own department and at the end at degree section. Wastage of time and student get
pretty much upset because of the manual job of clearance.
14
Chapter 1
Introduction
Redundancy of data is much big and sometimes student have to Check-In one
department thrice or maybe more.
Ambiguity of data is also possible because of the data not integrated with each
other.
1.4 Existing System

The existing system is manual. The student eligible to acquire the degree go
through different departments manually to get the clearance done. In this way the students
get way big struggle and is very difficult to acquire the degree. The system is not
automated and student goes through manually to concern departments and wastes a lot of
time also. Redundancy and ambiguity chance is much possible in this situation.
In this system we will also facilitate the student as well as the administration in
order to go through the clearance.
Time will be saved much with this application and students will not get frustrated in
order to get their degree.
1.5 Proposed System

We are proposing to develop a Web-Based Solution that we help the students and
administration which will facilitate the student for getting the clearance done.
Main features for this system will be:
User Account Management System.
Hostel Clearance.
Library clearance.
Fee Clearance.
Academic Clearance.
Degree Section.
15
Chapter 1
1.5.1
Introduction
Benefits of proposed system
1.5.1.1
Easy Modification
Simple website layout and mobile application layout where donor can easily
manage donations.
1.5.1.2
Simple to use
Very clean interface. User wont get lost in unnecessary options. All it takes to add
a user by filling little information about the student to get cleared.
1.5.1.3
Search Engine Optimization (SEO)
Very good Google indexation is achieved thorough well optimized HTML code and
possibility to set individual page title, URL address, keywords and META description for
each donation and category.
1.6 Scope of the project

We are proposing to develop a Web-Based Solution that we help the students and
administration which will facilitate the student for getting the clearance done.
Main features for this system will be:
User Account Management System.
Hostel Clearance.
Library clearance.
Fee Clearance.
Academic Clearance.
Degree Section.
16
CHAPTER 2
System Analysis
17
1.7 System Analysis

This chapter describes the analysis model of the system which explains the
problem domain, use-cases and actors, and requirements of the system and sequence
diagrams of the system.
1.7.1
Functional Requirements
The system should provide clearance statement services also how the system
should react to particular inputs and how the system should behave in particular
situations.
1.7.1.1 Registration Module
Students can get registered into the system. Registered students can login to the
system by username and password.
1.7.1.2 Tracking His/her Clearance Process
Student can tack their clearance process from their home page. At the home page
their application process status will be visible and they can check that how many
departments has been cleared and his/her application is now at which department.
1.7.1.3 User Management
Administrator can manage students from admin panel. Administrator can add,
Clerks, clear an application and can reject an application due to some problem.
1.7.2
1.7.2.1
Non Functional Requirements

Easy Modification
Simple website layout and mobile application layout where donor can easily
manage donations.
1.7.2.2
Simple to use
Very clean interface. User wont get lost in unnecessary options. All it takes to add
a donation by filling little information about what you want to donate.
1.7.2.3
Efficiency
The system provides reliability. Easy in understanding and use. Users get all
information at same place which saves time.
18
1.7.2.4
Availability
The system is available 24 hours a day users can make donation at any time.
1.7.2.5
Reliability
University Clearance Workflow system is a web based and android application

so user is able to make donation using web and mobile as well.
19
1.8 Use Case Diagram
Figure 2.1 Use Case Diagram
20
1.9 Use Case in Detail

1.9.1
Login
User enters his/her username and password and logs in to the system.
1.9.2
Student Registration
Student can register to this system. After student gets registered his request will be
forwarded automatically the Library and his/her clearance process will be started.
1.9.3
Resend Request
User can register by entering username and email address for registration process.
1.9.4
Forgot Password
Register user select forgot password and by entering his/her email, new password
will be emailed on user email address.

1.9.5
Manage Department Clearance

User is entitled for the department clearance and message is delivered to the
concerned clerk for the clearance. The process is then checked against the concerned
student that his/her course work is completed or not and the check is applied.
1.9.6
Manage Fee Clearance

User is entitled for the fee department clearance and message is delivered to the
concerned clerk for the clearance. The process is then checked against the concerned
student that his/her fee is deposited within the due date and the dues against the
concerned students is checked and verified and if the dues are cleared the clerk will clear
its dues from fee department.
1.9.7
Manage Hostel Clearance

User is entitled for the hostel clearance and message is delivered to the concerned
clerk for the clearance. The process is then checked against the concerned student that
his/her mess dues are cleared. When cleared from the warden and the request is
transferred to the all hostels warden. Then it is cleared from the all hostels warden that all
the dues against hostel are cleared by the concern student.
21
1.9.8
Manage Library Clearance

User is entitled for the library clearance and message is delivered to the concerned
his/her mess dues are cleared and he/she has submitted their hostel card. When cleared
from the clerk and tutor the request is transferred to the warden. Then it is cleared from
the warden that all the dues against hostel are cleared by the concern student.
1.9.9
Manage Degree Clearance

User is entitled for the hostel clearance and message is delivered to the concerned
his/her mess dues are cleared and he/she has submitted their hostel card. When cleared
from the clerk the request is transferred to the warden. Then it is cleared from the warden
that all the dues against hostel are cleared by the concern student.
1.10 Use Case Description

1.10.1 Manage Users
Scope: University Clearance Workflow
Level: User goal
Scenario 1:
(Add New Clerk): Admin
Scenario 2:
(Retrieve User): Admin
Scenario 1:Add New User
Description and Priority:
Goal in context
User wants to be added.
Use Case Name
Add New Clerk.
Pre-Condition
System should be in running state
Success and conditions
Clerk registration done successfully
Failed Condition
Clerk registration not done successfully
Primary Actor
Admin
Trigger Event
Admin selects the register option.

22
Main Success Scenario:

Sr. #
Actor
System response
Admin selects the register

option.
System display form
Admin selects add new System prompts user to enter user

information.
user option.
Admin
enter
the
information
4
valid System validates the entered

information.
User selects the submit

option.
System display confirmation message.
Extension:
1A. System becomes unavailable.
3A. User enters wrong information.
1. System shows error message (e.g. inappropriate format).
2. The use case continues at step 3.
3B.Administratorgives incomplete information
1. System shows error message (e.g. missing address).
5A. Username or email is already registered
1. System shows the error message.
2. Process terminates.
23
Scenario 2: Search User

Goal in context
Administrator can view information of user.
Use Case Name
Search User.
Pre-Condition
Administrator is authenticated and user is

registered.
Users information retrieved successfully.
Failed Condition
Users information not retrieved successfully.
Primary Actor
User
Administrator selects pending request option.
Trigger Event

Sr. #
Actor
System response
Administrator selects
pending request option.
System displays all user pending lists.
Administrator selects the

required one record.
System displays user information in

updateable format.
Extension:
1A.Administrator selects wrong option.
1.10.2 Login
Description and Priority

Goal in context
User wants to login the system.
Use Case Name
Login.
Pre-Condition
System should be in running state.
User logs in successfully

connection establishes.
and
Failed Condition
User logs in successfully

connection not establishes.
and
Primary Actor
User.
24
Trigger Event
User selects login option.

Sr. #
Actor
System response

System prompts the user enter his/her
username and password.
User enters his/her

username and password.
System validates the entered username

and password and logs the user into
the system.
Extension:
2A.User enters invalid name or password.
1. System asks administrator/user to re-enter username and password.
2. This step should be repeated three times.
3. System shows error message.
1.10.3 Forgot Password

Goal in context
Retrieve the password.
Use Case Name
Forgot password.
Pre-Condition
User is registered.
System should be in running state
Users password successfully changed.
Failed Condition
Users password
changed.
Primary Actor
User.
Trigger Event
not
successfully
User selects Forgot password option.

Sr. #
Actor
System response
25
User
selects
password option.
2
Forgot System prompts user to enter his/her

email.
User enters his/her email.
System validates entered information

and display confirmation message.
Extension:
3A.User gives incomplete information
1. System shows error message (e.g. empty post).
3B.User gives wrong information
1. System shows error message (e.g. empty post).
1.10.4 Register

Goal in context
New user is being registered into the

system.
Use Case Name
Register
Pre-Condition
User registration done successfully.
Failed Condition
User
registration
successfully.
Primary Actor
User.
User selects Register option.
Trigger Event
not
done

Sr. #
Actor
System response
User selects the register

option.
System prompts the user to enter his

username and email.
User enters username and

email.
System validates the entered

information
26

option.
System sends username and password

on his/her email and displays
confirmation message.
Extension:
1A. System becomes unavailable.
3A.User enters wrong information.
1. System shows error message (e.g. inappropriate format).
3B.User gives incomplete information
1. System shows error message (e.g. missing address).
5A.Username or email is already registered
1. System shows the error message.
2. Process terminates.
1.10.5 Manage Library Clearance
Use Case: Manage Library Clearance
Scenario 1:
(Clearance Application): Admin
Scenario 2:
(Reject Application): Admin/User
Scenario 3:(Process Application): Admin/User

Scenario 4:(Pending Application): Admin/User
Scenario 1: Clearance Application

Goal in context
Administrator can view clearance

application.
Use Case Name
Manage Library Clearance.
Pre-Condition
Administrator is authenticated.
Library clearance is done successfully.
Failed Condition
Library clearance
successfully.
Primary Actor
User.
Trigger Event
User checks the clearance application

requests.
is
not
done
27

Sr. #
Actor
System response
User checks the process

application requests.
System displays requests.
User checks the status.
User clicks the Clear

button.
System validates entered information.
User enter Information.
System displays confirmation

message.
Extension:
4A. User selects problem option.
1. Problem is explained.
2. Delivery message to the respective student.
4B.User selects cancel option.
Scenario 2: Reject Application

Goal in context
Administrator
application.
can
view
reject
Use Case Name
Pre-Condition
Reject application is checked.
Failed Condition
Reject application is not checked.
Primary Actor
Administrator.
Trigger Event
Admin hits the option button

Sr. #
Actor
System response
28
Administrator
hits
the System shows the applications status.
reject application option.
Scenario 3: Process Application
Description and priority:

Goal in context
Administrator
application.
can
view
process
Use Case Name
Pre-Condition
Process application is checked.
Failed Condition
Process application is not checked.
Primary Actor
Administrator.
Trigger Event

Sr. #
Actor
Administrator
System response
hits

2
Administrator sends the System shows the status.

rejected Application.
29
Scenario 4: Pending Application

Goal in context
Administrator
application.
can
view
pending
Use Case Name
Pre-Condition
Pending application is checked.
Failed Condition
Pending application is not checked.
Primary Actor
Administrator.
Trigger Event

Sr. #
Actor
System response
User checks the pending

System shows the status.
1.10.6 Manage Network Administration

Use Case: Manage Network Administration
Scenario 1:
Scenario 2:


Goal in context

application.
Use Case Name
Manage Network Admin Clearance.
Pre-Condition
30
Network Admin clearance is done

successfully.
Failed Condition
Network Admin clearance is not done

successfully.
Primary Actor
User.
Trigger Event

requests.

Sr. #
Actor
System response


button.
User enters Information.

message.
Extension:
Scenario 2:
Reject Application

Goal in context
Administrator
application.
can
view
reject
Use Case Name
Pre-Condition

31
Failed Condition
Primary Actor
Administrator.
Trigger Event

Sr. #
Actor
Administrator
System response
hits

Goal in context
Administrator
application.
can
view
process
Use Case Name
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event

Sr. #
Actor
Administrator
System response
hits
32
33

Goal in context
Administrator
application.
can
view
pending
Use Case Name
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event

Sr. #
Actor
System response

34
1.10.7 Manage Hostel Clearance

Use Case: Manage Hostel Clearance
Scenario 1:
Scenario 2:


Goal in context

application.
Use Case Name
Manage Hostel Clearance.
Pre-Condition
Hostel clearance is done successfully.
Failed Condition
Hostel clearance
successfully.
Primary Actor
User.
Trigger Event

requests.
is
not
done

Sr. #
Actor
System response


button.

message.
35
Extension:
Scenario 2:
Reject Application

Goal in context
Administrator
application.
can
view
reject
Use Case Name
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event

Sr. #
Actor
Administrator
System response
hits

Goal in context
Administrator
application.
can
view
process
Use Case Name
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event

36

Sr. #
Actor
Administrator
System response
hits


Goal in context
Administrator
application.
can
view
pending
Use Case Name
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event

Sr. #
Actor
System response

37
1.10.8 Manage Account Section

Use Case: Manage Accounts Clearance
Scenario 1:
Scenario 2:


Goal in context

application.
Use Case Name
Manage Accounts Clearance.
Pre-Condition
Accounts
clearance
successfully.
Failed Condition
Accounts clearance
successfully.
Primary Actor
User.
Trigger Event

requests.
is
is
done
not
done

Sr. #
Actor
System response


button.

message.
38
Extension:
Scenario 2:
Reject Application

Goal in context
Administrator
application.
can
view
reject
Use Case Name
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event

Sr. #
Actor
Administrator
System response
hits

Goal in context
Administrator
application.
can
view
process
Use Case Name
Pre-Condition
Failed Condition

39
Primary Actor
Administrator.
Trigger Event

Sr. #
Actor
Administrator
System response
hits


Goal in context
Administrator
application.
can
view
pending
Use Case Name
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event

Sr. #
Actor
System response

40
41
1.10.9 Manage Examination Section

Use Case: Manage Examination Section
Scenario 1:
Scenario 2:


Goal in context

application.
Use Case Name
Manage Exams Clearance.
Pre-Condition
Exams clearance is done successfully.
Failed Condition
Exams clearance
successfully.
Primary Actor
User.
Trigger Event

requests.
is
not
done

Sr. #
Actor
System response


button.

message.
42
Extension:
Scenario 2:
Reject Application

Goal in context
Administrator
application.
can
view
reject
Use Case Name
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event

Sr. #
Actor
Administrator
System response
hits

Goal in context
Administrator
application.
can
view
process
Use Case Name
Pre-Condition
Failed Condition

43
Primary Actor
Administrator.
Trigger Event

Sr. #
Actor
Administrator
System response
hits


Goal in context
Administrator
application.
can
view
pending
Use Case Name
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event

Sr. #
Actor
System response

44
45
1.10.10
Manage Head of Department
Use Case: Manage Library Clearance

Scenario 1:
Scenario 2:


Goal in context

application.
Use Case Name
Manage HOD Clearance.
Pre-Condition
HOD clearance is done successfully.
Failed Condition
HOD clearance
successfully.
Primary Actor
User.
Trigger Event

requests.
is
not
done

Sr. #
Actor
System response


button.

message.
46
Extension:
Scenario 2:
Reject Application

Goal in context
Administrator
application.
can
view
reject
Use Case Name
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event

Sr. #
Actor
Administrator
System response
hits

1.
47

Goal in context
Administrator
application.
can
view
process
Use Case Name
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event

Sr. #
Actor
Administrator
System response
hits

2

Goal in context
Administrator
application.
can
view
pending
Use Case Name
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
48

Sr. #
Actor
System response

49
CHAPTER 3
System Design
50
Chapter 3
System Design
1.11 Sequence Diagram

A Sequence Diagram is an interaction diagram that shows how processes operate
with one another and in what order. It is a construct of a Message Sequence Chart.
A sequence diagram shows object interactions arranged in time sequence. It
depicts the objects and classes involved in the scenario and the sequence of
messages exchanged between the objects needed to carry out the functionality of
the scenario. Sequence diagrams are typically associated with use case
realizations in the Logical View of the system under development. Sequence
diagrams are sometimes called event diagrams, event scenarios
Sequence Diagram shows, as parallel vertical lines (lifelines), different processes
or objects that live simultaneously, and, as horizontal arrows, the messages
exchanged between them, in the order in which they occur. This allows the
specification of simple runtime scenarios in a graphical manner.
1.12 System Sequence Diagrams

Following are the fully defined System Sequence Diagram of our System.
1.12.1 Login
51
Chapter 3
System Design
Figure 2.2 Login
52
Chapter 3
System Design
1.12.2 Student Registration
Figure 2.3 Register Student
53
Chapter 3
System Design
1.12.3 Resend Request
Figure 2.4 Resend Request
54
Chapter 3
System Design
1.12.4 Clerk Registration
Figure 2.6 Clerk Registration
55
Chapter 3
System Design
1.12.5 Clear Student Request
Figure 2.7 Clear Student Request
56
Chapter 3
System Design
1.12.6 Reject Student Request
Figure 2.8 Reject Student Request
57
Chapter 3
System Design
1.12.7 Forward Student Request
Figure 2.9 Forward Student Request
58
Chapter 3
System Design
1.12.8 Manage Network Administrator
Figure 2.10 Manage Network Administration
59
Chapter 3
System Design
1.12.9 Manage Processed Applications
Figure 2.11 Manage Process Application
1.12.10
Manage Pending Applications
Figure 2.12 Manage Pending Application
60
Chapter 3
System Design
1.12.11Manage Hostel Clearance
Figure 2.13 Manage Hostel Clearance Application
61
Chapter 3
1.12.12
System Design
Manage Accounts Clearance
Figure 2.14 Manage Accounts Clearance
62
Chapter 3
1.12.13
System Design
Manage Examination Clearance
Figure 2.15 Manage Examination Office Clearance
63
Chapter 3
1.12.14
System Design
Figure 2.16 Manage Head of Department
64
Chapter 3
System Design
1.13 Domain Model
Figure 2.17 Domain Model
65
Chapter 3
System Design
1.14 Activity Diagram
Figure 2.18 Activity Diagram
66
Chapter 3
System Design
1.15 Class Diagram
Figure 2.19 Class Diagram

67
Chapter 3
System Design
1.16 ERD Diagram
Figure 2.20 Entity Relation Diagram
68
Chapter 3
System Design
CHAPTER 4
Implementation
69
1.17 Implementation
This chapter will elaborate the interface along with the basic principles that are kept
in view while designing the interface. An idea can become worthless when it is not
conveyed properly. This chapter introduces how this application is implemented.
1.18 Tools and Technologies

Selection of tools plays an important role in developing software application.
Following are the tools used for development.
1.18.1 ASP.NET
ASP.NET is a set of Web development tools offered by Microsoft. Programs like
Visual Studio .NET and Visual Web Developer allow Web developers to create dynamic
websites using a visual interface. Of course, programmers can write their own code and
scripts and incorporate it into ASP.NET websites as well. Though it often seen as a
successor to Microsoft's ASP programming technology, ASP.NET also supports Visual
Basic.NET, JScript .NET and open-source languages like Python and Perl.
ASP.NET is built on the .NET framework, which provides an application program
interface (API) for software programmers. The .NET development tools can be used to
create applications for both the Windows operating system and the Web. Programs like
Visual Studio .NET provide a visual interface for developers to create their applications,
which makes .NET a reasonable choice for designing Web-based interfaces as well.
In order for an ASP.NET website to function correctly, it must be published to a
Web server that supports ASP.NET applications. Microsoft's Internet Information Services
(IIS) Web server is by far the most common platform for ASP.NET websites. While there
are some open-source options available for Linux-based systems, these alternatives often
provide less than full support for ASP.NET applications.
4.2.2 SQL SEVER 2012
SQL Server is a relational database management system (RDBMS) from
Microsoft that's designed for the enterprise environment. SQL Server runs on T-SQL
(Transact -SQL), a set of programming extensions from Sybase and Microsoft that add
70
several features to standard SQL, including transaction control, exception and error
handling, row processing, and declared variables..
4.2.3 Microsoft Visual Studio 2013

Visual Studio is a service offered by the Microsoft Company, integrated development
environment for various high-level languages. The current version 12.0 ("Visual Studio 2013"),
Visual Basic .NET, C, C ++, C ++ / CLI, C ++ / CX, C #, F #, SQL Server, Typescript and python,
as well as HTML, JavaScript and CSS for the development of Windows Store apps. J # is no
longer
included
in
Visual
Studio
2008.
Visual Studio allows the programmer to develop both traditional Windows programs and dynamic
websites and web services for the Internet / Intranet and Windows Apps imposed by Windows 8
Windows Store. The focus is therefore on Windows 8 on the creation of those same apps that are
based on the newly introduced with this version of Windows Runtime environment. Among all
previous versions of Windows, the emphasis continues to be placed on applications for the .NET
Framework,
developed
by
Microsoft,
on
the
runtime-based
software
platform.
With Visual C ++, however, the development of native Win32 / Win64 programs is possible.
These programs are run when the user later, but may need u. Additional software components
("Microsoft
Visual
++
Redistributable
Package
20xx")
are
also
installed.
Visual Studio 2003 to Visual Studio 2008 with the .NET Compact Framework and the software
development for mobile devices, such as smart phones and PDAs, are supported. For Visual
Studio 2010 only support the development for Windows Phone 7 is available, which is based on
XNA and Silver light.
1.18.2
71
CHAPTER 5
Testing
72
Chapter 5
Testing
1.19 System Testing

This chapter will discuss the test performed on this application. Different test
strategies are carried out to make sure this application works fine. Testing is extremely
important, both to ensure that the system meet requirements, and to ensure that it is free
of errors. That is why it is performed throughout the development process at every level,
while developing software there is a tendency to push the end product "out the door" as
soon as possible.
System testing is an essential step for the development of a reliable and error-free
system. Testing is a process of executing a program with the explicit intension of finding
errors but this does not mean to embarrass the programmer or fail the product but the
positive intention to remove as many problems from the system. A test case is a set of
data items that the system processes as normal input. Good testing involves much more
than just running the program a few times to see whether it works.
1.20 Testing Strategies

System testing makes a logical assumption that the parts of the system are correct,
the goal will be successfully achieved. The adequate testing or non-testing, leads to the
failures. Software testing is a critical element of software quality assurance and
represents the ultimate review of specification, design and coding. The basic testing
strategies are as follow.
1.20.1 Unit Testing

In the unit testing different modules of the system are tested separately. The
purpose of this testing is to determine that each module is functioning properly and to
locate errors in modules. System modules are individually tested for this project; and
noted each module are working according to the desired specification and requirements.
1.20.2 Integration Testing

After the unit testing are the modules are combined are tested at the same time. The
purpose of this testing is to determine whether all the modules are interfacing with each
other correctly or not. System is tested in integrated who were also working correctly.
73
Chapter 5
Testing
1.20.3 System Testing

System testing involves the set of tests that ensures that the entire system performed
according to the specifications. The system is checked using the actual data values. Also
the donation and subscription are checked against the requirements.
1.21 Test Plan

1.21.1 Objectives
University Clearance Workflow is a web based application that is designed for the
students that are eligible for the clearance of the degree from the university. This
application is just for the purpose that the students get their clearance on time and without
the delay and waste of time.
1.21.2 Software Test Environment

The software requirements are Adobe Dreamweaver, MySQL, Microsoft Visio and
Eclipse for development.
Hardware: The minimum hardware requirements are a Pentium III processor with 512
MB RAM and a minimum 40 GB HDD.
Personnel: Asif Iqbal and Toqeer Hussain performed testing.
1.22
74
Chapter 5
Testing
1.23 Test Cases

1.23.1 Login
Test Case Id: TCUC01
Test Case Name: Login
Project Name: University Clearance Workflow
Pre-Condition: System should be in running state
Steps:
N
o
Steps
1.
2.
User enters his/her name

and password.
Actual Result
Expected Result
System prompts the user enter

his/her name and password.
System will prompts

the user enter his/her
name and password.

name and password and logs
the user into the system.
System validates the

entered name and
password and logs the
user into the system.
Post Condition: User logs in successfully and connection establishes
1.23.2 Register

Test Case Name: Register
Pre-Condition: System should be in running state
Steps:
No
Steps
Actual Result
Expected Result
1.
User selects Register option
System prompts the user to

enter his username and email.
System will prompt

the user to enter his
username and email.
75
Chapter 5
Testing
2.
User enters username and

email.
3.

option.

information.
System will validate

the entered
information.
System sends username and

password on his/her email and
displays confirmation message.
System will send

username and
password on his/her
email and displays
confirmation
message.
Post Condition: User registration done successfully
76
Chapter 5
Testing
1.23.3 Retrieve User

Test Case Name: Retrieve User
Pre-Condition: Administrator is authenticated and user is registered.
Steps:
No
Steps
Actual Result
Expected Result
1.
Administrator select user

option form admin panel.
System displays all user lists.
System will
displays all user
lists.
2.

System displays user

information in updateable
format.
System will display

user information in
updateable format.
Post Condition: Users information retrieved successfully
77
Chapter 5
Testing
1.23.4 Update User

Test Case Name: Update User
Pre-Condition: Administrator and user are authenticated.
Steps:
No
Steps
Actual Result
Expected Result
1.
User selects edit profile

option.
System displays information of

user in updatable format.
System display
information of
user in updatable
format.
2.

System displays user information

in updateable format.
System display
user information
in updateable
format.
3.
User enters his/her

information.
System validates the enter

information.
System will
validate the enter
information.
4.
User selects update profile

option.

message.
System will
display
confirmation
message.
Post Condition: Users information updated successfully
78
Chapter 5
Testing
1.23.5 Forgot Password

Test Case Name: Forgot Password
Pre-Condition: User is registered. System should be in running state.
Steps:
No
Steps
Actual Result
Expected Result
1.
User selects Forgot password

option.
System prompts user to enter

his/her email.
System will
prompt user to
enter his/her
email.
2.
User enters his/her email.
System validates entered

information and display
confirmation message.
System will
validate entered
information and
display
confirmation
message.
Post Condition: Users password successfully changed.
79
Chapter 5
Testing
1.23.6 Manage Library Clearance

Test Case Name: Manage Library Clearance
Pre-Condition: System should be in running state.
Steps:
No
Steps
Actual Result
Expected Result
1.
User selects the clearance

after login.
System displays clearance

requests.
System will
display clearance
requests.
2.
User selects specific student.
System displays the specific

student information.
System will
display the
specific student
information.
3.
User checks the status of the

student.
System validates the status.
System will
validate status.
4.
User selects the clear

option.

message.
System will
display
confirmation
message.
Post Condition: Library Clearance done successfully.
80
Chapter 5
Testing
1.23.7 Manage Process Application

Test Case Name: Manage Process Application
Steps:
No
Steps
Actual Result
Expected Result
1.
User selects the process

application option after login.
System displays search option.
System will
display search
option.
2.
User enters the information

(roll.no.).
System retrieves specific record.
System will
retrieve specific
record.
User clicks the search

option.
System retrieves matching

records.
System will
retrieve matching
records.
Post Condition: Process Application information retrieved successfully
81
Chapter 5
Testing
1.23.8 Manage Pending Application

Test Case Name: Manage Pending Application
Steps:
No
Steps
Actual Result
Expected Result
1.
pending Application option
after login.
System displays all the pending

requests.
System will
display all the
pending requests.
2.
Administrator checks the

pending application requests.

message.
System will
display
confirmation
message.
Post Condition: Library Pending Application is checked successfully.
82
Chapter 5
Testing
1.23.9 Manage Network Administration

Test Case Name: Manage Network Administrator Clearance
Steps:
No
Steps
Actual Result
Expected Result
1.

after login.

requests.
System will
display clearance
requests.
2.

System will
display the
specific student
information.
3.

student.
System will
validate status.
4.

option.

message.
System will
display
confirmation
message.
Post Condition: Network Administration done Successfully.
83
Chapter 5
Testing
1.23.10
Manage Process Application

Steps:
No
Steps
Actual Result
Expected Result
1.

application option.
System will
display search
option.
2.

(roll. no.).
System will
retrieve specific
record.
sa

option.

records.
System will
retrieve matching
records.
84
Chapter 5
Testing
1.23.11Manage Pending Application

Steps:
No
Steps
Actual Result
Expected Result
1.
after login.

requests.
System will
display all the
pending requests.
2.


message.
System will
display
confirmation
message.
Post Condition: Network Admin Pending Application is checked successfully.
85
Chapter 5
Testing
1.23.12
Manage Hostel Section

Test Case Name: Manage Hostel Clearance
Steps:
No
Steps
Actual Result
Expected Result
1.

after login.

requests.
System will
display clearance
requests.
2.

System will
display the
specific student
information.
3.

student.
System will
validate status.
4.

option.

message.
System will
display
confirmation
message.
Post Condition: Hostel Clearance done successfully.
86
Chapter 5
Testing
1.23.13

Steps:
No
Steps
Actual Result
Expected Result
1.

application option.
System will
display search
option.
2.

(roll.no.).
System will
retrieve specific
record.

option.

records.
System will
retrieve matching
records.
87
Chapter 5
Testing
1.23.14
Manage Pending Application

Steps:
No
Steps
Actual Result
Expected Result
1.
after login.

requests.
System will
display all the
pending requests.
2.


message.
System will
display
confirmation
message.
Post Condition: Hostel Pending Application is checked successfully.
88
Chapter 5
Testing
1.23.15
Manage Accounts Section

Test Case Name: Manage Accounts Clearance
Steps:
No
Steps
Actual Result
Expected Result
1.

after login.

requests.
System will
display clearance
requests.
2.

System will
display the
specific student
information.
3.

student.
System will
validate status.
4.

option.

message.
System will
display
confirmation
message.
Post Condition: Accounts Clearance done successfully.
89
Chapter 5
Testing
1.23.16

Steps:
No
Steps
Actual Result
Expected Result
1.

application option.
System will
display search
option.
2.

(roll. no.).
System will
retrieve specific
record.

option.

records.
System will
retrieve matching
records.
90
Chapter 5
Testing
1.23.17

Steps:
No
Steps
Actual Result
Expected Result
1.
after login.

requests.
System will
display all the
pending requests.
2.


message.
System will
display
confirmation
message.
Post Condition: Accounts Pending Application is checked successfully.
91
Chapter 5
Testing
1.23.18
Manage Examination Section

Test Case Name: Manage Examination Clearance
Steps:
No
Steps
Actual Result
Expected Result
1.

after login.

requests.
System will
display clearance
requests.
2.

System will
display the
specific student
information.
3.

student.
System will
validate status.
4.

option.

message.
System will
display
confirmation
message.
Post Condition: Examination Clearance done successfully.
92
Chapter 5
Testing
1.23.19

Steps:
No
Steps
Actual Result
Expected Result
1.

application option.
System will
display search
option.
2.

(roll. no.).
System will
retrieve specific
record.

option.

records.
System will
retrieve matching
records.
93
Chapter 5
Testing
1.23.20

Steps:
No
Steps
Actual Result
Expected Result
1.
after login.

requests.
System will
display all the
pending requests.
2.


message.
System will
display
confirmation
message.
Post Condition: Exam Pending Application is checked successfully.
94
Chapter 5
Testing
1.23.21

Test Case Name: Manage HOD Clearance
Steps:
No
Steps
Actual Result
Expected Result
1.

after login.

requests.
System will
display clearance
requests.
2.

System will
display the
specific student
information.
3.

student.
System will
validate status.
4.

option.

message.
System will
display
confirmation
message.
Post Condition: HOD Clearance done successfully.
95
Chapter 5
Testing
1.23.22

Steps:
No
Steps
Actual Result
Expected Result
1.

application option.
System will
display search
option.
2.

(roll. no.).
System will
retrieve specific
record.

option.

records.
System will
retrieve matching
records.
96
Chapter 5
Testing
1.23.23

Steps:
No
Steps
Actual Result
Expected Result
1.
after login.

requests.
System will
display all the
pending requests.
2.


message.
System will
display
confirmation
message.
Post Condition: HOD Pending Application is checked successfully.
97
Chapter 5
Testing
CHAPTER 6
Conclusion
98
Chapter 7
User Manual
1.24 Conclusion
We feel very proud after development of University Clearance Workflow

application successfully. Before starting of this project we have theoretical knowledge of
computer science, but it is far away from theory to develop a real life system that
completely fulfill user requirements.
This project will be great benefits of students of COMSATS Institute of Information
Technology to get there degree clearance without wasting time, power and money.
During the development of the project we have achieved the following benefits:
How to interact with user
System analysis and data collection
A good knowledge of system design and modeling
Project management
Latest tools and technologies
Testing strategies
User documentation
99

Thesis

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Thesis

Încărcat de

Drepturi de autor:

Formate disponibile

University Clearance Workflow

Department of Computer Science

COMSATS INSTITUTE OF INFORMATION TECHNOLOGY

University Clearance Workflow

Mr. Shahzad Rizwan

Our supervisor has attested the attached document

We confirm to state that this project is free from any type of

This work, entitled University Clearance Workflow has been

Bachelor in Computer Science

Department of Computer Science

COMSATS INSTITUTE OF INFORMATION TECHNOLOGY

University Clearance Workflow

are Eligible to apply for clearance

Windows 8Professional 64-bit

Corei3, 2.4 GHz, RAM: 6 GB

Need of the Project........................................................................................................ 10

Benefits of proposed system......................................................................................11

Non Functional Requirements...................................................................................14

Use Case Diagram........................................................................................................ 16

Use Case in Detail......................................................................................................... 17

Manage Department Clearance.................................................................................17

Manage Fee Clearance............................................................................................. 17

Manage Hostel Clearance......................................................................................... 17

Manage Library Clearance........................................................................................ 18

Manage Degree Clearance.......................................................................................18

Use Case Description.................................................................................................... 18

Scenario 1: Add New User......................................................................................................... 18

Manage Library Clearance....................................................................................23

Scenario 1: Clearance Application.............................................................................................23

Manage Network Administration............................................................................26

Scenario 1: Clearance Application.............................................................................................26

Scenario 3: Process Application................................................................................................ 28

Manage Hostel Clearance.....................................................................................30

Scenario 1: Clearance Application.............................................................................................30

Scenario 3: Process Application................................................................................................ 31

Manage Account Section.......................................................................................33

Scenario 1: Clearance Application.............................................................................................33

Scenario 3: Process Application................................................................................................ 34

Manage Examination Section................................................................................36

Scenario 1: Clearance Application.............................................................................................36

Scenario 3: Process Application................................................................................................ 37

Manage Head of Department................................................................................39

Scenario 1: Clearance Application.............................................................................................39

Scenario 3: Process Application................................................................................................ 41

System Sequence Diagrams......................................................................................... 44

Clear Student Request..........................................................................................49

Reject Student Request......................................................................................... 50

Forward Student Request......................................................................................51

Manage Network Administrator..............................................................................52

Manage Processed Applications............................................................................53

Manage Pending Applications...............................................................................53

Manage Hostel Clearance.....................................................................................54

Manage Accounts Clearance.................................................................................55

Manage Examination Clearance............................................................................56

Manage Head of Department................................................................................57

Tools and Technologies.................................................................................................63

4.2.2 SQL SEVER 2012......................................................................................................... 63

Software Test Environment....................................................................................67

Manage Library Clearance....................................................................................73

Manage Process Application.................................................................................74

Manage Pending Application.................................................................................75

Manage Network Administration............................................................................76

Manage Process Application.................................................................................77

Manage Pending Application.................................................................................78