A TrAining reporT on

Submitted for the Requirement of

Training Certificate
SUBMITTED BY : VIKASH RANJAN
REGISTRATION NO : DSPMU2021005455
DEPARTMENT : MCA
COLLEGE : Dr. Shyama Prasad Mukherjee University,Ranchi
 ACKnoWLeDgeMenT

I take this opportunity to express my profound gratitude

and deep regard to my guide Mr. Ashokeshwer Godara
(Dy.Manager (System) CCL HQ) for his exemplary
guidance, monitoring and constant encouragement
throughout the course of the internship.

I also take this opportunity to express a deep sense of

gratitude to System department and HRD
department CCL, Ranchi for their cordial support,
valuable information and guidance which helped me in
completing this task through various stages.

Lastly, I thank the almighty, my parents and friends for

their constant encouragement. Without which this
assignment would not have been possible.
 DeCLArATion

I hereby declare that the entire work embodied in this

project has been carried out by me and no part of it has
been submitted for any degree/diploma of any university/
institution previously.

NAME : VIKASH RANJAN

REGISTRATION NO : DSPMU2021005455
DEPARTMENT : MCA
COLLEGE : DSPMU, RANCHI
 CerTiFiCATe

This is to certify that this project has been made by VIKASH

RANJAN of MCA department (DSPMU, Ranchi) on the topic
‘STORE MANAGEMENT SYSTEM’ under the guidance of Mr.
Ashokeshwer Godara at CCL Headquarters. Training period
was from 07/05/2023 to 08/07/2023.

GUIDED BY :-

Mr. Ashokeshwer Godara

Dy.Manager (System)

CCL Headquarter,

Darbhanga House, Ranchi

GM HRD

CCL Headquarter,

Darbhanga House, Ranchi

 TABLe oF ConTenT
 About the company
 Introduction
About the project
The purpose and scope
Existing system
Benefits of Proposed System:
 Modules
Details about the department: -
Departments: -
Admin: -
Issue hardware: -
Status of the Request: -
Reports: -
 ER diagram
 Software requirement specification
Introduction
Module
Hardware requirement
Software requirement
Functional requirement
Non-functional requirement
Design constraints
 Overall description
Product perspective:
Product functions
User characteristics
Assumptions and Dependencies
 Coding
Admin login
Department signup
Listed computer peripherals
Issued computer peripherals
 Screen captures
Home page
Login page
User dashboard
Admin page
Admin dashboard
 Conclusion
 CENTRAL COALFIELDS LIMITED
Central coalfields limited is a category-1 mini rattan company since October
2007. Formed on 1st November 1975, CCL (formally national coal
development corporation limited) was one of the five subsidiaries of Coal
India Ltd. Which was the first holding company for coal in the country(CIL
now has 8 subsidiaries).

CCL has a proud past. As NCDC, it heralded the beginning of nationalization

of coal mines in India. NCDC was set up in October 1956 as government
owned company in pursuance of the industrial policy resolution of 1948 and
1956 of the government of India. It was started with nucleus of 11 old state
collieries (owned by the railways) having a total annual production of 2.9
million tons of coal.

Project area under CCL

 Barka-Sayal
 Argada
 North Karanpura
 Rajhara
 Rajrappa
 Piparwar
 Kathara
 Kuju
 Hazaribagh
 Bokaro & Kargali
 Dhori
 Magadh Amrapali
 Mines rescue station
 INTRODUCTION

The store management deals in management of records. The records include

computer peripherals which are required by different departments of an
organisations accordingly. Maintaining these records manually becomes
difficult thus we are proving such system a computerized backend. In this
system each department is provided with a department id and all the
records are maintained in a table along with the department’s id. Any
information can be accessed according to department’s id anytime from the
table and also at the time of issuing computer peripherals.

ABOUT THE PROJECT

The aim of this project is to computerize the operation of issuing COMPUTER

PERIPHERALS in the college or any another organization. It is very difficult
to manage all the works manually. There may have many problems in
accuracy, managing information etc. The proposed system has been
designed to replace the existing manual system and is user friendly.

THE PURPOSE AND SCOPE

The main purpose of Store Management System is to help automate the

entire Store process performed in the organization. The main objective of
the proposed system is to eliminate the limitations of the existing system.
Computers are fast and tireless machines that can process large number of
results. In short, it provides quality reports.

The goals of Store Management System are:

 To Minimize the time delay for issuing computer peripherals.
 Minimize the amount of paper work require.
 Quick processing.
 Most of the works should be done by the computers, reducing the
works.
 To provide a searchable database to view the reports.
 Unnecessary document flow and duplication of data will be eliminated
 Easy access to information.
Existing System:

Existing system is based on manual work and all process are done manually.
Various types of reports, registers and bills are being prepared on a periodic
basis manually. This involves a lot of paper works which results in various
difficulties in terms of time and storage space. Report preparation is also
done in manually which results in the wastage of both time and manpower.

Benefits of Proposed System:

The main objective of the proposed system is to eliminate the limitations of

the existing manual system. Most of the limitations of the existing system
can be overcome by the proposed system. Speed and accuracy are the main
advantages of proposed system. There is no redundancy of data. Since all
the details are stored in computer searching time can be reduced. The
information can be more secure because the computer systems are more
secure. The proposed system eliminates the drawbacks of the existing
system to a great extent and it provides security of data.
 MODULES

Details about the department: -

This module deals with the complete information about the departments who applied
for peripherals. This information contains department name, department id and other
information.

Departments: -
This page is used to store the details of the departments, to whom the peripherals is
issued. This page stores the details of the computer peripherals issued to specific
departments.

Admin: -
This page stores the details of admin, available devices, detail of available computer
devices like UDI number, manufacture company etc. The admin is authorised to issue
the computer peripherals.

Issue hardware: -
This module deals with the issue of hardware to the departments. This also contains the
changes in the hardware if occurred due to some defects etc.

Status of the Request: -

This module contains the complete information about the computer peripheral and
details about the total number of issued hardware to that particular department.

Reports: -
Various reports are generated, which provide the information like list of hardware
present in the stock, list of the computer peripheral issued to different
departments, list of departments having system etc.
 ER DIAGRAM

Dept name
Name

Contact no UDIN
Dept id

Computer
Department
peripherals

request

Issues maintenance
hardware

Issue
Admin
date

maintenance
ss

Hardware

Dept id
Reports

UDIN

Dept name
Issue date
company
 SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION

Requirements specification is the starting step for the development

activities. It is currently one of the weak areas of software engineering.
During requirement specification, the goal is to produce a document of the
client’s requirements. This document forms the basis of development and
software validation. The basic reason for the difficulty in software
requirements specification comes from the fact that there are three
interested parties- the client, the end users and the software developer.
System requirement give an idea about what are the necessary things that
are needed for the proposed system, which plays a very important role in
the development of any system. This chapter deals with what are hardware
components that are needed for the system, application, software that are
required for the development of the system and the functional requirement
of the system. Frontend tools helps to visualize the system, while backend
helps in activities which are not visible to the end user.

MODULE

This project consists of 2 modules

3.2.1 Admin
3.2.2 Department/User

Admin module:
Functionalities:
Adding computer peripherals.
Managing department’s request.
Having data of available devices.
Adding new peripherals with respective company.

Department module:
Functionalities:
Adding department details.
Make request for computer peripherals.
Add hardware details required .
View all issued devices.
View feedback and send response to the admin.
Set the user’s name and password .
Update Profile.

HARDWARE REQUIREMENTS

PROCESSOR : Intel Pentium 4 or more

SPEED : 1.40GHz or faster
RAM : 4 GB or more
MONITOR : 15” CRT, or LCD monitor
HARD DISK : 500 GB hard disk or more
FLOPPY DRIVE : 1.44 MB or more
CD DRIVE : LG 52X
KEYBOARD : Normal or Multimedia
MOUSE : Compatible mouse
OPERATING SYSTEM : 32/64-Bit operating system, x86/x64- based processor

SOFTWARE REQUIREMENTS

OPERATING SYSTEM : Windows XP/7/8/8.1/10/11

LANGUAGE : PHP
WEB TECHNOLOGY : HTML, CSS, JavaScript and PHP
BACKEND : MYSQL
IDE & TOOLS : Xampp, Any Web Browser
FRONT END : HTML5, CSS3
CONTROL END : JavaScript
BACK END : PHP, MySQL

FUNCTIONAL REQUIREMENTS

Input/output:
First Admin login into the web application and add new department into the organization.
Department login with his id password and can manage his account as well as request for any
peripheral device. Department login with his id-password and can view .issued devices and can
update his account

Storage Requirements:
All the details of Admin, Department, list of available and issued computer peripheral’s
details are stored in the database and the updating of the data can be done through
database(internet).
NON-FUNCTIONAL REQUIREMENTS

Usability: The system is designed with completely automated process. Hence

there is no or less intervention.

Reliability and Security: The System is more reliable because of the qualities
that are inherited from chosen platform. And it provides secure access of
confidential data with unique id and password.

Supportability: The system is designed to be the cross platform supportable.

The system is supported on a wide range of hardware and software
platform.

DESIGN CONSTRAINT

Design constraints in a store management system refer to the limitations or

restrictions that influence the system's design and implementation. These constraints
may arise from various factors such as technical considerations, resource limitations,
regulatory requirements, or organizational policies. Here are some common design
constraints in a store management system:
Technology Stack: The system may need to be built using specific technologies or
programming languages based on the organization's existing infrastructure, skill sets,
or compatibility requirements.
Hardware and Infrastructure: The system's design may be constrained by the available
hardware resources, network infrastructure, or server capacities that impact factors
such as scalability, performance, and reliability.
Budget and Resource Constraints: The system's design and implementation may be
limited by budget constraints, availability of resources (both human and financial), or
time constraints that influence the scope and complexity of the system.
Security and Privacy Regulations: The design must adhere to relevant security and
privacy regulations, such as data encryption, user consent requirements, data access
restrictions, and protection of personal information.
Accessibility Standards: The system's design should comply with accessibility
standards and guidelines, ensuring that users with disabilities can access and use the
system effectively.
Integration with Existing Systems: The system may need to integrate with existing
store systems or third-party systems, which can impose design constraints related to
data formats, APIs, protocols, or compatibility requirements.
User Experience Guidelines: The system's design may need to align with established
user experience guidelines or branding standards of the organization, ensuring a
consistent and intuitive user interface.
Performance Requirements: The system's design must meet performance
requirements, such as response times, concurrent user support, or scalability, within
the given constraints of hardware, infrastructure, and available resources.
Data Management and Storage: The design should consider constraints related to data
management, storage, and retrieval, such as database technologies, data replication,
backups, or compliance with data retention policies.
Organizational Policies and Processes: The system's design may need to align with
specific organizational policies, workflows, or processes related to hardware
operations, user management, or financial procedures.
Regulatory Compliance: The system's design may be constrained by legal and
regulatory requirements specific to the hardware domain, such as copyright laws, or
intellectual property rights.
Time-to-Market Constraints: The design may need to be completed within specific
timeframes or milestones, considering business priorities, market demands, or time-
sensitive projects.
Considering these design constraints ensures that the store management system
meets the necessary technical, regulatory, and organizational requirements, while also
being feasible and practical to implement within the given limitations.
 OVERALL DESCRIPTION

Product perspective:-
The product perspective In focuses on delivering a comprehensive and user-
friendly digital platform that enables libraries to manage their operations
efficiently and provides a seamless experience for patrons accessing library
resources remotely. Here are key aspects to consider from a product
perspective:

Web-Based Interface: The store management system should have a web-

based interface accessible via browsers, ensuring compatibility across
different devices and operating systems. The interface should be responsive,
visually appealing, and easy to navigate.

Digital Catalog Management: The system should support the management of

various digital resources, including monitor, keyboard, mouse, scanner. It
should provide capabilities to add, update, and organize digital items, assign
metadata, and facilitate searching and browsing through the digital catalog.

User Registration and Authentication: The system should allow patrons to

register for account online, providing necessary personal information, and
generating unique login credentials. Strong authentication mechanisms, such
as username-password combinations or multi-factor authentication, should
be implemented to ensure secure access to the system.

Search and Discovery: The store management system should offer advanced
search functionality, enabling patrons to search for digital resources using
keywords, filters, and other criteria. It should provide relevant search
results, display detailed item information, and support features like previews
and sample chapters to aid in resource discovery.

Borrowing and Access: Patrons should be able to borrow digital resources

directly from the store management system. The system should facilitate
controlled access to digital items. It should also track borrowing durations
and enforce any restrictions or licensing agreements.

Online Reservations and Requests: Patrons should have the ability to reserve
or request digital resources that are currently in use by others. The system
should manage the queue, notify patrons when the requested items become
available, and automate the lending process.

Personalized Recommendations: The system can leverage user data, such as

borrowing history or preferences, to offer personalized recommendations for
digital resources. This feature can help patrons discover new materials
aligned with their interests and enhance their overall experience.

User Management and Communication: The store management system

should provide tools for admin to manage patron accounts, track user
activities, handle account renewals, and communicate with patrons
regarding overdue items, reservation updates. Email notifications or
messaging functionalities can be integrated for effective communication.

Analytics and Usage Reports: The system should offer analytics and
reporting features to provide insights into resource usage, popular items,
user behaviour, and other relevant metrics. These analytics can help admin
make data-driven decisions, optimize their collections, and improve services
based on user needs.

Security and Privacy: The system should prioritize security measures to

protect user data, ensure secure transactions, and guard against
unauthorized access. Data encryption, secure server configurations, regular
security updates, and compliance with privacy regulations are essential
aspects to address.

Scalability and Reliability: The store management system should be

designed to handle increasing user loads and growing digital collections.
Scalability measures, such as cloud-based infrastructure or load balancing,
should be implemented to ensure the system's performance and availability.

Support and Upgrades: Adequate technical support and documentation

should be provided to admin and patrons in using the system effectively.
Regular software updates, bug fixes, and feature enhancements should be
delivered to address any issues and introduce new functionalities.

An effective store management system aims to make hardware resources

easily accessible, simplify administrative tasks.
PRODUCT FUNCTIONS:
In a store management system, there are several key functions that facilitate efficient
management of store operations and enhance the user experience. Here are some
important functions typically found in such systems:

User Registration and Account Management: Allows patrons to create accounts online,
providing personal information and generating unique login credentials. Enables admin
to manage user accounts, track user activities, handle account renewals, and maintain
user-specific settings.

Hardware Management: Provides capabilities to manage the store's digital resources,

including adding, updating, and organizing items in the sequence. Allows admin to
assign metadata (such as monitor, mouse, keyboard, scanner) to resources, ensuring
accurate search and retrieval.

Search and Discovery: Offers a robust search functionality, allowing users to search for
digital resources based on various criteria such as monitor, mouse, scanner, keyboard,
or UDI. Provides search filters, advanced search options, and relevance-ranking
algorithms to facilitate resource discovery.

Borrowing and Circulation: Enables patrons to borrow digital resources online,

specifying borrowing durations and managing borrowing limits.

Online Reservations and Requests: Allows users to place reservations or requests for
digital resources that are currently in use by others. Manages reservation queues,
sends notifications to patrons when the requested items become available, and
automates the lending process.

Digital Resource Access: Provides secure and controlled access to digital resources,
allowing patrons to download or access them online. Implements digital rights
management (DRM) techniques to protect copyright and enforce access restrictions as
per licensing agreements.

Personalized Recommendations: Utilizes user data, such as borrowing history or

preferences, to offer personalized recommendations for digital resources.
User Communication and Notifications: Facilitates communication between admin and
user through messaging features or email notifications. Sends automated notifications
for overdue items, reservation updates, account renewals, or store announcements.

Administrative Dashboard: Provides admin with a centralized dashboard to manage

and monitor various aspects of the system, including user accounts, borrowing
activities, reservation queues, catalo updates, and system configurations.

Reporting and Analytics: Generates reports and analytics on resource usage, popular
items, user behaviour, and other relevant metrics. Offers insights to help admin make
data-driven decisions, optimize collections, and improve services based on user needs.

Integration with External Providers: Integrates with external digital content providers,
such as online databases or hardware, to offer seamless access to a broader range of
digital resources. Enables users to search and access resources from multiple providers
within the same system.

System Configuration and Customization: Allows admin to configure system settings,

customize workflows, and tailor the system to meet specific hardware requirements.
Provides flexibility in adjusting parameters, user permissions, and display options.

Security and Privacy: Implements robust security measures to protect user data, ensure
secure transactions, and prevent unauthorized access. Adheres to privacy regulations
and guidelines to safeguard user privacy and confidentiality.

Help and Support: Provides comprehensive documentation, user guides, FAQs, and
contextual help within the system to assist users in navigating and utilizing the
features effectively. Offers technical support channels for addressing user queries or
troubleshooting issues.

These functions collectively contribute to the smooth operation of a store management

system, ensuring efficient resource management, streamlined user experiences, and
effective hardware services.
USER CHARACTERISTICS:
In a store management system, user characteristics refer to the specific
attributes or information associated with each user account. These
characteristics help in identifying and managing user accounts effectively.
Here are some common user characteristics in a store management system:

User ID: A unique identifier assigned to each user for login and system
identification purposes.

Username: A chosen name or handle used by the user to log in to the

system.

Password: A secure and confidential code known only to the user to

authenticate their identity.

Department Information: Includes department's name, contact details

(email address, phone number, etc.), and address for communication
purposes.

Membership Type: Indicates the type of user account or membership level,

such as department.

Borrowing Privileges: Specifies the department user ID, duration, and any
restrictions on borrowing materials based on the user's membership type.

Reading History: Keeps track of the hardware use by the department,

helping them keep a record of their reading preferences and history.

Access Level: Determines the user's access rights within the system, such as
administrative privileges or restricted access to certain features.

Preferences: User-specific settings or preferences, such as language

preferences, notification preferences, or preferred genres.

These user characteristics aid in managing user accounts, ensuring security,

providing personalized services, and maintaining a smooth operation of the
store management system.
ASSUMPTIONS AND DEPENDENCIES:
Assumptions and dependencies in a store management system refer to the
underlying conditions or prerequisites that need to be met for the system to
function properly. These assumptions and dependencies can impact the
design, implementation, and operation of the system. Here are some
common assumptions and dependencies in a store management system:

Assumptions:

Internet Access: It is assumed that the hardware and its users have access
to a reliable internet connection to use the online system effectively.

Hardware and Infrastructure: The assumption is made that the store has the
necessary hardware, such as servers, computers, and networking
equipment, to support the online system and handle the expected user load.

Data Accuracy and Availability: The system assumes that the accurate and
up-to-date data, including the hardware information, user records, and
availability of hardware and resources.

User Proficiency: It is assumed that hardware users have basic computer

literacy and the necessary skills to navigate the online system, search for
hardware, and interact with the available features.

Dependencies:

Database Management System: The store management system relies on a robust

and efficient database management system to store and retrieve information. The
selection and setup of the database system are crucial dependencies.

Integration: The system may depend on external databases or services for

integration, such as UDI databases or book metadata providers, to ensure accurate
and correct information.

Authentication and Security Services: The system may depend on external

authentication and security services, such as LDAP (Lightweight Directory Access
Protocol) or Single Sign-On (SSO) systems, to ensure secure user authentication
and data protection.
Email and Notification Services: The system may rely on email or notification
services to send automated reminders, notifications, or communication to users.
Dependence on a reliable email service is important in this case.

Integration with Store Hardware: The online system may need to integrate
with physical library hardware, such as barcode scanners, RFID systems, or
self-checkout machines, to provide a seamless user experience and
streamline operations.

System Updates and Maintenance: Dependencies may exist on the

availability of system updates, patches, or bug fixes to ensure the system's
stability, security, and compatibility with other software components.

It's important to identify and address these assumptions and dependencies

during the planning and implementation stages of an store management
system to ensure a smooth and reliable operation. Failure to meet these
dependencies can impact the system's functionality, security, and user
experience.
 CODING

Admin login-
<?php
session_start();
error_reporting(0);
include('includes/config.php');
if($_SESSION['alogin']!=''){
$_SESSION['alogin']='';
}
if(isset($_POST['login']))
{
$username=$_POST['username'];
$password=md5($_POST['password']);
$sql ="SELECT UserName,Password FROM admin WHERE
UserName=:username and Password=:password";
$query= $dbh -> prepare($sql);
$query-> bindParam(':username', $username, PDO::PARAM_STR);
$query-> bindParam(':password', $password, PDO::PARAM_STR);
$query-> execute();
$results=$query->fetchAll(PDO::FETCH_OBJ);
if($query->rowCount() > 0)
{
$_SESSION['alogin']=$_POST['username'];
echo "<script type='text/javascript'> document.location ='admin/dashboard.php';
</script>";
} else{
echo "<script>alert('Invalid Details');</script>";
}
}
?>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1,
maximum-scale=1" />
<meta name="description" content="" />
<meta name="author" content="" />
<title>Store Management System</title>
<!-- BOOTSTRAP CORE STYLE -->
<link href="assets/css/bootstrap.css" rel="stylesheet" />
<!-- FONT AWESOME STYLE -->
 <link href="assets/css/font-awesome.css" rel="stylesheet" />
<!-- CUSTOM STYLE -->
<link href="assets/css/style.css" rel="stylesheet" />
<!-- GOOGLE FONT -->
<link href='http://fonts.googleapis.com/css?family=Open+Sans' rel='stylesheet'
type='text/css' />

</head>
<body>
<!------MENU SECTION START-->
<?php include('includes/header.php');?>
<!-- MENU SECTION END-->
<div class="content-wrapper">
<div class="container">
<div class="row pad-botm">
<div class="col-md-12">
<h4 class="header-line">ADMIN LOGIN FORM</h4>
</div>
</div>

<!--LOGIN PANEL START-->

<div class="row">
<div class="col-md-6 col-sm-6 col-xs-12 col-md-offset-3" >
<div class="panel panel-info">
<div class="panel-heading">
LOGIN FORM
</div>
<div class="panel-body">
<form role="form" method="post">
<div class="form-group">
<label>Enter Username</label>
<input class="form-control" type="text" name="username" autocomplete="off"
required />
</div>
<div class="form-group">
<label>Password</label>
<input class="form-control" type="password" name="password" autocomplete="off"
required />
</div>
<button type="submit" name="login" class="btn btn-info">LOGIN </button>
</form>
</div>
</div>
</div>
</div>
<!---LOGIN PABNEL END-->
</div>
</div>
<!-- CONTENT-WRAPPER SECTION END-->
<?php include('includes/footer.php');?>
<!-- FOOTER SECTION END-->
<script src="assets/js/jquery-1.10.2.js"></script>
<!-- BOOTSTRAP SCRIPTS -->
<script src="assets/js/bootstrap.js"></script>
<!-- CUSTOM SCRIPTS -->
<script src="assets/js/custom.js"></script>
</script>
</body>
</html>

Department signup-

<?php
session_start();
include('includes/config.php');
error_reporting(0);
if(isset($_POST['signup']))
{

//Code for student ID

$count_my_page = ("studentid.txt");
$hits = file($count_my_page);
$hits[0] ++;
$fp = fopen($count_my_page , "w");
fputs($fp , "$hits[0]");
fclose($fp);
$StudentId= $hits[0];
$fname=$_POST['fullanme'];
$mobileno=$_POST['mobileno'];
$email=$_POST['email'];
$password=md5($_POST['password']);
$status=1;
$sql="INSERT INTO
tblstudents(StudentId,FullName,MobileNumber,EmailId,Password,Status)
VALUES(:StudentId,:fname,:mobileno,:email,:password,:status)";
$query = $dbh->prepare($sql);
$query->bindParam(':StudentId',$StudentId,PDO::PARAM_STR);
 $query->bindParam(':fname',$fname,PDO::PARAM_STR);
$query->bindParam(':mobileno',$mobileno,PDO::PARAM_STR);
$query->bindParam(':email',$email,PDO::PARAM_STR);
$query->bindParam(':password',$password,PDO::PARAM_STR);
$query->bindParam(':status',$status,PDO::PARAM_STR);
$query->execute();
$lastInsertId = $dbh->lastInsertId();
if($lastInsertId)
{
echo '<script>alert("Your Registration successfull and your student id is
"+"'.$StudentId.'")</script>';
}
else
{
echo "<script>alert('Something went wrong. Please try again');</script>";
}
}

?>

<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1"
/>
<meta name="description" content="" />
<meta name="author" content="" />
<!--[if IE]>
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<![endif]-->
<title>Store Management System | Student Signup</title>
<!-- BOOTSTRAP CORE STYLE -->
<link href="assets/css/bootstrap.css" rel="stylesheet" />
<!-- FONT AWESOME STYLE -->
<link href="assets/css/font-awesome.css" rel="stylesheet" />
<!-- CUSTOM STYLE -->
<link href="assets/css/style.css" rel="stylesheet" />
<!-- GOOGLE FONT -->
<link href='http://fonts.googleapis.com/css?family=Open+Sans' rel='stylesheet'
type='text/css' />
<script type="text/javascript">
function valid()
{
 if(document.signup.password.value!= document.signup.confirmpassword.value)
{
alert("Password and Confirm Password Field do not match !!");
document.signup.confirmpassword.focus();
return false;
}
return true;
}
</script>
<script>
function checkAvailability() {
$("#loaderIcon").show();
jQuery.ajax({
url: "check_availability.php",
data:'emailid='+$("#emailid").val(),
type: "POST",
success:function(data){
$("#user-availability-status").html(data);
$("#loaderIcon").hide();
},
error:function (){}
});
}
</script>

</head>
<body>
<!------MENU SECTION START-->
<?php include('includes/header.php');?>
<!-- MENU SECTION END-->
<div class="content-wrapper">
<div class="container">
<div class="row pad-botm">
<div class="col-md-12">
<h4 class="header-line">User Signup</h4>

</div>

</div>
<div class="row">

<div class="col-md-9 col-md-offset-1">

<div class="panel panel-danger">
<div class="panel-heading">
 SINGUP FORM
</div>
<div class="panel-body">
<form name="signup" method="post" onSubmit="return valid();">
<div class="form-group">
<label>Enter Full Name</label>
<input class="form-control" type="text" name="fullanme" autocomplete="off" required />
</div>

<div class="form-group">
<label>Mobile Number :</label>
<input class="form-control" type="text" name="mobileno" maxlength="10"
autocomplete="off" required />
</div>

<div class="form-group">
<label>Enter Email</label>
<input class="form-control" type="email" name="email" id="emailid"
onBlur="checkAvailability()" autocomplete="off" required />
<span id="user-availability-status" style="font-size:12px;"></span>
</div>

<div class="form-group">
<label>Enter Password</label>
<input class="form-control" type="password" name="password" autocomplete="off"
required />
</div>

<div class="form-group">
<label>Confirm Password </label>
<input class="form-control" type="password" name="confirmpassword"
autocomplete="off" required />
</div>

<button type="submit" name="signup" class="btn btn-danger" id="submit">Register Now

</button>

</form>
</div>
</div>
</div>
</div>
</div>
 </div>
<!-- CONTENT-WRAPPER SECTION END-->
<?php include('includes/footer.php');?>
<script src="assets/js/jquery-1.10.2.js"></script>
<!-- BOOTSTRAP SCRIPTS -->
<script src="assets/js/bootstrap.js"></script>
<!-- CUSTOM SCRIPTS -->
<script src="assets/js/custom.js"></script>
</body>
</html>

Listed computer peripherals:-

<?php
session_start();
error_reporting(0);
include('includes/config.php');
if(strlen($_SESSION['login'])==0)
{
header('location:index.php');
}
else{

?>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1"
/>
<meta name="description" content="" />
<meta name="author" content="" />
<title>Store Management System | Issued Hardware</title>
<!-- BOOTSTRAP CORE STYLE -->
<link href="assets/css/bootstrap.css" rel="stylesheet" />
<!-- FONT AWESOME STYLE -->
<link href="assets/css/font-awesome.css" rel="stylesheet" />
<!-- DATATABLE STYLE -->
<link href="assets/js/dataTables/dataTables.bootstrap.css" rel="stylesheet" />
<!-- CUSTOM STYLE -->
 <link href="assets/css/style.css" rel="stylesheet" />
<!-- GOOGLE FONT -->
<link href='http://fonts.googleapis.com/css?family=Open+Sans' rel='stylesheet'
type='text/css' />

</head>
<body>
<!------MENU SECTION START-->
<?php include('includes/header.php');?>
<!-- MENU SECTION END-->
<div class="content-wrapper">
<div class="container">
<div class="row pad-botm">
<div class="col-md-12">
<h4 class="header-line">Manage Issued Hardware</h4>
</div>

<div class="row">
<div class="col-md-12">
<!-- Advanced Tables -->
<div class="panel panel-default">
<div class="panel-heading">
Request Hardware
</div>
<div class="panel-body">

<?php $sql = "SELECT

tblhardwares.HardwareName,tblcategory.CategoryName,tblcompany.CompanyName,tblhar
dware.ISBNNumber,tblbooks.BookPrice,tblbooks.id as
bookid,tblbooks.bookImage,tblbooks.isIssued from tblbooks join tblcategory on
tblcategory.id=tblbooks.CatId join tblauthors on tblauthors.id=tblbooks.AuthorId";
$query = $dbh -> prepare($sql);
$query->execute();
$results=$query->fetchAll(PDO::FETCH_OBJ);
$cnt=1;
if($query->rowCount() > 0)
{
foreach($results as $result)
{ ?>
<div class="col-md-4" style="float:left; height:300px;">
<img src="admin/bookimg/<?php echo htmlentities($result->bookImage);?>" width="100">
<br /><b><?php echo htmlentities($result->BookName);?></b><br
/>
<?php echo htmlentities($result->CategoryName);?><br />
<?php echo htmlentities($result->AuthorName);?><br />
<?php echo htmlentities($result->ISBNNumber);?><br />
<?php if($result->isIssued=='1'): ?>
<p style="color:red;">Hardware Already issued</p>
<?php endif;?>
</div>

<?php $cnt=$cnt+1;}} ?>

</div>
</div>
<!--End Advanced Tables -->
</div>
</div>

</div>
</div>
</div>

<!-- CONTENT-WRAPPER SECTION END-->

<?php include('includes/footer.php');?>
<!-- FOOTER SECTION END-->
<!-- JAVASCRIPT FILES PLACED AT THE BOTTOM TO REDUCE THE LOADING TIME -->
<!-- CORE JQUERY -->
<script src="assets/js/jquery-1.10.2.js"></script>
<!-- BOOTSTRAP SCRIPTS -->
<script src="assets/js/bootstrap.js"></script>
<!-- DATATABLE SCRIPTS -->
<script src="assets/js/dataTables/jquery.dataTables.js"></script>
<script src="assets/js/dataTables/dataTables.bootstrap.js"></script>
<!-- CUSTOM SCRIPTS -->
<script src="assets/js/custom.js"></script>

</body>
</html>
<?php } ?>

Issued computer peripherals:-

<?php
session_start();
error_reporting(0);
include('includes/config.php');
if(strlen($_SESSION['login'])==0)
{
header('location:index.php');
}
else{

?>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1"
/>
<meta name="description" content="" />
<meta name="author" content="" />
<title>Store Management System | Issued Hardware</title>
<!-- BOOTSTRAP CORE STYLE -->
<link href="assets/css/bootstrap.css" rel="stylesheet" />
<!-- FONT AWESOME STYLE -->
<link href="assets/css/font-awesome.css" rel="stylesheet" />
<!-- DATATABLE STYLE -->
<link href="assets/js/dataTables/dataTables.bootstrap.css" rel="stylesheet" />
<!-- CUSTOM STYLE -->
<link href="assets/css/style.css" rel="stylesheet" />
<!-- GOOGLE FONT -->
<link href='http://fonts.googleapis.com/css?family=Open+Sans' rel='stylesheet'
type='text/css' />

</head>
<body>
<!------MENU SECTION START-->
<?php include('includes/header.php');?>
<!-- MENU SECTION END-->
 <div class="content-wrapper">
<div class="container">
<div class="row pad-botm">
<div class="col-md-12">
<h4 class="header-line">Manage Issued Hardware</h4>
</div>

<div class="row">
<div class="col-md-12">
<!-- Advanced Tables -->
<div class="panel panel-default">
<div class="panel-heading">
Issued Hardware
</div>
<div class="panel-body">
<div class="table-responsive">
<table class="table table-striped table-bordered table-hover"
id="dataTables-example">
<thead>
<tr>
<th>#</th>
<th>Hardware Name</th>
<th>UDIN </th>
<th>Issued Date</th>

</tr>
</thead>
<tbody>
<?php
$sid=$_SESSION['stdid'];
$sql="SELECT
tblbooks.BookName,tblbooks.ISBNNumber,tblissuedbookdetails.IssuesDate,tblissuedbookde
tails.ReturnDate,tblissuedbookdetails.id as rid,tblissuedbookdetails.fine from
tblissuedbookdetails join tblstudents on
tblstudents.StudentId=tblissuedbookdetails.StudentId join tblbooks on
tblbooks.id=tblissuedbookdetails.BookId where tblstudents.StudentId=:sid order by
tblissuedbookdetails.id desc";
$query = $dbh -> prepare($sql);
$query-> bindParam(':sid', $sid, PDO::PARAM_STR);
$query->execute();
$results=$query->fetchAll(PDO::FETCH_OBJ);
$cnt=1;
if($query->rowCount() > 0)
{
foreach($results as $result)
{ ?>
<tr class="odd gradeX">
<td class="center"><?php echo htmlentities($cnt);?></td>
<td class="center"><?php echo htmlentities($result-
>BookName);?></td>
<td class="center"><?php echo htmlentities($result-
>ISBNNumber);?></td>
<td class="center"><?php echo htmlentities($result-
>IssuesDate);?></td>
<td class="center"><?php if($result->ReturnDate=="")
{?>
<span style="color:red">
<?php echo htmlentities("Not Return Yet"); ?>
</span>
<?php } else {
echo htmlentities($result->ReturnDate);
}
?></td>
<td class="center"><?php echo htmlentities($result->fine);?></td>

</tr>
<?php $cnt=$cnt+1;}} ?>
</tbody>
</table>
</div>

</div>
</div>
<!--End Advanced Tables -->
</div>
</div>

</div>
</div>
</div>

<!-- CONTENT-WRAPPER SECTION END-->

<?php include('includes/footer.php');?>
<!-- FOOTER SECTION END-->
 <!-- JAVASCRIPT FILES PLACED AT THE BOTTOM TO REDUCE THE LOADING TIME -->
<!-- CORE JQUERY -->
<script src="assets/js/jquery-1.10.2.js"></script>
<!-- BOOTSTRAP SCRIPTS -->
<script src="assets/js/bootstrap.js"></script>
<!-- DATATABLE SCRIPTS -->
<script src="assets/js/dataTables/jquery.dataTables.js"></script>
<script src="assets/js/dataTables/dataTables.bootstrap.js"></script>
<!-- CUSTOM SCRIPTS -->
<script src="assets/js/custom.js"></script>

</body>
</html>
<?php } ?>
 SCREEN CAPTURES

HOME PAGE:-
LOGIN PAGE:-
USER DASHBOARD:-
ADMIN PAGE:-
ADMINE DASHBOARD:-
 CONCLUSION

Store Management Program has been created keeping in mind

the needs of Small and Medium scale of computer peripherals.
It’s efficient software that includes all the basic functionalities like
making data entries for new hardware, registering a new user,
editing and deleting records that are required for smooth
functioning of a store. Additionally the user login and issued
history are also stored and can be accessed by the administrator.
It also facilitates the admin to create new user groups and edit
their access levels and functions (like that of the assistants).
Apart from this the general users are also given the rights to not
only keep track of the computer peripherals that they have issued
but they too can search for the different computer peripheral
devices.