Abbi Project

CHAPTER -1
SYSTEM INTRODUCTION
1.1 PROJECT INTRODUCTION
When a Computer Software succeeds- when it meets the needs of the people
Who use it.When it performs flawlessly over a long period of time, when it is easy to modify
and even easier to use-it can and does change things for the better. But when Software fails,
when its users are dissatisfied, when it is error prone, when it is difficult to change and even
harder to use, bad things can and do happen.
We all want to build software that makes things better, avoiding the bad things that lurk in the
shadow of failed efforts. To succeed we need discipline when software is designed and built.
Many individuals and companies still develop software haphazardly, even as they build
systems to service the most advanced technologies of the day. As result, the quality of software
that we produce suffers and bad things happen.
This project is intended to serve as a guide to the software developed on
HOSTEL MANAGEMENT
I have tried to follow the principles and rules as suggested by the software engineers as far as
possible, in order to make this software a successful one.
1.2 DESCRIPTION OF THE PROJECT:

Managing a hostel is tedious task and system through its hostel management system is a
dynamic as well as practical approach as it helps the management to completely administer the
boarding functionalities. It allows easily managing and controlling the various aspects such as
hostel application, registrations and admission, allotment of rooms, blocks, fees, mess
complaints, request, correspondence and discipline.
This system in fact has become a boon for college as well as universitys authorities as it has
simplified their task by relieving them from the cumbersome and time consuming procedures
involved. The hostel module has been endowed with the features such as creating blocks and
floors with details, automatically generating list of room numbers for the needed floor,
predefining the fees, facilities charges, fines, tracking mess related information by generating
a token ID to student, setting menu for mess, keeping record of staff and student attendance
and maintaining complaint register. It has proved to be immensely benefitting while allocating
rooms also. Not only the applications are received and maintained by the system, the module
also analyses and appraises the applications on the basis of availability of any other criteria and
ABHISHEK RATHORE 03215202012
1|Page
marks them as qualified or disqualified. This module also offers variety of reports such
allocation list, fine report, joining report etc. to keep an eye on the entire functioning of hostel.
The hostel management system makes use of one lone centralized database running from a
central server. The most important benefit of implementing such a system is that it brings in
the transparency in the entire management which helps to induce discipline in the hostel and
develops a trust between the students and the management.
For admission into hostel, the following special features can be seen in respect of software
hostel management and they are automatic room allocation, saving of inmates particulars for
use at any time, financial management, mess management and all other benefits expected by
inmates.
This software is capable of managing inquiry details, student details, details of faculty
members, payment details and the like. The special features of this software hostel
management are managing of administration panel, information panel, hostel account panel,
student panel, hostel mess and food panel and more.
With this software, the administration is able to reduce employees as well as paper work and
to keep the records of the students and other inmates of the hostel such as allocation of rooms,
arrangement of meals, transfer of rooms, providing necessary facilities in the rooms,
maintaining discipline, maintaining records of visitors, looking after security aspects and other
essential facilities.
With the help of software hostel management, students are able to maintain separate hostel
account and rooms are allotted according to types and deciding on the number of occupants in
each room, waiting list maintenance, issuance of receipts to the fees collected and more.
OBJECTIVE OF THE PROJECT
To create an atmosphere of harmony and cooperation amongst the students.

To provide the students a peaceful and calm environment to enable them excel in every
aspect of their personality development.
To create amongst the students a sense of responsibility and to inculcate discipline.
To provide good quality food for student to keep them fit and healthy.
SCOPE OF THE PROJECT

This software product the hostel management to improve their services for all
the students of the hostel. This also reduce the manual work of the persons in admin penal and
the bundle of registers that were search when to find the information of a previous student,
because through this system you can store the data of those students who had leaved the
hostel
three
years
ago.
Through this you can check the personal profile of all the current students
within few minutes the data base of the system will help you to check a particular one. The
2|Page
system will help you to check the mess bills of every student and the students hostel dues. The
students of the hostel will be recognized from the ID number allocated at the room rental time
1.3 SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION
This document aims at defining the overall software of "HOSTEL MANAGMENT".
It gives an exclusive and elaborate description of hostel management functionality and the
products must contain only the requirements mentioned below. Any changes required by the
developers must be requested and subsequently a new document should be released.
PURPOSE:
This document describes the software requirements for the functioning of a hostel management.
It is intended for admin, hosteller and users.
SCOPE:
The function of HOSTEL MANAGMENT is to support the functioning provide hostel. The
advantage of hostel is that student is not required to go different rooms for living.
Definitions, Acronyms and Abbreviations

1. Username
2. Password
3. Balance amount
4. Balance deposit
References:
1. IEEE Recommended practice for software development
specification-IEEE std8333-1993.
requirement
2. WIKIPEDIA
Overview:
The rest of this SRS document describes the various System Requirements, Interfaces,
Features, And Functionality in details.
3|Page
CHAPTER- 2
SYSTEM ANALYSIS AND FEASIBILITY STUDY
2.1 FUNCTIONAL AND NON FUNCTIONAL REQUIREMENTS
There are two types of requirements:
1. Functional requirements
2. Non- Functional requirements
FUNCTIONAL REQUIREMENTS
These are related to the expectations from the intended software. They describe what the
software has to do. They are also called product features. Sometimes, functional requirements
may also specify what the software should not do.
Functional Requirements should include:
MAIN PAGE:It contains various form like login, sign up by navigating these form customer can get desired
information.
USER LOGIN MODULE:In this module, existing user gives the user-name and password and then he\she can access the
other details and if he\she is current user then first he would have to register himself by option
Registration module.
REGISTRATION MODULE:This module gives a registration form to the user for the Registration. After a unique user-name
and password he would be registered by which he would be login.
NON-FUNCTIONAL REQUIREMENTS
In systems engineering and requirements engineering, a non-functional requirement is a
requirement that specifies criteria that can be used to judge the operation of a system, rather
than specific behaviors. This should be contrasted with functional requirements that define
specific behavior or functions. The plan for implementing functional requirements is detailed
in the system design. The plan for implementing non-functional requirements is detailed in the
system architecture.
4|Page
PRACTICALITY: The system is quite stable and can be operated by the people with
average intelligence.
EFFICIENCY: I tried to involve accuracy, timeliness and comprehensiveness of the system

output.
COST: It is desirable to aim for the system with a minimum cost subject to the
condition that it must satisfy the entire requirement.
FLEXIBILITY: I have tried that the system should be modifiable depending on the
changing needs of the user. Such modifications should entail extensive reconstructing
or recreation of software. It should also be portable to different computer systems.
SECURITY: This is very important aspect which I followed in this designing phase and
tried to covers the areas of hardware reliability, fall-back procedures, and physical security of
data.
2.2 FEASIBILITY STUDY

Having come up with the proposed system, we know determine whether the proposed solution
is feasible or not. Feasibility analysis determines whether the proposed system can realize
project goals and practical implementation of the project is feasible or not.
Feasibility is the measure of how beneficial or practical the development of a computerized
system will be able to an organisation in our case. Their aspects have been considered to
evaluate the feasibility study for this project.
Technical feasibility is a measure of the practical of a special technical solution and the
available of technical resources and expertise. Operational feasibility is a measure of how well
the system will work in the organisation and how people feel about the system.
Economic feasibility is a measure of the cost effectiveness of the system. Economic feasibility
is a measure of the cost effectiveness of the system.
5|Page
Feasibility criteria
Technical Feasibility
This evaluation determines whether
The technology needed for the
Proposed system is available and
How it can be applied within the
Organisation. Technical evaluation
Must also assess whether the
organisation had expertise to use it.
Assessment of proposed solution

The proposed system is developed
using VB.NET a programming
language.
VB.net is a programming language to
design and develop database driven
applications.
The above tools are readily available,
easy to work and widely used for the
developing commercial applications.
The proposed system will reduce the

manual work and paper work and
It covers two aspects
speed up the process of whole
Functionality and Acceptance within HOSTEL MANAGMENT.
the organisation.
It fully supports the managements
Functionality includes issues such as requirements of desire reports and
determining whether the system can queries.
provide the store right information and
on the time.
The proposed system will be gladly
Acceptance implies how well received accepted by the staff and will make
this system would be from both user their routine work user friendly.
and management perspective.
Operational Feasibility
ECONOMIC FEASIBILITY
COST BENEFIT ANALYSIS
It looks at the financial aspects of the

project. It determine whether the
management has enough resources and
budged to invest in the proposed
system and the estimated time for the
recovery cost incurred. It also
determines whether it is worthwhile to
invest the money in the proposed
project. Economic Feasibility is
determined by means of cost benefit
analysis.
is always included by both

Tangible and Intangible items. We,
Being are concerned only with
intangible costs and benefits.
Intangible cost includes the efforts in

consulting
various
Business
Organisation developing the proposed
system.
6|Page
Cost Benefit Analysis is the weighing

of costs against benefits of the
proposed system to determine the cost
effectiveness.
Intangible benefits includes ease of

maintenance of Data Less redundancy
and faster processing of the data.
Thus, provide accurate information
quickly.
2.3 HARDWARE AND SOFTWARE REQUIREMENTS:

HARDWARE:
Processor -Minimum: 1.5 GHZ Intel Pentium 4(Or higher for best results)
Memory - Minimum: 4GB of RAM.
Disk Space - Minimum: 750 MB of disk space is required for product. Package.
Installation: Additional disk space is required for the resources that you develop.
Note:
1. Space requirements can be reduced or increased depending on the features that you install.
2. Additional disk space is required if you download the product package to install this product.
Display - 1024 x 768 resolution minimum using 256 Colours (or higher for the best results).
Other-Hardware-Microsoft mouse or compatible pointing device.
SOFTWARE REQUIREMENTS
Platforms:
Operating system - Windows 8, 7 Ultimate, XP.
Environment:
Visual Basic.Net 2010
SQL Server 2008
Front-end used
The .Net Framework (pronounced Dot Net) is a software framework that runs primarily on
Microsoft Windows. It includes a large library and supports several programming languages
which allows language interoperability (each language can use code written in the other
7|Page
languages). Programs written for the .NET Frame execute in a software environment (as
contrasted to hardware environment), known as the Common Language Runtime (CLR), an
application virtual machine that provides important services such as security, memory
management, and exception handling. The class library and the CLR together constitute the
.NET Framework.
The .Net Framework's Base Class Library provides user interface, data access, database
connectivity, cryptography, web application development, numeric algorithms, and network
communications. Programmers produce software by combining their own source code with the
.NET Framework and other libraries. The .NET Framework is intended to be used by most new
applications created for the windows platform. Microsoft also products a popular integrated
environment largely for .NET software called Visual Studio.
DESIGN FEATURES
Interoperability:
Because computer system commonly require interaction between new and older applications,
the .Net Framework provides means to access functionality that is implemented in programs
that execute outside the .NET environment. Access to COM components is provided in the
system. Runtime, Interop services and System. Enterprise services namespaces of the
framework, access to other functionality is provided using P/Invoke feature.
Common language runtime engine:

The Common Language Runtime (CLR) is the execution engine of the .NET Framework. All
.Net programs execute under the supervision of the CLR, guaranteeing certain properties and
behaviours in the areas of memory management, security and exception handling.
Language independence:
The .NET Framework introduces a Common Type System (CTS). The CTS specification
defines all possible data types and programming constructs supported by the CLR and how
they may or may not interact with each
other conforming to the Common Language
Infrastructure (CLI) specifications. Because of this feature .NET Framework supports the
exchange of types and object instances between libraries and applications written using any
conforming .NET language.
Base class library:

The Base Class Library (BCL), part of Framework Class Library (FCL), is a library of
functionality available to all language using .NET Framework. The BCL provides classes
8|Page
which encapsulate a number of common functions, including file reading and writing, graphic
rendering, database interaction, XML document manipulation and so on.
Simplified deployment:
The .NET Framework includes design features and tools that help manage the installation of
computer software to ensure that it does not interface with previously installed software, and
that it conforms to security requirements.
Security:
The design is meant to address some of the vulnerabilities, such as buffer overflows, that have
been exploited by malicious software. Additionally .NET provides a common security model
for all applications.
Portability:
While Microsoft has never implemented the full framework on any system except Microsoft
Windows, the framework is engineered to be platform agnostic, and cross platform
implementation are available for other operating systems (see silver light and the alternative
implementations section below). Microsoft submitted the specifications for the Common
Language Infrastructure (which includes the core class libraries, Common Type System, and
the Common Intermediate Language), the C# language, and the C++/CLI language to both
ECMA and the ISO, making them available as open standards. This makes it possible for the
third parties to create compatible implementations of the framework and its languages on other
platforms.
Architecture:
The purpose of Common Language Infrastructure (CLI) is to provide a language neutral
platform for application development and execution, including functions for Exception
handling, Garbage Collection, security, and interoperability. By implementing the core aspects
of the .NET framework within the scope of the CLI, this functionality will not be tied to a
single language but will be available across the many languages supported by the framework.
Microsoft's implementation of CLI is called the Common Language Runtime (CLR).
9|Page
Security:
.NET has its own security mechanism with two general features: Code Access Security (CSA)
and validation and verification. Code Access Security is based on evidence that is associated
with a specific assembly. Typically the evidence is the source of the assembly (whether it is
installed on the local machine or has been downloaded from the intranet or internet). Code
Access Security uses evidence to determine the permissions granted to the code. Other code
can demand the calling code is granted a specified permission. The demand causes the CLR to
perform a call stack walk: every assembly of each method in the call stack is checked for the
required permission, if any assembly is not granted the permission a security exception is
thrown.
Class library:
The .NET Framework includes a set of class libraries. The class library is organised in a
hierarchy of namespaces. Most of the built APIs are the part of either System.* or Microsoft.*
namespaces. These class libraries implement in large number of common functions, such as
file reading and writing, graphic rendering, database interaction, and XML document
manipulation, among others. The .Net class libraries are available to all CLI complaint
languages. The .NET Framework class library is divided into two parts: the Base Class Library
and the Framework Class Library.
The Base Class Library (BCL) includes a small subset of the entire class library and is the
core set of classes that serve as the basic API of common language runtime. The classes in the
mscrolib.dll and some of the classes in System.dll and System.core.dll are considered to be a
part of BCL. The BCL classes are available in both .Net Framework, Microsoft Silver Light
and Mono.
The Framework Class Library (FCL) is a superset of BCL classes and refers to the entire
class library that ships with .Net Framework. It includes an expanded set of libraries, including
Windows Forms, Foundation, and Windows Communication Foundation among others. The
FCL is much larger in scope than standard libraries for languages like C++ and comparable in
scope to the standard libraries of java.
Memory management
The .NET Framework CLR frees the developer from the burden of managing memory
(allocating and freeing up when done), instead it does the memory management itself by
detecting when the memory can be safely freed. Memory is allocated to instantiations of .NET
10 | P a g e
types (objects) from the managed heap, a pool of memory managed by CLR. As long as there
exists a reference to an object, which might be either a direct reference to an object, which
might be either a direct reference to an object via a graph of objects, the object is considered to
be in use. When there is no reference to an object, and it cannot be reached or used, it becomes
garbage, eligible for collection .NET Framework includes a garbage which runs periodically,
on a separate thread from the applications thread, that enumerates all the unusable objects and
reclaims the memory allocated to them.
The .NET Garbage Collector (GC) is a non-deterministic, compacting, mark and sweep
garbage collector. The GC runs only when a certain amount of memory has been used or there
is enough pressure for memory on the system. Since it is not guaranteed when the conditions
is to reclaim memory are reached, the GC runs are non-deterministic. Each .NET Applications
has a set of roots, which are pointers to objects on the managed heap (Managed objects). These
includes references to static objects and objects defined as local variables or method parameters
currently in scope, as well as objects referred to by CPU Registers. When GC runs, it pauses
the application, and for each object reachable. It uses .NET Metadata and reflection to discover
the objects encapsulated by an object, and then recursively walk them. It then enumerates all
the objects on the heap (which are initially allocated contiguously) using reflection. All objects
are not marked as reachable are garbage. This is the mark phase. Since the memory held by
garbage is not any consequence, it is considered free space. However, this leaves chunks of
free space between objects which are initially contiguous. The objects are then compacted
together to make used memory contiguous again. Any reference to an object invalidated by
moving the objects is updated by the GC to reflect the new location. The application is resumed
after the garbage collection is over.
The GC used by .NET Framework is actually generational. Objects are assigned a generation,
newly created objects belong to Generation 0. The objects that survive a garbage collection are
tagged as Generation 1, and the Generation 1 objects that survive another collection are
Generation 2 objects. The .NET Framework uses up to Generation 2 objects. Higher generation
objects are garbage collected less frequently than lower collection, as older objects tend to have
a larger lifetime than newer objects. Thus, by removing older (and thus more likely to survive
a collection) objects from the scope of a collection run, fewer objects need to be checked and
compacted.
Reason for using vb.net

Visual Basic .NET, part of the Visual Studio .NET suite, boasts a number of new features
designed to make programming faster and easier. In addition to the basic features, such as
variables, data types, constants, arrays, enumerations, operators, expressions, statements, and
procedures, some of the new features of Visual Basic are
Assemblies: An EXE or a DLL file that forms the basis of deployment, version control,
reuse, and security permissions of an application.
11 | P a g e
Namespaces: The components of assemblies, namespaces primarily organize the objects

present in the assemblies. An assembly can contain more than one namespace.
Adding references: You need to add a reference to the external object that you want to
use in your current application.
Attributes: The tags that are used to provide additional information about the elements
defined in a Visual Basic .NET program. Some of the most common uses of attributes are
To explain COM properties for classes, interfaces, and methods
To explain assemblies
To specify security requirements of methods
To specify features required to enforce security
Inheritance: Enables you to create classes that are derived from some other classes known
as base classes. Inheritance provides you the advantage of defining a class only once. You
can then reuse this functionality by deriving new classes from this class.
Windows Forms: With a new forms package called Windows Forms, Visual Basic .NET
allows the developers to inherit a form from an existing form.
Structured exception handling: Enables you to create more efficient and robust error
handlers by using structured exception handling, which allows you to detect and remove
errors at runtime.
Multithreading: Enables your applications to handle multiple tasks simultaneously.
Backend
Ms sql server 2008
SQL SERVER 2008 (formerly condemned "KATMAI") was released on august6, 2008 and
aims to make data management self tuning, self-organizing, and self-maintaining with the
development of SQL SERVER always on technologies, to provide near-zero downtime. SQL
SERVER 2008 also includes support for structured and semi-structured data, including digital
media formats for pictures, audio, video, and other multimedia data. In current version, such
multimedia data can be stored as BLOBs(binary large objects),but they are generic bit streams
.Intrinsic awareness of multimedia data will allow specialized functions to be performed on
them. According to Paul Flessner, senior Vice President, Server Applications, Microsoft Corp.,
SQL SERVER 2008 can be data storage backend for different varieties of data: XML, email,
time/calendar, file, document, spatial, etc. as well as perform search, query, analysis, sharing
and synchronization across all data types.
Other new data types include specialized date and time types and a spatial data type for
location-dependent data. Better support for unstructured and semi-structured data is provided
12 | P a g e
using the new FILESTREAM data type, which can be used to reference any file stored on the
file system. Structured data and metadata about the file is stored in SQL Server database,
whereas the unstructured component is stored in the file system .Such files can be accessed
both via Win32 file handling APIs as well as via SQL SERVER using T-SQL; doing the latter
accesses the file data as a BLOB. Backing up and restoring the database backs up or restores
the referenced files as well. SQL SERVER 2008 also natively supports hierarchical data, and
includes T-SQL constructs to directly deal with them, without using recursive queries.
The full-text search functionality has been integrated with the database engine. According to a
Microsoft technical article, this specifies management and improves performance.
Spatial data will be stored in two types. A "Flat Earth"(geometry or planar) data type
Represents geospatial data which has been projected from its native, spherical, coordinate
system into a plane. A "Round Earth" data type (Geography) uses an ellipsoidal model which
the Earth is defined as a single continuous entity which does not suffer from the singularities
such as the international dateline, poles or map projection zone "edges"
Approximately 70 methods are available to represent spatial operation for the Open Geospatial
Consortium Simple Features for SQL, Version 1.1
SQL Server includes better compression features, which also helps in improving scalability .It
enhanced the indexing algorithms and introduced the notion of filtered indexes. It also includes
RESOURCE GOVERNOR that allows reserving resources for certain users or workflows .It
also includes capabilities for transparent encryption of data (TED) as well as compression of
Backups.
The version SQL SERVER management studio included with SQL SERVER 2008 supports
intelligence for SQL queries against a SQL SERVER 2008 Database engine .SQL SERVER
2008 also makes the database available via windows PowerShell providers and management
functionality available as CMDLT, so that the server and all the running instances can be
managed from windows PowerShell.
Sql server tables

SQL Server stores records related to each other in a table. Different tables are created for the
various groups of information. Related tables are grouped together to form a database.
13 | P a g e
Primary key
Every table in SQL Server has a field or a combination of fields that uniquely identifies each
record in the table .The unique identifier is called the Primary key, or Simply the Key. The
Primary Key provides the means to distinguish one record from all other in a table. It allows
the user and the database system to identify, locate and refer to one particular record in the
database.
Relational database
Sometime all the information of interest to a business operation can be stored in a table. SQL
SERVER makes it very easy to link the data in multiple tables. Matching an employee to the
department in which they work is one example. This is what makes SQL server a relational
database management system, or RDBMS. It stores data in two or more tables and enables you
to define relationships between the tables and enables you to define relationships between the
tables
FOREIGN KEY
When a field is one table matches the primary key of another field is referred to as foreign key.
A foreign key is a field or a group of fields in one table whose values match those of the primary
key of another table.
Referential integrity
Not only dose SQL Server allow you to link multiple table, it also maintains consistency
between them .Ensuring that the data among related tables is correctly matched is referred to
as maintaining referential integrity.
Data abestraction
A major purpose of a database system is to provide users with an abstract view of the data. This
system hides certain details of how data is stored and maintained .Data abstraction is divided
into three levels.
Physical level: This is the level of abstraction at which one describes how the data are actually
stored.
14 | P a g e
Conceptual level: At this level of database abstraction all the attributed and what data are
actually stored is described and entries relationship among them.
View level: This is the highest level of abstraction at which one describes only part of the
database.
Advantages of rdbms
- Redundancy can be avoided
-Inconsistency can be eliminated
-Data can be shared
-Standards can be enforced
-Security restrictions can be applied
-Integrity can be maintained
-Conflicting requirements can be balanced
-Data independence can be achieved
Disadvantage of rdbms
A significant disadvantage of the DBMS system is cost. In addition to the cost of purchasing
of developing the software, the hardware has to be upgraded to allow for the extensive
programs and the workspace required for their execution and storage. While centralization
backed reduces duplication, the lack of duplication requires that the database be adequately
backed up so that in case of failure the data can be recovered.
Features of sql server (rdbms)

SQL SERVER is one of the leading database management system (DBMS) because it is the
only Database that meets the uncompromising requirements of today's most demanding
information system. From complex decision support system (DSS) to the most rigorous online
transaction processing (OLTP) application, even application that require simultaneous
15 | P a g e
DSS and OLTP access to the same critical data, SQL Server leads the industry in both
performance and capability SQL Server is a truly portable ,distributed ,and open DBMS that
delivers unmatched performance, continuous operation and support for every database.
SQL SERVER RDBMS is high performance fault tolerant DBMS which is specially designed
for online transaction processing and for handling large database application.
SQL SERVER with transaction processing option offers two features which contribute to very
high level of transaction processing throughput, which are
-The row level lock manage
Enterprise with data sharing

The unrivalled portability and connectivity of the SQL SERVER DBMS enables all the system
in the organization to be linked into a singular, integrated computing resource,
Portability
SQL SERVER is fully portable to more than 80 distinct hardware and operating system
platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens of proprietary platforms.
This portability gives complete freedom to choose the database server platform that meets the
system requirements.
Open system
SQL SERVER offers a leading implementation of industry- standard SQL .SQL Server's open
architecture integrates SQL SERVER and non- SQL SERVER DBMS with industrys most
comprehensive provides transparent access to data from other relational database and even nonrelational database.
Distributed data sharing

SQL Server's networking and distributed database capabilities to access data stored on remote
server with the same ease as if the information was stored on a single local computer.
A single SQL statement can access data at multiple sites .you can stored data were system
requirements such as performance, security or availability dictate.
16 | P a g e
Unmatched performance
The most advance architecture in the industry allows SQL SERVER BBMS to deliver
unmatched performance.
Sophisticated concurrency control

Real World applications demand access to critical data .with most database systems
application becomes "conventional bound" -which performance is limited not by the cpu
power or by disk I/O, but user waiting on another for data access .
SQL Server employs full, unrestricted row- level locking and contention free queries to
minimize and in many cases entirely eliminates contention wait time.
2.4 Tools used

Microsoft visual basic
Microsoft visual basic is the fastest and easiest way to create the applications for Microsoft
Windows. Whether one is an experience professional or brand new to windows programming.
Visual basic provides them with a complete set of tools to simplify the rapid application
development. I straightaway comes to a brief introduction of Microsoft visual basic.
So what is visual basic? The "visual" part refers to the methods used to create the graphical
user interface (GUI). Rather than writing numerous lines of code to describe the appearance
and location of the interface element, rebuild objects can simply be dragged and dropped into
places of screens.
The "Basic" part refers to the BASIC (Beginners all-purpose symbolic introduction code)
language, a language used more programmers than any other language in the history of
computing. Visual Basic has evolved from the original basic language and now contain several
hundred statements, functions and key words many of which relate directly to the windows
GUI.
Beginners can create application by learning just a few of the key words, yet the power of the
language allows professional to accomplish using any other windows programming language.
The visual basic programming language is not unique to visual basic. The visual basic
programming language is not unique to visual basic. The visual basic programming system,
Application addition included in the Microsoft excel and many windows application using the
same language, the visual basic system scripting edition control's.
17 | P a g e
Integerated development environment

The working environment in visual basic is referred to as the integrated development or IDE
because it integrates much different function. Such as design, editing, compiling and debugging
within a common environment. In most traditional development tools each of these function
would operate as the separate programming, each with its own interface.
The Visual Basic Integrated Environment (IDE) consists of the following elements:
Menu bar
Displays the commands you used to work with the visual basic. Besides the standard file, edit,
view, window and help menus are provided to access function specific to programming such
as project, format or debug.
Context menus
Contains short cut to frequently performed action.
Tool bars
Provide quick access to the commonly use in the programming environment.
Tool box
Provide a set of tools that is used at design time to place control on a form in addition to the
default tool box layout, custom layout can also be created by selecting add tab from the context
menu and adding controls to the resulting tab.
Project explorer window

Lists forms and modules in your current project, a project is the collection of files you used to
build an application.
Properties window
Lists the properties setting for the selecting for m or control a property is a character stick of
an object. Such as size, caption, colour.
Object browser
Lists object available for use in the project and gives a quick way to navigate through code.
The object browser can be used to explorer in the Visual Basic and other application. See what
methods and properties are available for those objects, and paste code procedures into your
application.
18 | P a g e
Form designer
Serves as a window that is customized to design the interface of the application. Controls
graphics and pictures can be added to a form to create the look wanted. Each form in the
application has its own form designer window.
Code editor window

Serves as an editor for entering application code. A separate code editor window is created for
each form or code module in the application.
Form layout window

The form layout windows allows positioning the application using a small graphical
representation of the screen.
Immediate locals and watch windows

Those additional windows are provided for use in debugging the application. They are only
available when the application is running with in the IDE.
Visual basics provides a great deal of flexibility, allowing configuring the working
environment to best suit the programmer's individual style. A choice can be made between a
single and multiple document interfaces, and the size and positioning of the various integrated
development environment (IDE) element can be adjusted.
The layout will pressed between sessions of Visual Basic
SDI or MDI INTERFACES
Two different styles are available for the visual basic:
Single document interface (sdi) or multiple document interface (mdi) with the
SDI option. All of the ID windows are free to be moved anywhere on the screen: as long as
visual basic is the current application they will remain on the of any other application with the
MDI option, all of the IDE windows are contains with a single resize able parent window.
Docking windows
Many of the windows in the IDE can be docked, or connected to each other or to the edge of
the screen. These include the tool box form layout window, project explorer, properties
window, colour, palette and immediate locals and watch windows.
With the MDI option, windows can be docked to any size of the parent windows, with the SDI
they can only be docked beneath the menu bars. Docking application can be table and on off.
For are given window by selecting the application check box on the docking tabs of the option
dialogue box, available from the option command on the tool and menus.
19 | P a g e
2.5 GANTT CHART

When creating a software project schedule, the planner begins with a set of tasks (the work
break down structure). If automated tools are used, the work break down is input as a task
network or task outline. Efforts, duration, and start date are then input for each task. In
addition, task may be assigned to specific individuals.
As a sequence of this input, a timeline chart, also called a Gantt chart, is generated. A Gantt
chart can be developed for the entire project. Alternatively, separated it depicts a part of a
software project schedule that emphasizes the concept scooping task for a new word processing
software project. All project tasks (for concept scooping) are listed in the left hand column.
The horizontal bars occur at the same time on the calendar, task concurrency is implied. The
diamonds indicate milestones.
Once the information necessary for the generation of the Gantt chart has been input, the major
of software project scheduling tools produce tables a tabular listing of all project tasks, their
planned and actual start and end dates, and a verify of related information. Used in conjunction
with the Gantt Chart project tables enable the project manager to track
Progress.
20 | P a g e
2.6 PROTOTYPE MODEL

The basic idea here is that instead of freezing the requirements before a design or coding can
proceed, a throwaway prototype is built to understand the requirements. This prototype is
developed based on the currently known requirements. By using this prototype, the client can
get an actual feel of the system, since the interactions with prototype can enable the client to
better understand the requirements of the desired system. Prototyping is an attractive idea for
complicated and large systems for which there is no manual process or existing system to help
determining the requirements. The prototype are usually not complete systems and many of the
details are not built in the prototype. The goal is to provide a system with overall functionality.
Diagram of Prototype model:
Advantages of Prototype model:
Users are actively involved in the development

Since in this methodology a working model of the system is provided, the users get a better
understanding of the system being developed.
Errors can be detected much earlier.
Quicker user feedback is available leading to better solutions.
Missing functionality can be identified easily
Confusing or difficult functions can be identified Requirements validation, Quick
implementation of, incomplete, but functional, application.
Disadvantages of Prototype model:
Leads to implementing and then repairing way of building systems.
21 | P a g e
Practically, this methodology may increase the complexity of the system as scope of the
system may expand beyond original plans.
Incomplete application may cause application not to be used as the full system was
designed
Incomplete or inadequate problem analysis.
When to use Prototype model:
Prototype model should be used when the desired system needs to have a lot of interaction
with the end users.
Typically, online systems, web interfaces have a very high amount of interaction with end
users, are best suited for Prototype model. It might take a while for a system to be built
that allows ease of use and needs minimal training for the end user.
Prototyping ensures that the end users constantly work with the system and provide a
feedback which is incorporated in the prototype to result in a useable system. They are
excellent for designing good human computer interface systems.
22 | P a g e
CHAPTER 3
SYSTEM DESIGN
Introduction
System Design is an essential activity in the system Development life cycle. System design
is the general detailed specification of the computer based solution that was selecting during
system analysis. In the end, user requirement were translated into specification for the computer
based information System.
Three phases of System Design:
1.) Physical design
2.) Database Design
3.) Interface Design
3.1 DATA DICTIONARY

LOGIN TABLE:
COLUMN NAME
DATA TYPE
Username
Varchar
Password
Varchar
1. User login
COLUMN NAME
DATA TYPE
Username
Varchar
Password
Varchar
23 | P a g e
2. Registration
COLUMN NAME
DATA TYPE
Roll_no
Varchar
Hosteler_name
Char
Gender
Varchar
Date_of_joining
Char
Date_of_completion
Char
Address
Integer
Phone_no
Varchar
Email_id
Varchar
Stream
Varchar
Hosteler_picture
Image
3. hosteler profile
COLUMN NAME
DATA TYPE
Roll_no
Varchar
Father_name
Char
Mother_name
Float
address
DATA TYPE
5. Payment
COLUMN NAME
DATA TYPE
Roll_no
Varchar
Room_type
Varchar
Furniture_charges
Varchar
24 | P a g e
Food_prefrences
Varchar
Payament_type
Varchar
Draft/cheque
Varchar
6. User registration
COLUMN NAME
DATA TYPE
Username
Varchar
Password
Varchar
Re-enter password
Varchar
Date_of_birth
Varchar
Email_id
Varchar
Address
Varchar
3.2 PHYSICAL DESIGN

Explain relationship between various components (process, output, entities) of the system
through DFD's or other relative diagrams.
3.2.1 DATA FLOW DIAGRAM (DFDS)

A DFD is a graphical representation of the flow of the data through an information System.
DFDs can also be used for the visualization of data processing.
A DFD provides no information about the timing of the process or about what It is
common practice to draw a context level DFD first, which shows the interaction between
the system and the external agents which act as data sinks. It is also known as Level 0 DFD.
The context DFD is next Exploded to produce a Level 1 DFD that show some of detail of
the system being modeled.
The Level 1 DFD shows how the system is divided into sub systems(processes),
each of shows how a system is divided into subsystems, each of which deals with one
or more of the data flows to or from an external agent, and which together provide
all functionality of the system as a whole.
DFD are used to provide the end user with a physical idea of where the data they input
25 | P a g e
ultimately has an effect upon the structure of the whole system from order to dispatch to report.
Symbols used in DFD:-
Function
File/Database
Flow
Source
Her processes will operate in sequence or in parallel. It is quite diff from flowchart.
26 | P a g e
O_level
1_level
27 | P a g e
2_level
3.2.2USE CASE DIAGRAM

A use case diagram at its simplest is a representation of au= user's interaction with the system
and depicting the specifications of a use case. A use case diagram can portray the different
types of users of a system and the various ways that they interact with the system. This type of
diagram is typically used in conjunction with the textual use case and will often be
accompanied by other types of diagram as well.
Main Advantages of Use Case Diagram:
1. The use case diagram provides a comprehensive summary of the whole software system in
a single illustration.
2. The use cases are mainly composed of narrative text. Hence, unlike many other modelling
techniques, the non-technical stake holders (e.g. customers etc.) are also able to understand the
model for the software system. This means that feedback can be obtained at a very early stage
of the development from the customers.
3. The use case model can be utilized in several other aspect of software development as well,
e.g. Cost Estimation, Project Planning, Test Case Preparation and User Documentation.
28 | P a g e
S No.
Name
1.
Actor
An Actor or an external agent

lies outside the system model.
An Actor may be a person or an
information system i.e. external
to the system model an stick
figure and is not part of the
system itself. Actor appear
outside the rectangle.
2.
Use Case
It appears within the rectangle. It

describes a process.
3.
Relationship
It is a solid line between the

Actor
and
usecase.
A.
relationship
establish
only
between the Actor and Usecase
or Usecases only, not in between
the Actors.
Symbol
Description
29 | P a g e
USECASE
3.2.3SEQUENCE DIAGRAM
Sequence Diagrams Represent the objects participating the interaction horizontally and time
vertically. A Use Case is a kind of behavioural classifier that represents a declaration of an
offered behaviour. Each use case specifies some behaviour, possibly including variants that the
subject can perform in collaboration with one or more actors. Use cases define the offered
behaviour of the subject without reference to its internal structure. These behaviours, involving
interactions between the actor and the subject, may result in changes to the state of the subject
and communications with its environment. A use case can include possible variations of its
basic behaviour, including exceptional behaviour and error handling.
30 | P a g e
31 | P a g e
3.2.4 STATE CHART DIAGRAM

A state diagram is a type of diagram used in computer science and related fields to
describe the behavior of systems. State diagrams require that the system described is
composed of a finite number of states; sometimes, this is indeed the case, while at other
times this is a reasonable abstraction.
State diagrams are used to give an abstract description of the behavior of a system.
This behavior is analyzed and represented in series of events that could occur in one
or more possible states.
Symbols used in State Chart Diagram
32 | P a g e
Initial State
States
Transition
Final State
STATE CHART DIAGRAM
33 | P a g e
3.3DATABASE DESIGN
3.3.1 ENTITY RELATIONSHIP(ER) DIAGRAM
Definition: An entity-relationship (ER) diagram is a specialized graphic that illustrates
the relationships between entities in a database. ER diagrams often use symbols to represent
three different types of information.
1. Boxes are commonly used to represent entities.
2. Diamonds are normally used to represent relationships
3. Ovals are used to represent attributes...
Also Known As: ER Diagram, E-R Diagram, entity-relationship model
Entity - Relationship(ER) Modelling
ER Model Concepts
--Entities and Attributes -- Entity Types, Value Sets, and Key Attributes - -Relationships and
Relationship Types -- Weak Entity Types--Roles and Attributes in Relationship Types
->A database can be modeled as:
a collection of entities,
Relationship among entities.
Entity Relationship approach: -One of the most well-known modeling methods

Developed by P.Chem. In 1976, Many variations since then
i.
Entity: -A real-world object that can be distinctly identified may represent some real
physical object. E.g., Satish is a government employee; Kareena Kapoor is an actress; my
car is a Honda City
An entity is an object that exists and is distinguishable from other objects.

Example: specific person, company, event, plant
ii.
An entity set - Entity set is a set of entities of the same type that share the same
properties.
Example: set of all persons, companies, trees, holidays.
An Entity should be:
An Object that will have many instances in the
34 | P a g e
DB
An Object that will have multiple attributes
An Object that we are trying to model.
An Entity should not be:

User of the Database
An 0/P of the Database(e.g. Report)
iii.
Attributes: -An entity is represented by a set of attributes, that is, descriptive

properties possessed by all members of an entity set(value from corresponding
entity).
Example: a) customer = (customer-name, social-security, customer- street, customercity)
b) Account = (account-number, balance)
iv.
Domain: -The set of permitted values for each attribute
v.
Attribute types:
Simple and composite attributes.
Single-valued and multi-valued attributes 'Null attributes
Derived attributes
Identifiers (Key) attribute
35 | P a g e
SYMBOLS OF ER DIAGRAM
36 | P a g e
E_R DIAGRAM
3.4 INTERFACE DESIGN

Interface Design is a design of computers, appliances, machines, mobile
communication etc. with the focus on the user's experience and interaction. The goal
of user interaction as simple
As possible, in terms of accomplishing user goals what is often called user centric
design.
There are several phases and processes in the user interface design, some of which are
more demanded upon than others, depending on the project.
Functionality requirement gathering assembling a list of the functionality required

by the system to accomplish the goal of the project
User analyses of the potential users of the system either through discussion with the
people question involve
What would the user want the system to do?

How would the system fit in with the user normal workflow
37 | P a g e
How technically savvy is the user & what similar system does the user already use.
What interface look & field styles appeal to the user.
3.4.1 INPUT DESIGN

The input design link is the link that ties the information system into the user's
environment.
The major aspects that must be taken into consideration at the time if input is: What data to input,
How data should be arranged and coded.

Methods of performing input validation
Step to be followed when an error occurs.
User registration table
Registration
38 | P a g e
Payment
Hosteler_profile
Admin_login
39 | P a g e
3.4.2 OUTPUT DESIGN

SCREENSHOT
40 | P a g e
41 | P a g e
42 | P a g e
CHAPTER 4
SYSTEM
TESTING,
MAINTENANCE
IMPLEMENTATION
AND
4.1 SYSTEM TESTING

Introduction:
The implementation phase of software development is concerned with translating design
specification into source code. The preliminary goal of implementation is to write the code
and internal documentation so that conformance of the code to its specification can be easily
verifies, and so that debugging, testing and modifications are eased. This goal can be achieved
by making the source code as clear and straightforward as possible. Simplicity, clarity and
elegance are the hallmark of good programs. Obscurity, cleverness, and complexity are
indications of inadequate design and misdirected thinking.
Source code clarity is enhanced by structured coding techniques, by good coding style, by
appropriate supporting documents, by good internal comments, and by feature provided in
modern languages.
The implementation team should be provided with a well-defined set of software requirement,
an architectural design specification, and a detailed design description .Each team member
misunderstand the objectives of implementation
SOME SPECIAL TERMS IN TESTING FUNDAMENTAL:

-ERROR: The term error is used in two ways .It refers to difference between the actual output
of software and correct output, in this interpretation, error is essential measure of difference
between actual and ideal. Error is also used to refer to human action that result in software
containing a detect or fault.
-FAULT: fault is a condition but causes to fail in performing its required function. A fault is a
basic reason for software malfunction and is synonymous with the commonly used term Bug.
-FAILURE: Failure is the inability of a system or component to perform a required function

according to its specifications. a software failure occurs if the behaviour. Failure may be caused
due to functional or performance reasons.
43 | P a g e
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 high probability of finding an as yet undiscovered error.
3. A successful test is one that uncovers an as yet undiscovered error.
Testing should systematically uncover different classes of errors in a minimum amount of time
and with a minimum amount of effort. A secondary benefit of testing is that it demonstrates
that the software appears to be working as stated in the specifications. The data collected
through testing can also provide an indication of the software's reliability and quality. But,
testing cannot show the absence of defect -- it can only show that software defects are present.
TESTING PRINCIPLES
Before applying methods to design effective test cases, a software engineer must understand
the basic principles that guide software testing.
1. All tests should be traceable to customer requirements. As we have seen, the objective
of software testing is to uncover errors. It follows that the most severe defects (from the
customers point of view) are those that cause the program to fail to meet its
requirements.
2. Tests should be planned long before testing begins. Test planning can begin as soon as
the requirements model is complete. Detailed definition of test cases can begin as soon
as the design model has been solidified. Therefore, all tests can be planned and designed
before any code has been generated.
3. The Pareto principle applies to software testing. Stated simply, the Pareto principle
implies that 80 percent of all errors uncovered during testing will likely be traceable to
20 percent of all program components. The problem, of course, is to isolate these
suspect components and to thoroughly test them.
4. Testing should begin in the small and progress toward testing in the large. The first
tests planned and executed generally focus on individual components. As testing
progresses, focus shifts in an attempt to find errors in integrated clusters of components
and ultimately in the entire system
5. Exhaustive testing is not possible. The number of path permutations for even a
moderately sized program is exceptionally large. For this reason, it is impossible to
execute every combination of paths during testing. It is possible, however, to adequately
cover program logic and to ensure that all conditions in the component-level design
have been exercised. To be most effective, testing should be conducted by an
independent third party. By most effective, we mean testing that has the highest
probability of finding errors (the primary objective of testing).
Basics of software testing

There are two basics of software testing: black box testing and white box testing.
44 | P a g e
1. Black box Testing

Black box testing is a testing technique that ignores the internal mechanism of the system and
focuses on the output generated against any input and execution of the system. It is also called
functional testing.
2. White box Testing

White box testing is a testing technique that takes into account the internal
Mechanism of a system. It is also called structural testing and glass box testing.
4. Unit Testing
Unit testing is the testing of an individual unit or group of related units. It falls
Under the class of white box testing. It is often done by the programmer to test that the unit
he/she has implemented is producing expected output against given input.
4. Integration Testing
Integration testing is testing in which a group of components are combined to
Produce output. Also, the interaction between software and hardware is tested in Integration
testing if software and hardware components have any relation. It may fall under both white
box testing and black box testing.
5. System Testing
System testing is the testing to ensure that by putting the software in different environments
(e.g., Operating Systems) it still works. System testing is done with full system implementation
and environment. It falls under the class of black box testing.
6. Acceptance Testing
Acceptance testing is often done by the customer to ensure that the delivered product meets
the requirements and works as the customer expected. It falls under the class of black box
testing.
7. Regression Testing
Regression testing is the testing after modification of a system, component, or a group of
related units to ensure that the modification is working correctly and is not damaging or
imposing other modules to produce unexpected results. It falls under the class of black box
testing.
8. Beta Testing
Beta testing is the testing which is done by end users, a team outside development, or publicly
releasing full pre-version of the product which is known as beta version. The aim of beta testing
is to cover unexpected errors. It falls under the class of black box testing.
45 | P a g e
4.2 TEST CASES:

Project/System/Component : Login
Created
by:
saurabh kumar
Test Case ID: T001
Creation Date:
06/11/2014
Feature/Function/Requirements to Test:
Data or Activities Required to Test
Expected Results
Username & Password are valid
Username
Password
Accepted
User Verification
User Verified
Project/System/Component : Login
&
are
Created by:
saurabh kumar
Test Case ID: T002
Creation Date:
06/10/2014
Expected Results
Username & Password are not valid
Username
&
Password are not
Accepted
User Verification
User is not Verified
46 | P a g e
Project/System/Component : user registration
Created by:
saurabh kumar
Test Case ID: T003
Creation Date:
10/10/2014
Expected Results
New user provides all information demanded by the form
User successfully
registered
If left blank any mandatory field
Error
displays
Project/System/Component : registration
Created
by:
saurabh kumar
Test Case ID: T004
Creation Date:
message
15/10/2014
Expected Results
User successfully
registered
Error
displays
message
47 | P a g e
Project/System/Component : hosteler profile
Created
by:
saurabh kumar
Test Case ID: T005
Creation Date:
16/10/2014
Expected Results
Submit
Error
displays
Project/System/Component : payament
Created
by:
saurabh kumar
Test Case ID: T006
Creation Date:
message
17/10/2014
Expected Results
Submit payment
Error
displays
message
SYSTEM DEBUGGING
The goal of testing is to identify errors (bugs) in the program. The process of testing generates
symptoms and a program's failure is a clear symptom of the presence of an error. After getting
a symptom, we began to investigate the cause and the place of that error .After identification
of place, we examine that portion to identify the cause of the problem.
This process is called DEBUGGING.
48 | P a g e
DEBUGGING TECHNIQUES:
PRESSMAN explained the few characteristics of bugs that provide some clues:
1. "The symptom and the cause may be geographically remote. That is the symptom may appear
in one part of a program, while the cause may actually be located in other part. Highly coupled
program structures may complicated this situation.
2. The symptom may disappear (temporarily) when another error is corrected.
3. The symptom may actually be caused by non-errors (e.g. round off inaccuracies).
4. The symptom may be caused by human error that is not easily traced.
5. The symptom may be result of timing problems rather than processing problems.
6. It may be difficult to accurately reproduce input conditions (eg. a real time application in
which input ordering is indeterminate).
7. The symptom may be intermittent. This is particularly common in embedded system that
couple hardware with the software inextricably.
8. The symptom may be due to causes that are distributed across a number of task running on
different processors.
49 | P a g e
CHAPTER 5
MAINTENANCE
5.1 IMPLEMENTATION OF SOFTWARE

Software maintenance is the activity of modifying the software product after delivery in order
to correct faults, improve performance and to improve other attributes. Software maintenance
is a vital element of SDLC. Software maintenance is a very broad activity that includes error
correction, deletion of obsolete capabilities and optimization.
The following steps are to be followed to implement the software:1.
2.
3.
4.
5.
6.
Copy the HOSTEL MANAGEMENT PROJECT to the local drive of the machine.
Execute SQL server.
Copy file hm.txt from the project folder to the query analyser and execute.
Create database HM .Use HM
Copy the path of the database and change the path in each and every form of the project.
Execute the project.
5.2 TYPES OF MAINTENANCE

Corrective Maintenance
This refers to the modification initiated by the defects in the software i.e. it fixes the faults in
the software without changing or adding to the software functionality. The purpose corrective
maintenance is to correct or fix the discovered problems in the system.
A defect can result from design error, logic error and coding error. Design error occurs when
changes made to the software are incorrect. Logical errors result from invalid tests etc. Coding
errors are caused by incorrect implementation of detailed logic.
Adaptive Maintenance
It includes modifying the software to match the changes in the changing environment i.e.
it modified to preserve functionality in a changing environment. Adaptive maintenance is
also a modification done after the delivery in order to keep the software product useable in
changing environment.
50 | P a g e
Perfective Maintenance
It means improving processing efficiency or performance or restricting the software to
improve changeability. This may include enhancement of existing system functionality,
computational efficiency etc. It improves software performance, maintainability and can
extend the functionality of the application.
Preventive maintenance
It is done to detect or to correct latent before they become effective faults. This simply
means the prevention of future problems. In this changes are made to the system in order
to prevent further faults and to improve the structure and maintainability of the software.
51 | P a g e
CHAPTER 6
SCOPE OF IMPROVEMENT & CONCLUSION
6.1 Scope of improvement, summary & conclusion
It has been a great pleasure for me to work on this exciting and challenging project.
This project proved good for me as it provided practical knowledge of not only programming
in ASP.NET and vb.NET web based application and no some extent Windows Application and
SQL Server, but also about all handling procedure related with hostel management syatem.
It also provides knowledge about the latest technology used in developing web enabled
application and client server technology that will be great demand in future. This will provide
better opportunities and guidance in future in developing projects independently.
Benefits:
The project is identified by the merits of the system offered to the user. The merits of this
project are as follows:
Its a web-enabled project.
This project offers user to enter the data through simple and interactive forms. This is very
helpful for the client to enter the desired information through so much simplicity.
The user is mainly more concerned about the validity of the data, whatever he is entering.
There are checks on every stages of any new creation, data entry or updating so that the
user cannot enter the invalid data, which can create problems at later date.
Sometimes the user finds in the later stages of using project that he needs to update some
of the information that he entered earlier. There are options for him by which he can update
the records. Moreover there is restriction for his that he cannot change the primary data
field. This keeps the validity of the data to longer extent.
User is provided the option of monitoring the records he entered earlier. He can see the
desired records with the variety of options provided by him.
From every part of the project the user is provided with the links through framing so that
he can go from one option of the project to other as per the requirement. This is bound to
be simple and very friendly as per the user is concerned. That is, we can sat that the project
is user friendly which is one of the primary concerns of any good project.
52 | P a g e
Data storage and retrieval will become faster and easier to maintain because data is stored
in a systematic manner and in a single database.
Decision making process would be greatly enhanced because of faster processing of

information since data collection from information available on computer takes much less
time than manual system.
Allocating of sample results becomes much faster because at a time the user can see the
records of last years.
Easier and faster data transfer through latest technology associated with the computer and
communication.
Through these features it will increase the efficiency, accuracy and transparency,
6.2 Limitation:
The size of the database increases day-by-day, increasing the load on the database back up and
data maintenance activity.
Training for simplest computer operations is necessary for the
users working on the
system.
Future Scope
This System being web-based and an undertaking of Cyber Security Division, needs to
be thoroughly tested to find out any security gaps.
A console for the data centre may be made available to allow the personnel to monitor
on the sites which were cleared for hosting during a particular period.
Moreover, it is just a beginning; further the system may be utilized in various other
types of auditing operation viz. Network auditing or similar process/workflow based
applications...
Future Possibilities
Retail Store Manager is a well-designed software .Considering needs of different entrepreneurs
its working team organized its functionalities, so that new updating can be made without
altering the current structure of the software .It is also possible to do Maintenance with least
53 | P a g e
possible efforts. There are different needs of each entrepreneur and no one software can
possibly fulfil them at their prices i.e. each functionality cost build software cost. Keeping all
this in mind Retail Store manager is build. Functionalities that can be added up in future are:
Network connectivity for online business

To connect various retail outlets with each other through Internet or private network.
Establishment of email system of its own.
Exchange of documents, business info etc. using implementation of secured network
Adding up functionalities for Wholesale enterprises will be easier by utilizing the
current retail functionalities (like stock management).
Accountancy can be done using organized database of Retail Store Manager in Future.
Functionalities for documents and various reports generation can be updated according
to user desires.
Bar Code Reader can be implemented.
6.3. CONCLUSION
This project is successfully implemented in Visual Basic 2010 and SQL Server 2008 and was
seen all respect of specification. Any Number of records can be maintained according to given
schedule Of HOSTEL MANAGEMENT.
Till now it is successfully working. As far as the modification in this project is considered, this
facility is built in this project. You can become user and take advantage of special offers.
It is granted that this project will work as it is at present and also in the future as all specification
are along the time and frame Of the department. Also this project can be successfully
implemented in any of hotel management system for online.
54 | P a g e
BIBLIOGRAPHY
BOOKS:
1. Charles Hampfed (2000) Visual Basic University of
Toronto
2. Herbert Schildt (2000) Visual Basic 6.0 Tata McGraw Hill
3. John Zukowski (2000) Visual Basic 6.0 BPB Publications
4. Jamie Jaworsky Visual Basic 6.0Techmedia
5. Stefen Denninger Visual Basic 6.0Authors Press
ONLINE REFERENCE:
www.w3schools.com
www.theserverside.com
www.visual.com
55 | P a g e

Abbi Project

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Abbi Project

Uploaded by

Copyright:

Available Formats

CHAPTER -1

This project is intended to serve as a guide to the software developed on

1.2 DESCRIPTION OF THE PROJECT:

OBJECTIVE OF THE PROJECT

To create an atmosphere of harmony and cooperation amongst the students.

SCOPE OF THE PROJECT

1.3 SOFTWARE REQUIREMENT SPECIFICATION

Definitions, Acronyms and Abbreviations

ABHISHEK RATHORE 03215202012

EFFICIENCY: I tried to involve accuracy, timeliness and comprehensiveness of the system

2.2 FEASIBILITY STUDY

ABHISHEK RATHORE 03215202012

Assessment of proposed solution

The proposed system will reduce the

COST BENEFIT ANALYSIS

It looks at the financial aspects of the

is always included by both

ABHISHEK RATHORE 03215202012

Intangible cost includes the efforts in

Cost Benefit Analysis is the weighing

Intangible benefits includes ease of

2.3 HARDWARE AND SOFTWARE REQUIREMENTS:

Common language runtime engine:

Base class library:

ABHISHEK RATHORE 03215202012

Reason for using vb.net

ABHISHEK RATHORE 03215202012

Namespaces: The components of assemblies, namespaces primarily organize the objects

To explain COM properties for classes, interfaces, and methods

To specify security requirements of methods

To specify features required to enforce security

Multithreading: Enables your applications to handle multiple tasks simultaneously.

Sql server tables

ABHISHEK RATHORE 03215202012

Features of sql server (rdbms)

ABHISHEK RATHORE 03215202012

Enterprise with data sharing

Distributed data sharing

ABHISHEK RATHORE 03215202012

Sophisticated concurrency control

2.4 Tools used

ABHISHEK RATHORE 03215202012

Integerated development environment

Project explorer window

ABHISHEK RATHORE 03215202012

Code editor window

Form layout window

Immediate locals and watch windows

2.5 GANTT CHART

ABHISHEK RATHORE 03215202012

2.6 PROTOTYPE MODEL

Advantages of Prototype model:

Users are actively involved in the development

Disadvantages of Prototype model:

Leads to implementing and then repairing way of building systems.

ABHISHEK RATHORE 03215202012

When to use Prototype model:

ABHISHEK RATHORE 03215202012

3.1 DATA DICTIONARY

ABHISHEK RATHORE 03215202012

ABHISHEK RATHORE 03215202012

3.2 PHYSICAL DESIGN

3.2.1 DATA FLOW DIAGRAM (DFDS)

ABHISHEK RATHORE 03215202012