Report Third Page

ONLINE COLLEGE STUDENT DATABASE MANAGEMENT SYSTEM
CHAPTER 01
INTRODUCTION
An Online College Student Database Management is a System that manages the
records of student regarding Attendance, IA Marks, Units, Courses and examination part.
An Online College Student Database Management System (OCSDMS) is designed to
help collages for management of College students. Extensive information is available at your
fingertips through this System. Viewing student data, managing Courses, Student details and
reshuffling, managing semester, IA Marks, faculty, category and for examination, block
allocation, subject management, result and related issues are made simple and easy. There are
custom search capabilities to aid in finding student information and working on student
records. This can make the system easier to navigate and to use maximizing the effectiveness
of time and other resources. OCSDMS allows the keeping of personnel data in a form that
can be easily accessed and analyzed in a consistent way.
The OCSDMS module is a component covering many other student aspects from
application to retirement. The system records basic personal information, admission
information, education information regarding student. Leading edge systems provide the
ability to "read" applications and enter relevant data to applicable database fields, notify
student and provide result. Student management function involves
 student Basic Information
 Manage faculty
 Manage designation
 Manage course and specialty
 Roll number generation
 Manage semester and year
 admission seat management
 IA Result management
 Subject management
In OCSDMS, every user has a Login ID and Password. Also all the users have
different permission rights to access the applications. These rights are Dynamic and can be
changed.
There are three main roles in the system. Admin, accountant and operator. Admin has
complete access to the whole system, while accountant is only concerned with payment of
DEPT OF CSE, BTLITM Page 1

fees for the admission of the student. Operator is the role that is responsible for the use of the
system.
The Admin role can be as follow:
 Introduce new quota, board, category, course, etc
 Manage faculties
 Manage subjects
 Seat management
 Management of semester
 Generation of student roll number
 Manage examination IA marks
The operator role can:
 New admission and enrolment
 Search student
 Viewing the Marks, Courses, Academic Year details of students
 Block allocation
 View the Result, etc.
Now when the user with the particular role Logs on he can see only those pages which are
allowed to them.

CHAPTER 02
SYSTEM ANALYSIS
2.1 PURPOSE OF THE PROJECT:
The project is about to handle all the information of the student regarding admission
and examination. Also it manages resources which were managed and handled by manpower
previously. The main purpose of the project is to integrate distinct sections of the organization
into consistent manner so that complex functions can be handled smoothly by any technical
or non-technical persons.
The project aims at the following matters:
 Automation of admission and enrolment as per board, quota, category, available seats.
 Assistance in decision-making.
 To manage information of student, faculty and courses.
 Consistently update information of all the students.
 Reports- To gather all the related information of the Students.
All the above-mentioned matters are to be incorporated in the application along with some
additional requirements.
The main purpose of the Admin Module is to introduce new things and configure
important aspects. For e.g. only admin is authorized to introduce quota, board, subject,
category, etc. and only admin is allowed to configure exam and set fees structure. So the
master screens for all these are visible to only admin role. This is done by the Admin Module.
It also can create the users and Physical and Logical Locations. Thus the main purpose of the
Admin Module is to managing the dynamic working of the system.
2.2 SCOPE OF THE PROJECT:
The scope of the project includes the following
 Any college can use this system as it is not client centric.
 All admission and examination related work for the student can be done using this
system.
 Deliver Electronic Workplace
 Provide Bi-lingual support
 Application Support & Maintenance after deployment to production

2.3 PROJECT MODULES:
 2.3.1 PRODUCT PERSPECTIVE:
The Online College Student Database Management System is a new self-contained

Software product which will be produced by the project team in order to overcome the
problems that have occurred due to the current manual system. The newly introduced system
will provide an easy access to the system and it will contain user friendly functions with
attractive interfaces. The system will give better options for the problem of handling large
scale of physical file system, for the errors occurring in calculations and all the other required
tasks that has been specified by the client. The final outcome of this project will increase the
efficiency of almost all the tasks done to Manage Student Database in a much convenient
manner.
PRODUCT FUNCTIONS:
 View Student Details, Academic Year, Units ,IA marks

 Search Student by Name/Courses/Academic Year
 Print the IA Marks obtained
 Manage Guest (Add, Update Guest)
 Manage Student Details (Add, Update, Delete)
 Manage Academic Courses (Add, Edit, Delete)
 Manage Users (Add, Update, Delete)
 Issue CSV
 Update the User Personal Details
 Retrieve the Students Details, Courses, IA marks, Academic
Performances.
2.3.2 FUNCTIONAL REQUIREMETNS:
USER REQUIREMENTS:
FUNCTION 1: login
Actor: Admin, Operator, Accountant

Pre Condition: None
Input: User Id and Password
Output: Home Page as per role

Flow:
 User Logs in with username and password.
 If correct then Home Page is displayed.
FUNCTION 2: Modify student Details
Actor: operator
Pre Condition: User must be logged on
Input: student ID
Output: The changes as per modification of the student details in DB
Flow:
 Operator selects the link from the list.
 Then he enters the ID of the student to be modified.
 Then he modifies the details as required.
 Then he submits to effect the changes.
FUNCTION 3: Search student
Actor: Admin, Operator
Input: Detail of student as per selected search criteria.
Output: Student with his/her complete details.
Flow:
 User selects the link from the list.
 Then he selects the search criteria.
 Then he enters the details as per search criteria.
 Then he deletes, adds or edits the roles from the list.Search result is displayed.
Alternate Flow:
 If the user clicks the ‘Cancel’ button, then no changes are reflected in the DB.
 If there is no such student then appropriate message is shown.
FUNCTION 4: Add board

Actor: Admin
Input: Board details that is to be added.
Output: The changes are reflected in the DB
Flow:
 Admin selects the link from the list.

 Then he enters the proper details of the board to be added.
 On clicking “Save” button, the board is added to the DB.
Alternate Flow:
 If the admin did not provided the mandatory fields then alert is shown.
FUNCTION 5: Modify/Manage Faculty Details

Actor: Admin
Input: Faulty ID
Output: The changes as per modification of the Faculty details in DB
Flow:
 Then he enters the ID of the Faculty to be modified.
 Then he modifies the details as required.
 Then he submits to effect the changes.
Alternate Flow:
 If the Admin clicks the ‘Cancel’ button, then no changes are reflected in the
DB.
FUNCTION 6: Configure Semester Details

Actor: Admin
Pre Condition: User must be logged on and he must be Admin
Input: Details of the Semester to be configured.
Flow:
 Admin selects the link.
 then He selects Semester to be configured.
 Details of the Semester are provided.
 On clicking “Save”, information is saved to DB.
Alternate Flow:
 If the Admin clicks on ‘Cancel’ button then no changes should be reflected.
 If semester Details are not valid then alert are shown.
 If mandatory fields are empty then alerts are shown.

FUNCTION 7: Generate Roll Number

Actor: Admin
Input: Year, Course and Semester are selected for which roll number are to be
assigned.
Output: The Students are assigned with roll numbers.
Flow:
 Admin clicks on the ‘Roll number Master’ link.
 He then selects the Course, Year and Semester.
 He then clicks on “assign roll no” button.
 Roll number and student are saved in DB.
Alternate Flow:
 If the user clicks on ‘Cancel’ button then no changes should be reflected.
FUNCTION 8: Declare Result IA marks

Actor: Operator
Input:
 Year, Course and Semester for which result to be set.
 Exam type for which result is to be declared.
 Marks details of student as per subject.
Output: The Students marks and status of “pass” or “fail” is stored in DB.
Flow:
 Admin clicks on the ‘set result’ link.
 He then selects the Course, Year and Semester.
 He then selects type of the exam.
 He then add marks of each student as per subjects.
FUNCTION 9: Configure subject for exam

Actor: Admin
Input: Subjects and type of exam to be configured

Output: Database is saved as per configuration.
Flow:
 Admin clicks on the ‘Subject Exam master’ link.
 He then selects the Subjects.
 He then selects type of exam.
 He then set duration, passing marks and other details.
 Details are saved in DB.
Alternate Flow:
 If the user clicks on ‘Cancel’ button then no changes should be reflected.
 If mandatory fields are empty then alert is shown.
 If entry is not found to be valid then alert is shown.
FUNCTION 10: Add Subject

Actor: Admin
Input: Subject details that are to be added.
Flow:
 Then he enters the proper details of the Subject to be added.
 On clicking “Save” button, the Subject is added to the DB.
FUNCTION 11: block allocation master

Actor: Admin
Input:
 Exam that to be conducted.
 Block to be allocated to exam.
Flow:
 Then he selects the exam type for which block is to be allocated.

 Then he select of the block to be added.
 On clicking “Save” button, the data is added to the DB.
Alternate Flow:
 If the admin clicks the ‘Cancel’ button, then no changes are reflected in the
DB.
 If block is not available then proper message is shown.
FUNCTION 12: Examination IA Marks

Actor: Admin
Input: criteria by which report is to be generated.
Output: Generated report is shown.
Flow:
 Admin selects the link from the list
 Then he selects the criteria.
 On clicking “show” button, the report is shown.

CHAPTER 03
SYSTEM REQUIREMENT
3.1 USER CHARACTERISTICS:
Administrator:
The administrator has all the rights to access the system. He is the one who has all
rights to view the applicant details, modify those details, The administrator also keeps a track
of the file status of the applicants.
User :
Applicant is the one who wish to visit OCSDMS website. The applicant can fill in his
own details and register himself for membership to use portal services. The applicant has
rights to view and modify his own details, generate its candidature of containing his own
details in academic web part. The applicant also rights to create groups, modify groups, invite
member, modify member, join group, slam book requests, etc. In sort, the applicant can
access the application like a moderator of his/her group.
Faculty :
He can view log sheet submitted by trainee day to day filled student which is applying
for his/her status and day to day log sheet submission- this can be done, only when the
supervisor approve their log sheet, faculty gives review to trainee after looking his/her
remarks by the supervisor. The Supervisor is approve the log sheet is done by administrator
and give them remarks on it and supervisor also update trainee log sheet.
3.2 HARDWARE AND SOFTWARE REQUIREMENTS:

The following are minimum hardware and requirements that should be present to run
the project successfully.
Table : Tools and Technology
Development technologies PHP 5.6.31, SQL, JavaScript, XML
Development tools Xampp Control Panel V3.2.2, SQL

Application server Localhost
Database SQL
Operating system Windows XP Profession Edition, Windows Vista

Enterprise Edition.
Web browser Google Chrome 6.0 and above
Hardware P-IV 2.4, 1 GB RAM, 80 GB HDD
3.2 Hardware Requirements:

Table 3.2.1 Hardware Requirement:
Client Configuration
Operating System: Windows XP/2000/Windows 8/9/10
RAM: 256 MB minimum
400MB Minimum Free Space on DriveMicrosoft Office
Server Configuration
2 Server, each with following configuration
2 CPU
Operating System: Win XP/Windows 8/9/10
RAM: 512MB Minimum
40GB Minimum Free Space on Drive
750MHz
One Server with SQL Application Server
Other Server with SQL Database Server
Software Requirements:
Table 3.2.2 Software Requirement:
System Software
MS SQL Application Server enterprise edition
MS SQL Database Server enterprise edition
Microsoft Office/windows 8/9/10
Reporting server
IIS 6.0 or higher

3.3 CONSTRAINTS:
3.3.1 Regulatory Policies
 The length of the project is 4 months which a limited amount of time.
 The project developers are beginners and will take time to understand about the
technology.
 The users of the system are any registered applicants to apply for membership in
OCSDMS, authorized administrator and non-registered users can also used interface
pages.
3.3.2 Reliability Requirements
 The system should be reliable enough so that the data found in the database system is
consistent at any point.
 The system should be able to handle loads of requests from different users around the
world at the same time.
3.3.3 Criticality Of The Application
 The system is a web-based application and so fails to work if there is no Internet
connection. The system might not work if the Internet connection slows down.
 The system stops working in case if the database server or the application server stops
working.
 The system might give erroneous output if it fails to connect to the database server
3.3.4 Safety and Security Considerations
 The Intranet password security.
 Each applicant is given a login account through which he can view his own
information and also modify and save it. He has the rights to access only his own
information.
 The administrator has rights through which he can access and manage whole system.
The password is encrypted before it is sent over the network. This increases the
security level.
 MY SQL Server 2005 provides greater security to the database

CHAPTER 04
SYSTEM DESIGN
4.1 SYSTEM REQUIREMENTS:

Registration details of the applicant.
 Login details of the applicant.
 Personal details of the applicant.
 Information of all the members of the applicant’s group.
 Information of all the friend list of the applicant’s account.
 Educational and employment information
 All information and rules regarding the e-forms must follow.
 Details regarding the purpose of user visit to academy..
 Answers to the questionnaire for skill assessment of visitor.
 Communication with whole system.
4.1.1 Non-Functional Requirements
 Usability
The interface should use terms and concepts, which are drawn from the experience of
the people who will make most of the system. For example, map and date should be
displayed in its traditional fashion.
 Efficiency
The system must provide easy and fast access without consuming more cost.
 Reliability
User should never be surprised by the behavior of the system and it should also
provide meaningful feedback when errors occur so that user can recover from the errors.
4.2 FEASIBILITY STUDY:
The aim of the feasibility study activity is to determine whether it would be financially and
technically feasible to develop the system or not. A feasibility study is carried out from
following different aspects:
Operational Feasibility:

The system has been developed for any user who wants to use this system. We have
given a demo of our project and the users found the system friendly and easy to use. The
interoperability with the existing system is also checked after uploading the website. So they
may face certain problems in using the user interface. So keeping this consideration in mind
we have provided field for each and every field on the forms. The administrator also may be
non-technical, so the user interface is designed in such a way that it gets comfortable for the
non-technical person to operate easily.
Technical Feasibility:
It determines if the system can be implemented using the current technology. This
system has been developed using asp.net (VB) as front end and MY SQL Server 2005 as
backend. Though the MVS 2008 technology was new to us it was not so difficult for us to
learn it. This was also new to us but it didn’t take much effort and time to get used to it. We
had earlier worked with Access and not MY SQL Server 2005 but getting familiar with it was
also easy.
Economical Feasibility:
The company being a well-to-do company didn’t have any problem in buying any
software that was required in developing the application. The software’s we used were readily
available. So as such we didn’t face any economical constrains.
Implementation Feasibility:
This project can easily be made available online without much consideration of the
hardware and software. The only required thing at the applicant’s side is the Internet
connection and a web browser, which are a no difficult issue these days. A database server
and application server are required to set up at the admin side. After setting up the project
online, even the administrator can access the system from anywhere.
4.3 REQUIREMENTS VALIDATION:

Requirement Validation examines the specification to ensure that all system
requirements have been stated unambiguously; those inconsistencies, errors have been
detected and corrected and the work products conform to the standard. Source of the
requirements are identified. Final statement of requirement has been examined by original
source
 Requirements related to main requirements are found.
 Requirements are testable.
 Requirements are clearly stated and are not misinterpreted.
 All sources of requirements are covered to get maximum requirement.
 All methods of finding requirements are applied.
 Requirement associated with system performance, behavioral and operational
characteristics are clearly stated.
 Requirements are being discussed with the client in order to remove the
misinterpretations if they exist.
 Each requirement is being analyzed to prove its feasibility for the current system.
4.4 DATA MODELING:
4.4.1 Class Diagram:
A class diagram describes the static strace of a system. It shows how a system is
structured rather than how it behaves. The static structure of a system consists of a number of
class diagrams and their dependencies. The main constituents of a class diagram are classes
and their relationships: generalization, aggregation, association, and various kinds of
dependencies.
Following diagram represents various classes of the system. The relations between
these classes are shown in the next diagram.

Fig 4.4.1 Data Flow Diagram
SCHEMA DIAGRAM

4.4.2 SCHEMA DIAGRAM OF ONLINE COLLEGE STUDENT DATABASE

MANAGEMENT

4.4.2 ER Diagram
An entity-relationship diagram (ERD) is an abstract and conceptual representation

of data. Entity-relationship modeling is a database modeling method, used to produce a type
of conceptual schema or semantic data model of a system, often a relational database, and its
requirements in a top-down fashion.
Fig 4.4.3 ER diagram of Online College Student Database Management

CHAPTER 05

SYSTEM IMPLEMENTATION
5.1 MODULE DESCRIPTION:
Registration:
 The Customer should be able to register with their details

 The system should record following customer details into member
database.
 Name
 Email
 Password
 Address
 DOB
Logging In:
 The system should verify the customer email & password against the
member database when logging in After login, member should be directed
to Home screen
Admin Access:
 The system should enable customer to check for viewing of student details
 The system should display all the necessary information of students.
 The system should allow customer to confirm or cancel edit/update the
information student.
 The system should record student details into database
Faculty Access:
 The system should allow Faculty to update, add or delete details of student’s
information
 The system should provide customer desk portal access to Faculty for
providing response to student inquiry
Guest Access:
 The system should the students to view the information without any
edit/update access and student can report to Faculty.
 The system should enables to take a print of the student’s performance and
CSV format too.

5.2 DATA MODELLING:
Data modeling defines primary data objects, composition of each data object, and
attributes of the object, relationships between each object and other objects and between
objects and the processes.
Attendance Table:
FIELDS TYPE
Student Varchar
Regno Varchar
Week Varchar
Date Date
Unit Int
Attended Varchar
Id Int
Semester Int
Acadmicyear Varchar
Table 5.2.1 Attendance Table
Courses Table:
FIELDS TYPE
Id Int
Name Varchar
Table 5.2.2 Course Table
Marks Table:
FIELDS TYPE
Id Int
Name Varchar
Unit Int
Student Varchar
Regno Varchar
Year Varchar
Marks Int
Grade Varchar
Academicyear Varchar
Semester Varchar
Date Date
Table 5.2.3 Marks Table
Membership group permissions Table:

FIELDS TYPE
PermissionID Int
GroupID Int
Tablename Varchar
AllowInsert Tinyint
AllowView Tinyint

AllowEdit Tinyint
AllowDelete Tinyint
Table 5.2.4 Membership group Table
Membership groups Table:

FIELDS TYPE
GroupID Int
Name Varchar
Description Text
AllowSignup Tinyint
NeedsApproval Tinyint
Table 5.2.5 Membership groups Table
Membership User permissions Table:

FIELDS TYPE
PermissionID Int
MemberID Varchar
Tablename Varchar
AllowInsert Tinyint
AllowView Tinyint
AllowEdit Tinyint
AllowDelete Tinyint
Table 5.2.5 Membership users permissions Table
Table 5.2.6 Membership Users Table
Units Table:
FIELDS TYPE
Id Int
Name Varchar
Table 5.2.7 Units Table
FIELDS TYPE
RecID Bigint

TableName Varchar
PkValue Varchar
MemberID Varchar
DateAdded Bigint
DateUpdated Bigint
GroupID Int
Membership Users Table:
FIELDS TYPE
MemberId Varchar
passMD5 Varchar
Email Varchar
SignupDate Date
GroupID Int
isBanned Tinyint
isApproved Tinyint
Custom1 Text
Custom2 Text
Custom3 Text
Custom4 Text
Pass_reset_key Varchar
Pass_reset_expiry Int
Table 5.2.8 Membership Users Table
Students Table:-
FIELDS TYPE
Regno Varchar
Name Varchar
Course Int
Year Varchar
Academicyear Int
Table 5.2.9 Student Table

CHAPTER 06
SYSTEM TESTING
TESTING:
Testing is the process of detecting errors. Testing performs a very critical role for
quality assurance and for ensuring the reliability of software. The results of testing are used
later on during maintenance also.
6.1 Test Cases for Searching Student:
Sr. No. Test Condition Expected Output Actual Output Pass/Fail

1 Initial mode of opening Initial mode should Initial mode is cancel. Pass
the page be cancel.
2 ‘Add’ button ‘Add’ button should ‘Add’ button is Pass
be disabled always disabled
3 Clicking on ‘query’ System should enable System allows all the Pass
button all controls and controls and ‘cancel’
‘fetch’ and ‘cancel’ and ‘fetch’ mode are
button should be available.
enabled

4 In query mode clicking System should show System displays alert Pass
on ‘fetch’ button alert for criteria or for mandatory fields
without selecting search details is not
criteria or search details provided.
5 On clicking ‘fetch’ System should show Alert box is shown if Pass

button in query mode alert for improper details are not valid
with improper search details. as per search criteria.
details for particular
search criteria.
6 On clicking ‘fetch’ System should System shows student Pass

button with proper display student details details.
details. as per records in
database.
7 Clicking on modify/edit It should allow to edit Fields are editable Pass

button details and ‘cancel’ and ‘cancel’ and
and ‘save’ button are ‘save’ buttons are
only enabled. only enabled.
8 Clicking ‘save’ button System should show System shows alert Pass
without filling alert for required box for required
mandatory fields fields fields.
Table 6.1 Test Cases for Searching Student
6.2 Test Cases for Adding, editing, updating the Students:
Sr. No. Test Condition Expected Output Actual Output Pass/Fail

1 Initial mode of Initial mode should Initial mode is cancel Pass
opening the page be cancel .and list if list of all available
all available board board is shown.
should be shown
2 Clicking ‘Add’ button ‘save’ and ‘cancel’ save’ and ‘cancel’ Pass
button should be button are enabled
enabled and fields and fields are
are editable. editable.
3 Clicking ‘save’ without System should show Alert is shown by the Pass
filling mandatory alert for the system for the
details mandatory fields mandatory fields.
4 Clicking ‘save’ with System should show Alert box is shown Pass
providing existing alert that ‘board by the system.
board already exists’

5 Clicking ‘save’ with System should insert System inserts data Pass
filling complete details data to database and to database and ‘add’
‘add’ and ‘query’ and ‘query’ button
button should be are enabled.
enabled.
6 Clicking on ‘query’ System should System allows all the Pass
button enable all controls controls and ‘cancel’
and ‘fetch’ and and ‘fetch’ mode are
‘cancel’ button available.
should be enabled
7 In query mode clicking System should show System displays alert Pass
on ‘fetch’ button alert for Roll no is for Roll no is not
without entering Roll not entered. selected.
no
8 On clicking ‘fetch’ System should show Details of board is Pass
button in query mode if all details of board as shown as read only
Roll no is provided. read only mode and manner, and modify
‘modify’ and ‘cancel’ and cancel mode are
button should be only allowed.
enabled
9 Clicking on ‘cancel’ in System should clear System resets all Pass
any mode all fields and go to control and cancel
cancel mode mode is shown
10 Clicking on modify It should allow to Fields are editable Pass
button edit details and and ‘cancel’ and
‘cancel’ and ‘save’ ‘save’ buttons are
button are only only enabled.
enabled.
Table 6.2 Test Cases for Adding, editing, updating the Students
6.2 TEST USED IN THIS PROJECT:
6.2.1 Psychology of Testing:
The aim of testing is often to demonstrate that a program works by showing that it has
no errors. The basic purpose of testing phase is to detect the errors that may be present in the
program. Hence one should not start testing with the intent of showing that a program works,
but the intent should be to show that a program doesn’t work. Testing is the process of
executing a program with the intent of finding errors.
6.2.2 System Testing:

The philosophy behind testing is to find errors. Test cases are devised with this in
mind. A strategy employed for system testing is code testing.
6.2.3 Code Testing:

This strategy examines the logic of the program. To follow this method we developed
some test data that resulted in executing every instruction in the program and module i.e.

every path is tested. Systems are not designed as entire nor are they tested as single systems.
To ensure that the coding is perfect two types of testing is performed or for that matter is
performed or that matter is performed or for that matter is performed on all systems.
 Link Testing:
Link testing does not test software but rather the integration of each module in
system. The primary concern is the compatibility of each module. The Programmer tests
where modules are designed with different parameters, length, type etc.
 Integration Testing:
After the unit testing we have to perform integration testing. The goal here is to see if
modules can be integrated properly, the emphasis being on testing interfaces between
modules. This testing activity can be considered as testing the design and hence the emphasis
on testing module interactions..
 System Testing:
Here the entire software system is tested. The reference document for this process is
the requirements document.
CHAPTER 07
SAMPLE OUTPUT AND SCREENSHOTS

Fig 7.1 showing Sign Up

This shows the sign up of our project
Fig 7.2 showing in Sign In

This is where the user need to login with his credentials.

Fig 7.3 Password Reset Page.

The User can reset the Password by using the Password Reset page.
Fig 5.4 Sign Out Page

The user can log out his account from the project using sign out option.

Fig 7.5 Menu Page

This shows the Menu Page of Online College Student Database Management System
Projects with the dashboard, Contact Us and all the details of Students info.
Fig 7.6 Students List

This shows the Student list of all the students.

Fig 7.7 Adding a new Student

The user can add a new Student into the Student list can save it accordingly
Fig 7.8 CSV of Students

This shows the list of CSV of the students

Fig 7.9 Units List

This shows how the Units can be added newly into the project
Fig 7.10 Courses

This shows the list of the Courses available in project

Fig 7.11 Adding a New Courses

This shows how the New Course can be added into the project.
Fig 7.12 Attendance Record

This shows the list of Attendance Record of the Students in the project.

Fig 7.13 Adding Attendance Record

This shows how the student attendance can be added into the Attendance record
Fig 7.14 Marks List

This shows the Marks list of all the Students present in the Project

Fig 7.15 Academic Year

This shows the list of Academic years available in the project
Fig 7.16 Student List based on Academic Year

This shows the list of all the students according to their Academic years.

Fig 7.17 Academic Year Details Marks Filters

This shows the Academic year Details of Marks Filters in the project, using this Filters one
can the order of the students, Academic years.etc.

CHAPTER 08
SYSTEM MANAGEMENT
STUDY OF CURRENT SYSTEM:

The current system for the Student Management System deals with maintaining a
physical contact with the academy management dept. for filling all the details and the
documentation work. The management doesn’t needs to visit the academy management dept.
and collect the assignment and submitting his/her documents directly.
According to the current system, the management has to fill in the forms manually, go
to the account management dept., and submit him the form. The applicant needs to visit the
academy portal now and then in order to get his work accomplished. The admin also has to
manage all the users. He needs to maintain records of all the users, their activity status,
submission methods and installation details on paper. The Manual process is more error prone
and also slow. Moreover Students in the academy can interface his/her work area only. But if
an online application is available then they can communicate whole system. Thus a
simulation of this entire process can be a boon to the applicants as well as the admin.

CHAPTER 09:
CONCLUSION AND DISCUSSION
9.1 CONCLUSION:
 OCSDMS will be helpful to perform paperless work and manage all data.
 This provides easy, accurate, unambiguous and faster data access.
 Lesser learning curve - Consistent user interface, customized for the group of users,
statistical information in various graphical and tabular forms.
9.2 DISCUSSION:
Self Analysis of Project Viabilities:

SMS is a very efficient system for the management of student admission and
examination. Most of all the task of admission and examination can be easily done with this
system. This can be used by any organization.
Also this system uses the latest technologies like AJAX, XML. So it was easy enough
to develop the project. If any changes in the system are to be made then they can be done
very easily.
Problem Encountered and Possible Solutions:
Problem of creating control using JavaScript were faced during development. But
with help of internal guide and other team members problems were solved.
The problems encountered during the training undergone at Tata Consultancy Services
were purely due to lack of knowledge in various technical aspects.
The lack of in depth knowledge in various concepts of java script, database concepts,
etc. was the problems faced. Moreover the lack of practical know-how of these aspects did
cause a few hindrances in early stages of training but later with the help and guidance of team
members it became easier to cope up with these concepts and applications.

BIBLIOGRAPHY
[1]www.google.com
[2]www.wikiphp.org
[3]www.github.com
[4]www.kashipara.com
[5]http://www.w3schools.com/js/js_datatypes.asp
[6]http://www.w3schools.com/sql/sql_insert.asp
[7]http://www.w3schools.com/sql/sql_update.asp
[8]http://www.w3schools.com/php/php_forms.asp
References:
 Database systems Models, Languages, Design and Application
Programming, RamezElmasri and Shamkant B. Navathe, 7th Edition,
2017, Pearson.
 Database management systems, Ramakrishnan, and Gehrke, 3rd Edition,
2014, McGraw Hill.

 Silberschatz Korth and Sudharshan, Database System Concepts, 6th
Edition, McGrawHill, 2013.

 Coronel, Morris, and Rob, Database Principles Fundamentals of Design,
Implementation and Management, Cengage Learning 2012.

 Fundamentals of software engineering by Rajib mall, PHPlearning
 Web development and application development by Ivan Byross BPB
publications.

Report Third Page

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Report Third Page

Загружено:

Авторское право:

Доступные форматы

ONLINE COLLEGE STUDENT DATABASE MANAGEMENT SYSTEM

DEPT OF CSE, BTLITM Page 1

DEPT OF CSE, BTLITM Page 2

DEPT OF CSE, BTLITM Page 3

The Online College Student Database Management System is a new self-contained

 View Student Details, Academic Year, Units ,IA marks

2.3.2 FUNCTIONAL REQUIREMETNS:

Actor: Admin, Operator, Accountant

DEPT OF CSE, BTLITM Page 4

FUNCTION 4: Add board

DEPT OF CSE, BTLITM Page 5

FUNCTION 5: Modify/Manage Faculty Details

FUNCTION 6: Configure Semester Details

DEPT OF CSE, BTLITM Page 6

FUNCTION 7: Generate Roll Number

FUNCTION 8: Declare Result IA marks

FUNCTION 9: Configure subject for exam

DEPT OF CSE, BTLITM Page 7

FUNCTION 10: Add Subject

FUNCTION 11: block allocation master

DEPT OF CSE, BTLITM Page 8

FUNCTION 12: Examination IA Marks

DEPT OF CSE, BTLITM Page 9

3.1 USER CHARACTERISTICS:

3.2 HARDWARE AND SOFTWARE REQUIREMENTS:

Development tools Xampp Control Panel V3.2.2, SQL

DEPT OF CSE, BTLITM Page 10

Operating system Windows XP Profession Edition, Windows Vista

Web browser Google Chrome 6.0 and above

Hardware P-IV 2.4, 1 GB RAM, 80 GB HDD

3.2 Hardware Requirements:

DEPT OF CSE, BTLITM Page 11

DEPT OF CSE, BTLITM Page 12

4.1 SYSTEM REQUIREMENTS:

DEPT OF CSE, BTLITM Page 13

4.3 REQUIREMENTS VALIDATION:

DEPT OF CSE, BTLITM Page 15

DEPT OF CSE, BTLITM Page 16

4.4.2 SCHEMA DIAGRAM OF ONLINE COLLEGE STUDENT DATABASE

DEPT OF CSE, BTLITM Page 17

An entity-relationship diagram (ERD) is an abstract and conceptual representation

Fig 4.4.3 ER diagram of Online College Student Database Management

DEPT OF CSE, BTLITM Page 18

 The Customer should be able to register with their details

DEPT OF CSE, BTLITM Page 19

Membership group permissions Table:

DEPT OF CSE, BTLITM Page 20

Membership groups Table:

Membership User permissions Table:

DEPT OF CSE, BTLITM Page 21

DEPT OF CSE, BTLITM Page 22

6.1 Test Cases for Searching Student:

Sr. No. Test Condition Expected Output Actual Output Pass/Fail

DEPT OF CSE, BTLITM Page 23

5 On clicking ‘fetch’ System should show Alert box is shown if Pass

6 On clicking ‘fetch’ System should System shows student Pass

7 Clicking on modify/edit It should allow to edit Fields are editable Pass

6.2 Test Cases for Adding, editing, updating the Students:

Sr. No. Test Condition Expected Output Actual Output Pass/Fail

DEPT OF CSE, BTLITM Page 24

6.2 TEST USED IN THIS PROJECT:

6.2.1 Psychology of Testing:

6.2.2 System Testing:

6.2.3 Code Testing: