Beruflich Dokumente
Kultur Dokumente
Asif Iqbal
Toqeer Hussain
Supervised by:
Mr. Shahzad Rizwan
NUMBER OF
MEMBERS
PROJECT ID
TITLE
SUPERVISOR NAME
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
YES / NO
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
Date: 05-06-2015
External Examiner:
Head of Department:
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:
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
SystemUsed:
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
1.3
Problem Statement........................................................................................................ 10
1.4
Existing System............................................................................................................. 11
1.5
Proposed System.......................................................................................................... 11
1.5.1
1.6
CHAPTER 2.................................................................................................................................. 13
System Analysis............................................................................................................................ 13
1.7
System Analysis............................................................................................................ 14
1.7.1
Functional Requirements...........................................................................................14
1.7.2
1.8
1.9
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
1.9.6
1.9.7
1.9.8
1.9.9
1.10
1.10.1
Manage Users....................................................................................................... 18
Login...................................................................................................................... 20
1.10.3
Forgot Password................................................................................................... 21
1.10.4
Register................................................................................................................. 22
1.10.5
Reject Application............................................................................................... 27
Reject Application............................................................................................... 31
Reject Application............................................................................................... 34
Scenario 2:
Reject Application............................................................................................... 37
Reject Application............................................................................................... 40
Sequence Diagram........................................................................................................ 44
1.12
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
1.12.6
1.12.7
1.12.8
1.12.9
1.12.10
1.12.11
1.12.12
1.12.13
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
1.18.1
ASP.NET................................................................................................................ 63
10
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
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
1.23.7
1.23.8
1.23.9
1.23.10
1.23.11
1.23.12
1.23.13
1.23.14
1.23.15
1.23.16
1.23.17
1.23.18
1.23.19
1.23.20
1.23.21
1.23.22
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.
Ambiguity.
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.
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.
Hostel Clearance.
Library clearance.
Fee Clearance.
Academic Clearance.
Degree Section.
15
Chapter 1
1.5.1
Introduction
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
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.
Hostel Clearance.
Library clearance.
Fee Clearance.
Academic Clearance.
Degree Section.
16
CHAPTER 2
System Analysis
17
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
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
19
20
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
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
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
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
clerk for the clearance. The process is then checked against the concerned student that
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
clerk for the clearance. The process is then checked against the concerned student that
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.
Scenario 2:
Goal in context
Pre-Condition
Failed Condition
Primary Actor
Admin
Trigger Event
Actor
System response
Admin
enter
the
information
4
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).
2. The use case continues at step 3.
5A. Username or email is already registered
1. System shows the error message.
2. Process terminates.
23
Search User.
Pre-Condition
Failed Condition
Primary Actor
User
Administrator selects pending request option.
Trigger Event
Actor
System response
Administrator selects
pending request option.
Extension:
1A.Administrator selects wrong option.
1.10.2 Login
Login.
Pre-Condition
and
Failed Condition
and
Primary Actor
User.
24
Trigger Event
Actor
System response
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
Forgot password.
Pre-Condition
User is registered.
System should be in running state
Failed Condition
Users password
changed.
Primary Actor
User.
Trigger Event
not
successfully
Actor
System response
25
User
selects
password option.
2
Extension:
3A.User gives incomplete information
1. System shows error message (e.g. empty post).
2. The use case continues at step 3.
3B.User gives wrong information
1. System shows error message (e.g. empty post).
2. The use case continues at step 3.
1.10.4 Register
Register
Pre-Condition
Failed Condition
User
registration
successfully.
Primary Actor
User.
User selects Register option.
Trigger Event
not
done
Actor
System response
26
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.User gives incomplete information
1. System shows error message (e.g. missing address).
2. The use case continues at step 3.
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:
Scenario 2:
Pre-Condition
Administrator is authenticated.
System should be in running state.
Failed Condition
Library clearance
successfully.
Primary Actor
User.
Trigger Event
is
not
done
27
Actor
System response
Extension:
4A. User selects problem option.
1. Problem is explained.
2. Delivery message to the respective student.
4B.User selects cancel option.
1. The use case continues at step 1.
Administrator
application.
can
view
reject
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
Actor
System response
28
Administrator
hits
Administrator
application.
can
view
process
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
Actor
Administrator
System response
hits
29
Administrator
application.
can
view
pending
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
Actor
System response
Scenario 2:
Pre-Condition
Administrator is authenticated.
30
Failed Condition
Primary Actor
User.
Trigger Event
Actor
System response
Extension:
4A. User selects problem option.
3. Problem is explained.
4. Delivery message to the respective student.
4B.User selects cancel option.
2. The use case continues at step 1.
Scenario 2:
Reject Application
Administrator
application.
can
view
reject
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
Actor
Administrator
System response
hits
Administrator
application.
can
view
process
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
Actor
Administrator
System response
hits
32
33
Administrator
application.
can
view
pending
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
Actor
System response
34
Scenario 2:
Pre-Condition
Administrator is authenticated.
System should be in running state.
Failed Condition
Hostel clearance
successfully.
Primary Actor
User.
Trigger Event
is
not
done
Actor
System response
35
Extension:
4A. User selects problem option.
5. Problem is explained.
6. Delivery message to the respective student.
4B.User selects cancel option.
3. The use case continues at step 1.
Scenario 2:
Reject Application
Administrator
application.
can
view
reject
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
Actor
Administrator
System response
hits
Administrator
application.
can
view
process
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
Actor
Administrator
System response
hits
Administrator
application.
can
view
pending
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
Actor
System response
37
Scenario 2:
Pre-Condition
Administrator is authenticated.
System should be in running state.
Accounts
clearance
successfully.
Failed Condition
Accounts clearance
successfully.
Primary Actor
User.
Trigger Event
is
is
done
not
done
Actor
System response
38
Extension:
4A. User selects problem option.
7. Problem is explained.
8. Delivery message to the respective student.
4B.User selects cancel option.
4. The use case continues at step 1.
Scenario 2:
Reject Application
Administrator
application.
can
view
reject
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
Actor
Administrator
System response
hits
Administrator
application.
can
view
process
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
Actor
Administrator
System response
hits
Administrator
application.
can
view
pending
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
Actor
System response
40
41
Scenario 2:
Pre-Condition
Administrator is authenticated.
System should be in running state.
Failed Condition
Exams clearance
successfully.
Primary Actor
User.
Trigger Event
is
not
done
Actor
System response
42
Extension:
4A. User selects problem option.
9. Problem is explained.
10. Delivery message to the respective student.
4B.User selects cancel option.
5. The use case continues at step 1.
Scenario 2:
Reject Application
Administrator
application.
can
view
reject
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
Actor
Administrator
System response
hits
Administrator
application.
can
view
process
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
Actor
Administrator
System response
hits
Administrator
application.
can
view
pending
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
Actor
System response
44
45
1.10.10
Scenario 2:
Pre-Condition
Administrator is authenticated.
System should be in running state.
Failed Condition
HOD clearance
successfully.
Primary Actor
User.
Trigger Event
is
not
done
Actor
System response
46
Extension:
4A. User selects problem option.
11. Problem is explained.
12. Delivery message to the respective student.
4B.User selects cancel option.
6. The use case continues at step 1.
Scenario 2:
Reject Application
Administrator
application.
can
view
reject
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
Actor
Administrator
System response
hits
47
Administrator
application.
can
view
process
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
Actor
Administrator
System response
hits
Administrator
application.
can
view
pending
Pre-Condition
Failed Condition
Primary Actor
Administrator.
Trigger Event
48
Actor
System response
49
CHAPTER 3
System Design
50
Chapter 3
System Design
1.12.1 Login
51
Chapter 3
System Design
52
Chapter 3
System Design
53
Chapter 3
System Design
54
Chapter 3
System Design
55
Chapter 3
System Design
56
Chapter 3
System Design
57
Chapter 3
System Design
58
Chapter 3
System Design
59
Chapter 3
System Design
1.12.10
60
Chapter 3
System Design
61
Chapter 3
1.12.12
System Design
62
Chapter 3
1.12.13
System Design
63
Chapter 3
1.12.14
System Design
64
Chapter 3
System Design
65
Chapter 3
System Design
66
Chapter 3
System Design
Chapter 3
System Design
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.
several features to standard SQL, including transaction control, exception and error
handling, row processing, and declared variables..
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
73
Chapter 5
Testing
1.22
74
Chapter 5
Testing
Steps
1.
2.
Actual Result
Expected Result
1.23.2 Register
Steps
Actual Result
Expected Result
1.
75
Chapter 5
Testing
2.
3.
76
Chapter 5
Testing
Steps
Actual Result
Expected Result
1.
System will
displays all user
lists.
2.
77
Chapter 5
Testing
Steps
Actual Result
Expected Result
1.
System display
information of
user in updatable
format.
2.
System display
user information
in updateable
format.
3.
System will
validate the enter
information.
4.
System will
display
confirmation
message.
78
Chapter 5
Testing
Steps
Actual Result
Expected Result
1.
System will
prompt user to
enter his/her
email.
2.
System will
validate entered
information and
display
confirmation
message.
79
Chapter 5
Testing
Steps
Actual Result
Expected Result
1.
System will
display clearance
requests.
2.
System will
display the
specific student
information.
3.
System will
validate status.
4.
System will
display
confirmation
message.
80
Chapter 5
Testing
Steps
Actual Result
Expected Result
1.
System will
display search
option.
2.
System will
retrieve specific
record.
System will
retrieve matching
records.
81
Chapter 5
Testing
Steps
Actual Result
Expected Result
1.
Administrator selects
pending Application option
after login.
System will
display all the
pending requests.
2.
System will
display
confirmation
message.
82
Chapter 5
Testing
Steps
Actual Result
Expected Result
1.
System will
display clearance
requests.
2.
System will
display the
specific student
information.
3.
System will
validate status.
4.
System will
display
confirmation
message.
83
Chapter 5
Testing
1.23.10
Steps
Actual Result
Expected Result
1.
System will
display search
option.
2.
System will
retrieve specific
record.
sa
System will
retrieve matching
records.
84
Chapter 5
Testing
Steps
Actual Result
Expected Result
1.
Administrator selects
pending Application option
after login.
System will
display all the
pending requests.
2.
System will
display
confirmation
message.
85
Chapter 5
Testing
1.23.12
Steps
Actual Result
Expected Result
1.
System will
display clearance
requests.
2.
System will
display the
specific student
information.
3.
System will
validate status.
4.
System will
display
confirmation
message.
86
Chapter 5
Testing
1.23.13
Steps
Actual Result
Expected Result
1.
System will
display search
option.
2.
System will
retrieve specific
record.
System will
retrieve matching
records.
87
Chapter 5
Testing
1.23.14
Steps
Actual Result
Expected Result
1.
Administrator selects
pending Application option
after login.
System will
display all the
pending requests.
2.
System will
display
confirmation
message.
88
Chapter 5
Testing
1.23.15
No
Steps
Actual Result
Expected Result
1.
System will
display clearance
requests.
2.
System will
display the
specific student
information.
3.
System will
validate status.
4.
System will
display
confirmation
message.
89
Chapter 5
Testing
1.23.16
Steps
Actual Result
Expected Result
1.
System will
display search
option.
2.
System will
retrieve specific
record.
System will
retrieve matching
records.
90
Chapter 5
Testing
1.23.17
No
Steps
Actual Result
Expected Result
1.
Administrator selects
pending Application option
after login.
System will
display all the
pending requests.
2.
System will
display
confirmation
message.
91
Chapter 5
Testing
1.23.18
Steps
Actual Result
Expected Result
1.
System will
display clearance
requests.
2.
System will
display the
specific student
information.
3.
System will
validate status.
4.
System will
display
confirmation
message.
92
Chapter 5
Testing
1.23.19
Steps
Actual Result
Expected Result
1.
System will
display search
option.
2.
System will
retrieve specific
record.
System will
retrieve matching
records.
93
Chapter 5
Testing
1.23.20
Steps
Actual Result
Expected Result
1.
Administrator selects
pending Application option
after login.
System will
display all the
pending requests.
2.
System will
display
confirmation
message.
94
Chapter 5
Testing
1.23.21
Steps
Actual Result
Expected Result
1.
System will
display clearance
requests.
2.
System will
display the
specific student
information.
3.
System will
validate status.
4.
System will
display
confirmation
message.
95
Chapter 5
Testing
1.23.22
Steps
Actual Result
Expected Result
1.
System will
display search
option.
2.
System will
retrieve specific
record.
System will
retrieve matching
records.
96
Chapter 5
Testing
1.23.23
Steps
Actual Result
Expected Result
1.
Administrator selects
pending Application option
after login.
System will
display all the
pending requests.
2.
System will
display
confirmation
message.
97
Chapter 5
Testing
CHAPTER 6
Conclusion
98
Chapter 7
User Manual
1.24 Conclusion
Project management
Testing strategies
User documentation
99