1

G.H. Raisoni College Of Engineering & Management, Pune

A PROJECT REPORT ON

“Blood Bank Management

System”

Submitted by: Guided By: Sunita Mam

Group no: D3

1. Ayesha Pathan (Roll no 66 )

2. Rajani Jadhav (Roll no: 71)

3. Laxman Bhosle (Roll no:75 )

4. Nikhil Gudmewar(Roll no: 84)

CERTIFICATE
2

This is to certify that “ Scholarship Management System” embodies the original work done
by Nikita Avhad, Manjusha Dhamdhere, Nayan Dhawas, Sagar Dighe during this project
submission as a partial fulfilment of the requirement for the MiniProject in subject DBMS of
B.E. Degree, V Semester, of Pune University during the academic year 2017-2018

Date:

Place: Pune

Project Guide Head of Department Director

(Prof. Poonam Gupta (Dr.J. B. Sankpal)

ACKNOWLEDGEMENT
3

The satisfaction that accompanies that the successful completion of any task would be
incomplete without the mention of people whose ceaseless cooperation made it possible,
whose constant guidance and encouragement crown all efforts with success.

We are grateful to our project guide Ms. …………for the guidance, inspiration and constructive
suggestions that helpful us in the preparation of this project. We also thank our other staff
members who have helped in successful completion of the project.

CONTENTS
4

S.N Title Page No

O
1. Introduction 6
1.1 Purpose
1.2 Overview

2. Planning 8
2.1 Problem statement and objectives
2.1.1 Problems with conventional systems
2.1.2 Goals of proposed system

3. System Definition 11
3.1 Background
3.2 Scope
3.3 User Characteristics
3.4 System Analysis

4. Requirement collection and analysis 13

4.1 Requirement gathering
4.2 Software Requirements Specification (SRS)
4.2.1 Environmental Characteristics
4.2.2 Functional requirements
4.2.3 Non-Functional requirements
4.2.4 Sources of Information gathering
4.2.5 Use case Diagram

5. Database Design 16
5.1 Conceptual Model
5.2 Logical Model
5.3 Relational Schema
5.4 Schema Diagram

6. Normalized Tables 20

7. DBMS Selection 23

8. Application Design 24

9. Project Implementation
9.1 Implementation of front end 25
5

9.2 Implementation of database (back-end)

10. Testing 32

11. Conclusion 35

12. Bibliography 35

1. INTRODUCTION

1.1) Purpose
6

• The Software is to provide enhanced features of our Scholarship Management System.

• It maintains two levels of users:

- Administrator Level
-Student Level(Normal User)

• The Software includes:

- Maintaining Student details.

- Maintaining detail updates of students: academics and personal, trustees amount.

- Providing Scholarship to eligible students.

-Maintaining details of eligible students.

1.2) Overview

- Project is related to Scholarship Management System.

- The project maintains two levels of users:

• Student User-

-Main facilities available in this project are:

• Create account for new user and Apply for Scholarship.

• Update Information and Bank details.

• Administrator Level-

-Main facilities available in this project are:

• Maintaining records of Students.

• Maintaining student academic details and personal details.

• Maintaining trustee’s details.

• Providing Scholarship to eligible students.

• Transferring respective Scholarship Amount to eligible students.

7

- In this project collection of data is from different students.

- Changes in student details and Scholarship Amount will be updated in the database.

- Administrator can find out Details of eligible students.

2. PLANNING
8

Planning is the preliminary stage to achieve the objective of project. The various stages
included in the Planning are as follows:

1. Identification of enterprise plans and goals with subsequent determination of

information system needs.

2. Evaluation of current information system to determine existing strengths and

weaknesses.

3. Appraisal of IT opportunities that might yield competitive advantage.

2.1) Problem Statement and Objectives:

To overcome the drawbacks of the previously existing Scholarship management systems.

2.1.1) Problems with conventional system

1. Lack of immediate retrievals: The information is very difficult to retrieve and to find
particular information like- E.g. - To find out application forms for student, the student has to
go through various registers. This results in inconvenience and wastage of time.

2. Lack of immediate information storage: The information generated by various

transactions takes time and efforts to be stored at right place.

3. Lack of prompt updating: Various changes to information like student details and
trustee’s details are difficult to make as paper work involved.

4. Error prone manual calculation: Manual calculations are error prone and take a lot of
time this may result in incorrect information. For example Scholarship amount calculation of
eligible students.

5. Preparation of accurate and prompt reports: This becomes a difficult task as

information is difficult to collect from various registers.

2.1.2) Goals of proposed system:

1. Planned approach towards working: The working in the organization will be well
planned and organized. The data will be stored properly in data stores, which will help in
retrieval of information as well as its storage.

2. Accuracy: The level of accuracy in the proposed system will be higher. All operations
would be done correctly and it ensures that whatever information is coming from the centre is
accurate.
9

3. Reliability: The reliability of the proposed system will be high due to the above stated
reasons. The reason for the increased reliability of the system is that now there would be
proper storage of information.

4. No Redundancy: In the proposed system utmost care would be that no information is

repeated anywhere, in storage or otherwise. This would assure economic use of storage space
and consistency in the data stored.

5. Immediate retrieval of information: The main objective of proposed system is to provide

for a quick and efficient retrieval of information. Any type of information would be available
whenever the user requires.

6. Immediate storage of information: In manual system there are many problems to store
the largest amount of information.

7. Easy to Operate: The system should be easy to operate and should be such that it can be
developed within a short period of time and fit in the limited budget of the user.

Alternative Solutions:

1. Improved Manual System: One of the alternative solutions is the improvement of the
manual system. Anything, which can be done by using automated methods, can be done
manually. But the question arises how to perform thing manually in a sound manner.
Following are some suggestions, which can be useful in the manual system.

More sophisticated register maintenance for various students’ information and a good system
for writing scholarship cheque and application forms availed for the students can be
maintained at central place.

Adequate staff may be maintained so that updations are made at the very moment at the same
time. Proper person for proper work should be made responsible so that a better efficiency
could be achieved. This needs a lot of work force.

2. Batch System: Another alternative solution can be used of computer based batch system
for maintaining the information regarding application forms, list of scholarship holder
students and trustee’s. A batch system refers to a system in which data is processed in a
periodical basis.
The batch system is able to achieve most of the goals and sub goals. But a batch system data
is processed in sequential basis. Therefore batch system is not suggested.

3. Online System: This system (CSS) provides online storage/ updations and retrieval
facility. This system promises very less or no paper work and also provides help by admin
and its user friendly.

In this system everything is stored electronically so very less amount of paper work is
required and information can be retrieved very easily without searching here and there into
registers. This system is been discussed here.
10

3. SYSTEM DEFINITION

3.1) Background
11

Any Foundation can provide Scholarship for needy and eligible student by using this
Scholarship management System.

Scholarship management system provides facilities like:

1. Managing student’s details

- Managing student’s bank, personal, academic details.

-Providing scholarship to eligible students.

-Keeping record of amount transferred by trustees.

- Keeping record of the student’s.

- Keeping information about annual income of the students.

-Transfer the Scholarship Amount to student’s bank Account.

- Student’s can update their information and can see the list of scholarship holder students.

- Admin can check foundation balance.

These are the various jobs that need to be done in a scholarship management by the admin
and students. All this work is done on computers.

The work is done as follows:

-Information about students is done by just writing the student’s personal details, by stud_info
type. Whenever the student comes up his information is stored freshly.

-Scholarship is given to the student’s who have their annual income less than 200000 and
scholarship amount is distributed as per students HSC result.

-Information to students is generally recorded on the document, which contains scholarship

information. It is destroyed after some time period to decrease the paper load in the office but
stored in the database.

All this work is done manually by the admin and lot of documents are needed to be handled
and taken care of.

3.2) Scope:

It can be used by any foundation which provides scholarship to students.

12

3.3) Administrator Characteristics

Every user (administrator) should be:

• Comfortable of working with computer.

• He must have knowledge in banking Transaction.

• He must also have basic knowledge of English.

Every user (student) should be:

• Comfortable of working with computer.

• He must also have basic knowledge of English.

3.4) System analysis:

Analysis of the system can be divided into following 3 phases:

 Structured Analysis
 Package Selection
 System specifications

4. REQUIREMENT COLLECTION AND ANALYSIS

4.1) Requirement gathering and analysis:
13

This activity typically involves interviewing the students and studying the existing documents
to collect all possible information regarding the system. If the project involves automating
some existing procedures.

The main purpose of this activity is to clearly understand the exact requirements of the
student. After the exact student requirements are understood, the next step is to identify and
resolve the various requirements problems. The most important requirement problems are the
problems of anomalies and incompleteness.

4.2) Software Requirements Specification (SRS)

Once the analyst has performed all the above mentioned activities, all the requirements are to
be systematically organized in the form of an SRS document. The SRS document usually
contains all the user requirements in an informal form.

An SRS document clearly documents the following aspects of a system:

 Environmental characteristics
o Hardware
o Software
 Functional Requirements
 Non-Functional Requirements

4.2.1) Environmental Characteristics:

Hardware Requirements
Processor RAM Disk Space
Pentium III,Pentium IV or 64 Mb or higher 130 Mb
higher
Software Requirements
Operating System Database
Win-7,Win-8.1 MongoDB

4.2.2) Functional Requirements:

Each high-level functional requirement corresponds to an instance of use of the system by the
user in some way. Each high-level requirement typically involves accepting some data from
the user, transforming it to required response, and outputting the response to the user.

Some of the functional requirements which we have tried to gather for our project on
Scholarship Management System are as:

Student from poor background need scholarship as they can’t afford to pay fees.
Admin will look after the Scholarship processes working.

Only Eligible students will get scholarship.

14

A Manager is hired that will take care of collecting the documents of students for
conformation and he/she will solve query’s of students.

4.2.3) Non-Functional Requirements:

Non-Functional requirements are the ones that specify criteria that can be used to judge the
operation of a system, rather than specific behaviors.

The ones concerned for the project are as:

 Security
Security is the degree of protection against danger, damage, loss and crime. In
order to ensure security, a login is maintained which is user name and
password secured and hence forth is accessible by only certain trustworthy
people from admin.

 Maintainability
Maintainability refers to the ease with which a product can be maintained in
order to:
o Isolate requirements of their cause
o Meet new requirements
o Make future management easier or,
o Cope with a changed environment

It involves continuous improvement and can be achieved as system is

monitored on a regular basis and the student’s feedback can help to make and
maintain changes in the future.

 Performance
Good performance is maintained by providing a reliable and high quality
service to the students as student satisfaction is the top most priority.

 Testability
Testability refers the capability of a system to be tested. As this system depicts
a real life scenario it can be easily tested, as to how it is able to store student
details and generate the bill for the facilities availed properly or not.

 Usability
Usability is the ease of use and learn ability. System is made very user friendly
using interactive GUI so that it is easy to use, understand and maintain as well.

 Robustness
Robustness is the ability of a system to cope with errors during execution. As
the system has been tested for all sorts of invalid and unexpected inputs hence
it is Robust in nature.

 Accessibility
15

Accessibility can viewed as the ‘ability to access’ and benefit from some
system or entity. System is accessible only to admin in this case and hence is
easily accessible and easy to maintain.

 Portability
It describes that how easy it is to reuse the system. It requires generalized
abstraction between the application logic and system interfaces. This system is
quite portable as a few minor changes and it can cater to various scholarship
centres.

4.2.4) Sources of information/requirement gathering:

Information can be gathered from two major sources:

1. Internal Sources
 Personal staff
 Professional staff
 System Documentation or manuals.
 Reports and transaction documents.

2. External Sources
 Government Documents.
 Internet

5. DATABASE DESIGN

5.1 Conceptual Design:

 16

Administrator handling the system:

Admin Logs in the system Maintains the system by After performing specified tasks, system shut
performing certain tasks down.

Maintains student’s personal as well as Managing Trustees records

academics and bank details

Maintaining Foundation Account

Sort the List of students by their annual

income and marks.

Transfer Scholarship
Amount

Keeping track of students and their scholarship

amount.

Students handling the system:

Student Logs in the system Maintains the system by After performing specified tasks, system shut
performing certain tasks down.

Apply for Scholarship Update Bank Details

Update information Check the List of Students

5.2 Logical Model:

Student
17

Mo-Name Pincode

User-Name Amount

Name Gender amount

Address
DOB
Sch- Fund
Holder Foundation Transfer

Name

Income

Qualification Password

Pay-ment Trustee

SSCMarks HSCMarks Eli-Stdnt

Amount
Tru_Name

Curr-Details

Payment-Mode
Clg-Name

Acc_No.
Branch Amount
AcadmicYear Bank_Name

Branch
IFSC_Code

Branch MICR_Code

5.3 Relational Schema:

Table_Schol._Holder
Username
Table_Trustee
Password
Name
E-Mail
Amount
Contact_no
18

Table_Bank
Bank_Name
Branch
Account_no
IFSE-code
MICR-code Table_Account
Table_student Password
username Balance
Name Tru_Amount
Mother_name Trans_Amount
Date of birth Total
Address
Annual Income
SSC details
HSC details
Current details
Scho_Amount
Table_Admin
Username
Password

5.4 Schema Diagram:

Tables:

1.Scholarship_Holder:
19

Username Password E-mail Contact

No.

2.Student:

User- Nam Mothe Add Pin Date E- Contac Annua SSC HSC Current
nam e r name . cod of mai t No. l Detail Detail Details
e e Birt l income s s
h

3.Bank:

Username Bank Bank Account IFSE code MICR

name Branch No. code

4.Trustee:

Name Sanction Total

Amount

5.Foundation Account:

Password Balance Trustees Transfer Total

Amount Amount

6. NORMALIZED TABLES

1. Scholarship_Holder:

Username Password E-mail Contact

20

No.

Username-> password, E-mail, Contact No.

The table Student is in 1 NF as:

 All the underlying domains of the relation contain atomic (indivisible) values.
 No repeating groups in the table.
 All attributes dependent on primary key.

The table Student is in 2 NF as:

 It is in 1 NF
 It includes no partial dependencies as every non key attribute is fully dependent on the
primary key.

The table Student is in 3 NF as:

 It is in 2 NF
 Every non key attribute is non-transitively dependent upon the primary key.

2. Student:

User- Nam Mothe Date E- Contac Annua

nam e r name of mai t No. l
e Birt l income
h

Username-> Name, Mother name, Date of Birth, E-mail, Contact No., Annual income

User- Add Pin

nam . cod
e e

Username-> Add, Pin code

User- SSC HSC Current

name Detail Details Details
s
Details, HSC Details, Current Username-> SSC
Details

The table Products, Services are in 1 NF as:

 The underlying domain of the relation contains atomic (indivisible) values.
 No repeating groups in the table.

The table Products, Services are in 2 NF as:

 It is in 1 NF
21

 It includes no partial dependencies as there are no non key attributes.

The table Products, Services are in 3 NF as:

 It is in 2 NF
 It includes no transitive dependencies as there are no non key attributes.

3.Bank:

Username Bank Bank Account IFSE code MICR

name Branch No. code

Username-> Bank name, Bank Branch, Account No., IFSE code, MICR code

All the above tables are in 1 NF as:

 All the underlying domains of the relation contain atomic (indivisible) values.
 No repeating groups in the table.
 All attributes dependent on primary key.

All the above tables are in 2 NF as:

 It is in 1 NF
 It includes no partial dependencies as every non key attribute is fully dependent on the
primary key.

All the above tables are in 3 NF as:

 It is in 2 NF
 Every non key attribute is non-transitively dependent upon the primary key.

4.Trustees:

Name Sanction Total

Amount

Name-> Sanction Amount, Total

The above table is in 1 NF as:

 All the underlying domains of the relation contain atomic (indivisible) values.
 No repeating groups in the table.
 All attributes dependent on primary key.

The above table is in 2 NF as:

 It is in 1 NF
 It includes no partial dependencies as every non key attribute is fully dependent on the
primary key.

The above table is in 3 NF as:

22

 It is in 2 NF
 Every non key attribute is non-transitively dependent upon the primary key.

5. Foundation Account:

Password Balance Trustees Transfer Total

Amount Amount

Password -> Balance, Trustees Amount, Transfer Amount, Total

The above table is in 1 NF as:

 All the underlying domains of the relation contain atomic (indivisible) values.
 No repeating groups in the table.
 All attributes dependent on primary key.

The above table is in 2 NF as:

 It is in 1 NF
 It includes no partial dependencies as every non key attribute is fully dependent on the
primary key.

The above table is in 3 NF as:

 It is in 2 NF
 Every non key attribute is non-transitively dependent upon the primary key.

7. DBMS SELECTION

Back-end desired features:

23

1. Multiple user support.

2. Efficient data handling.

3. Provide inherent features for security.

4. Efficient data retrieval and maintenance.

5. Stored procedures.

6. Popularity.

7. Operating System compatible.

8. Easy to install.

9. Various drivers must be available.

10. Easy to implant with the Front-end.

According to above stated features we selected MongoDB as the backend.

8. APPLICATION DESIGN

Front-end selection:
24

An important issue for the development of a project is the selection of suitable front-end.
When we decided to develop the project we went through an extensive study to determine the
most suitable platform that suits the needs of the organization as well as helps in development
of the project.

The aspects of our study included the following factors.

1. It must have a graphical user interface that assists employees that are not from IT
background.

2. Scalability and extensibility.

3. Flexibility.

4. Robustness.

5. According to the organization requirement and the culture.

6. Must provide excellent reporting features with good printing support.

7. Platform independent.

8. Easy to debug and maintain.

9. Event driven programming facility.

10. Front end must support some popular back end like MongoDB.

9. PROJECT IMPLEMENTATION

9.1 Implementation of Front-End:

25
26
27
28

Code: (for validation and insertion in student document)

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;
using MongoDB.Bson;
using MongoDB.Driver;
using MongoDB.Driver.Builders;

namespace scholarship_management
{
public partial class Form3 : Form
{

public Form3()
{
InitializeComponent();
}

private void Form3_Load(object sender, EventArgs e)

{

private void button1_Click(object sender, EventArgs e)

{
29

MongoServer mongo = MongoServer.Create();

mongo.Connect();
MongoDatabase db;

db = mongo.GetDatabase("project");

MongoCollection<BsonDocument> bk =
db.GetCollection<BsonDocument>("scholarship_holder");

BsonDocument mybk = new BsonDocument {

{ "username",un_tbox.Text },
{"password" , pass_tbox.Text},
{"e_mail",mail_tbox.Text},
{"contact",no_tbox.Text}
};

bk.Insert(mybk);
MessageBox.Show("Successfully Created Acount!");

this.no_tbox.Text = null;
this.un_tbox.Text = null;
this.pass_tbox.Text = null;
this.repass_tbox.Text = null;
this.mail_tbox.Text = null;

private void un_tbox_Validated(object sender, EventArgs e)

{
MongoServer mongo = MongoServer.Create();
mongo.Connect();
MongoDatabase db;

db = mongo.GetDatabase("project");

// MongoCollection<BsonDocument> bk =
db.GetCollection<BsonDocument>("books");
MongoCollection<info> bk = db.GetCollection<info>("scholarship_holder");

foreach (info mybk in bk.FindAll())

{
if (this.un_tbox.Text == mybk.username)
{
MessageBox.Show("already exist");
break;
}
}

if (this.un_tbox.TextLength < 5)
30

{
MessageBox.Show("username should contain atlest 5 letters");
this.un_tbox.Text = null;
}

private void pass_tbox_Validated(object sender, EventArgs e)

{
if (this.un_tbox.TextLength < 5)
{
MessageBox.Show("password should contain atlest 5 letters");
this.pass_tbox.Text = null;
}

private void repass_tbox_Validated(object sender, EventArgs e)

{
if (this.pass_tbox.Text != this.repass_tbox.Text)
{
MessageBox.Show("Please enter correct password");
this.repass_tbox.Text = null;
}

private void no_tbox_Validated(object sender, EventArgs e)

{
if ((this.no_tbox.TextLength < 10))
{
MessageBox.Show("Invalid Number");
}
}

private void pre_btn_Click(object sender, EventArgs e)

{
Form2 obj = new Form2();
this.Hide();
obj.Show();
}

private void un_tbox_TextChanged(object sender, EventArgs e)

{

private void mail_tbox_Validated(object sender, EventArgs e)

{
string email = mail_tbox.Text;
31

if (email.LastIndexOf("@") > -1)

{
// MessageBox.Show("Valid Email address ");
}
else
{
MessageBox.Show("Not a valid Email address ");
}
}

private void no_tbox_KeyPress(object sender, KeyPressEventArgs e)

{
if (!(char.IsDigit(e.KeyChar)))
MessageBox.Show("Invalid Contact");
}
32

10. TESTING

10.1 Testing

 Testing a piece of code consists of subjecting the code to a set of test inputs (or test
‘cases) and observing if the piece of code behaves as expected or not.

 If the code fails to behave as expected, then the conditions under which failure occurs
are noted for later debugging and correction.

 Thus testing provides a practical way of reducing defects in a system and increasing
the user’s confidence in a system.

 The main objectives of testing are as follows:

 To make sure that the program during operation will perform as per the
specifications lay down at the time of system analysis.

 To ensure that the control incorporated in the program and the system
functionality are significant.

 To make sure that during the operation, incorrect inputs and processing will be
detected and handled.

10.2 Testing the Project:

1. Data integrity through constraints:

A constraint refers to a condition or a check that is applied to a column (field) or set of

columns in a table. The constraints applied to maintain data integrity are also known as
Integrity Constraints.

These constraints ensure database integrity, thus are sometimes called database integrity
constraints. A few of them used in the project are as:

a) Primary Key Constraint:

This constraint declares a column as the primary key of the table. This constraint is
similar to unique constraint except that only one column
(Or one group of columns) can be applied in this constraint. The primary key does not
allow NULL values.

Username, Trustee_Name, Account_Password are the primary keys which avoids

duplication of rows and does not allow null values.
33

b) Foreign Key Constraint:

Whenever two tables are related by a common column (or set of columns) then the related
columns(s) in the parent table (or primary table) should be either declared as a primary
key or unique key and the related column(s) in the child table (or related table) should
have Foreign Key Constraint.

For instance,
Username is acting as a foreign key in bank details, academic details, which references
the Username of the Scholarship_Holder table which is acting as the primary key.

c) Unique Constraint:

This constraint ensures that no two rows have the same value in the specified column(s).

For instance,
Unique constraint has been applied on the Username number of the student as no two
Usernames can ever be identical.

d) NOT NULL Constraint:

By default tables can contain NULL values. By applying the NOT NULL constraint on a
particular column(s), it becomes mandatory to enter value for that column(s).

For instance,
NOT NULL has been enforced on the s_name, bank_name, contact of the student .

e) Check Constraint:

This constraint limits values that can be inserted into a column of a table.

For instance,
The check constraint has been applied in order to ensure that the students annual income
should not be greater than 2000000.

f) Default Constraint:

Using the default constraint, a default value can be specified for a column using the
DEFAULT clause. When a user does not enter a value for the column (having default
value), automatically the defined default value is insert in the field.

For instance,
When scholarship Amount Transfer to students account the value of scholarship amount
balance become zero.

2. Validating the tables:

34

Data entered through tables is added in accordance with the constraints applied.

For example,
Entering only numeric values for Student contact and marks.

3. Checking of Errors:

Different command buttons and toolbar buttons are tested so as to check whether it
performs the correct intended function or not. Combo boxes and list boxes are checked so
as to know whether all the options are present or not. Common issues like submission of
forms without filling in the required entries are checked.

1) Unique Constraint Violated:

The value being depicted as primary key cannot be NULL and redundant.

Hence while inserting data, it is made sure that each and every student is assigned a
unique Username and a unique name for an trustee. It should also be made sure that
the appropriate data is entered for fields not allowing NOT NULL values.

2) Parent Key Not found:

The parent key should be present in the parent table and then only the foreign key
value(s) should be inserted in the child table.

For instance,
It is made sure that, details of a student has been saved prior to computing the
scholarship amount and services availed by the student.
35

CONCLUSION

The project on a Scholarship Management System is for computerizing the working in a

scholarship.

The software takes care of all the requirements of an average scholarship and is capable to
provide easy and effective storage of information related to students that come up to the
scholarship.

The system also provides the facility of backup as per the requirement.

BIBLIOGRAPHY

1. Database System Concepts by Henry F. Korth

2. MongoDB- O’Reilly Publications
3. www.w3schools.com
4. www.mongodb.org