Student Database Management System Finale
Student Database Management System Finale
Student Database Management System Finale
Abstract
An organized and systematic once solution is essential for all universities and
organizations. There are many departments of administration for the maintenance of
college information and student databases in any institution. All these departments
provide various records regarding students. Most of these track records need to
maintain information about the students. This information could be the general details
like student name, address, performance etc or specific information related to
departments like collection of data. All the modules in college administration are
interdependent. They are maintained manually. So they need to be automated and
centralized as, Information from one module will be needed by other modules. For
example, when a student needs his course completion certificate it needs to check
many details about the student like his name, reg. number, year of study, exams he
attended and many other details. So it needs to contact all the modules that are once,
department and examination and result of students.
With that in mind, we overhauled the existing Student Database Management
System and made necessary improvement to streamline the processes. Our work is
useful for easy user interface. We are planning to utilize the powerful database
management, data retrieval and data manipulation. We will provide more ease for
managing the data than manually maintaining in the documents. Our work is useful
for saving valuable time and reduces the huge paper work.
ACKNOWLEDGEMENT
Success is never achieved single handed so, it is our duty to acknowledge all those
who have provided a helping hands in making this project success.
Firstly, I would like to express my deep sense of gratitude towards my project
guide Mr. Chidanand Bhattacharya for their valuable guidance, co-operation and
approval given by them in successful completion of project work.
I am grateful to H.O.D. Prof. Abdul Halim of T.B.Girwalkar Polytechnic,
Ambajogai who always solved our problems.
I am also very much thankful to our Prof. M.B.Shetti principle of T.B.Girwalkar
Polytechnic, Ambajogai for providing facilities time to time about this project work.
Last but not least a great deal of appreciation and best wishes to all my friends for
their contribution & encouragement during this work.
INDEX
Contents Page No
1. Introduction 4
2. Requirement 5
3. Activities Performed 6
5. Introduction To Ms-Access 10
6. ER Diagram 15
7. Table used 17
8. Testing 19
9. Screen Layout 21
10. Conclusion 27
Bibliography 28
1. INTRODUCTION
2. REQUIREMENT
Hardware Requirements:-
Software Requirements:-
3. ACTIVITIES PERFORMED
Planning Maintenance
Planning:-
5. INTRODUCTION TO MS-ACCESS
For example, suppose the phone numbers of your suppliers are stored in various
locations: in a card file containing supplier phone numbers, in product information files in
a file cabinet, and in a spreadsheet containing order information. If a supplier's phone
number changes, you might have to update that information in all three places. In a
database, however, you only have to update that information in one place the supplier's
phone number is automatically updated wherever you use it in the database.
What is a database?
A database is a tool for collecting and organizing information. Databases can store
information about people, products, orders, or anything else. Many databases start as a list
in a word-processing program or spreadsheet. As the list grows bigger, redundancies and
inconsistencies begin to appear in the data.
The data becomes hard to understand in list form, and there are limited ways of
searching or pulling subsets of data out for review. Once these problems start to appear,
it's a good idea to transfer the data to a database created by a database management
system (DBMS), such as Office Access 2007.
A computerized database is a container of objects. One database can contain more
than one table. For example, an inventory tracking system that uses three tables is not
three databases, but one database that contains three tables. Unless it has been specifically
designed to use data or code from another source, an Access database stores its tables in a
single file, along with other objects, such as forms, reports, macros, and modules. Access,
you can:
Tables:
A database table is similar in appearance to a spreadsheet, in that data is stored in
rows and columns. As a result, it is usually quite easy to import a spreadsheet into a
database table. The main difference between storing your data in a spreadsheet and
storing it in a database is in how the data is organized.
To get the most flexibility out of a database, the data needs to be organized into
tables so that redundancies don't occur. For example, if you're storing information about
employees, each employee should only need to be entered once in a table that is set up
just to hold employee data. Data about products will be stored in its own table, and data
about branch offices will be stored in another table. This process is called normalization.
Each row in a table is referred to as a record. Records are where the individual
pieces of information are stored. Each record consists of one or more fields. Fields
correspond to the columns in the table. For example, you might have a table named
"Employees" where each record (row) contains information about a different employee,
and each field (column) contains a different type of information, such as first name, last
name, address, and so on. Fields must be designated as a certain data type, whether it's
text, date or time, number, or some other type.
Another way to describe records and fields is to visualize a library's old-style card
catalog. Each card in the cabinet corresponds to a record in the database. Each piece of
information on an individual card (author, title, and so on) corresponds to a field in the
database.
Forms:
Forms are sometimes referred to as "data entry screens." They are the interfaces
you use to work with your data, and they often contain command buttons that perform
various commands. You can create a database without using forms by simply editing your
data in the table datasheets. However, most database users prefer to use forms for
viewing, entering, and editing data in the tables.
Forms provide an easy-to-use format for working with the data, and you can also
add functional elements, such as command buttons, to them. You can program the buttons
to determine which data appears on the form, open other forms or reports, or perform a
variety of other tasks. For example, you might have a form named "Customer Form" in
which you work with customer data. The customer form might have a button which opens
an order form where you can enter a new order for that customer.
Forms also allow you to control how other users interact with the data in the
database. For example, you can create a form that shows only certain fields and allows
only certain operations to be performed. This helps protect data and to ensure that the data
is entered properly.
Reports:
Reports are what you use to summarize and present data in the tables. A report
usually answers a specific question, such as "How much money did we receive from each
customer this year?" or "What cities are our customers located in?" Each report can be
formatted to present the information in the most readable way possible.
A report can be run at any time, and will always reflect the current data in the
database. Reports are generally formatted to be printed out, but they can also be viewed
on the screen, exported to another program, or sent as e-mail message.
Queries:
Queries are the real workhorses in a database, and can perform many different
functions. Their most common function is to retrieve specific data from the tables. The
data you want to see is usually spread across several tables, and queries allow you to view
it in a single datasheet. Also, since you usually don't want to see all the records at once,
queries let you add criteria to "filter" the data down to just the records you want. Queries
often serve as the record source for forms and reports.
Certain queries are "updateable," meaning you can edit the data in the underlying
tables via the query datasheet. If you are working in an updateable query, remember that
your changes are actually being made in the tables, not just in the query datasheet.
Queries come in two basic varieties: select queries and action queries. A select
query simply retrieves the data and makes it available for use. You can view the results of
the query on the screen, print it out, or copy it to the clipboard. Or, you can use the output
of the query as the record source for a form or report. An action query, as the name
implies, performs a task with the data. Action queries can be used to create new tables,
add data to existing tables, update data, or delete data.
Macros:
Macros in Access can be thought of as a simplified programming language which
you can use to add functionality to your database. For example, you can attach a macro to
a command button on a form so that the macro runs whenever the button is clicked.
Macros contain actions that perform tasks, such as opening a report, running a query, or
closing the database. Most database operations that you do manually can be automated by
using macros, so they can be great time-saving devices.
Modules:
Modules, like macros, are objects you can use to add functionality to your
database. Whereas you create macros in Access by choosing from a list of macro actions,
you write modules in the Visual Basic for Applications (VBA) programming language. A
module is a collection of declarations, statements, and procedures that are stored together
as a unit. A module can be either a class module or a standard module. Class modules are
attached to forms or reports, and usually contain procedures that are specific to the form
or report they're attached to. Standard modules contain general procedures that aren't
associated with any other object. Standard modules are listed under Modules in the
Navigation Pane, whereas class modules are not.
Features of MS-ACCESS:-
Access is multi-featured Database Management System that can use by both
beginners and those who have pervious Database Management System experience. This
section describes some of the key features of Access.
6. ER Diagram
Username Password
Administrator
Gender
Name Adds
Mobile No.
Address
Category Branch
Pays
Description of ER diagram:
There are 3 main entities
1) Administrator
2) Student
3) Fees
Administrator:
It has two attributes like username and password. It is the only one who can access the
whole database with authentication. It does the operations like add Student modify
student delete student, also handles the whole task related to the fees transaction and all
the important task
Student:
It is the entity which includes the attributes like name, academic year, branch, class,
category, gender, address, mobile no. It has a relationship for paying fees entity.
Fees:
It has attributes like name, receipt no, tution fees paid, development fees paid, other fees
paid, date of receipt
Here name is used as a primary key
7. TABLES USED
1. Table: Student
Meets the business and technical requirement that guided its design and development,
and Works as expected
Software testing has three Main purposes: verification, validation, and defect
finding.
The verification process confirms that the software meets its technical specification. A
specification is a description of a function in terms of a measurable output value given
a specific input value specific precondition. A simple specification may be along the time
of a SQL query retrieving data for a single account against the multi-month account
account-summery table must return these eight fields <list> ordered by month within 3
second of submission.
The validation process confirms that the software meets the business requirement. A
simple example of business requirement is after choosing a branch office name,
information about the branch customer account managers will appear in a new window.
The new window will present manager identification and summery information about
each managers customer base: <list of data elements.>. other requirement provides
details on how the data will be summarized, formatted and displayed.
A defect is a variens between the expected and actual result. The defects altimate source
may be traced to a fault introduced in the specification, design, or development (coding)
phases.
Testing will be performed by running the system using the dummy data. It also
tested whether the system identifiers the problem correctly. Testing is vital to the success
of the system.
System testing makes logical assumption that if all parts of the system are
working correctly, the requirements have been satisfied completely. And if requirement
have been full filled, the goal can be achieved very easily.
But no system is 100% accurate; there can still be some faults in the system. The
testing is done to overcome in maximum number of problem in the system and to make
the system bug free.
9. SCREEN LAYOUT
Login Page:
Main Menu:
Add Student:
Student Details:
Accept Fees:
Receipt Details:
10. CONCLUSION
The college can handle full-scale computer and computer related resource.
College Administration System deals with all the activities done by computer such as
registration and admission process, staff and class management, time etc all these process
are handled by computer management system.
BIBLIOGRAPHY
[1] Book Keeping and Accountancy - L.N. Chopde & D.H. Choudhary.
[4] Teach Your Self Visual Basic 6.0 (21 Days) - Greg Perry