A Minor Project Report

On

LIBRARY MANAGEMENT SYSTEM

Submitted in partial fulfilment of requirements for the award of the

Degree of

BACHELOR OF ENGINEERING

in

COMPUTER SCIENCE AND ENGINEERING

Under the guidance of

Mr. R. VIKRAM Assistant Professor/CSE

Submitted By

ARUNMOZHI K (927621BCS012)
DEVADHARSHINI A (927621BCS020)
HEENA J (927621BCS041)
KIRUPA (927621BCS060)

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

M.KUMARASAMY COLLEGE OF ENGINEERING

(Autonomous)

KARUR – 639 113

May,2021.

i
 M. KUMARASAMY COLLEGE OF ENGINEERING
(Autonomous Institution affiliated to Anna University, Chennai)

KARUR – 639113

BONAFIDE CERTIFICATE

Certified that this minor project report “LIBRARY MANAGEMENT

SYSTEM” is the bonafide work of “ARUL JEEVIKA. M (19BCS4011),
DIVYABHARATHI. T (19BCS4028), ISWARYA. M (19BCS4043),” who
carried out the project work during the academic year 2020- 2021 under my supervision.

Signature Signature

Mr. R.VIKRAM M.E., Dr. S.THILAGAMANI M.E., Ph.D.,

SUPERVISOR, HEAD OF THE DEPARTMENT,

Department of Computer Science Department of Computer Science

and Engineering, and Engineering,
M. Kumarasamy College of Engineering, M. Kumarasamy College of Engineering
Thalavapalayam, Karur -639113 Thalavapalayam, Karur -639113.

ii
 DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

VISION OF THE INSTITUTION

To emerge as a leader among the top institutions in the field of technical education

MISSION OF THE INSTITUTION

Produce smart technocrats with empirical knowledge who can surmount the global
challenges
Create a diverse, fully-engaged, learner-centric campus environment to provide quality
education to the students
Maintain mutually beneficial partnerships with our alumni, industry, and Professional

associations

VISION OF THE DEPARTMENT

To achieve education and research excellence in Computer Science and Engineering

MISSION OF THE DEPARTMENT

To excel in academic through effective teaching learning techniques

To promote research in the area of computer science and engineering with the focus on
innovation

To transform students into technically competent professionals with societal and ethical

responsibilities

PROGRAM EDUCATIONAL OBJECTIVES (PEOs)

PEO 1:Graduates will have successful career in software industries and R&D divisions through
continuous learning.
PEO 2: Graduates will provide effective solutions for real world problems in the key domain
of computer science and engineering and engage in lifelong learning.
PEO 3: Graduates will excel in their profession by being ethically and socially responsible.

iii
PROGRAM OUTCOMES (POs)
Engineering students will be able to:
1. Engineering knowledge: Apply the knowledge of mathematics, science, engineering
fundamentals, and an engineering specialization to the solution of complex engineering
problems.
2. Problem analysis: Identify, formulate, review research literature, and analyze complex
engineering problems reaching substantiated conclusions using first principles of
mathematics, natural sciences, and engineering sciences.
3. Design/development of solutions: Design solutions for complex engineering problems
and design system components or processes that meet the specified needs with
appropriate consideration for the public health and safety, and the cultural, societal, and
environmental considerations.
4. Conduct investigations of complex problems: Use research-based knowledge and
research methods including design of experiments, analysis and interpretation of data,
and synthesis of the information to provide valid conclusions.
5. Modern tool usage: Create, select, and apply appropriate techniques, resources, and
modern engineering and IT tools including prediction and modeling to complex
engineering activities with an understanding of the limitations.
6. The engineer and society: Apply reasoning informed by the contextual knowledge to
assess societal, health, safety, legal and cultural issues and the consequent
responsibilities relevant to the professional engineering practice.
7. Environment and sustainability: Understand the impact of the professional engineering
solutions in societal and environmental contexts, and demonstrate the knowledge of, and
need for sustainable development.
8. Ethics: Apply ethical principles and commit to professional ethics and responsibilities
and norms of the engineering practice.
9. Individual and team work: Function effectively as an individual, and as a member or
leader in diverse teams, and in multidisciplinary settings.
10. Communication: Communicate effectively on complex engineering activities with the
engineering community and with society at large, such as, being able to comprehend and
write effective reports and design documentation, make effective presentations, and give
and receive clear instructions.

iv
 11. Project management and finance: Demonstrate knowledge and understanding of the
engineering and management principles and apply these to one’s own work, as a member
and leader in a team, to manage projects and in multidisciplinary environments.
12. Life-long learning: Recognize the need for, and have the preparation and ability to
engage in independent and life-long learning in the broadest context of technological
change.

PROGRAM SPECIFIC OUTCOMES (PSOs)

PSO1: Professional Skills: Ability to apply the knowledge of computing techniques to

design and develop computerized solutions for the problems.
PSO2: Successful career: Ability to utilize the computing skills and ethical values in
creating a successful career.

v
 ABSTRACT WITH PO AND PSO MAPPING

ABSTRACT POs PSOs

MAPPED MAPPED

In our project library management system, the PO1(3) PSO 1(3)

login page contains username and password as PO 2(3) PSO 2(2)
PO 3(2)
login credentials. After the completion of
PO 4(2)
successful login, he or she will be enter into a PO 5(2)
home page showing options such as new student, PO6(1)
issues book, return book, statistics, new book. PO 7(3)
According to the user’s choice , he or she will PO 8(2)
redirected into new page asking for the student PO 9(3)
information. The student information includes PO 10(3)
PO 11(2)
student name, student id, course, branch etc. If it a
PO 12(2)
new person he or she asked to sign up. Statistics
include the details about issue date and return
book. The library management system is used to
overcome the entire problem which they are facing
currently, and making complete atomization of
manual or semiautomatic process of library
management system.

Note: 1- Low, 2-Medium, 3- High

SUPERVISOR HEAD OF THE DEPARTMENT

vi
 ABSTRACT

On Road Vehicle Breakdown Assistance (ORVBA) is going to be a good solution for the

people who seek help in the remote locations with mechanical issues of their vehicle.

Users of the On Road Vehicle Breakdown Assistance will be the registered public and

they will be getting connected with the particular mechanic through the trustworthy

On Road Vehicle Breakdown Assistance (ORVBA) system. Because only the legally

licensed and approved mechanics are enlisted in the On Road Vehicle Breakdown

Assistance (ORVBA) system. Also they are under monitoring by the ORVBA system for

not charging any extra service fee from the users as every user is updating their

feedback about the availed service through ORVBA system.

vii
 TABLE OF CONTENTS

CHAPTER TITLE PAGE

No. No.

Abstract vii

List of Figures ix

Acronyms/List of Abbreviations x

1 Introduction 1

1.1 Overview 2

1.2 Domain Introduction 3

1.3 Problem Statement 5

1.4 Objective 6

2 Literature Survey 7

3 Feasibility Study 9

4 Project Methodology 11

4.1 Block diagram of LMS 11

4.2 Module Description 12

5 Results and Discussion 13

6 Conclusion 23

References 24

viii
 LIST OF FIGURES

FIGURE No. TITLE PAGE No.

1.1 Library Management System 1

3.1 Feasibility study for Library 9

Management System

4.1 Block Diagram of LMS 11

5 Output Screenshot 13

ix
 LIST OF ACRONYMS / ABBREVIATIONS

LMS Library Management System

DLI Digital Library Initiative
SQR System Requirement Specification
RDBMS Relational Database Management System

x
 CHAPTER-I

INTRODUCTION

1.1. PROJECT OVERVIEW

Describe the contents and organization of the rest of this document.

Since there is already a Table of Contents, this overview will be less formal

but more informative. Describe the two basic remaining sections, the Overall

Description and the Requirements Specification.

EXISTING SYSTEM

 In an existing system there are users who have their own mechanic

database which is very minimal. And also they have no idea if their

vehicles are broke down or had any mechanical issue in remote

locations or any long distant locations from their known mechanic

shops. Users with the contacts of people at the particular place may

look for a help from them only if they are ready to do.

 It is not possible to find out the suitable mechanic for the desired

service at remote locations. The only way they have is to look for any

other transportation at the time of issue and then they need to get a

mechanic to the particular location at which they have left their

vehicle.

PROPOSED SYSTEM

The proposed system of On Road Vehicle Breakdown Assistance (ORVBA)

system can search for list of mechanic at any location or the nearby

locations which will help them in an unexpected situations raised by the

mechanical issues of their vehicles. Only the licensed mechanics can get

listed here while the search. And there are available mechanic who can

come and repair the mechanical issues in the users vehicle.

Advantages of proposed system

Branded mechanic shop is available.

CHAPTER-II

SYSTEM SPECIFICATIONS

The system requires the following as minimum recommended configuration

for processing.

Software Requirements

Operating System : Windows 7

User Interface : ASP.Net

Platform : Microsoft Visual Studio 2010

Database : SQL Server2008

Server Deployment : IIS(Internet Information Server)6.0

Frame Work : .Net Framework 4.0

Hardware Requirements

Processor : PentiumIV

Hard Disk : 250GB

RAM : 3GB
 CHAPTER-III

MODULE DESCRIPTION

 User

 Mechanic

User

Register

User has to register their basic details to get access with this

application service.

Login

Once they have registered they need to login to avail the service at the

needy time.

View Details

Logging in with the application will provide you the lists of mechanics

that have the approval of the application.

Search records & call

So that the users can search the mechanic among the list according to their

place and time.

Post feedback

After all the process every user has to give their feedback with this

application to about their adopted service through this medium.

Mechanic

Register

At first every mechanic has to register their details with the admin for

getting approval.
Login

Registered mechanics can login their accounts if they got their approval

from the admin.

Post details

Here mechanics have to post their details like name, location, services

available, etc.

View feedback

Using the feedbacks provided by the users/customers of the service

mechanics have to maintain or improve their service.

DATAFLOW DIAGRAM

USE-CASE DIAGRAM
 OVERVIEW

OF

TECHNOLOGIES USED

Front End – Asp.NET

ASP.Net is a web development platform, which provides a

programming model, a comprehensive software infrastructure and various

services required to build up robust web application for PC, as well as

mobile devices. ASP.Net works on top of the HTTP protocol and uses the

HTTP commands and policies to set a browser-to-server two-way

communication and cooperation.

ASP.Net is a part of Microsoft .Net platform. ASP.Net applications are

compiled codes, written using the extensible and reusable components or

objects present in .Net framework. These codes can use the entire hierarchy

of classes in .Net framework.

The ASP.Net application codes could be written in either of the following

languages:
 C#

Visual Basic .Net

Jscript

J#

ASP.Net is used to produce interactive, data-driven web applications

over the internet. It consists of a large number of controls like text boxes,

buttons and labels for assembling, configuring and manipulating code to

create HTML pages.

ASP.Net Web Forms Model:

ASP.Net web forms extend the event-driven model of interaction to the web

applications. The browser submits a web form to the web server and the

server returns a full markup page or Html page in response.

All client side user activities are forwarded to the server for statefull

processing. The server processes the output of the client actions and triggers

the reactions. Now, HTTP is a stateless protocol. Asp.Net framework helps in

storing the information regarding the state of the application.

ASP.Net Component model

The ASP.Net component model provides various building blocks of

ASP.Net pages. Basically it is an object model, which describes:

Serverside counterparts of almost all HTML elements or tags, like <form>

and <input>.Server controls, which help in developing complex user-

interface for example the Calendar control or the Grid view control.

ASP.Net web application is made of pages. When a user request an ASP.Net

page, the IIS delegates the processing of the page to the ASP.Net runtime
system.

.NET platform:

The .Net platform is an integral component of the Microsoft Windows

operating system for building and running next generation software

applications and web services. The .Net development framework provides a

new and simplified model for programming and developing applications on

the Windows platform. It provides such advantages as multiplatform

applications, automatic resource management, and simplification of

application development.

As security is an essential part of .Net, it provides security support,

such as code authenticity check, resources access authorizations,

declarative and imperative security, and cryptographic security methods for

embedding into the user’s application. In addition, it significantly extends

the development platform by providing tools and technologies to develop

internet-based distributed application.

The .NET framework is an integral windows component that supports

building and running the next generation of applications and XML web

services. The key component of the .NET frame work are the common

language run time and the .NET frame work class library, which includes

ADO.NET, ASP.NET and windows forms. The .NET framework provides a

managed execution environment simplified development and deployment

and integration with a wide variety of programming languages.

This framework is made up of the following parts:

 The common language runtime(CLR)

 The base class libraries.

 Object oriented internet development with ASP.NET

 Rich client user interface using windows forms

 RAD for the internet using web forms

The .NET framework is a new computing platform that simplifies

application development in the highly distributed environment of the

internet. The .NET framework is designed to fulfill following objectives:

 To provide a consistent object oriented programming environment

whether object code is stored and executed locally but internet-

distributed or executed remotely.

 To provide a code execution environment that minimizes software

deployment and versioning conflicts.

 To provide a code execution environment that guarantees safe

execution of code, including code created by an unknown or semi

trusted third party.

 To provide a code execution environment that eliminates the

performance problem of scripted or interpreted environments.

 To make the developer experience consistent across widely types of

application, such as windows based applications and web based

applications.

 To build all communication on industry standards to ensure that

code based on the .NET framework can integrate with any other code.
 The .NET framework has two main components: the common

language runtime and the .Net framework class library. The common

language runtime is the foundation of the .NET framework. You can think of

the runtime as an agent that manages code at execution time, and remoting

while also enforcing strict type safely and other forms of code accuracy that

ensure security and robustness in fact the concept of code management is a

fundamental principle of the runtime.

Code that targets the runtime is known as managed code, while code

that does not target the runtime is known as unmanaged code. The class

library, the other main component of the .NET frameworks is a

comprehensive, object-oriented collection reusable types that you can use to

develop applications ranging from traditional command line or graphical

user interface (FGUI) applications to application base d on the latest

innovations provided by ASP.NET, such as web forms and XML web

services.

The .NET framework can be hosted by unmanaged component that

load the common language runtime into their processes and initiate the

execution of managed code.

ASP.NET works directly with the runtime to enable ASP.NET

application and XML web services, both of which are discussed later in this

topic, Internet explorer is an example of unmanaged application that hosts

the runtime (in the form of a MIME type extension).

Using internet explorer to the host runtime enables you to embed

managed components or windows forms controls in HTML documents.

Hosting the runtime in this way makes mobile code 9similar to Microsoft
ActiveX controls) possible, but with significant improvement that only

managed code can offer, such as semi-trusted execution and secure isolated

file storage.

The following illustration shows the relationship of the common

language runtime and the class library to your application and to the overall

system. The illustration also shows how managed code operated with in a

larger architecture.

We can use the .NET framework to develop the following types of

application and services:

 Console applications

 Window GUI application (Windows Forms) ASP.NET applications

 XML Web services

 Windows services

Common Language Runtime (CLR)

The common language runtime (CLR) is responsible for runt-time

services such as language integration; security enforcement; and memory,

process and thread management. In addition, it has a roll at development

time when features such as life cycle management strong type naming,

cross-language exception handling, dynamic binding and so on, reduce the

amount of code that a developer must write to turn the business logic the

reusable component. The runtime can be hosted by high performance,

server-side applications, such a s Microsoft Internet Information Services

(IIS) for building web applications with ASP.NE and the next release of
Microsoft SQL Server. This infrastructure enables you to use code

“managed” by the .NET framework to write your business logic, while still

enjoying the superior performance of the industry’s best enterprises servers

that support runtime hosting.

ASP.NET

ASP.NET is a set of Microsoft.NET framework technologies used for

building web applications and XML Web services. ASP.NET page execute on

the server and generate markup such as HTML, WML or XML that is sent to

a desktop or mobile browser. ASP.NET pages use a compiled, event-driven

programming model that improves performance and enables the separation

of application logic and user interface. Both ASP.NET pages and ASP.NET

web services files contain server-side (as opposed to client side logic) written

in Visual basic .NET, C#.NET or any .NET compatible language, Web

applications and XML Web Services take advantage of the features of the

common language runtime, such as type safety, inheritance, language,

interoperability, versioning, and integrated security.

IIS

Microsoft Internet Information S4ervices (IIS; formerly called Server is

a set of Internet-based services for servers using Microsoft Windows. It is

the world’s second most popular web server in terms of overall websites. As

of September 2007 it served 34.94% of all websites and 36.63% of all active
websites according to Net craft. The servers currently include FTP, SMTP,

NNTOP, and HTTP/HTTPS.

ADO.NET

ADO.NET provides consistent access to data sources such a Microsoft

SQL Server and XML, as well as to data sources exposed through OLE DB

and ODBC. Data sharing consumer applications can use ADO.NET to

connect to these data sources and retrieve, manipulate and update the data

that they contain.

ADO.NET separates data access from data manipulation into discrete

components that can be used separately or in tandem. ADO.NET

includes .NET Frame work data providers for connecting to a database,

executing commands and retrieving results. Those results are either

processed directly, placed in and ADO.NET Dataset objects in order to be

exposed to the used in an ad hoc manner, combined with data from multiple

sources or remote between tiers. The ADO.NET Dataset object can also be

used independently of a .NET Framework data provider to manage data local

to the application or sourced from XML.

The ADO.NET classes are found in System.Data.dll and are integrated

with the XML classes found in System.Xml.dll. When compiling code that

uses the System. Data, namespace reference both System.Data.dll and

System.Xml.dll.

ADO.NET provided functionality to developers writing managed code

similar to the functionality provided to native component object model

(COM) developers by ActiveX Data Objects (ADO).

ADO.NET COMPONENTS

There are two components of ADO.NET that you can use to access

and manipulate data:

 .NET Framework data providers.

 The Dataset

.NET FRAMEWORK DATA PROVIDERS

The .NET Framework Data providers are components that have been

explicitly designed for data manipulation and fast, forward-only, read-only

access to data. The connection object provides connectivity to a data

source. The command object enables access to database commands to

return data, modify data, run stored procedures and send or retrieve

parameter information. The Data Adapter provides a high-performance

stream of data from the data source. Finally, the Data Adapter provides the

bridge between the Dataset object and the data source.

The Data Adapter uses command object to execute SQL commands at

the data source to both load the Dataset with data and reconcile changes

made to the data in the Dataset back to the data source.

DATASET

The ADO.NET Dataset is explicitly designed for data access

independent of any data source. As a result, it can be used with multiple

and differing data sources used with XML data or used to manage data local

to the application. The Dataset contains a collection of one or more Data

Table objects made up to rows and columns of data as well as primary key,
foreign key, constraint and relation information about the data in the Data

Table objects.

BENEFITS OF ADO.NET

ADO.NET offers several advantages over previous versions of ADO

and over other data access components. These benefits fall into the

following categories:

1. Interoperability

2. Maintainability

3. Programmability

4. Scalability

C# language

C# syntax is highly expressive, yet it is also simple and easy to learn.

The curly-brace syntax of c# will be instantly recognizable to anyone familiar

with c, c++ or java. Developers who know any of these languages are

typically able to begin to work productively in c# within a very short time.

As an object-oriented language, the c# supports the concepts of

encapsulation, inheritance, data binding and polymorphism. All variables

and methods, including the Main method, the application’s entry point, are

encapsulated within class definitions.

Back End- SQL Database 2008

SQL stands for structured Query Language. SQL is used to

communicate with a database. According to ANSI, it is the standard

language for relational database management systems. SQL statements are

used to perform task such as update data on a database, or retrieve data

from a database.

However, the standard SQL commands such as “select”, “insert”,

“update” “delete”, “Create”, and “Drop” can be used to accomplish almost

ever

CHAPTER-IV

FEASIBILITY STUDY

Feasibility study is conducted once the problem is clearly understood.

Feasibility study is a high level capsule version of the entire system analysis

and design process. The objective is to determine quickly at a minimum

expense how to solve a problem. The purpose of feasibility is not to solve

the problem but to determine if the problem is worth solving.

The system has been tested for feasibility in the following points.

1. Technical Feasibility

2. Economical Feasibility

3. Operational Feasibility.

1. Technical Feasibility

The project entitles "Web based tourism and travel planner” is

technically feasibility because of the below mentioned feature. The project

was developed in Java which Graphical User Interface.

It provides the high level of reliability, availability and compatibility.

All these make Java an appropriate language for this project. Thus the

existing software Java is a powerful language.

2. Economical Feasibility

The computerized system will help in automate the selection leading

the profits and details of the organization. With this software, the machine

and manpower utilization are expected to go up by 80-90% approximately.

The costs incurred of not creating the system are set to be great, because

precious time can be wanted by manually.

3. Operational Feasibility

In this project, the management will know the details of each project

where he may be presented and the data will be maintained as decentralized

and if any inquires for that particular contract can be known as per their

requirements and necessaries.

Implementation

Implementation is the stage where the theoretical design is turned

into a working system. The most crucial stage in achieving a new success

full system and the giving confidence on the new system for the users that it

will work efficiently and effectively.

The system can be implemented only after thorough testing is done

and if it is found to work according to the specification.

 It involves careful planning, investigation of the current system and its

constraints on implementation, design of methods to achieve the change

over and an evaluation of change over methods a part from planning. Two

major tasks of preparing the implementation are education and training of

the users and testing of the system.

The implementation phase comprises of several activities. The required

hardware and software acquisition is carried out. The system may require

some software to be developed. For this, programs are written and tested.

The user then changes over to his new fully tested system and the old

system is discontinued.

Testing

The testing phase is an important part of software development. It is

the computerized system will help in automatedprocess of finding errors and

missing operations and also a complete verification to determine whether

the objectives are met and the user requirements are satisfied.

Software testing is carried out in three steps:

1. The first includes unit testing, where in each module is tested to

provide its correctness, validity and also determine any missing

operations and to verify whether the objectives have been met.

Errors are noted down and corrected immediately. Unit testing is

the important and major part of the project. So errors are rectified

easily in particular module and program clarity is increased. In

this project entire system is divided into several modules and is

developed individually. So unit testing is conducted to individual

modules.
2. The second step includes Integration testing. It need not be the case,

the software whose modules when run individually and showing perfect

results, will also show perfect results when run as a whole. The individual

modules are clipped under this major module and tested again and verified

the results. This is due to poor interfacing, which may results in data being

lost across an interface. A module can have inadvertent, adverse effect on

any other or on the global data structures, causing serious probable

3. The final step involves validation and testing which determines which

the software functions as the user expected. Here also some modifications

were. In the completion of the project it is satisfied fully by the end user.

Maintenance and environment

As the number of computer based systems, grieve libraries of computer

software began to expand. In house developed projects produced tones of

thousand soft program source statements. Software products purchased

from the outside added hundreds of thousands of new statements. A dark

cloud appeared on the horizon. All of these programs, all of those source

statements-had to be corrected when false were detected, modified as user

requirements changed, or adapted to new hardware that was purchased.

These activities were collectively called software Maintenance.

The maintenance phase focuses on change that is associated with

error correction, adaptations required as the software's environment evolves,

and changes due to enhancements brought about by changing customer

requirements. Four types of changes are encountered during the

maintenance phase.
  Correction

 Adaptation

 Enhancement

 Prevention

Correction

Even with the best quality assurance activities is lightly that the

customer will uncover defects in the software. Corrective maintenance

changes the software to correct defects.

Maintenance is a set of software Engineering activities that occur after

software has been delivered to the customer and put into operation.

Software configuration management is a set of tracking and control activities

that began when a software project begins and terminates only when the

software is taken out of the operation.

We may define maintenance by describing four activities that are

undertaken after a program is released for use:

 Corrective Maintenance

 Adaptive Maintenance

 Perfective Maintenance or Enhancement

 Preventive Maintenance or reengineering

Only about 20 percent of all maintenance works are spent "fixing mistakes".

The remaining 80 percent are spent adapting existing systems to changes in

their external environment, making enhancements requested by users, and

reengineering an application for use.

Adaptation
Over time, the original environment (E>G., CPU, operating system, business

rules, external product characteristics) for which the software was developed

is likely to change. Adaptive maintenance results in modification to the

software to accommodate change to its external environment.

Enhancement

As software is used, the customer/user will recognize additional functions

that will provide benefit. Perceptive maintenance extends the software

beyond its original function requirements.

Prevention

Computer software deteriorates due to change, and because of this,

preventive maintenance, often called software engineering, must be

conducted to enable the software to serve the needs of its end users. In

essence, preventive maintenance makes changes to computer programs so

that they can be more easily corrected, adapted, and enhanced. Software

configuration management (SCM) is an umbrella activity that is applied

throughout the software process. SCM activities are developed to

Software Methodology

The software methodology followed in this project includes the object-

oriented methodology and the application system development

methodologies. The description of these methodologies is given below.

Application System Development – A Life cycle Approach

Although there are a growing number of applications (such as decision

support systems) that should be developed using an experimental process

strategy such as prototyping, a significant amount of new development work

continue to involve major operational applications of broad scope. The

application systems are large highly structured. User task comprehension

and developer task proficiency is usually high. These factors suggest a linear

or iterative assurance strategy. The most common method for this stage

class of problems is a system development life cycle modal in which each

stage of development is well defined and has straightforward requirements

for deliverables, feedback and sign off. The system development life cycle is

described in detail since it continues to be an appropriate methodology for a

significant part of new development work.

The basic idea of the system development life cycle is that there is a

well-defined process by which an application is conceived and developed and

implemented. The life cycle gives structure to a creative process. In order to

manage and control the development effort, it is necessary to know what

should have been done, what has been done, and what has yet to be

accomplished. The phrases in the system development life cycle provide a

basis for management and control because they define segments of the flow

of work, which can be identified for managerial purposes and specifies the

documents or other deliverables to be produced in each phase.

The information system development cycle for an application consists of

three major stages.

1)Definition.

2)Development.

3)Installation and operation.

The requirements are then translated into a physical system of forms,

procedures, programs etc., by the system design, computer programming

and procedure development. The resulting system is test and put into

operation. No system is perfect so there is always a need for maintenance

changes. To complete the cycle, there should be a post audit of the system

to evaluate how well it performs and how well it meets the cost and

performance specifications. The stages of definition, development and

installation and operation can therefore be divided into smaller steps or

phrases as follows.

Definition

Proposed definition : preparation of request for proposed applications.

Feasibility assessment : evaluation of feasibility and cost benefit of

proposed system.

Information requirement analysis : determination of information needed.

Design

Conceptual design : User-oriented design of application

development.

Physical system design : Detailed design of flows and processes in

applications processing system and preparation of program specification.

Development

Program development : coding and testing of computer programs.

Procedure development : design of procedures and preparation of user

instructions.

Installation and operation

Conversion : final system test and conversion.

Operation and maintenance : Month to month operation and

maintenance
Post audit : Evaluation of development process,

application system and results of use at the completion of the each phase,

formal approval sign-off is required from the users as well as from the

manager of the project development.

CHAPTER-V

TESTING

Testing is a process of executing a program with the intent of finding an

error. Testing is a crucial element of software quality assurance and

presents ultimate review of specification, design and coding.System Testing

is an important phase. Testing represents an interesting anomaly for the

software. Thus a series of testing are performed for the proposed system

before the system is ready for user acceptance testing.A good test case is

one that has a high probability of finding an as undiscovered error. A

successful test is one that uncovers an as undiscovered error.

Testing Objectives

1.Testing is a process of executing a program with the intent of finding an

error.

2.A good test case is one that has a probability of finding an as yet

undiscovered error.

3.A successful test is one that uncovers an undiscovered error.

Testing Principle
1. All tests should be traceable to end user requirements.

2.Tests should be planned long before testing begins.

3.Testing should begin on a small scale and progress towards testing in

large.

4.Exhaustive testing is not possible.

5.To be most effective testing should be conducted by a independent third

party.

The primary objective for test case design is to derive a set of tests

that has the highest livelihood for uncovering defects in software. To

accomplish this objective two different categories of test case design

techniques are used. They are

White box testing

Black box testing

White-box testing

White box testing focus on the program control structure. Test cases

are derived to ensure that all statements in the program have been executed

at least once during testing and that all logical conditions have been

executed.

Block-box testing

Black box testing is designed to validate functional requirements

without regard to the internal workings of a program. Black box testing

mainly focuses on the information domain of the software, deriving test

cases by partitioning input and output in a manner that provides through

test coverage. Incorrect and missing functions, interface errors, errors in

data structures, error in functional logic are the errors falling in this

category.

Testing strategies

A strategy for software testing must accommodate low-level tests that are

necessary to verify that all small source code segment has been correctly

implemented as well as high-level tests that validate major system functions

against customer requirements.

Testing fundamentals

Testing is a process of executing program with the intent of finding error. A

good test case is one that has high probability of finding an undiscovered

error. If testing is conducted successfully it uncovers the errors in the

software. Testing cannot show the absence of defects, it can only show that

software defects present.

Testing Information flow

Information flow for testing flows the pattern. Two class of input

provided to test the process. The software configuration includes a software

requirements specification, a design specification and source code.

Test configuration includes test plan and test cases and test tools. Tests are

conducted and all the results are evaluated. That is test results are

compared with expected results. When erroneous data are uncovered, an

error is implied and debugging commences.

Unit testing:
 Unit testing is essential for the verification of the code produced

during the coding phase and hence the goal is to test the internal logic of the

modules. Using the detailed design description as a guide, important paths

are tested to uncover errors within the boundary of the modules. These

tests were carried out during the programming stage itself. All units of SQL

were successfully tested.

Integration testing

Integration testing focuses on unit tested modules and build the

program structure that is dictated by the design phase.

System testing

System testing tests the integration of each module in the system. It

also tests to find discrepancies between the system and it’s original

objective, current specification and system documentation. The primary

concern is the compatibility of individual modules. Entire system is working

properly or not will be tested here, and specified path ODBC connection will

correct or not, and giving output or not are tested here these verifications

and validations are done by giving input values to the system and by

comparing with expected output. Top-down test implementing here.

Acceptance Testing

This testing is done to verify the readiness of the system for the

implementation. Acceptance testing begins when the system is complete. Its

purpose is to provide the end user with the confidence that the system is
ready for use. It involves planning and execution of functional tests,

performance tests and stress tests in order to demonstrate that the

implemented system satisfies its requirements.

Tools to special importance during acceptance testing include:

Test coverage Analyzer – records the control paths followed for each test

case.

Timing Analyzer – also called a profiler, reports the time spent in various

regions of the code are areas to concentrate on to improve system

performance.

Coding standards – static analyzers and standard checkers are used to

inspect code for deviations from standards and guidelines.

Test Cases

Test cases are derived to ensure that all statements in the program have

been executed at least once during testing and that all logical conditions

have been executed.

Using White-Box testing methods, the software engineer can drive test cases

that

Guarantee that logical decisions on their true and false sides.

Exercise all logical decisions on their true and false sides.

Execute all loops at their boundaries and within their operational bounds.

Exercise internal data structure to assure their validity.

The test case specification for system testing has to be submitted for review

before system testing commences.

 CHAPTER-VI

Source code

Login

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Configuration;

using System.Data;
using System.Data.SqlClient;

publicpartialclassAdmin : System.Web.UI.Page

SqlConnection conn =

newSqlConnection(ConfigurationManager.ConnectionStrings["onroad"].Conn

ectionString);

protectedvoid Page_Load(object sender, EventArgs e)

conn.Open();

protectedvoid Button1_Click(object sender, EventArgs e)

string usname= Request["uname"];

string psw = Request["pswd"];

if ((usname == "") || (psw == ""))

Response.Write("<script>alert('Username or Password cannot be

null')</script>");

else

SqlCommand cmd = newSqlCommand("SELECT * FROM register where

username='" + usname + "' and password='" + psw + "'", conn);

SqlDataReader read = cmd.ExecuteReader();

if (read.Read())

Response.Cookies["usrname"].Value = Request["uname"];

Response.Redirect("UploadDocuments.aspx");

else

Response.Write("<script>alert('Wrong Credentials')</script>");

Register

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Configuration;

using System.Data;

using System.Data.SqlClient;
using System.IO;

publicpartialclassregister : System.Web.UI.Page

SqlConnection conn =

newSqlConnection(ConfigurationManager.ConnectionStrings["Tax"].Connecti

onString);

protectedvoid Page_Load(object sender, EventArgs e)

protectedvoid Button1_Click(object sender, EventArgs e)

conn.Open();

SqlCommand cmd = newSqlCommand("insert into

register(name,username,password,email,mobile,address) values('" +

TextBox1.Text + "','" + TextBox2.Text + "','" + TextBox3.Text + "','" +

TextBox4.Text + "','" + TextBox5.Text + "','" + TextBox6.Text + "')", conn);

int i=cmd.ExecuteNonQuery();

if (TextBox1.Text == "")

string script="alert('Please Enter Your Name')";

ClientScript.RegisterClientScriptBlock(this.GetType(), "Alert", script,

true);
 }

elseif(TextBox2.Text =="")

string script = "alert('Please Enter User Name')";

ClientScript.RegisterClientScriptBlock(this.GetType(), "Alert", script,

true);

elseif (TextBox3.Text == "")

string script = "alert('Please Enter Password')";

ClientScript.RegisterClientScriptBlock(this.GetType(), "Alert", script,

true);

elseif (TextBox4.Text == "")

string script = "alert('Please Enter Email Id')";

ClientScript.RegisterClientScriptBlock(this.GetType(), "Alert", script,

true);

elseif (TextBox5.Text == "")

string script = "alert('Please Enter Mobile')";

ClientScript.RegisterClientScriptBlock(this.GetType(), "Alert", script,

true);

}
elseif (TextBox6.Text == "")

string script = "alert('Please Enter Address')";

ClientScript.RegisterClientScriptBlock(this.GetType(), "Alert", script,

true);

elseif (i == 1)

string script = "alert('Registration has been Sucessfully')";

ClientScript.RegisterClientScriptBlock(this.GetType(), "Alert", script,

true);

else

string script = "alert('Not Register')";

ClientScript.RegisterClientScriptBlock(this.GetType(), "Alert", script,

true);

TextBox1.Text = "";

TextBox2.Text = "";

TextBox3.Text = "";

TextBox4.Text = "";

TextBox5.Text = "";

TextBox6.Text = "";
 }

protectedvoid Button2_Click(object sender, EventArgs e)

TextBox1.Text = "";

TextBox2.Text = "";

TextBox3.Text = "";

TextBox4.Text = "";

TextBox5.Text = "";

TextBox6.Text = "";

Mechanic

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Configuration;

using System.Data;

using System.Data.SqlClient;
publicpartialclasscomplaintform : System.Web.UI.Page

SqlConnection conn =

newSqlConnection(ConfigurationManager.ConnectionStrings["Tax"].Connecti

onString);

protectedvoid Page_Load(object sender, EventArgs e)

protectedvoid Button1_Click(object sender, EventArgs e)

conn.Open();

SqlCommand cmd = newSqlCommand("INSERT INTO

complaint(username,mobile,address,email,depart,query) values('" +

TextBox1.Text + "','" + TextBox2.Text + "','" + TextBox3.Text + "','" +

TextBox4.Text + "','" + TextBox5.Text + "','" + TextBox6.Text + "')", conn);

cmd.ExecuteNonQuery();

conn.Close();

Label5.Visible = true;

Label5.Text = "successfull";

Response.Redirect("download.aspx");

}
}

Message Admin

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Configuration;

using System.Data;

using System.Data.SqlClient;

publicpartialclassAddTax : System.Web.UI.Page

int tax;

SqlConnection conn =

newSqlConnection(ConfigurationManager.ConnectionStrings["Tax"].Connecti

onString);

protectedvoid Page_Load(object sender, EventArgs e)

{
 }

protectedvoid Button1_Click(object sender, EventArgs e)

conn.Open();

string username = Request.Cookies["usrname"].Value;

SqlCommand cmd = newSqlCommand("INSERT INTO message

(username,message) VALUES ('" + username + "','" + message.Text + "')",

conn);

cmd.ExecuteNonQuery();

Response.Write("<script>alert('Message Sent Successfully')</script>");

conn.Close();

User login

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Configuration;
using System.Data;

using System.Data.SqlClient;

publicpartialclassAdmin : System.Web.UI.Page

SqlConnection conn =

newSqlConnection(ConfigurationManager.ConnectionStrings["Tax"].Connecti

onString);

protectedvoid Page_Load(object sender, EventArgs e)

conn.Open();

protectedvoid Button1_Click(object sender, EventArgs e)

string usname= Request["uname"];

string psw = Request["pswd"];

if ((usname == "") || (psw == ""))

Response.Write("<script>alert('Username or Password cannot be

null')</script>");

else

SqlCommand cmd = newSqlCommand("SELECT * FROM policereg where

username='" + usname + "' and password='" + psw + "'", conn);

SqlDataReader read = cmd.ExecuteReader();

if (read.Read())

Response.Cookies["uname"].Value = Request["uname"];

Response.Redirect("ViewDocuments.aspx");

else

Response.Write("<script>alert('Wrong Credentials')</script>");

Police reg

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Configuration;

using System.Data;
using System.Data.SqlClient;

using System.IO;

publicpartialclasspolicereg : System.Web.UI.Page

SqlConnection conn =

newSqlConnection(ConfigurationManager.ConnectionStrings["Tax"].Connecti

onString);

protectedvoid Page_Load(object sender, EventArgs e)

protectedvoid Button1_Click(object sender, EventArgs e)

SqlCommand cmd = newSqlCommand("insert into

policereg(id,name,username,password,mobile,email,depart) values('" +

TextBox1.Text + "','" + TextBox2.Text + "','" + TextBox3.Text + "','" +

TextBox7.Text + "','" + TextBox5.Text + "','" + TextBox4.Text + "','" +

TextBox6.Text + "')", conn);

try

conn.Open();
 cmd.ExecuteNonQuery();

string script = "alert('Your data has been inserted Successfully');";

ClientScript.RegisterClientScriptBlock(this.GetType(), "Alert", script,

true);

//Response.Redirect("Login.aspx");

catch

conn.Close();

string script = "alert('Your data not inserted ');";

ClientScript.RegisterClientScriptBlock(this.GetType(), "Alert", script,

true);

TextBox1.Text = "";

TextBox2.Text = "";

TextBox3.Text = "";

TextBox7.Text = "";

TextBox5.Text = "";

TextBox4.Text = "";
 TextBox6.Text = "";

protectedvoid Button2_Click(object sender, EventArgs e)

TextBox1.Text = "";

TextBox2.Text = "";

TextBox3.Text = "";

TextBox7.Text = "";

TextBox5.Text = "";

TextBox4.Text = "";

TextBox6.Text = "";

viewfeedback

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Data;

using System.Data.SqlClient;

using System.Configuration;

using System.IO;
using System.Collections;

publicpartialclassViewDocuments : System.Web.UI.Page

SqlConnection conn =

newSqlConnection(ConfigurationManager.ConnectionStrings["Tax"].Connecti

onString);

protectedvoid Page_Load(object sender, EventArgs e)

conn.Open();

SqlCommand cmd = newSqlCommand("SELECT * FROM documents", conn);

SqlDataReader read = cmd.ExecuteReader();

GridView1.DataSource = read;

GridView1.DataBind();

conn.Close();

protectedvoid DownloadFile(object sender, EventArgs e)

string filePath = (sender asLinkButton).CommandArgument;

Response.ContentType = ContentType;

Response.AppendHeader("Content-Disposition", "attachment;

filename=" + Path.GetFileName(filePath));

Response.WriteFile(filePath);

Response.End();

}
protectedvoid DeleteFile(object sender, EventArgs e)

conn.Open();

string[] commandArgs = (sender

asLinkButton).CommandArgument.ToString().Split(newchar[] { ',' });

string id = commandArgs[0];

string fpath = Server.MapPath(commandArgs[1]);

SqlCommand cmd = newSqlCommand("DELETE FROM documents where

id='" + id + "'", conn);

cmd.ExecuteReader();

conn.Close();

File.Delete(fpath);

Response.Redirect(Request.Url.AbsoluteUri);

}
viewMessages

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Configuration;

using System.Data;

using System.Data.SqlClient;

publicpartialclassViewMessage : System.Web.UI.Page

SqlConnection conn =

newSqlConnection(ConfigurationManager.ConnectionStrings["Tax"].Connecti

onString);

protectedvoid Page_Load(object sender, EventArgs e)

if (!Page.IsPostBack)

conn.Open();

SqlCommand cmd = newSqlCommand("SELECT * FROM message ", conn);

SqlDataReader read = cmd.ExecuteReader();

GridView1.DataSource = read;

GridView1.DataBind();

conn.Close();

}
SCREENSHOTS

Home
Mechanic Login
User login
Register page
MECHANIC REGISTER
 CHAPTER-VII

CONCLUSION

The entire project has been developed and deployed as per the

requirements stated by the user, it is found to be bug free as per the testing

standards that is implemented. Any specification-untraced errors will be

concentrated in the coming versions, which are planned to be developed in

near future.

It offers following benefits :

1)     It eliminates all parent-child  relationships and instead represented all

data in the database as simple row/column tables of data values.

2)     Flexibility in data modeling.

3)     Easy access to all data.

4)     Each table is an independent entity and there is no physical

relationship between tables.

5)     Reduce data storage and redundancy.

6)     Independent of physical storage and  logical data design.

7)     A wide level data manipulation language (SQL).

BIBLIOGRAPHY

TEXTBOOK

1. Andrew Troelsen , C# and .NetPlatform,Apress,1st edition,2001.

2. StephenWalther (2008), ASP.NET Unleashed, India: Dorling Kindersley.

3. Ramesh Bangia,ASP.NET and C#,5th edition,2004.

4. Sivaprasath koirala,C# and ASP.NET Projects,BPB Publication.

5. J.G.R.Sathiaseelan,N.Sasikaladevi,Programming with C# .NET

WEBSITES
1.https://www.w3schools.com/ASP

2.www.tutorialteacher.com

3. www.tutorialpoint.com

4.www.csharpcorner.com

5.www.dotnettricks.com