Scribd
Upload
426 views27 pages

Student Database

This document describes a student database management system that aims to automate the process of maintaining student details like personal information, fees payments, marks, and academic records. It discusses the drawbacks of existing manual systems like being time-consuming and prone to errors. The proposed system provides advantages like a user-friendly interface, fast access to data, more storage capacity, and search functionality. It describes modules for admission, transactions, reports and provides details of the requirements, development tools, and data collection process.

Uploaded by

Bharathi Gunasekaran
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
426 views27 pages

Student Database

This document describes a student database management system that aims to automate the process of maintaining student details like personal information, fees payments, marks, and academic records. It discusses the drawbacks of existing manual systems like being time-consuming and prone to errors. The proposed system provides advantages like a user-friendly interface, fast access to data, more storage capacity, and search functionality. It describes modules for admission, transactions, reports and provides details of the requirements, development tools, and data collection process.

Uploaded by

Bharathi Gunasekaran
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 27

STUDENT DATABASE MANAGEMENT

SYSTEM
ABSTRACT
• The Project is an attempt at developing packages for maintaining all the
details about Admission, Payment particulars and Academic details for
institution such as student name, personal details and mark details etc.
• Display of the same maintaining note books manually is tedious, time
consuming process; keeping these things in mind this project has been
developed to increase the speed and accuracy of the total process carried by
our project.
STACKHOLDERS

• Student
• Admin
SYSTEM STUDY
• Existing system drawbacks
• Proposed system advantages
EXISTING SYSTEM
• this project of “library management” of gives us the complete information
about the library.
• We can enter the record of new books and retrieve the details of books
available in the library.
• We can issue the books to the students and maintain their records and can
also check how many books are issued and stock available in the library.
• In this project we can maintain the late fine of students who returns the
issued books after the due date.
• Throughout the project the focus has been on presenting information and
comments in an easy and intelligible manner.
EXISTING SYSTEM DRAWBACKS

• Library management system have very large library that will difficult to
update.
• If the software is corrupted ,whole data will be collapsed.
PROPOSED SYSTEM

• To overcome the drawbacks of the existing system.


• Proposed system is an automated Library Management System.
• Through our software user can add books, search books, renewal, update
information, edit information, and return books in quick time.
PROPOSED SYSTEM ADVANTAGES
• User friendly interface
• Fast access to database
• Less error
• More Storage Capacity
• Search facility
• Look and Feel Environment
• Quick transaction
PROJECT DESCRIPTION
• A library management system enhances the efficiency of the librarians
and library users.
• A library management system reduces the cost of management.
• The system eliminates the need to employ many workers and keep different
manual files thereby reducing the cost.
MODULE DESCRIPTION
• Master
• Transaction
• Reports
MASTER
ADMISSION MENU:
The option Admin Details from the Admission Menu is used to admit the new
students into the institution. In this option the user has to enter all the personnel
details of the students. Here the student personnel details are stored in the
admission and personal details tables. Here the not null validations are done for the
following fields Name, student Date of Birth.
ACADEMIC DETAILS:
When a new student admitted into the institution, the previous institution details are
stored in Academic table. Here the not null validations are done for the following
fields Previous institution name, previous class and percentage. The previous
institution class must be less then one class of current class and it must not greater
than current class.
STUDENT INFO:
The option student info from the Admission menu is used to view all the
student names in a particular class and the user can edit the name if need. The data
for this option is taken from student details.
I & II TERM FEE MASTER:
The option I and II Term entry from the fees master menu is used to store the
fees parameter for I and II term. The parameters entered here are used in the fee
transactions
TRANSACTIONS

I TERM FEE COLLECTION:


The option I Term collection from transaction menu is used to collect the I
Term fees from the students. Here the receipt number will automatically
generated. The fees parameter details are taken from the Fee master table and
stored in I term table.
II TERM FEE COLLECTION:
The option II Term collection from transaction menu is used to collect the II
Term fees from the students. Here the receipt number will automatically
generated. The fees parameter details are taken from the Fee master table and
stored in II term table.
REPORT

• Reports module is designed to give user friendly information to give status on the
day to day transaction made in college system. It can be generated by the admin for
various purposes. Based on the reports admin take decisions of the system.
REQUIREMNET PHASE

• software requirements
• hardware requirements
• Testing tools
• Development tools
• Data collection
Software requirements
operating system : windows 7
front end : VB.NET
back end : SQL server
Hardware requirements

Processor : Pentium Dual Core


Hard Disk : 80 GB
RAM : 1GB RAM
Monitor : 15 ” VGA Color Monitor
Keyboard : 104 Keys Keyboard
Mouse : LOGITECH
Testing tools
• Unit testing
• Block box testing
• White box testing
• Module testing
• Integration testing
• Validation testing
• Output testing
• Code testing
Unit resting
• In this online examination system unit testing check login form. Unit
testing focuses verification efforts on the smallest unit of the software
design, the module.
• Unit testing focuses verification efforts on the smallest unit of the software
design, the module. This is also known as “Module Testing”.
• The modules are tested separately.
• This testing carried out during programming stage itself. In this testing each
module is found to be working satisfactorily as regards to the expected
output from the module.
Block box testing

Black box testing attempts to derive sets of inputs that will fully
exercise all the functional requirements of a system. It is not
an alternative to white box testing. This type of testing
attempts to find errors in the following categories:
• incorrect or missing functions,
• interface errors,
• errors in data structures or external database access,
• performance errors and
• Initialization and termination errors.
White box testing

• Tests are based on coverage of code statements, branches,


paths, and conditions. Also, the tests are based on knowledge
of the internal logic of an application's code.
Integration testing

• In this integration testing the modules are check one by one up to


end module. Data can be grossed across an interface; one module
can have adverse efforts on another.
• Integration testing is systematic testing for construction the program
structure while at the same time conducting tests to uncover errors
associated with in the interface.
• The objective is to take unit tested modules and build a program
structure. All the modules are combined and tested as a whole.
• Here correction is difficult because the isolation of cause is
complicate by the vast expense of the entire program.
• Thus in the integration testing stop, all the errors uncovered are
corrected for the text testing steps.
Output testing

• In output testing each test has a different purpose all the work should verify
that all the system elements have been properly integrated and perform
allocated functions. No system could be useful if it does not produce the
required output.
• Here, output testing is done by checking whether the data being updated
through database is coming in the correct portion and position of the website
template.
• User Acceptance Testing: User acceptance of a system is the key factor of the
success of any system. The system under study is tested for the user acceptance
by constantly keeping in touch with the prospective system users at the time of
developing and making changes wherever required.
• Test Data: Taking various kinds of test data does the above testing. Preparation
of test data plays a vital role in the system testing after preparing the test data
the system under study is tested using the test data. While testing the system by
using the test data errors are again uncovered and corrected by using above
testing steps and corrections are also noted from the future use.
Validation testing
• At the conclusion of integration testing software is completely assembled
as a package, interfacing errors have been uncovered and corrected and a
final series of software tests begins, validation test begins.
• Validation test can be defined in many ways. But the simple definition is
that validation succeeds when the software function in a manner that can
reasonably expected by the examiners.
• After validation test has been conducted one of two possible conditions
exists.
• One is the function or performance characteristics confirm to specifications
and are accepted and the other is deviation from specification is uncovered
and a deficiency list is created.
• Proposed system under consideration has been tested by using validation
testing and found to be working satisfactorily.
Module testing
• This is also known as unit testing. Unit testing focuses on the verification
of the smallest unit of software design of the module. In this each module
was found to be working satisfactory as per the expected output of the
module.
Development tools
Data collection

• Admin collect the student details ,fees details ,mark details and academic
details.
• Student collect the personalized information and view fees details.
Thank you

You might also like