A

PROJECT REPORT

ON

“Website of Hostel (“Garima Girls Hostel”)

Project work Submitted in partial fulfillment of the
Requirement for the Award of Degree for

BACHELOR
In
Computer science

Submitted to under the

guidance of
Mrs. APARNA dubey Mrs. APARNA
dubey

(hod)

Prepared by

Nidhi Yadav & ISHA JAFRI

DLS cOLLEGE , BILASPUR university

Bilaspur (c.g.)
 A

PROJECT REPORT

BILASPUR university
DLS COLLEGE

Bilaspur (c.g.)

CERTIFICATE

This is to certify that ………………………………………………………….. bearing Roll No. ……………….. ,

Enroll no. ………… have developed software project Titled “Online Banking System” for the

Partial fulfillment of the award of the Degree of Master of Science in Computer

Science.

Head of department Under the guidance of

MRS. APARNA DUBEY MRS. APARNA DUBEY

HOD,COMPUTER DEPARTMENT COMPUTER DEPARTMENT

DLS COLLEGE, BILASPUR(C.G.) DLS COLLEGE, BILASPUR(C.G.)

 ACKNOWLEDGEMENT

At every outset I express my gratitude to almighty lord for showering his grace and blessings upon
me to complete this project.

Although our name appears on the cover of this book, many people had contributed in some form or
the other form to this project Development. We could not done this project without the assistance or
support of each of the following we thank you all.

I wish to place on my record my deep sense of gratitude to my project guide, MRS APARNA
DUBEY, for his constant motivation and valuable help through the project work. Express my
gratitude to MRS APARNA DUBEY (HOD) computer dept, DLS college, Bilaspur (C.G.) for his
valuable suggestions and advices throughout the M.Sc.(CS) course.

I am also thankful to all the faculties of computer science dept, DLS College, Bilaspur (C.G.) for his
valuable suggestions and discussion whenever required.

………………

ABSTRACT
 As the name specifies “Garima Girls Hostel Website” is developed for

managing various activities in the hostel. For the past few years the number of

educational institutions is increasing rapidly. Thereby the number of hostels is also

increasing for the accommodation of the students studying in this institution. And

hence there is a lot of strain on the person who are running the hostel and software’s

are not usually used in this context. This particular project deals with the problems on

managing a hostel and avoids the problems which occur when carried manually.

Identification of the drawbacks of the existing system leads to the development

of computerized hostel management system that will be compatible to the existing

system with the system which is more users friendly and more GUI oriented. We can

improve the efficiency of the system, thus overcome the drawbacks of the existing

hostel management system. Less human error, Strength and strain of manual labour

can be reduced, High security, Data redundancy can be avoided to some extent, Data

consistency, Easy to handle, Easy data updating, Easy record keeping, Backup data

can be easily generated.

CONTENTS

1. INTRODUCTION
2. SYSTEM ANALYSIS
  FEASIBILITY STUDY
 IMPLEMENTATION PLAN
 GENERAL METHODOLOGY IN DEVELOPING SOFTWARE
PROJECT
 EXISTING SYSTEM AND ITS DRAWBACKS
 PROPOSED SYSTEM AND ITS MERITS
 HARDWARE AND SOFTWARE REQUIREMENTS
3. SOFTWARE REQUIREMENT SPECIFICATION
 USER REQUIREMENT DOCUMENT
4. SYSTEM DESIGN/IMPLEMENTATION DETAILS
 CLIENT-SERVER MODEL
 DATA FLOW DIAGRAMS
 E-R DIAGRAM
5. TESTING
 TYPES OF TESTING
6. SCREEN
7. CONCLUSION
8. BIBLIOGRAPHY
 INTRODUCTION

1. INTRODUCTION

Main objective of this project is to provide solution for hostel to manage most there

work using computerized process. This website will help admin to handle student’s

information, room allocation details, payment details, room information.

 As the name specifies “Garima Girls Hostel Website” is website developed for

managing various activities in the hostel. For the past few years the numbers of

educational institutions are increasing rapidly. Thereby the numbers of hostels are

also increasing for the accommodation of the students studying in this institution.

And hence there is a lot of strain on the person who are running the hostel and

software’s are not usually used in this context. This particular project deals with the

problems on managing a hostel and avoids the problems which occur when carried

manually.

.
 SYSTEM ANALYSIS

2. SYSTEM ANALYSIS

2.1 FEASIBILITY STUDY:

Feasibility study is conducted once the problem is clearly

understood. The feasibility study which is a high level capsule version of the entire system analysis
and design process. The objective is to determine whether the proposed system is feasible or not and
it helps us to the minimum expense of how to solve the problem and to determine, if the problem is
worth solving.

The following are the three important tests that have been carried out for feasibility study.
1. Technical Feasibility.

2. Economical Feasibility.

3. Operation Feasibility.

1. TECHNICAL FEASIBILITY:

In the technical feasibility study, one has to test whether the

proposed system can be developed using existing technology or not. It is planned to implement the
proposed system in JSP. The project entitled “Garima Girls Hostel Website” is technically feasible
because of the following reasons.

 All necessary technology exists to develop the system.

 The existing system is so flexible that it can be developed further.

2. ECONOMICAL FEASIBILITY:

As a part of this, the costs and benefits associated with the proposed
systems are to be compared. The project is economically feasible only if tangible and intangible
benefits outweigh the cost. We can say the proposed system is feasible based on the following
grounds.

 The cost of developing the full system is reasonable.

 The cost of hardware and software for the application is less.

3. OPERATIONAL FEASIBILITY:

The project is operationally feasible because there is sufficient support from the
project management and the users of the proposed system. Proposed system definitely does not harm
and will not produce the bad results and no problem will arise after implementation of the system.

2.2 IMPLEMENTATION PLAN:

The main plan for the system developed is to upgrading existing system to the
proposed system. There are mainly 4 methods of upgrading the existing to proposed

 Parallel Run System.

 Direct Cut-Over System.
  Pilot system.
 Phase-In Method.

Parallel Run System:

It is the most secure method of converting from an existing to new system. In

this approach both the systems run in parallel for a specific period of time. During that period if any
serious problems were identified while using the new system, the new system is dropped and the
older system is taken at the start point again.

Direct Cut-Over Method:

In this approach a working version of the system is implemented in one part of

the organization such as single work area or department. When the system is deemed complete it is
installed throughout the organization either all at once (direct cut-over) or gradually (phase-in).

Phase-In Method:

In this method a part of the system is first implemented and over time other
remaining parts are implemented.

Implementation Plan Used:

The Workflow Management system is developed on the basis of “Parallel Run

method” because we upgraded the system, which is already in use to fulfill the requirements of the
end-user. The system already in use is treated as the old system and the new system is developed on
the basis of the old system and maintained the standards processed by the older system. The
upgraded system is working well and is implemented on the client successfully.

2.3 General Methodology in Developing Software Project

 The general methodology in developing a system is involved in different
phases, which describe the system’s life cycle model for developing software project. The concept
includes not only forward motion but also have the possibility to return that is cycle back to an
activity previously completed. This cycle back or feedback may occur as a result of the failure with
the system to meet a performance objective or as a result of changes in redefinition of system
activities. Like most systems that life cycle of the computer-based system also exhibits distinct
phases.

Those are:

1. Requirement Analysis Phase

2. Design Phase
3. Development Phase
4. Coding Phase
5. Testing Phase

1. Requirement Analysis Phase:

This phase includes the identification of the problem in order to identify the
problem; we have to know information about the problem, the purpose of the evaluation for
problem to be known. We have to clearly know about the client’s requirements and the
objectives of the project.

2. Design Phase:
Software design is a process through which the requirements are translated
into a representation of software. One of the software requirements have been analyzed and
specified, the software design involves three technical activities: design, coding generation
and testing. The design of the system is in modular form i.e. the software is logically
partitioned into components that perform specific functions and sub functions. The design
phase leads to modules that exhibit independent functional characteristics. It even leads to
interfaces that reduce the complexity of the connections between modules and with the
external environment. The design phase is of main importance because in this activity,
decisions ultimately affect the success of software implementation and maintenance.

3. Development Phase:
 The development phase includes choosing of suitable software to solve the
particular problem given. The various facilities and the sophistication in the selected software
give a better development of the problem.

4. Coding Phase:
The coding phase is for translating the design of the system-produced during
the design phase in a given programming language, which can be executed by a computer and
which performs the computation specified by the design.

5. Testing Phase:
Testing is done in various ways such as testing the algorithm programming
code: sample data debugging is also one of following the above testing.

ARCHITECTURAL PATTERN

Model-View-Controller

The Model Layer

The model layer in a Java based web application can be implemented using any Java-based
technology, such as EJB, Hibernate, or JDO. In our Internet Banking System the model is
represented as simple JavaBeans containing the data and business logic in a simple data access
object. As far as possible, the model objects should be developed so that they have no knowledge of
the environment. This allows us to more easily reuse them across environments and applications.

The View Layer

The view layer of most Java based web applications is made up of Java Server pages. To facilitate
the development of the view, Java provides a set of JSP tag libraries. These tag libraries allow us to
easily provide fully internationalized user interfaces that interact with the model components of a
web application.

The vast majority of dynamic Web front ends are based on HTML forms, and users of such
applications have come to expect from these applications certain behaviors, such as form validation.
With standard JSP, this is a tedious process that involves recording the contents of the form and
populating every form element with information from a JavaBeans in case of error. Java facilitates
this sort of form processing and validation using Custom tags. These, in combination with the JSP
tag libraries, make View development with forms really simple and natural.

The Controller Layer

Java includes a Servlet that implements the primary functions of the Controller, which is to map the
incoming URL to a model object. The Servlet provides the following functions:

1. Decide what action is required to service a users request

2. Provide view data to the view
3. Decide which view to show next

A Java developer must provide these actions (models) to implement the logic of their application.

What is Model-View-Controller?

. Let’s start by looking at how the Model, the View, and the Controller interact with one another:

Figure 1: Model 2/MVC architecture

As you can see from the above diagram, the user interacts with the Controller components (usually
represented by Servlets) by submitting requests to them. In turn, the Controller components
instantiate Model components (usually represented by JavaBeans or other similar technology), and
manipulate them according to the logic of the application. Once the Model is constructed, the
Controller decides which View (usually represented by Java Server Pages) to show to the user next,
and this View interacts with the Model to show the relevant data to the user.

Using Java Server Pages or Servlets alone is known as Model 1.

Model 2 was not particularly innovative or new. It uses Servlets to resemble Controller and Java
Server Pages for resembling views. Many people realized that it follows the well-known MVC
pattern that was developed back in the days of Smalltalk. As such, Java programmers tend to use
the terms Model 2 and MVC interchangeably.

2.4. EXISTING SYSTEM:

The current system is as mentioned earlier very complicated and expensive as compared to
the new system. It also wastes the precious time of the faculties which can then be used in solving
student queries and helping them improvise.

The existing banking system is completely manually and time taking system. It is
complicated system.

2.5 PROPOSED SYSTEM:

1.SECURITY: There is a lot of security of data on this content management system. One cannot
open our system without knowing the password. Immediately after opening login screen will
appear on screen. Only after entering the correct username and password user can operate our system.

2. REFERENTIAL INTEGRITY: User cannot change the date in the transaction files. Addition of
data can be done only on the master files date in transaction files cannot be entered until addition is done
on the master files.

3. EASY RETRIEVAL OF DATA:

Data is retrieved easily and quick using sql commands. Online commands are used to retrieve
huge amount of data.

4. GENERATION OF AUTOMATIC VALUES:

In project in some screen some fields generated automatically like Profile detail, Account number,
etc.

OVERVIEW OF PROPOSED SYSTEM

1. MENU DRIVEN:
The project uses menu throughout which we can choose required options. Menus are self-explanatory,
as they are very easy to use and user can go to any other web page using the menu.
2. USER CONFIRMATION:
Whenever the user tries to delete or edit the data, the system asks for the confirmation. This issued to
avoid the accidental changes to the database. A confirmation is also provided for the exit of the
application.

3. GRAPHICALUSER INTERFACE:
User is provided with a graphical interface in which user can select from various options and can
perform desired operations with perfect understanding of the menu selected.

4. MULTIPLE DOCUMENT INTERFACE:

The package provides a multiple document interface to the user. The user can view more than one
entry form or pages at the same time.
5. SECURITY AND ACCESS:
A password form has been provided at the beginning of the package. Entering the correct password
will take user to the main user page.

BUSINESS CONTEXT
Existing banking system is a manual system, which leads to a number of problems in maintaining
proper records. These are:

1. PAPER WORK: All the activities that are performed by Management involve a lot of paper work
involving register consultations and entries. A separate file has to be maintained for each kind of
activity and for different periods of time.
2. TIME CONSUMPTION:
A lot of time is consumed in referencing the registers involved for particular activities and a lot of
computation as well as report verification activity are also paper based and time consuming.
3. COMPLEXITY: Complexity of information handling and the gathering and determination
of information is usually the most difficult problem faced.
4. REDU NDANCY: Maintaining separate files for each department can lead to duplication of data
present in files. This can lead to: a) Inconsistencies b) Update anomalies) Decentralization problems
5. HUMAN ERRORS: Human kind of errors may be generated in typing errors and slow arithmetic
calculations, fatigue and boredom.
6. ILLEGAL ACCESS: The security of a lot of documents, which are paper, based in difficult may
be in terms of illegal access or manipulation by malicious personals either intentionally or by accident.
7. DYNAMIC ENVIRONMENT: As the working environment is dynamic and company policies
change time and again, changing the way of working will be difficult.

2.6 HARDWARE AND SOFTWARE REQUIREMENTS:

HARDWARE REQUIREMENTS:

Server Configuration:

 Minimum 1GB Hard Disk preferable,

 P-III processor or equivalent,
 RAM 256 MB,
  Windows with Apache preloaded.
Client Configuration:
PC with browser .
SOFTWARE REQUIREMENTS:

 Operating System - Windows

 Language - HTML
 Database - Oracle
 Network - LAN

SOFTWARE REQUIREMENT
SPECIFICATION
 3. SOFTWARE REQUIREMENT SPECIFICATION:
SCOPE OF THE DEVELOPMENT OF THE PROJECT:

Database Tier:
The concentration is applied by adopting the Oracle 8i Enterprise versions. SQL
(Structured Query Language) is taken as the standard query language.

Web Tier:
The web tier interface is developed to build a web application which facilities the
user to work on browser specific environment to have distributed architecture. The components are
designed using HTML standards and Java Server Pages power the dynamic of page design.

Data Base Connectivity Tier:

The communication architecture is designed by concentrating on standards of JSP.

The database connectivity is established using the Java Database Connectivity.

Overview:

A System Requirements Specification (SRS) is a description of a particular product,

program or a set of programs that performs a set of functions in a target environment.

During analysis SRS deals with 5 issues

 Functionality
 External Interfaces
 Performance
 Attributes
 Constraints
 The Software Requirements Specification (SRS) begins the translation process
that converts the software requirements into the language the developers will use. The SRS draws
on the use-cases from the feasibility system study report and analyzes the situations from a
number of perspectives to discover and eliminate inconsistencies, ambiguities, and omissions
before development progresses significantly under mistaken assumptions.

3.1 USER REQUIREMENT DOCUMENT:

Functional Requirements:

This section analyzes various angles of the functionality to be developed. You do not need to
use each type of analysis for the entire system. Select only that analysis that best allow you to
complete your understanding of the requirements.

Internet banking System consists of the following modules:

Non-functional Requirements:

Performance Requirements:

System can withstand even though many no. of users requested the desired
service. As we are keeping server of the Internet Banking System and access is given to the
restricted users.

Safety and Reliability Requirements:

By incorporating a robust and proven RDBMS into the system, reliable

performance and integrity of data is ensured.
 SYSTEM DESIGN AND
IMPLEMENTATION DETAILS

4. SYSTEM DESIGN AND IMPLEMENTATION DETAILS

4.1 CLIENT SERVER MODEL

When an architect designs a building, he has a vision of the finished product

and produces a result based on that vision. Client-Server, on the other hand, is more like Darwinian
Model of evolution of a living species. No one has a vision of the finished products; rather, day-
today events and gradual changes affect it over time in reaction to those events.

In the beginning, application was fairly simple, reading input transaction in

a ‘batch’, processing them against a data store, and the output was a paper. Record retrieval was
usually a set of subroutines embedded in the updating program.

Common functions gradually migrated from the application to the operating

system. Database processing was one of the first major functions to be removed from application
control. Much of the time database functions in the application included retrieval, replacement and
insertion. Since it was a function has to be introduced database administration. This new function
was separated from the application code and involved defining the structure of the database; value
ranges backup, rollback, and so forth.

Advantages of Client-Server Model:

 The hardware and software can be placed where it will do the most good.
 In Client-Server model PCs, the power can be spread across the client and the server.
 On client side, an Active X object is used to present data.
 By having the client side it can do more work.
 The client software supplies the interface (Such as windowed program) and the knowledge of
how to pass the request to the server and the format of the data for the user when it’s returned
from the server. The server’s job is to manipulate the data according to the user’s request.
Data Flow Diagram

Context level DFD

Student Module
Registration process

Admin module

Allotment process

Vacating process
E - R Diagram

HTML (Hyper Text Markup Language):

 Hyper Text Markup Language (HTML), the languages of the World Wide Web
(WWW), allows users to produce web pages that include text, graphics and pointer to other web
pages (Hyperlinks).

HTML is not a programming language but it is an application of ISO standard

8879, SGML (Standard Generalized Markup Language), but specialized to hypertext and adapted to
the web. The idea behind Hypertext is that instead of reading text in rigid linear structure, we can
easily jump from one point to another point. We can navigate through the information based on our
interest and preference. A Markup language is simply a series of elements, each delimited with
special characters that define how text or other items enclosed within the elements should be
displayed. Hyperlinks are underlined or emphasized works that load to other documents or some
portions of the same document.

HTML can be used to display any type of document on the host computer, which
can be geographically at a different location. It is a versatile language and can be used on any
platform or desktop.

HTML provides tags (special codes) to make the document look attractive. HTML
tags are not case-sensitive. Using graphics, fonts, different sizes, color, etc., can enhance the
presentation of the document. Anything that is not a tag is part of the document itself.

The HTML is a collection of platform independent styles, indicated by the markup

tags that define invented by Tim Benners Lee while at CERN. HTML documents are plain text that
can be created using text editor. We can also use word processing software if we remember to save
documents as “text only with line breaks”.

Every HTML document should contain certain standard HTML tags. Each
document should contain Head and Body text. The head contains the title of the document and the
body contains the text, which is made up of paragraphs, lists and other elements. Browser expects
specific information because those are programmed according to HTML and Standard Generalized
Markup Language (SGML) specifications.

The HTML tags <html>, <head>, <title> and <body> and their corresponding end
tags should be used in each HTML file.

<HTML>:
 This element tells the browser that the file contains HTML coded information. The file
extension .html also indicates this is an HTML document and must be used.

<HEAD>:

The <head> element identifies the part of our HTML coded document that contains the title.
The title is shown as part of the browser’s windows.

<TITLE>:

The <title> element contains the document title and identifies its content in global context.

<BODY>:

The largest part of the HTML document. This portion of our HTML code is displayed
within the text area of the browser window.

Advantages:

 A HTML document is small and hence easy to send over the net. It is small because it does
not include formatted information.
 HTML is platform independent.
 HTML tags are not case-sensitive.
DHTML (Dynamic Hyper Text Markup Language):

With the explosion of interest in the World Wide Web, Hypertext Markup
Language (HTML) has assumed a prominent place in the computer world. HTML has evolved to
meet the increasing demand for eye-catching and mind-catching websites. Until recently, however
the evolutionary process mostly involved new and improved tags and attributes. The end products,
static web pages that often required repeated time-consuming round trips between client and server
machines, clearly showed a new direction was in order.

Dynamic HTML is that new direction. It combines HTML with cascading style
sheets and scripting languages.

JAVASCRIPT:

JavaScript is a script-based programming language that was developed by

Netscape Communication Corporation. JavaScript was originally called Live Script and renamed as
JavaScript to indicate its relationship with Java. JavaScript supports the development of both client
and server components of Web-based applications. On the client side, it can be used to write
programs that are executed by a Web browser within the context of a web page. On the server side, it
can be used to write Web server programs that can process information submitted by a web browser
and then update the browser’s display accordingly.

Even though JavaScript supports both client and server Web programming, we
prefer JavaScript at client side programming since most of the browsers supports it. JavaScript is
almost as easy to learn as HTML, and JavaScript statements can be included in HTML documents by
enclosing the statements between a pair of scripting tags.

<SCRIPT>……….</SCRIPT> (Default is JAVASCRIPT)

Also we can write

<SCRIPT LANGUAGE=”JavaScript”>

……….JavaScript statements……….

</SCRIPT>

JavaScript is the scripting language developed by Netscape Communications and

is commonly used to create interactive Web pages. JavaScript v1.2 comes with six predefined
classes: Boolean, Number, Date, Math, String, and Array. Additional classes and objects have been
defined to allow access to portions of the PDF file.

JavaScript is a prototype-based language with a syntax loosely based on C. Like C,

the language has no input or output constructs of its own, where C relies on standard I/O libraries, a
JavaScript engine relies on a host environment into which it is embedded. There are many such host
environment applications, of which web technologies are the best-known examples.

One major use of web-based JavaScript is to write functions that are embedded in
or included from HTML pages and interact with the Document Object

Model (DOM) of the page to perform tasks which are not possible in HTML alone.
Some common examples of this usage follow:

 Opening or popping up a new window with programmatic control over the size, position and
look of the new window.
 Validation of the web from input values to make sure that they will be accepted before they
are submitted to the server.
 Changing images as the mouse cursor moves over them. This effect is often used to draw the
user’s attention to important links displayed as graphical elements.
JavaScript statements that are embedded within HTML code. When a request is
made to see a page, the HTML code that defines the requested page along with the embedded
JavaScript statements, are sent by the server to the client. Navigator interprets the HTML document
and executes the JavaScript code. The resultant page is displayed for the client. It is important to
understand this interpretation occurs on the client-side rather than the server-side.

The JavaScript check is very useful in addition to the CGI check because it can
catch mistakes before the form is actually sent to the server. In addition, when you use JavaScript the
server doesn’t need to spend quite so much time in error handling and is thus a little quicker. This
only matters if you have lots and lots of forms, but it’s good to keep it in mind.

JavaScript is a simple to comprehend, easy to use, general purpose scripting language. When used in
conjunction with a Web browser’s Document Object Model (DOM), it can produce powerful
dynamic HTML browser-based applications, which can also feature animation and sound.

Here are a few things we can do with a JavaScript:

 Validate the contents of a form and make calculations.

 Add scrolling or changing messages to the Browser’s status line.
 Animate images or rotate images that change when we move the mouse over them.
 Detect the browser in use and display different content for different browsers.
 Detect installed plug-ins and notify the user if a plug-in is required.
 We can do much more with JavaScript, including creating entire application.

JavaScript Vs Java:
 JavaScript and Java are entirely different languages.

A few of the most glaring differences are:

 Java applets are generally displayed in a box within the web document; JavaScript can affect
any part of the Web document itself.
 While JavaScript is best suited to simple applications and adding interactive features to web
pages; Java can be used for incredibly complex applications.
There are many other differences but the important thing to remember is that
JavaScript and Java are separate languages. They are both useful for different things; in fact they can
be used together to combine their advantages.

Advantages:

 JavaScript can be used for server-side and client-side scripting.

 It is more flexible than VB Script.
 JavaScript is the default scripting languages at Client-side since all the browsers support it.
 TESTING

5.TESTING
5.1 TYPES OF TESTING:

In software development project, errors can be injected at any stage during

development. The development of software involves a series of production activities where
opportunities for human fallibility’s are enormous. Because of human inability to perform and
communicate with perfection soft ware development is accomplished by a quality assurance activity.

Software testing is a critical element of software quality assurance and represents

the ultimate review of specification, design and coding .Testing presents an interesting anomaly for
the software engineer. The creates a series of test cases that are intended to demolish the software
engineer process that could be viewed as destructive rather than constructive.

TESTING OBJECTIVE

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

 A good test case is one that has a high probability of finding an as-yet undiscovered error.
  A successful test one that uncovers an as-yet undiscovered error.

The above objectives imply a dramatic change in viewpoint. They move counter
to the commonly held view that a successful test is one in which no errors are found .Testing cannot
show the absence of defects, it can only shoe that software errors are present.

Test Approaches:

Any engineered can be tested in one of the two ways.

1. Knowing the specified function that a product has been designed to perform tests can be
conducted that demonstrate each function is fully operational at the save time searching for
errors in each function.

2. Knowing the internal working of a product, test can be conducted to ensure that “all gears
mesh”.
That is that internal operation performs according to the specification and all internal components
have been adequately exercised. The first test approach is called Black box tasting and the second
approach is called White box testing.

Structural Testing (White Box Testing)

Introduction:

White box testing, sometimes called Glass box testing design method that uses the
control method of the procedural design to derive the test cases. Using white box testing methods the
software engineer can derive test cases that:

1. Guarantee that all independent paths with in a module have been exercised atleast once.
2. Exercise all logical decisions on their true and false sides.
3. Execute all loops at their boundaries and within their validity.
4. Logical errors and incorrect assumptions are inversely proportional to the probability that a
program path will be executed.
5. We often believe that logical path not likely to execute when, in fact , it may be executed on
regular basis.
6. Typographical errors are random.

Each of these reasons provides an argument for conducting white box tests. Black
box testing, no matters how through, may miss the kinds of errors above. ”Bugs lurk in corners and
congregate”. White-box testing is far more likely to uncover them. The design of test cases for
software and other engineered products can be as challenging as initial design of the product itself.
The tests that have the highest likelihood of finding the most errors with a minimum amount of time
and effort should be designed.

Test Case Specification:

A realistic goal for testing is to select a set of test cases. In the functional testing,
the test cases are decided solely on the basis of requirements .In the structural testing, they are
generated based on the actual code of the program or module to be tested.

In the test case specification we specify all the test cases that are used for the system
testing. First the different conditions that are need to be test, along with the test cases used for testing
are given. The test cases have been selected using the functional approach. The goal is to test the
different functional requirements as specified in the requirements documents. Test cases have been
selected for both valid and invalid inputs.

A rich variety of test case design methods have evolved for software.

These methods provide the developer with a systematic approach to testing.

Any engineered product can be tested in one of two ways.

1. Knowing the specified function that a product has been designed to perform.
2. Knowing the internal working of the project.
The first test approach is known as black box testing and the second is white box testing.

Functional Testing (Black Box Testing)

Introduction:

Black box testing focuses on the requirements of the software. That is black-box
testing enables the software engineer to drive a set of input conditions that will fully exercise all the
functional requirements of a program. Black –box testing attempts to find errors in the following
categories.

1. Introduction or missing function.

2. Interface errors.
3. Errors in data structures or external data access.
4. Initializing and termination errors.
Equivalence partitioning:

Equivalence partitioning is a black-box testing method that derives the input

domain of program into classes of data from which test cases can be derived. An ideal test case
single handedly uncovers a class of errors (e.g. incorrect processing of incorrect data) that might
otherwise require many cases to be executed before the general errors are observer.

Equivalence partitioning strives to define a test that uncovers the class of errors,
thereby reducing the total number of test that uncovers classes of errors, thereby reducing the total
number of test cases that must be developed.
 Testing case testing for equivalence partitioning is based on evaluation of
equivalence class for an input condition if a set of objects can be linked by relationship that are
symmetric, transitive and reflexive, an equivalence is present. An equivalence class represents a set
of valid or invalid states for input condition. Typically an input condition is a specific numeric value,
a range of values, a set of related values, or a condition.

System Test Plan

System Testing checks the product as a whole.

 Testing is done for user login.

 Testing is done for the security.
 Testing is done on the performance of the system.
 Allows usability testing.
 This system is thoroughly tested for all the possible conditions.

Levels of Testing

The different levels of testing that are to be conducted are

1. Code Testing
2. Program Testing
3. System Testing

Code Testing:

The code test has been conducted to test the logic of the program. Here, we have
tested with all possible combinations of data to find out logical errors. The code testing is done
thoroughly with all possible data available with library.

Program Testing:

Program testing is also called unit testing. The modules in the system are
integrated to perform the specific function. The modules have been tested independently, later
assembled and tested thoroughly for integration between different modules.

System Testing:

System testing has been conducted to test the integration of each module in the
system. It is used to find discrepancies between the system and its original objective. It is found that
there is an agreement between current specifications and system documentation.

Software Testing is carried out in three steps:

 The first step 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
the 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.

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.

The final step involves validation and testing which determines the software
functions as the user expected. Here also there may be some modifications. In the completion of the
project it is satisfied fully by the end user.

Integration Test Plan:

Data can be lost across an interface, one module can have an adverse effort on
other sub functions, when combined, may not produce the desired major functions. Integrated testing
is the systematic testing for constructing the uncover errors within the interface. The testing was
done with sample data. The developed system has run successfully for this sample data. The need for
integrated test is to find the overall system performance.

Unit Test:

In the unit testing we test each module individually and integrate with the
overall system. Unit testing focuses verification efforts on the smallest unit of software design in the
module. This is also known as module testing. The module of the system is tested separately. This
testing is carried out during programming stage itself. In the testing step each module is found to
work satisfactorily as regard to expected output from the module. There are some validation checks
for fields also. Foe example the validation check is done for varying the user input given by the user
for the validity of the data entered. It is very easy to find error debut the system.

OUTPUT TESTING:

After performance of the validation testing, the next step is output testing.
The output displayed or generated by the system under consideration is tested by asking the user
about the format required by the system
SCREENS
 CONCLUSION

7. Conclusion:

The expanded functionality of today’s website requires an appropriate approach

towards website development. This hostel management software is designed for
people who want to manage various activities in the hostel. For the past few years the
numbers of educational institutions are increasing rapidly.

Thereby the numbers of hostels are also increasing for the accommodation of the
students studying in this institution. And hence there is a lot of strain on the person
who are running the hostel and websites are not usually used in this context. This
particular project deals with the problems on managing a hostel and avoids the
problems which occur when carried manually.
 BIBILOGRAPHY

8. BIBILOGRAPHY

Text books Referred:

HTML: HTML Black Book by Steven Holzner

HTML and Dynamic HTML by Teri Kieffer