DATABASE DESIGN

Training and Placement Cell

Database Design
1. Introduction
Database:
A Database is collection of related data, which can be of any
size and complexity. By using the concept of Database, we can
easily store and retrieve the data. The major purpose of a database
is to provide the information, which utilizes it with the
information’s that the system needs according to its own
requirements.
Database Design:
Database design is done before building it to meet needs of
end-users within a given information-system that the database is
intended to support. The database design defines the needed data
and data structures that such a database comprises.
The database is physically implemented using MySQL.

2. Scope
2.1 Identification
This document describes the standards to be used when
designing and developing the database for “Training and
Placement Cell” Android Application. This design is based
on the Software Requirement Specification of “Training and
Placement Cell” Android Application. A database is an
integrated collection of logically related records or files.
Database design is used to describe any different parts of the
design of an overall database design.
Title: Database Design Document (DBDD) for “Training and
Placement Cell” Android Application.

2.2 DBDD Overview

DBDD explain all database required for the design of
“Training and Placement Cell” Android Application.
 3. Purpose
The purpose of this document is to describe the standards to be
used when designing and developing the database. It helps the
database designer to design the database configuration. Software
developers make use of this document to design the software.

3.1 Objectives of Database design document

The main objectives of database design document are,
 To produce physical database design.
 To produce logical database design.

4. Database Tables
 Student

Field Name Data Type SIZE Constraint Type DESCRIPTION

stud_rid Integer 5 Primary Key Citizen ID

Name Varchar 50 Not Null Student Name

Father_name Varchar 75 Not Null Student’s father name

Contact Varchar 10 Not Null Student’s contact number

Email Varchar 25 Not Null Student’s email ID

Password Varchar 100 Not Null Students Password

Address Varchar 1 Not Null Student’s address

Reg_no Varchar 11 Not Null Student’s Reg number

Sslc_mark Integer 3 Not Null Students SSLC mark

Puc_mark Integer 3 Not Null Student’s PUC mark

Skills Varchar 25 Not Null Student’s Skill

Dept_rid Integer 2 Not Null Student’s department

 Company
Field Name Data Type SIZE Constraint Type DESCRIPTION

comp_rid Integer 11 Primary Key Company ID

Name Varchar 50 Not Null Company Name

Branch Varchar 30 Not Null Company branch name

Contact Varchar 10 Not Null Company Contact

number

email Varchar 75 Not Null Company Email ID

address Varchar 100 Not Null Company Address

password Varchar 100 NOT NULL Company login

password

Website Varchar 50 Not Null Company website

 Application

Field Name Data Type SIZE Constraint Type DESCRIPTION

app_rid Integer 11 Primary Key Application ID

Stud_id Integer 11 Not Null Students ID

Op_rid Integer 10 Not Null Opening ID

Applied_date_time Date - Not Null Application date and

time

status Integer 11 Not Null Application status

 Department

Field Name Data Type SIZE Constraint Type DESCRIPTION

Dept_rid Integer 10 Primary Key Department ID

Name Varchar 25 Not Null Department Name

Status Integer 4 Not Null Department status

  Feedback

Field Name Data Type SIZE Constraint Type DESCRIPTION

fb_rid Integer 11 Primary Key Feedback ID

Stud_id Integer 11 Not Null Students ID

tite Varchar 25 Not Null Feedback title

Body Varchar 100 Not Null Feedback content

status Integer 11 Not Null Feedback status

 Opening

Field Name Data Type SIZE Constraint Type DESCRIPTION

opening_rid Integer 11 Primary Key Opening ID

comp_id Integer 11 Not Null Company ID

title Integer 10 Not Null Opening title

Short_desc Varchar 100 Not Null Opening description

Long_desc Varchar 200 Not Null Opening Description

status Integer 11 Not Null Opening status

Place Varchar 25 Not Null Opening Place

Created_at Date - Not Null Opening added Date

5. Entity Relationship Diagram

An entity-relationship (ER) diagram is a specialized graphic that
illustrates the entire relationship between entities in a database. ER
diagrams often use symbols to represent three different types of
information. Boxes are commonly used to represent entities. Diamonds
are normally used to represent relationships and ovals are used to
represent attributes.
 Entity: Entity is represented by a box within the ERD. Entities are
abstract concepts, each representing one or more instances of the
concept in question. An entity might be considered a container that
holds all of the instances of a particular thing in a system. Entities are
equivalent to database tables in a relational database, with each row of
the table representing an instance of that entity.

Relationship: Relationships are represented by Diamonds. A

relationship is a named collection or association between entities or
used to relate to two or more entities with some common attributes or
meaningful interaction between the objects.

Attributes: Attributes are represented by Oval. An attribute is a single

data item related to a database object. The database schema associates
one or more attributes with each database entity.

The Symbols used in E-R diagram are shown below:

Name Notation

Entity

Relationship
 Attributes

ER-Diagram:

name
contact id Stud_id
id
date

add RESUME
STUDENT

SSLC
marks
email college PUC
marks

View

username

password id name

Manage
ADMIN COMPANY

email
contact

address