WEB BASED STUDENT REGISTRATION SYSTEM

A PROJECT REPORT SUBMITTED BY

S.G.PERERA (S/18/495)

to the
DEPARTMENT OF STATISTICS AND COMPUTER SCIENCE

in partial fulfillment of the requirement

for the award of the degree of

BATCHER OF SCIENCE

of the

UNIVERSITY OF PERADENIYA

SRI LANKA

2018
Table of Contents
List of Tables .......................................................................................................................................... iv

List of Figures .......................................................................................................................................... v

Chapter 1................................................................................................................................................. 1

INTRODUCTION ................................................................................................................................... 1

Description of the system ............................................................................................................... 1

Objectives of the project................................................................................................................. 1

Problem domain.............................................................................................................................. 1

Chapter 2................................................................................................................................................. 3

BACKGROUND ..................................................................................................................................... 3

Existing system ................................................................................................................................ 3

Identified attributes of the existing system ................................................................................ 3

Shortcomings of the existing system .......................................................................................... 6

How does the proposed system fix the problems in the existing system? ................................ 6

Chapter 3................................................................................................................................................. 7

REQUIREMENT SPECIFICATION ........................................................................................................... 7

System functions ............................................................................................................................. 7

Use case diagram ........................................................................................................................ 8

Use cases in expanded format .................................................................................................... 9

System Requirements ................................................................................................................... 17

Hardware .................................................................................................................................. 17

Software .................................................................................................................................... 17

Chapter 4............................................................................................................................................... 18

DESIGN SPECIFICATIONS ................................................................................................................... 18

THREE TIRE ARCHITECTURE .......................................................................................................... 18

DATA FLOW MODEL ...................................................................................................................... 19

Data Flow Diagram .................................................................................................................... 19

ii
 Database design ........................................................................................................................ 20

ER diagram ................................................................................................................................ 20

Relational diagram .................................................................................................................... 21

Security ..................................................................................................................................... 22

Chapter 5............................................................................................................................................... 23

RESULTS AND DISCUSSION................................................................................................................ 23

CONCLUSION ................................................................................................................................. 23

Advantages of the System ........................................................................................................ 23

Further Developments .............................................................................................................. 23

References ............................................................................................................................................ 24

iii
 List of Tables
Table 1 : Description about each degree ................................................................................................ 2

Table 2 : Identified attributes of the existing system ............................................................................. 6

Table 3 : Manage Student ........................................................................................................................ 9

Table 4 : Manage Subject ...................................................................................................................... 10

Table 5: Manage Combinations ............................................................................................................ 11

Table 6: Manage course ........................................................................................................................ 12

Table 7: Manage results ........................................................................................................................ 13

Table 8: Manage Lecturer ..................................................................................................................... 14

Table 9 : View Results ........................................................................................................................... 15

Table 10 : Clear results .......................................................................................................................... 15

Table 11 : Generate Transcripts ............................................................................................................ 16

Table 12: Component of DFD ................................................................................................................ 19

iv
 List of Figures
Figure 1 : Use case diagram .................................................................................................................... 8

Figure 2: Three tire architecture ........................................................................................................... 18

Figure 3 : ER-Diagram............................................................................................................................ 20

Figure 4 : Relational Diagram ................................................................................................................ 21

v
 Chapter 1

INTRODUCTION

Description of the system

This is an information system developed for the course unit administration of the faculty of
Science of the University of Peradeniya so that it deals with many students’ records (specially
with their results), subject records and their meta data. The course unit administration is
responsible for handling all the students’ records, subject records and the generation of the
transcript. This system facilitates the information retrieval, analysis of the students’ results
and generates a transcript for each student of the faculty.

Objectives of the project

To develop a computer based software system to provide the following for the course unit
administration.

 Provide management information for decision making

 Provide easy accessible information for all appropriate

 Provide information that is accurate, secure, consistent, timely, reliable and complete

 Reduce administrative cost

 Reduce the paper driven aspects of the existing system

Problem domain

More than 2000 students enter the University of Peradeniya from different streams in each
year. They enter for different faculties based on their stream and their Z – score. From them
about 650 students enter the faculty of Science. This is the only faculty in the University that
recruits students from more than one stream. That is students enter to the faculty of Science

“WEB BASED STUDENT REGISTRATION SYSTEM” 1

from Physical, Biological, Arts and Commerce streams. The reason for this is faculty of Science
offers five types of B.Sc. degrees. They are General, Special, Applied Sciences, Computation
and Management and Statistics and Operations Research.

Degree Title Duration Allowed Streams Description

Basic degree with two or three

B.Sc. General 3 years Physical, Biological
subjects
Offered for best students after
B.Sc. Special 4 years Physical, Biological
two years to specialize one
B.Sc. Applied After thesubject
completion of
4 years Physical, Biological
Sciences general degree
B.Sc. Computation Physical, Biological, Offered for students chosen
4 years
and Management Arts, Commerce from their Z - score
B.Sc. Statistics and Offered for students chosen
4 years Physical
Operations Research from their Z - score
Table 1 : Description about each degree

Once they are entered to the faculty they follow a foundation course series. Some foundation
courses vary according to the students’ type. After the foundation period the authority
provides a combination based on the students’ selection and Z – score. A combination consists
with three subjects (For general students only). At the end of the 1st year a student can drop
one subject and complete the degree in two subjects. At the end of the 2nd year some students
are selected for the Special degree programme based on their GPA. After the completion of
the General degree a student get the opportunity to follow the Applied Sciences degree
programme. The SOR and CM students will not be given the above opportunities because
their degree has four year duration and based on fixed subject area.

“WEB BASED STUDENT REGISTRATION SYSTEM” 2

 Chapter 2

BACKGROUND
Existing system

The faculty of Science course unit administration maintains a database designed using
Microsoft Access. The database is used to store every detail of the student, courses and the
scholarships. The database was designed only to facilitate the information retrieval. It was
not designed to support the analysis of the students’ results. Also they are using a system
developed using Visual Basic in order to calculate the students’ GPA. The analysis of the
students’ results is a manual process which is done under the supervision of each department.
The following tables being used by the administration to generate transcripts for all students.

Identified attributes of the existing system

Column Name Description Data Type Length

PASS OUT STUDENTS

Approval of Senate
Confirmed Text 3
(Yes/No)
Acc_Year Academic year Number

Effective Effective date Date

Poac_Year Proper academic year Number

Pass Class Text 30

GPA Grade Point Average Number

Batch Batch Text 5

Category General/Special/Applied Text 20

Reg_No Registration number Text 10

Title Mr./Miss Text 5

Name Name with initials Text 50

“WEB BASED STUDENT REGISTRATION SYSTEM” 3

 Full Name Full name Text 100

Postpone Postponed years Number

Com_No Combination number Number

Sp_Sub Special subject Text 25

L1001 100 level subject 1 Text 25

L1002 100 level subject 2 Text 25

L1003 100 level subject 3 Text 25

L2001 200 level subject 1 Text 25

L2002 200 level subject 2 Text 25

L2003 200 level subject 3 Text 25

L3001 300 level subject 1 Text 25

L3002 300 level subject 2 Text 25

L3003 300 level subject 3 Text 25

Scoh1 Scholarship 1 Text 10

Scoh2 Scholarship 2 Text 10

Scoh3 Scholarship 3 Text 10

Repeat Repeat Times Number

PASS OUT GRADES

Enter_date_time Entered date time Date time

Acyear Academic year Number

Semester Semester Number

Batch Batch Text 5

Reg_No Registration number Text 10

“WEB BASED STUDENT REGISTRATION SYSTEM” 4

 Co-Code Course code Text 10

Grade Grade Text 2

Remark Repeat/Proper Text 10

Student Selection
Stuchoice Text 3
(Yes/No)
Modified Modified Text 5

COURSE

Sub_Code Subject code Text 10

Sup_Sub Supplementary Subject Text 10

Batch Batch Text 5

Pro_Co_Code Proper course code Text 10

Category Category Text 10

Credits Number of credits Number

General Compulsory
Gen_Compulsory Text 3
(Yes/No)
Special Compulsory
Spe_Compulsory Text 3
(Yes/No)
Remark Remark Text 100

Acyear Academic year Number

Semester Semester Number

Group Group Text 10

Type Foundation Text 10

SCHOLARSHIP

Code Scholarship code Text 10

Title Scholarship name Text 100

Subject Subject Text 25

“WEB BASED STUDENT REGISTRATION SYSTEM” 5

 Table 2 : Identified attributes of the existing system

Shortcomings of the existing system

 Less security

 High data redundancy

 Paper records are also kept

 More space required

 Time consuming analysis process

 Time consumption is high

How does the proposed system fix the problems in the existing system?
 Since a user name and a password is given to the user security is ensured

 The database is normalized and designed using relational model in order to reduce the
data redundancy, increase the consistency of the database and save the resources

 The database is designed in such a way that it support the analysis process

“WEB BASED STUDENT REGISTRATION SYSTEM” 6

 Chapter 3

REQUIREMENT SPECIFICATION
System functions

Once a student has registered for the faculty and the courses a record is made by the course
unit administration. Then the details of the student should be added to the system because
it does not support student registration and course registration.

The system is responsible for following tasks,

 Add student details

 Edit/Delete student details

 Add subject details

 Edit/Delete subject details

 Add combination details

 Edit/Delete combination delete

 Add course details

 Edit/Delete course details

 Add research details

 Edit/Delete research details

 Add student results

 Edit/Delete student results

 Add/Edit lecturer details

 View all results of a specific course

 Delete records of a specific year

 Generation of transcript

“WEB BASED STUDENT REGISTRATION SYSTEM” 7

Use case diagram

<<include>>
Add Student
<<include>> Delete Student

Manage Student <<include>> <<include>>

Update Student Find Student

View Results <<include>>Add Student

Delete Student
<<include>>

<<include>> <<include>>
Manage Subject Find Student
Update Student

Clear Record <<include>>

Add Combination
<<include>> Delete Combination

Manage Combination <<include>> <<include>>

Update Combination Find Combination

Administrator
<<include>>
Add Course
<<include>> Delete Course

Manage Course <<include>> <<include>>

Update Course Find Course

Generate Transcript
<<include>> Add Results
<<include>> Delete Results

Manage Results
<<include>> <<include>>
Update Results Find Results

<<include>>
Add Lecturer

<<include>>
Delete Lecturer

Manage Lecturer
<<include>>
Figure 1 : Use case diagram <<include>>
Update Lecturer Find Lecturer

“WEB BASED STUDENT REGISTRATION SYSTEM” 8

Use cases in expanded format
Use Case : Manage Student
Actors : Administrator
General Description/Goal: The Manage Student use case enables administrator to add a
new Student to the system with its properties or edit Student details.
Preconditions : The administrator has to login to the application
Flow of Events
Steps of Basic Flow :
1. Administrator can select either
1. Add a new Student or 2. Update a Student or 3. Delete a Student
Alternative Flows :
1.1 Add a new Student
Actor Action System Response
1.1.1 Selects Add Student option
1.1.2 Display a Add Student form
1.1.3 Enters the Student details and submit
1.1.4 Validate and update the database
Exceptional Courses : 1.1.4 – Incomplete details or duplicate Students will generate an
error
1.2 Update a Student
Actor Action System Response
1.2.1 Selects Update Student option
1.2.2 Find a Student record and view
1.2.3 Edits the Student details and submit
1.2.4 Validate and update the database
Sub flow : 1.2.2 Find Student Record
1.2.2.1 View a form to get Student regno
1.2.2.2 Enters the Student regno and
submit
1.2.2.3 Find match Student detail and
display
Exceptional Courses : 1.2.2 – If the Students’ regno mismatched will generate an error
1.3 Delete a Student
Actor Action System Response
1.3.1 Selects Delete Student option
1.3.2 Display Delete Student form
1.3.3 Enters the Student regno and submit
1.3.4 Delete the Student from the database
Table 3 : Manage Student

“WEB BASED STUDENT REGISTRATION SYSTEM” 9

 Use Case : Manage Subject
Actors : Administrator
General Description/Goal: The Manage Subject use case enables administrator to add a
new Subject to the system with its properties or edit Subject details.
Preconditions : The administrator has to login to the application
Flow of Events
Steps of Basic Flow :
1. Administrator can select either
1. Add a new Subject or 2. Update a Subject or 3. Delete a Subject
Alternative Flows :
1.1 Add a new Subject
Actor Action System Response
1.1.1 Selects Add Subject option
1.1.2 Display a Add Subject form
1.1.3 Enters the Subject details and submit
1.1.4 Validate and update the database
Exceptional Courses : 1.1.4 – Incomplete details or duplicate Subjects will generate an
error
1.2 Update a Subject
Actor Action System Response
1.2.1 Selects Update Subject option
1.2.2 Find a Subject record and view
1.2.3 Edits the Subject details and submit
1.2.4 Validate and update the database
Sub flow : 1.2.2 Find Subject Record
1.2.2.1 View a form to get Subject
1.2.2.2 Enters the Subject and submit
1.2.2.3 Find match Subject detail and
display will generate an error
Exceptional Courses : 1.2.2 – If the Subject mismatched
1.3 Delete a Subject
Actor Action System Response
1.3.1 Selects Delete Subject option
1.3.2 Display Delete Subject form
1.3.3 Enters the Subject and submit
1.3.4 Delete the Subject from the database
Table 4 : Manage Subject

“WEB BASED STUDENT REGISTRATION SYSTEM” 10

 Use Case : Manage Combination
Actors : Administrator
General Description/Goal: The Manage Combination use case enables administrator to
add a new Combination to the system with its properties or edit Combination details.
Preconditions : The administrator has to login to the application
Flow of Events
Steps of Basic Flow :
1. Administrator can select either
1. Add Combination or 2. Update Combination or 3. Delete Combination
Alternative Flows :
1.1 Add Combination
Actor Action System Response
1.1.1 Selects Add Combination option
1.1.2 Display a Add Combination form
1.1.3 Enters the Combination details and
submit 1.1.4 Validate and update the database
Exceptional Courses : 1.1.4 – Incomplete details or duplicate Combination will generate
an
1.2error
Update Combination
Actor Action System Response
1.2.1 Selects Update Combination option
1.2.2 Find a Combination record and view
1.2.3 Edits the Combination details and
submit 1.2.4 Validate and update the database
Sub flow : 1.2.2 Find Combination Record
1.2.2.1 View a form to get combno
1.2.2.2 Enters the combno and submit
1.2.2.3 Match Combination detail and
display will generate an error
Exceptional Courses : 1.2.2 – If the combno mismatched
1.3 Delete Combination
Actor Action System Response
1.3.1 Selects Delete Combination option
1.3.2 Display Delete Combination form
1.3.3 Enters the combno and submit
1.3.4 Delete the Combination from
Table 5: Manage database
Combinations

“WEB BASED STUDENT REGISTRATION SYSTEM” 11

 Use Case : Manage Course
Actors : Administrator
General Description/Goal: The Manage Course use case enables administrator to add a
new Course to the system with its properties or edit Course details.
Preconditions : The administrator has to login to the application
Flow of Events
Steps of Basic Flow :
1. Administrator can select either
1. Add a new Course or 2. Update a Course or 3. Delete a Course
Alternative Flows :
1.1 Add a new Course
Actor Action System Response
1.1.1 Selects Add Course option
1.1.2 Display a Add Course form
1.1.3 Enters the Course details and submit
1.1.4 Validate and update the database
Exceptional Courses : 1.1.4 – Incomplete details or duplicate Course will generate an error
1.2 Update a Course
Actor Action System Response
1.2.1 Selects Update Course option
1.2.2 Find a Course record and view
1.2.3 Edits the Course details and submit
1.2.4 Validate and update the database
Sub flow : 1.2.2 Find Course Record
1.2.2.1 View a form to get course code
1.2.2.2 Enters the course code and submit
1.2.2.3 Find match Course detail and display
Exceptional Courses : 1.2.2 – If the course code mismatched will generate an error
1.3 Delete a Course
Actor Action System Response
1.3.1 Selects Delete Course option
1.3.2 Display Delete Course form
1.3.3 Enters the Course and submit
1.3.4 Delete the Course from the database
Table 6: Manage course

“WEB BASED STUDENT REGISTRATION SYSTEM” 12

 Use Case : Manage Results
Actors : Administrator
General Description/Goal: The Manage Results use case enables administrator to add a
new Results to the system with its properties or edit Results details.
Preconditions : The administrator has to login to the application
Flow of Events
Steps of Basic Flow :
1. Administrator can select either
1. Add Results or 2. Update Results or 3. Delete Results
Alternative Flows :
1.1 Add Results
Actor Action System Response
1.1.1 Selects Add Results option
1.1.2 Display a Add Results form
1.1.3 Enters the course code, regno and
results details and submit 1.1.4 Validate and update the database
Exceptional Courses : 1.1.4 – Incomplete details or duplicate regno will generate an error
1.2 Update Results
Actor Action System Response
1.2.1 Selects Update Results option
1.2.2 Find a Results record and view
1.2.3 Edits the Results details and submit
1.2.4 Validate and update the database
Sub flow : 1.2.2 Find Results Record
1.2.2.1 View a form to get course code,
1.2.2.2 Enters the course code, regno and regno
submit 1.2.2.3 Find match Results detail and
Exceptional Courses : 1.2.2 – If the course codedisplay
and regno mismatched will generate an
error
1.3 Delete Results
Actor Action System Response
1.3.1 Selects Delete Results option
1.3.2 Display Delete Results form
1.3.3 Enters the course code, regno and
submit 1.3.4 Delete the Results from the database
Table 7: Manage results

“WEB BASED STUDENT REGISTRATION SYSTEM” 13

 Use Case : Manage Lecturer
Actors : Administrator
General Description/Goal: The Manage Lecturer use case enables administrator to add a
new Lecturer to the system with its properties or edit Lecturer details.
Preconditions : The administrator has to login to the application
Flow of Events
Steps of Basic Flow :
1. Administrator can select either
1. Add a new Lecturer or 2. Update a Lecturer or 3. Delete a Lecturer
Alternative Flows :
1.1 Add a new Lecturer
Actor Action System Response
1.1.1 Selects Add Lecturer option
1.1.2 Display a Add Lecturer form
1.1.3 Enters the Lecturer details and submit
1.1.4 Validate and update the database
Exceptional Courses : 1.1.4 – Incomplete details or duplicate Lecturer will generate an
error
1.2 Update a Lecturer
Actor Action System Response
1.2.1 Selects Update Lecturer option
1.2.2 Find a Lecturer record and view
1.2.3 Edits the Lecturer details and submit
1.2.4 Validate and update the database
Sub flow : 1.2.2 Find Lecturer Record
1.2.2.1 View a list of Lecturers
1.2.2.2 Selects the Lecturer and submit
1.2.2.3 Find match Lecturer detail and
display
Exceptional Courses : 1.2.4 – Incomplete details will generate an error
1.3 Delete a Lecturer
Actor Action System Response
1.3.1 Selects Delete Lecturer option
1.3.2 Display list of Lecturers
1.3.3 Selects the Lecturer and submit
1.3.4 Delete the Lecturer from the database
Table 8: Manage Lecturer

“WEB BASED STUDENT REGISTRATION SYSTEM” 14

 Use Case : View Results
Actors : Administrator
Purpose : View Results of a specific Course
Overview: The View Results use case enables administrator to view all the Results
entered to a specific Course. This gives the administrator a chance to check whether the
results were entered accurately. Since the results are generated as a report a printout of
the result sheet can also be taken.
Preconditions : The administrator has to login to the application
Flow of Events
Actor Action System Response
1. Selects View Results option
2. Display a View Results form
3. Enters the course code and submit
4. Validate and view the Results
Exceptional Courses : 4 – Incomplete details will generate an error
Table 9 : View Results

Use Case : Clear Data

Actors : Administrator
Purpose : Clear Student records of a specific year
Overview: The Clear Data use case enables administrator to delete records of a specific
year. This gives the administrator to free some space in the database. This deletes only
the student records of a specific year.
Preconditions : The administrator has to login to the application
Flow of Events
Actor Action System Response
1. Selects Clear Data option
2. Display a Clear Data form
3. Enters the year and submit
4. Validate and delete the records
Exceptional Courses : 4 – Incomplete details will generate an error
Table 10 : Clear results

“WEB BASED STUDENT REGISTRATION SYSTEM” 15

 Use Case : Generate Transcript
Actors : Administrator
General Description/Goal: The Generate Transcript use case enables administrator to
generate a Transcript for every Students.
Preconditions : The administrator has to login to the application
Flow of Events
Steps of Basic Flow :
1. Administrator can select either
1. Final Transcript or 2. Partial Transcript
Alternative Flows :
1.1 Final Transcript
Actor Action System Response
1.1.1 Selects Generate Transcript option
1.1.2 Display a Generate Transcript form
1.1.3 Enters the regno, effective date and
select Final Transcript and submit 1.1.4 Validate and generates the Final
Transcript
Exceptional Courses : 1.1.4 – Incomplete details will generate an error
1.2 Partial Transcript
Actor Action System Response
1.2.1 Selects Generate Transcript option
1.2.2 Display a Generate Transcript form
1.2.3 Enters the regno, effective date and
select Final Transcript and submit 1.2.4 Validate and generates the Partial
Transcript
Exceptional Courses : 1.2.4 – Incomplete details will generate an error
Table 11 : Generate Transcripts

“WEB BASED STUDENT REGISTRATION SYSTEM” 16

System Requirements

Hardware
 1 GHz or Higher Processor

 512 MB or Higher RAM

 40 MB HDD Space

 Printer

Software
 Windows XP/ Windows Vista

 .NET 2.0 Platform or Higher Version

 Microsoft SQL Server 2005

“WEB BASED STUDENT REGISTRATION SYSTEM” 17

 Chapter 4

DESIGN SPECIFICATIONS
THREE TIRE ARCHITECTURE

Here the three tire architecture is used to design the system.

Web interface
Client Tire

Application (ASP.NET/C#)
Middle Tire

Resource Tier Database

SQL Server 2005

Figure 2: Three tire architecture

“WEB BASED STUDENT REGISTRATION SYSTEM” 18

DATA FLOW MODEL

Data flow model can be explained by using DFD (data flow diagram).

Data Flow Diagram

DFD can be used to provide a clear representation of any function. It illustrates how data is process
by the System in terms of input and outputs. There are two methods to draw DFD. Those are
Yourdon & Coad method and Gane & Sarson method. Gane & Sarson method is used for draw DFD.

Component Description Graphical diagram

It shows a transformation of data flows

within the system. Process is a system
Process function
<Name>

External They represent the objects outside the

system and they are sources and destination <Name>
Entity of a data flow

Data It is a hold in place for information with in

the system. <Name>
Stores

Data They are pipelines through which

information flows
flows

Resource It shows flow any physical material

flow <resource>

Table 12: Component of DFD

“WEB BASED STUDENT REGISTRATION SYSTEM” 19

Database design

ER diagram

Figure 3 : ER-Diagram

“WEB BASED STUDENT REGISTRATION SYSTEM” 20

Relational diagram

Student Student_Subject
RegNo RegNo
Name SubjectNo
Address Type
Type
Sex
Year Combination Combination_Subject
Degree CombinationNo CombinationNo
Special_Subject SubjectNo
Combination_No

Course_Subject
CourseCode
SubjectNo

Student_Course
RegNo Course Subject
CourseCode CourseCode SubjectNo
Result Name Name
Repeat Credits
Semester Type
Level Compulsory_SOR
Followed_Level Compulsory_General
Compulsory_Special
Compulsory_Applied
Compulsory_CM_Arts
Compulsory_CM_Physical
Compulsory_CM_Biological Lecturer
Compulsory_CM_Commerce NIC
Lecturer_Course Name
NIC Department
CourseCode Telephone_No
Figure 4 : Relational Diagram

“WEB BASED STUDENT REGISTRATION SYSTEM” 21

Security
The Security is not a big issue in the course unit environment because the course unit staff
members are well educated and responsible people. Moreover there are three employees
work at the course unit and the System Analyst has a very good knowledge in IT whereas the
other two assistants have an acceptable knowledge in IT. Also the system is developed only
to the use of the course unit administration. Since this system is a standalone system and
used only by course unit staff an outsider has a very low chance of breaching into the system.
The database cannot be accessed by two users at the same time because the system supports
only to a one user. Therefore the errors occur due to the data sharing by many users have
been canceled. Therefore a single username and a password is given to the user because not
much security is needed for this system.

“WEB BASED STUDENT REGISTRATION SYSTEM” 22

 Chapter 5

RESULTS AND DISCUSSION

CONCLUSION

The project commenced by conducting a study on the current system. This was done in three stages.
First interviewed and discussed with the relevant client [Science Faculty IT Staff]. Web base system
development strategy is used to develop the system. Being involved in a project of this stature has
not only given us a wider experience of software of development but it has broadened our horizons
on both educational and social front. Techniques used in the production of this system will inevitably
be valuable for any work that we do in the future. Learning the value of correct planning followed by
analysis and design techniques has given us the good base to work from. The knowledge acquired
from software engineering, database management system and object oriented system development
was put in to practice to do the study of the current system.

After doing a postmortem on my working methodology and documents following advantages and
drawbacks were detected.

Advantages of the System

1. Since there is no such a web-based system available in the faculty of science, this can be
used to simplify the work.
2. Easy to use graphical user interfaces.
3. Reduces the unnecessary delay, uncertainty, and imperfect information of the existing
Manual System.
4. Provide security and reliability for data.

Further Developments
There are many things can be enhanced.

1. The GUI design can made more attractive. So that it can gain more traffic to the site.
2. Add more Facilities to both students and teachers
3. The efficiency can be improved : Database connection can be pooled to minimize the system
overhead

“WEB BASED STUDENT REGISTRATION SYSTEM” 23

 References
http://www.w3schools.com [2018]

http://www.asp.net/learn/[2018]

http://www.codeproject.com/[2018]

“WEB BASED STUDENT REGISTRATION SYSTEM” 24

 F
A
functions ....................................................................... 12
ARCHITECTURE ............................................................. 23

S
D
Security ......................................................................... 27
Data flow model ........................................................... 24

“WEB BASED STUDENT REGISTRATION SYSTEM” 25