PROJECT REPORT

ON
“GROUPFUND QUEUE MANAGEMENT ”

By

Mr. KARUN MANN

Mr. SUMEET MAHAJAN

BACHELOR OF COMPUTER APPLICATIONS

YEAR-III

ROLL NO.

ROLL NO.
Under Guidance
OF
Lect. SHIVANI KOUL

Submitted to

SACRED HEART COLLEGE OF MANAGEMENT

AND TECHNOLOGY, PALOURA, JAMMU
Affiliated To
UNIVERSITY OF JAMMU

1
 INDEX
TOPIC

INTRODUCTION

ABOUT COLLEGE 5

ABOUT PROJECT 5-6

Technical Specification 7-8

ABOUT TECHNOLOGIES USED 8-10

About .Net Technology 8-10

Origin of .Net Technology 10-11

About the .Net Framework 11

Various Components of .Net Framework 12

.Net Architecture 13-14

Major Components of .Net Framework 15

.Net Means For Developers 16-18

Benefits Of .Net 20-21

Web Server Role 19-20

HTTP Role 22-23

HTTP Method description 23

What AreWeb Applications 24

How Web Application Works 24 18

ASP.Net Web Application Architecture 25 19-20

Client /Server Interaction in a web application 26

2
What ASP.Net Provides 27-31

Programming Model In Asp.Net 32

Web Form Components 33-36

SOFTWARE ENGINEERING PROCESS 36-37

DEFINING THE FRAMEWORK 37-38

SYSTEM DEVELOPMENT LIFE CYCLE 39-42

TYPE OF SOFTWARE MAINTENANCE 42-43

SYSTEM DESIGN

DESIGN Concepts 44

Design Objectives 44-45

DESIGN MODULES 45-46

SYSTEM DESIGN 47

ARCHITECTURAL DESIGN 47-48

ENTITY RELATIONSHIP DIAGRAM 48-50

SYSTEM ANALYSIS

PROBLEM DEFINITION 51-52

PROPOSED SYSTEM 52-53

ADVANTAGES OF THE PROPOSED SYSTEM 53-54

CONCLUSION 55

3
SIGNIFICANCE OF PROJECT 55-56

REQUIREMENT ANALYSIS 56

PROBLEM RECOGNITION 57
EVALUATION AND SYNTHESIS 57-62

SOFTWARE ENGINEERING PARADIGM APPLIED 63

SYSTEM DESIGN 64-73

ENTITY RELATIONSHIP 74

DATA FLOW DIAGRAMS 75-81

Screen Shots 82-99

Coding 100-116

COMMENTS AND DESCRIPTIONS 117

ERROR HANDLING 117

VALIDATION CHECKS 117

Sql Server2005 As A Relational Database Management System 118-120

Testing 121-124

GANTT CHART 125

FUTURE SCOPE 125

FUTURE ENHANCEMENT 125

Appendix-A 126-127

Appendix-B 128

Glossary 129

4
 INTRODUCTION
About College:-
Sacred Heart College, Paloura Jammu got established in 2003.
This college is centrally located with a distance of 5 km from
the University of Jammu and 3 Km from the heart of Jammu
city i.e. Jewel Chowk. College is constructed on 12 canals of
land and having 42000 sq.ft constructed area .The college has
been hub of academic, social and intellectual activities ever
since its inception.

The college has a beautiful and pollution free campus having

the unique facility of guest house for the parents/ guardians of
the students belonging to far of places.

There is proper arrangement in the Library to use the Library

facilities by going through different newspaper/ journals/
Books displayed properly.

About Project:-
Today the world is very much dominated by the Information
Technology. Every organization whether big or small is
heading towards globalization. To sustain in the present era of

5
competition every field has been revolutionized by the
introduction of computers.

Presently every system involving the transactions related to

money and goods are being performed through the computer
that brings accuracy in the purpose. GroupFund Bank
consume less time towards work.

This project aims at automating the work of the GroupFund Bank.

The various activities like there is administrator who can change the
settings & design of the website. The Bank officer can handle the
requirements of the customer inside the network through our website
& Customer can send their requirements & the services they need
inside network through our website.

My Project “GroupFund Bank” will help the customer’s for not to

stand in the queue, they can get their services through online & there
is also less manually work to do for bank officer’s & ofcourse through
administrator we can change the settings & design of the website.
maintain the information related to customer’s, services through
computer which will save their time as well as their labour. They can
easily register customer’s, can handle their requirements and get the
information updated automatically.

Thus in short my project will be very helpful to automate the

work of the GroupFund Bank and reduce their workload
manifolds.

6
TECHNICAL SPECIFICATIONS
HARDWARE ENVIRONMENT

PC with the following Configuration

Processor - Pentium-III or Higher

RAM - 256 DDR 2 RAM

HARD DISK - 80 GB

FDD - 1.44MB

SOFTWARE ENVIRONMENT

Operating System - Microsoft Windows XP.

7
Backend - Microsoft SQL Server

Frontend - ASP.NET

Case Tool - Say Microsoft Word 2003, Ms Front

Page

ABOUT TECHNOLOGIES USED

ASP.NET

Microsoft.net is a set of software technologies for connecting

information, people, system, and devices. This new generation of
technology is based on web services small building-block applications
that can connect to each other as well as to other, large applications
over the internet. .net id the Microsoft solution for web services, the
next generation of software that connects our world of information,
devices, and people in a unified, personalized way.

.NET technology enables the creation and use of xml-based

applications, processes, and website as services that share and
combine information and functionality with each other by design, on
any platform. .net is a comprehensive family of products, built on

8
industry and internet standards, that provide for each aspect of
developing (tools), managing (servers), using (building block services
and smart clients) and experiencing (rich user experiences) web
services. .net will become part of the Microsoft applications, tools,
and servers you already use today-as well as new products that extend
web service capabilities to all of your business needs.

Microsoft.net is a set of Microsoft software technologies for

connecting information, people, systems, and devices. It enables a
high level of software integration through the use of web services
small, discrete, building block applications that connect to each other
as well as to other and larger applications over the internet.

The pc revolution launched in a world where every computer, whether

a pc or a mainframe, was an isolated island of information. Then, the
commoditization of pc hardware brought about the advent of
networked computers. This shift enabled some sharing of data within
an organization, essentially increasing the size of the islands but doing
little to connect them to each other. Information exchanges in this
new computing environment occur along many different avenues and
go on many different directions to provide the user with the
information required, regardless of its location or what kind of
hardware it resides on. The integration of systems is the guiding
principle – not an afterthought of distributed computing. Integration
9
delivers compelling benefits including faster, easier exchange of data
within and between organizations, and more opportunities for
businesses to connect with consumers.

Origin of .Net Technology

1. Ole Technology

Object linking and embedding technology was developed by

Microsoft in the early 1990 to enable easy interprocess
communications. To embed documents from one application into
another application. This enabled users to develop applications which
required inter- operability between various products such as MS Word
and MS Excel.

2. Com Technology

Microsoft introduced component-based model for developing soft

wares programs. In the components –based approaching a program is
broken into a number of independent components where each one
offers a particular service. It reduces the overall complexity of
software. Enables distributed developments across multiple
organization or departments and Enhances software maintainability

3. Dot Net Technology

10
 .NET technology is a third-generation component model. This
provides a new level of inter-operability compared to COM
technology. COM provides a standard binary mechanism for inter-
module communication .this mechanism is replaced by an
intermediate language called Microsoft Intermediate language (MSIL)
or simply IL.

The .Net Framework

The .NET framework is the foundation for .NET development

technologies. It is a Multilanguage development and execution
environment that makes it easy to build, deploy and run Web services,
standard Web applications. Framework enables the integration of
existing IT investments with new applications and services, and gives
developers and organizations the ability to solve the challenges of
deploying and operating Internet-scale applications and services, and
gives developers and organizations the ability to solve the challenges
of deploying and operating Internet-scale applications

11
Various components of the visual studio .net

12
Dot Net Architecture

There are around 27 different languages, which can be the probable

inputs to the .NET framework at the common language specification
layer. Once the specifications are complied, the process of further
delegation comes to light.

 The object built and written, pass through the stage of the
services layer. This enables the same language to arm their
objects with the services.
 The next step is to move further to collect the data and request
the class libraries for execution from the dependency layer.
 The final launch of the program is done with the help of base
layer comprising common language runtime.
 This the output is Visual Studio.NET

13
Compilation and Execution of a .Net Application

14
 The two major components of the .net framework include:

1. The common language runtime, which is the execution engine

for .net framework-based applications. Its functions include
code management (loading and executing code). Managing
memory for applications and objects, enforcing security rules
regarding what resources may be accessed by the code, and
interoperation between .net framework-based code and pre-
existing com objects.

2. Class libraries, which provides functionality for task such as

user interface design, threading, security management, network
communications, and so on. The three most significant groups
of classes are ado.net for data manipulation, asp.net for building
web services, and windows forms for building windows-based
smart client applications.
These components of the .net framework were
designed from inception to facilitate the inclusion of a
broad, highly flexible range of security options that can be
implemented y developers, administrators, and users. At a
high level, the security features of the .net framework
include:

15
.Net Means For Developers

Through the use of Microsoft Visual Studio .NET and the Microsoft
.NET framework, Microsoft provides developers with a full set of
development tools to quickly and easily create state-of-the-art
applications and Web services.

 Microsoft .NET, through Visual Studio and the .NET

Framework, will enable more rapid development of software
applications and services.
 The .NET framework and Visual Studio .NET will provide
greater reliability for applications and Web services.
 The use of Web services will allow applications and services
created with Microsoft .NET-connected software to integrate
more easily and efficiently.

Faster Development

Through the use of the common language runtime, a part of the

.NET Framework, developers can create Web services using any
modern programming language, greatly increasing the pool of
available developer resources as well as allowing developers the
freedom to use the programming language most suited to solve the
problem at hand.

16
  Visual studio .NET largely automates the transformation of
an application in to a Web service, decreasing the time and
effort necessary to quickly create and deploy solutions.
 .NET building block services, provides core capabilities
needed by many applications—without requiring additional
coding.

Greater Reliability

 The common language runtime provides for a managed

execution environment eliminating memory leaks, access
violation, and versioning problems.
 The .NET Framework enforces type safety, explicit code
sharing, and application isolation, guaranteeing that no Web
service can affect or illegally call another.
Means for Business

With .NET –connected software and services, businesses can

realize improvements in the time and cost associated with developing
and maintaining their business applications, as well as benefiting from
empowering employees with the ability to act on vital information
anywhere, from any smart device.

 .NET will deliver best of breed integration for businesses.

17
  Exposing Web services increases potential reach and
exposure, creating new business opportunities.
.NET promises substantial savings in development costs, as well as
creating new revenue streams, through the use of Web services

Rapid development

Microsoft Visual Studio .NET and the .NET Framework

empower developers to quickly and easily create cutting-edge Web
services and applications, building on their existing skills sets.
Through Multilanguage support, developers are freed to use the
appropriate language in building Web services.

Benefits of the Dot Net Approach

1. Simple and faster systems development.

2. Rich object model enhanced built in functionality.

3. Many different ways to communicate with the outside world.

4. Integration of different languages into one platform.

5. Easy deployment and execution.

6. Wide range of scalability.

18
7. Interoperability with existing applications.

8. Simple and easy to build sophisticated development tools.

9. Fewer bugs.

10. Potentially better performance.

It’s important to get an understanding of the roles of the Web server,

Web browser, and HTTP before starting your Web development. The
typical communication process can be generalized into the following
steps:

1. The Web browser initiates a request for a Web server resource.

2. HTTP is used to send the GET request to the Web server.

3. The Web server processes the request.

4. The Web server sends a response to the Web browser. HTTP

protocol is used to send the HTTP response to the Web browser.

5. The Web browser processes the response, displaying the Web page.

19
6. The user enters data and performs an action, such as clicking a
Submit button that causes the data to be sent back to the Web server.

7. HTTP is used to POST the data back to the server.

8. The Web server processes the data.

9. The Web server sends the response back to the Web browser.

10. HTTP is used to send the HTTP response to the Web browser.

11. The Web browser processes the response, displaying the Web
page.

THE WEB SERVER’S ROLE

Let’s start with the Web server. The original Web servers were
responsible for receiving and handling requests from the browsers via
HTTP. Each Web server handled the request and sent a response back
to the Web browser.

After that, the Web server closed the connection and released all
resources that were involved in the request. All resources were
released because the Web server needed to be able to handle
thousands of requests per minute, and the original Web pages were
20
simple, static HTML pages. The Web environment was considered to
be “stateless” because no data was held at the Web server between
Web browser requests, and because the connection was closed after
the response was sent. Web Browser Web Server GET Default.html
Display Page 1. Process request 2. Send response and close the
connection Client initiates communications with page request Server

Today’s Web servers deliver services that go far beyond the original
Web servers. In addition to serving static HTML files, the Web
servers can also handle requests for pages that contain code that will
execute at the server; the Web servers will respond with the results of
code execution, as shown in Figure 1-2. Web servers also have the
ability to store data across Web page requests, which means that Web
pages can be connected to form Web applications. Because many
Web sites are set up as Web applications containing many Web pages,
the idea of a Web server delivering a single page to the Web browser
and closing the connection is rather outdated. Web servers now
implement “keep alive” features for connections that make the Web
servers keep the connections to the Web browsers open for a period of
time with anticipation of additional page requests from a Web
browser.

21
Understanding Hypertext Transfer Protocol’s Role

HTTP is a text-based communication protocol that is used to request

Web pages from the Web server and send responses back to the Web
browser. HTTP messages are typically sent between the Web server
and Web browser using port 80, or, when using secure HTTP
(HTTPS), port 443.

When a Web page is requested, a textual command like the following

is sent to the Web server:

GET /default.aspx HTTP/1.1 Host: www.northwindtraders.com

Notice that the first line contains the method, also known as a verb or
a command, called GET, and is followed by the Uniform Resource
Locator (URL) of the Web page to be retrieved, which is followed by
an indicator of the HTTP version to be used. The method indicates
what action is to be performed by the Web server using the URL that
follows the method. Table 1-1 contains a list of some of the common
HTTP methods with a description of their uses. Note that, if
Distributed Authoring and Versioning (DAV) is enabled on the Web
site, many more verbs will be available, such as LOCK and
UNLOCK.

22
The second line identifies the name of the host that may be used by
the Web server if the Web server is hosting more than one Web site.
This process is known as using host headers to identify the Web site
that will handle the request(s).

HTTP METHOD DESCRIPTION

OPTIONS Used by client applications to request a lists of all

supported verbs. Checks to see if a server allows a particular verb
before wasting network bandwidth trying to send an unsupported
request.

GET Gets a URL from the server. A GET request for a specific URL,
say, /test.htm, retrieves the test.htm file. Data retrieved using this verb
is typically cached by the browser. GET also works with collections,
such as those in directories that contain collections of files. If you
request a directory, the server can be configured to return a default
file, such as index.html, that may be representative of the directory.

TECHNOLOGY USED: ASP.NET

The Project is developed using ASP.NET. The latest Web

Application Development Technology from Microsoft.
23
What are Web Applications?

These applications provide content from a server to client

machines over the Internet. Users view the Web application
through a Web browser.

HOW WEB APPLICATIONS WORKS?

Web applications use client/server architecture. The Web

application resides on a server and responds to requests from
multiple clients over the Internet, as shown in Figure.

24
 ASP.NET Web application architecture

On the client side, the Web application is hosted by a browser. The

application’s user interface takes the form of Hypertext Markup
Language (HTML) pages that are interpreted and displayed by the
client’s browser.

On the server side, the Web application runs under Microsoft

Internet Information Services (IIS). IIS manages the application,
passes requests from clients to the application, and returns the
application’s responses to the client. These requests and responses
are passed across the Internet using Hypertext Transport Protocol
(HTTP). A protocol is a set of rules that describe how two or more
items communicate over a medium, such as the Internet.
25
 Client/server interaction in a Web application

The executable portion of the Web application enables us to do

many things that you can’t do with a static Web site, such as:

 Collect information from the user and store that information

on the server
 Perform tasks for the user such as placing an order for a
product, performing complex calculations, or retrieving
information from a database
 Identify a specific user and present an interface that is
customized for that user
 Present content that is highly volatile, such as inventory,
pending order, and shipment information

This is only a partial list. Basically, you can do anything with a

Web application that you can imagine doing with any client/server
application. What makes a Web application special is that the
client/server interaction takes place over the Internet.

26
What ASP.NET Provides

ASP.NET is the platform that we use to create Web applications

and Web services that run under IIS. ASP.NET is not the only way
to create a Web application. Other technologies, notably the CGI,
also enable you to create Web applications. What makes ASP.NET
special is how tightly it is integrated with the Microsoft server,
programming, data access, and security tools.ASP.NET provides a
high level of consistency across Web application development.

1. Visual Studio .NET Web development tools.

These include visual tools for designing Web pages and

application templates, project management, and deployment tools
for Web applications.

2. The System Web namespaces.

These are part of the .NET Framework and include the

programming classes that deal with Web-specific items such as
HTTP requests and responses, browsers, and e-mail.

3. Server and HTML controls.

These are the user-interface components that you use to gather

information from and provide responses to users.

In addition to the preceding components, ASP.NET also uses

the following, more general programming components and

27
 Windows tools. These items aren’t part of ASP.NET.
However, they are key to ASP.NET programming.

 Microsoft Internet Information Services (IIS).

As mentioned in the previous section, IIS hosts Web

applications on the Windows server.

 The Microsoft Visual Basic .NET, Microsoft Visual C#, and

Microsoft Visual J# programming languages.

These three languages have integrated support in Visual

Studio .NET for creating Web applications.

 The .NET Framework.

This is the complete set of Windows programming classes,

including the ASP.NET classes as well as classes for other
programming tasks such as file access, data type conversion,
array and string manipulation, and so on.

 Microsoft ADO.NET database classes and tools.

These components provide access to Microsoft SQL Server

and ODBC databases. Data access is often a key component
of Web applications.

 Microsoft Application Center Test (ACT).

28
 This Visual Studio .NET component provides an automated
way to stress-test Web applications.

ASP.NET is the most complete platform for developing Web

applications that run under IIS. However, it is important to
remember that ASP.NET is not platform-independent. Because it
is hosted under IIS, ASP.NET must run on Windows servers. To
create Web applications that run on non-Windows/IIS servers,
such as Linux/Apache, you must use other tools—generally CGI.

Features of an Asp.net

1. Compiled code- code written in asp.net is compiled and not

interpreted .this makes asp.net applications faster to execute than
other server side scripts that are interpreted, such as scripts written in
a previous version of asp.

2. Enriched tool support: the ASP dot net framework is provided

with a rich toolbox and designer inVS.NET IDE.

3. Power and flexibility: asp.net applications are based on common

language runtime therefore the power and flexibility of the .net
platform is available to ASP .net application developers. Asp.net
applications enable you to ensure that the class library, messaging and

29
data access solutions are seamlessly accessible over the web. Asp. Net
is also language independent therefore, you can choose any. Net
language to develop your application.

4. Simplicity-ASP. Net enables you to build user interfaces that

Separate application logic from presentation content in addition, CLR

simplifies application development by using managed code services
such as automatic reference counting and garbage collection therefore
ASP dot net makes it easy to perform common tasks ranging from
form submission and client authentication to site configuration and
deployment.

5. Manageability- ASP dot net enables you to manage web

application by storing the configuration information in an xml file.
You can open the xml file in the visual studio .net.

6. Scalability- ASP dot net has been designed with scalability in

mind. It has features that help improve performance in multiprocessor
environment.

7. Security- ASP dot net provides a number of options for

implementing security and restricting user access to a web
application. All these options are configured within the configuration
file.

30
ASP.NET delivers the following other advantages to Web
application developers:

 Executable portions of a Web application compiled so they

execute more quickly than interpreted scripts
 On-the-fly updates of deployed Web applications without
restarting the server
 Access to the .NET Framework, which simplifies many
aspects of Windows programming
 Use of the widely known Visual Basic programming
language, which has been enhanced to fully support object-
oriented programming
 Introduction of the new Visual C# programming language,
which provides a type-safe, object-oriented version of the C
programming language
 Automatic state management for controls on a Web page
(called server controls) so that they behave much more like
Windows controls
 The ability to create new, customized server controls from
existing controls

31
PROGRAMMING MODEL IN ASP.NET

1. Web forms enable you to create user interface for web applications,
you. You use server controls to design the user interfaces of web
applications and then write code, which will be executed at the server-
side, to handle events triggered by these controls.

2. Web services enable you to remotely access certain functionality at

the server side. These services enable the exchange of data in a client-
to-server or a server-to server environment over the web by using
simple object Access Protocol.

3. In ASP.NET, web forms consist of a user interface and application

logic that is applied to the components of user interfaces.

4. A user interface consists of static HTML or XML elements; and

ASP.NET server controls. When you create a web application, HTML
or XML elements and server controls are saved in a file with an .aspx
extension. This file is called a page file.

5. Application logic consists of code that is applied to the user

interface elements of a web Form page. We can use any of the .NET
programming language, such as Visual Basic .NET or C#, to write the
logic for a web page.

32
WEB FORM COMPONENTS

Web forms can contain several different types of components, as

summarized in Table .we can use the server and HTML controls to
create the user interface on a Web form. The data controls and
system components appear on the Web form only at design time to
provide a visual way for you to set their properties and handle
their events. At run-time, data controls and system components do
not have a visual representation.

Components on a Web Form

Component Examples Description

33
Components on a Web Form

Component Examples Description

These controls
respond to user
events by running
event procedures on
the server. Server
controls have built-in
TextBox,Label,Button,
Server features for saving
ListBox,DropDownList,
controls data that the user
DataGrid
enters between page
displays. You use
server controls to
define the user
interface of a Web
form.
These represent the
standard visual elements
provided in HTML.
HTML Text Area, Table, Image, HTML controls are
controls Submit Button, Reset Button useful when the more
complete feature set
provided by server
controls is not needed.

34
 Components on a Web Form

Component Examples Description

Data controls provide a
SqlConnection, way to connect to,
Data SqlCommand, perform commands on,
controls OleDbConnection, and retrieve data from
OleDbCommand, Dataset SQL and OLE databases
and XML data files.

These components
provide access to
System FileSystemWatcher,Event
various system-level
components Log, MessageQueue
events that occur on the
server.

. Parts of an ASP.NET Web Application

Part Types of files Description

Content Web forms, Content files determine the

35
 . Parts of an ASP.NET Web Application

Part Types of files Description

HTML, appearance of a Web application.
images, audio, They can contain static text and
video, other images as well as elements that are
data composed on the fly by the program
logic (as in the case of a database
query).
The program logic determines how
The program logic determines how
the application responds to user
Executable actions. ASP.NET Web applications
Program
files, scripts have a dynamic-link library (DLL)
file that runs on the server, and they
logic
can also include scripts that run on
the client machine.

SOFTWARE ENGINEERING PROCESS

The attribute of web based system and application have a profound

influence on the web engineering process that is chosen. If immediacy
and continuous evolution are primary attribute of a web engineering, a
web engineering team might choose an agile process model that
produces web applications releases in the rapid fire sequence. On the

36
other hand, if the web application is to be developed over a long time
period) e.g., a major (e-commerce application), an incremental
process model can be chosen.

The network intensive nature of the application in this domain

suggests a population of the user that is diverse (thereby making
special demands on requirements elicitation and modeling) and an
application architecture that can be highly specialized. Because web
applications are often content-driven with an emphasis on aesthetic, it
is likely that parallel development activities will be scheduled within
the web applications process and involve a team of both technical and
non technical people (e.g., copywriter, graphic designer).

DEFINING THE FRAMEWORK

Any one of the agile process models (e.g., extreme programming,

adaptive software development, SCRUM)

To be effective, any engineering process must be adaptive. That is,

the organization of the project team, the modes of communication
among team members, the engineering activities and tasks to be
37
performed, the information that is collected and created, and the
methods used to produce a high quality product must all be adapted
tom the people doing the work, the project time line and constraint,
and the problem to be solved. Before we define a process framework
for web engineering, we must recognize that:

1. Web apps are often delivered incrementally. That is, frame work
activities will occur repeatedly as each increment is engineered
and delivered.

2. Changes will occur frequently. These changes may occur as a

result of the evaluation of a delivered increment or as a
consequence of changing business conditions.

3. Timelines are short. This mitigates against the creation and

review of voluminous engineering documentation, but it does
not preclude the simple reality that critical analysis, design,
and testing must be recorded in some manner.

38
SYSTEM DEVELOPMENT LIFE CYCLE

The basic idea of software development life cycle (SDLC) is that

there is a well defined process by which an application is conceived,
developed and implemented. The phases in the SDLC provide a basis
for the management and control because they define segments of the
flow of work, which can be identified for the managerial purpose and
specifies the documents or other deliveries to be produced in each
phase. System Development revolves around a life cycle that begins
with the recognition of user needs. In order to develop good software,
it has to go through different phases. There are various phases of the
System Development Life Cycle for the project and different models
for software development, which depict these phases. We decided to
use waterfall model, the oldest and the most widely used paradigm for
software engineering. The Various relevant stages of the System Life
Cycle of this Application Tool are depicted in the following flow
diagram.

39
Understanding Hypertext Transfer Protocol’s Role

SYSTEM ANAYLSIS

SYSTEM DESIGN

CODING

SYSTEM TESTING

SYSTEM IMPLEMENTATION

SYSTEM MAINTENANCE

Let us have a look on each of the above activities:

1. System Analysis

System Analysis is the process of diagnosing situations, done with a

defiant aim, with the boundaries of the system kept in mind to
produce a report based on the findings. Analysis is fact-finding
techniques where problem definition, objective, system requirement
specifications, feasibility analysis and cost benefit analysis are carried
out. The requirement of both the system and the software are
document and reviewed with the user.

2. System Design
System Design is actually a multistep process that focuses on four
distinct attributes of a program: data structures, software architecture,
interface representations, and procedural (algorithmic) detail. System
40
design is concerned with identifying the software components
(Functions, data streams, and data stores), specifying relationships
among components, specifying software structure, maintaining a
record of design decisions and providing a blueprint for the
implementation phase.

3. Coding

Coding step performs the translations of the design representations

into an artificial language resulting in instructions that can be
executed by the computer. It thus involves developing computer
programs that meet the system specifications of design stage.

4. System Testing
System testing process focuses on the logical internals of the
software, ensuring that all statements have been tested on the
functional externals, that is conducting tests using various tests data to
uncover errors that defined input will produce actual results that agree
with required results.

5. System Implementation

System Implementation is a process that includes all those activities

that take place to convert an old system to a new system. The new
system may be totally new system replacing the existing system or it
may be major modification to the existing system. Coding performs
the translations of the design representations into an artificial
language resulting in instructions that can be executed by the
computer. It thus involves developing computer programs that meet
the system design specifications. System implementation involves the
translation of the design specifications into source code and
debugging, documentation and unit testing of the source code.

41
6. System Maintenance
Maintenance is modification of a software product after delivery to
correct faults to improve performance or to adopt the product to a new
operating environment. Software maintenance can not be avoided due
to ware & tear caused by users. Some of the reasons for maintaining
the software are

1. Over a period of time, software original requirements may

change.

2. Errors undetected during software development may be found

during user & require correction.

3. With time new technologies are introduced such as hardware,

operating system etc. The software therefore must be modified
to adapt new operating environment.

TYPE OF SOFTWARE MAINTENANCE

 Corrective Maintenance: This type of maintenance is also called

bug fixing that may observed while the system is in use i.e correct
reported errors.

42
 Adaptive Maintenance: This type of maintenance is concern with
the modification required due to change in environment. (i.e
external changes like use in different hardware platform or use
different O.S.

 Perfective Maintenance: Perfective maintenance refers to

enhancement to the software product there by adding or support to
new features or when user change different functionalities of the
system according to customer demands making the product better,
faster with more function or reports.

 Preventive Maintenance: This type of maintenance is done to

anticipate future problems and to improve the maintainability to
provide a better basis for future enhancement or business changes.

43
SYSTEM DESIGN

DESIGN CONCEPTS

The design of an information system produces the detail that state

how a system will meet the requirements identified during system
analysis. System specialists often refer to this stage as Logical
Design, in contrast to the process of development program software,
which is referred to as Physical Design. System Analysis begins
process by identifying the reports and the other outputs the system
will produce. Then the specific on each are pin pointed. Usually,
designers sketch the form or display as they expect it to appear when
the system is complete. This may be done on a paper or computer
display, using one of the automated system tools available. The
system design also describes the data to be input, calculated or stored.
Individual data items and calculation procedures are written in detail.
The procedure tells how to process the data and produce the output.

DESIGN OBJECTIVES

The following goals were kept in mind while designing the system:

44
  To reduce the manual work required to be done in the existing
system.
 To avoid errors inherent in the manual working and hence make
the outputs consistent and correct.
 To improve the management of permanent information of the
Computer center by keeping it in properly structured tables and
to provide facilities to update this information efficiently as
possible.
 To make the system completely menu-driven and hence user
friendly, and hence user friendly, this was necessary so that even
non-programmers could use the system efficiently.
 To make the system completely compatible i.e., it should fit in
the total integrated system.
 To design the system in such a way that reduced future
maintenance and enhancement times and efforts.
 To make the system reliable, understandable and cost effective.

DESIGN MODULES

The software has been designed in a modular manner. There is a

separate module for the every function of this Jobs Portal. These are
then integrated to build an easy to use system.

Here is a brief listing of the various Design Modules of the Software:

45
The candidates seeking job (referred as job seekers now onwards) can
perform following operations:

 Register with the web site

 Post their resume.
 Modify their resume.
 Search for job postings.
 Browse searched job postings.
 Add job posting to their favorites list.
 Add frequently used searches to their favorites list.

The employers can perform following operations:

 Register with the web site.

 Enter profile of their company.
 Post one or more job postings.
 Modify the job postings.
 Search the resume database.
 Browse searched resumes.
 Add resumes to their favorites list.

46
SYSTEM DESIGN

The design stage takes the final specification of the system from
analysis stages and finds the best way of filing them, given the
technical environment and previous decision on required level of
automation.

The system design is carried out in two phases:

i) Architectural Design (High Level Design)

ii) Detailed Design (Low Level Design)

ARCHITECTURAL DESIGN

The high level Design maps the given system to logical data structure.
Architectural design involves identifying the software component,
decoupling and decomposing the system into processing modules and
conceptual data structures and specifying the interconnection among
components. Good notation can clarify the interrelationship and
interactions if interest, while poor notation can complete and interfere
with good design practice. A data flow-oriented approach was used to

47
design the project. This includes Entity Relationship Diagram (ERD)
and Data Flow Diagrams (DFD).

ENTITY RELATIONSHIP DIAGRAM

One of the best design approaches is Entity Relationship Method.

This design approach is widely followed in designing projects
normally known as “ Entity Relationship Diagram (ERD)”.

ERD helps in capturing the business rules governing the data

relationships of the system and is a conventional aid for
communicating with the end users in the conceptual design phase.
ERD consists of:

 Entity – It is the term use to describe any object, place, person,

concept, activity that the enterprise recognizes in the area under
investigation and wishes to collect and store data. It is
diagrammatically represented as boxes.

 Attribute – They are the data elements that are used to describe
the properties that distinguish the entities.

48
 Relationship – It is an association or connection between two or
more entities. They are diagrammatically represented as arrows.

A Unary relationship is a relationship between instances of the

same entity.

A Binary relationship is a relationship between two entities.

A N-ary relationship is a relationship among N entities. It is

defined only when the relationship does have a meaning without
the participation of all the N entities.

 Degree of Relationship – An important aspect of relationship

between two or more entities is the degree of relationship. The
different relationships recognized among various data stores in the
database are:

 One-to-One (1:1)
It is an association between two entities. For example, each
student can have only one Roll No.

 One-to-Many (1:M)
It describes entities that may have one or more entities related
to it. For example, a father may have one or many children.

49
  Many-to-Many (M:M)
It describes entities that may have relationships in both
directions. This relationship can be explained by considering
items sold by Vendors. A vendor can sell many items and
many vendors can sell each item.

ERD representation of the project is given below. It follows Chen’s

convention in which entities are represented as rectangles and
relationships as diamonds.

50
SYSTEM ANALYSIS
PROBLEM DEFINITION

GroupFund witnessed proliferated growth ever since it offered “No

Document Required” loan schemes and higher credit and cash
withdrawal limits on its credit and debit cards. These innovative
campaigns led to its exponential growth. The customer base has
multiplied by 10 times while the number of branches and ATM
centers has increase by 200%

As a result, customer had to wait for a longer time at the branches to

perform their activities. This led to chaos and mismanagement at
times. The senior management discussed the situation. The discussion
revealed that:

 Because of the increased customer base, the service timing has

decreased from 30 minutes per customer to a meager 2 meager 2
minutes per customer.
 Employees feel highly stressed out while dealing with the
increased number of mismanaged customer at the branch.
 Customers get only a few minutes to talk the bank staff after
waiting for a long time.
 Customers get only a few minutes to talk to the bank staff after
waiting for a long time.
51
  Customers often have to return home dissatisfied after waiting
for a long time.
The senior management decided to employ additional staff and
start using a queue management system to manage the high
footfall at its branches.
It should be quick, safe and easy to use. The system is meant
for the end users -the employer and the candidate.

PROPOSED SYSTEM

The features of the envisioned queue management system are:

 An Internet-enable application will be created.

 A central database will store information related to all the
products and services
offered by the bank and the information related to the customer
who visit the branch.
 The queue management system will generate a coupon number
for each customer visitng the bank. The different customer
service desks will cater to the different needs of the customers.
 A central display system will display the coupon number for
each customer service desk.

52
  The system will allow the bank staff to increment the ticket
number after they serve a customer.

ADVANTAGES OF THE PROPOSED SYSTEM

1. Easy to use

The system provides the relevant information by clicking on the

various slinks. The system is designed by keeping in mind the
end users, the employers who are busy with their works, and the
candidates get easily response for our request.

2. Secure
The system is highly secured; the end users are registered users
and also those who are not registered. The registered users have
a username and a password which grants permission to access
the restricted sites also.
3. Quick response

The users are able to make use of the up-to-date information,

which reduced the response time

4. Advanced loan search

53
 Candidates can view the most suitable loans and the customer
could make out the best qualified candidates through advanced
search.

5. Total Solution

The system is a complete solution for the bank employer’s

customer’s & administrator . It provides the facilities for the
customer’s & bank officer’s to do their work fastly.

6. Advanced methods

The advanced methods of GroupFund Bank is that it consumes

very less time. There is no problem for customer’s & bank
officer’s to do their work. Candidates do not wait in a queue for
their account & any services related to bank, Customer’s can
choose their services through computer.

7. Common communication network for the enterprise.

For this all above services internet should be must.

54
CONCLUSION

The task that bank employ’s & customer’s wanted to do can do in

very less time i.e it consumes very less time to perform their work.
Customer’s can get their services of bank without standing in a queue
& for bank officer’s also to handle the customer’s requirements
easily.Ofcourse the administrator who has the power to implement
new services, schemes, design, settings & every thing that is
necessary for the bank. The increasing of customer’s now is not a
burden for the bank employe’s infact it becomes very easy to store
their records of the customer’s.

SIGNIFICANCE OF PROJECT

Internet as it came Changed our Lives Altogether. Now a days we

more ever communicate through internet, buy through Internet and
more ever now bank facilities are also done through Internet only.
The World Wide Web has made significant impact on our lives. A
single mouse-click takes you to far off places.

55
Every Flight with the Internet has been a delightful experience right
from accessing information to enjoying the wonders of brilliant
applications that have been given the Internet their magical touch of
internet their magical touch of inter-activity, mind boggling, zapping
speeds and so more.

It is but obivious that in today’s world almost everybody would use

Internet to get any information.

REQUIREMENT ANALYSIS

Software requirement analysis is a software-engineering task that

bridges the gap between system level software allocation and software
design. For Developing the GroupFund Bank portal in-depth analysis
was done. The analysis was divided into the following three Parts.

 Problem Recognition

 Evaluation and Synthesis

 Specification & Review

56
PROBLEM RECOGNITION

The aim of the poroject was understood and through research was
done on internet to get a deep insight of how the proposed system will
work, we went to different bank portal websites and understood their
working. We recorded what all features will be required when we
build our website like for eg.

We need to keep a database of Jobseekers should be able to register

and post their resume and Employers should be able to register and
search for their requirement online etc. All these features were noted
down so that they could be incorporated in our application.

EVALUATION AND SYNTHESIS

Problem evaluation and solution synthesis was the next major area of
effort. It was in this step that all externally observable data objects,
evaluation of flow and content of information was defined. It was
decided in this phase that how our application will look and work,
what parameters it will take and what it will return.

Specification & Review

The main objective is to improve the quality of software that can be
done by inspection or walkthrough of formal technical reviews. The
main objective is

57
 To uncover errors in function, logfics or implementation.
 Verify software under revies to meet requirement specification.
 Ensure that software has been represented according to
predefined standards.
 Achive software development in uniform manner
 Make project more meaningfull.

Identification of the need:-

The current system of working GROUPFUND BANK is

manual. They face difficulties in managing the information
related to the customers, products, suppliers.

They face difficulty in maintaining the records of the goods

produced and the goods supplied.

Each and all information is recorded manually in the registers

and there is every possibility of losing records by mistake.

Overall the current system of GROUPFUND BANK is very

complex, error prone and time consuming.

Thus there is urgent need for replacing the current manual

working system with the new computerized system.

Preliminary Investigation:-

58
An initial investigation was done to study the working
procedure of the Sales Invoice System, during this investigation
I came to know about the working of the system. Thus during
this preliminary investigation my project was clear for the
preliminary phase of the feasibility study.

I also got initial analysis of some of the records related to the

availability of the goods, order of the required goods,
registration of supplier’s and some manual report formats.

Feasibility Study:-

Technical Feasibility: - The technologies I will use in my project

entitled “GROUFUND BANK” are very much in support of
the proposed system.

The technologies are user friendly and easy to use, more than
this they are secure. Thus overall entire project is technically
feasible. The users will be freed from the paper work and
confusion. In fact the person’s involved are themselves
interested in getting the manual system replaced with the
automated one. The proposed system is user friendly and even
a layman can use it.

Economical feasibility: For the proposed system to work, all that

is needed is to get hardware and software installed. The short-
term costs are over shadowed by the long-term gains. My

59
project cost includes cost of the system study, cost of
development and cost of user training.

Operational feasibility: - The current manual system of the

maintenance of the bank invoice is very problematic and
cumbersome. My project will overcome all those problems. The
managers can be trained easily and in less time for effective
usage of the new system.

Identification of the need:-

The current system of working GROUPFUND BANK is

manual. They face difficulties in managing the information
related to the customers, services, schemes.

They face difficulty in maintaining the records of the customers

& employees .

Each and all information is recorded manually in the registers

and there is every possibility of losing records by mistake.

Overall the current system of GROUPFUND BANK is very

complex, error prone and time consuming.

Thus there is urgent need for replacing the current manual

working system with the new computerized system.

Preliminary Investigation:-

An initial investigation was done to study the working

procedure of the GroupFund Bank, during this investigation I
60
came to know about the working of the system. Thus during
this preliminary investigation my project was clear for the
preliminary phase of the feasibility study.

I also got initial analysis of some of the records related to the

customers, the services the customers need, the customer just
login & check their account,bank officer also handle them
through this software & the administrator who can change the
settings of the website, interface, design & every thing that is
necessary for the Bank & the GroupFund Bank website.

Feasibility Study:-

Technical Feasibility: - The technologies I will use in my project

entitled “GROUPFUND BANK” are very much in support of
the proposed system.

The technologies are user friendly and easy to use, more than
this they are secure. Thus overall entire project is technically
feasible. The users will be freed from the paper work and
confusion. In fact the person’s involved are themselves
interested in getting the manual system replaced with the
automated one. The proposed system is user friendly.

Economical feasibility: For the proposed system to work, all that

is needed is to get hardware and software installed. The short-

61
term costs are over shadowed by the long-term gains. My
project cost includes cost of the system study, cost of
development and cost of user training.

Operational feasibility: - The current manual system of the

maintenance of the GroupFund Bank is very problematic and
cumbersome. My project will overcome all those problems. The
managers can be trained easily and in less time for effective
usage of the new system.

Behavioral Feasibility: “An evaluation of the behavior of the end

users, which may effect the development of the system.” The user
show minimal resistance to change, but they are satisfied with
functionality provided in the proposed system.

Schedule Feasibility: “Evaluates the time taken in the development

of the project”. The system had schedule feasibility.

62
SOFTWARE ENGINEERING PARADIGM APPLIED:

I have used waterfall model for the development of the project. As my

project was not so much complex and also the requirement gathering
here were straightforward and not ambiguous.

So I decided to apply the waterfall model, which is also called the

sequential or linear model.

Waterfall model being earliest, simplest and powerful model for

software development has the following phases.

FEASIBILTY STUDY

REQUIREMENT
DEFINITION

DESIGN
SPECIFICATIONS

CODING AND UNIT

TESTING

INTEGRATION
TESTING

IMPLEMENTATION
AND DELIVERY

MAINTENANCE

63
SYSTEM DESIGN

INTRODUCTION

Software design, the most creative and challenging phase of

System life cycle, follows system analysis. Blueprint of the project
and its implementation is prepared at this stage. Various steps
proceed in this steps are:

 Determination of output to be produced and its format

specification.

 Input, data and master files are designed.

 Details related to justification of the system and an estimation

of impact of the proposed system on the user and the
organization are documented and evaluated by the
management..

Software design methodology changes continually as new methods;

better analysis & broader understanding evolve. Software design is
relatively early stage in its evolution. Therefore, software design
methodology lacks the depth, flexibility, & quantities nature that is
normally associated with more classical engineering design
disciplines. However, techniques for software design do exist, criteria
for design qualities are available & design notation can be applied.
Once software requirements have been analyzed, software design

64
leads to the three technical activities- design, code & testing that are
required to build & verify structure.

Design is the only way that we can accurately translate a

customer's requirement into a finished product or system. Without
design, risk of building an unstable system exists - one that will fail
when small changes are made of one that may be difficult to test.

In the software design there are three distinct types of

activities: External Design, Architectural design & detailed design.
Architectural & Detailed designs are collectively known referred to as
Internal Design. Different steps of software design are shown in
figure5.1 on next page.

SYSTEM DESIGN

System design is a solution, "HOW TO APPROACH" to the

creation of a new system. This important phase is composed of
several steps. It provides the understanding and procedural details
necessary to implement the system. This may be referred as a system
development methodology, which is a vital part of Software
Engineering. There are several methodologies, which can be used for
the development of the system. these are RAD, Waterfall model,
Incremental Model etc.

Design

65
 Output Design Detail System

Documentation

Input Design Cost Justification

and candidate

system design
Design submitted to

management for
File Design
approval

Processing
Design
No
Abandon
Design
Project
accepted
?

Yes

Test Programs

Go to
implementation

Detailed design
66
During this phase the database and the program modules are designed
and detailed user procedure is documented. The interface between the
system user and computer are also defined. Detailed design involves
adaptation of existing code, modification of standard algorithms,
invention of new algorithms, design of data representation. Detailed
Design is strongly influenced by the programming languages used to
implement the system, but it is not concerned with the syntactic
aspect of implementation language.

Detailed design separates the activity of low-level design from

implementation, just as analysis and design activities isolate
consideration of what is desired from the structure that will achieve
the desired result.

Database design

A database is a repository for stored operational data. In database

environment, the common data is available and all communication is
done through this by different users. Instead of each program
managing its own data, data across every application is shared by
authorized personal.

All the general activities of the application are identified in the system
analysis phase. For the list of activities identified the subject area of
application need to be maintained. When the designing starts the
required tables are identified. A detailed description of the tables is

67
given in data dictionary. After identification of tables and the required
data relationship between tables is build, primary keys are identified.

External design

External design of the software involves conceiving, planning &

specifying the externally observable characteristics of a software
product. These characteristics include user displays & report formats,
external data sources & data sinks & the functional characteristics,
performance requirements & high- level process structure for the
product. External design begins during the analysis phase. The
distinction between Requirement definition & external design is not
sharp, but is a gradual shift in emphasis from detailed "what" to high
level "how".

5.2.4 Internal design

Internal design involves conceiving, planning out & specifying the

internal structure & processing details of the software product. The
goals of internal design are to specify internal structure & processing
details to record design decisions & Indicate why certain alternatives
& trade-offs were chose, to elaborate the test plan, & to provide a
blueprint for implementation, testing & maintenance activities. The
work products of internal design include a specification of
architectural structure; the details of algorithms & data structures &
the test plan.

5.2.5 Architectural design :

68
Architectural design involves identifying the software components,
decoupling them & decomposing them in to processing modules &
conceptual data structures & specifying the interconnection among
components. Good notations can clarify the interrelationship &
interactions of interest, while poor notations can complicate &
interfere within good design practice. The notations that shall be used
to describe "Overall Testing" include Entity-Relationship Diagram
(ERD), Context Analysis Diagram followed by Data Flow Diagrams
(DFDs).

Entity Relationship Diagram

One of the best-known design approaches is widely followed in

designing projects normally known as "ENTITY -RELATIONSHIP
DIAGRAMS (ERD)". ERD helps in capturing the business roles
governing the data relationships of the system & is a conventional aid
for communicating with the end users in the conceptual design stage.
ERD consists of:

 Entity: It is the tenn used to describe any object, place, person,

concept, activity that the enterprise recognizes in the area under
investigation & wishes to collect & store data about it. It is
diagrammatically represented as boxes

 Attribute: They are the data elements used to describe the

properties / qualities that istinguish the entities.

69
  Relationship: It is an association or connection between two or
more entities. They are diagrammatically represented as
arrowheads.

 A Unary relationship is a relationship between instances of same

entity.

 A Binary relationship is a relationship between two entities.

 A N-array relationship is a relationship among 'n' entities. It is

defined only when the relationship doesn't have a meaning
without the participation of all the 'n' entities.

Degree of relationship: An important aspect of relationship between

two or more entities is the degree of relationship. The different
relationships recognized among various data stored in the database
are:

One-to-One (1:1): It is an association between two entities. For

example, each customer can have only one Customer Code.

Registration Students

One-to-Many (1:M): It describes entities that may have a one or more

entities related to it. For example, a customer may have purchased
items using different bills.

Students Subjects

70
Many-to-Many (M:M): It describes entities that may have
relationships in both directions. This relationship can be explained by
considering products purchased by customer.
Student Subjects

Context Analysis Diagram: CAD is the top-level dataflow diagram,

which depicts the overview of the entire system. The major external
entities, a single process & the output data stores constitute the CAD.
Though this diagram doesn't depict the system in detail, it represents
the overall inputs, process & output of the entire system at a very high
level.

Input Design

Input design is a process of converting user oriented inputs to a

computerized format." Input design is the basic thing to be considered
in the system design. In this process the input screens are designed
according to the requirement of the user. In VB, forms are created
which serves as the input screens for the data entry .In such an
interface design, the user inputs the data by filling the blanks basis on
the screens. Each entry form has its own command buttons, which
provides users the facility to insert a new record, delete and modify an
existing record. The major approaches to input designs are menu,
formatted form, prompts and Alerts

71
Output Design

This is based on user requirements and the format is designed keeping

view of these necessities. Thus: "The output Design emphasizes on
providing a hard copy of information requested or displaying the
output on a CRT screen in a predefined format."

Forms Design

Computer output is the most important and direct source of

information to the user. Hence, an intelligent and efficient output
design improves the system relationships with the user and helps in
decision-making. A major form of output is the hard copy from the
printer."Forms Design elaborates on the way output is presented and
the layouts available for capturing information." The data available in
any system is vital to that system. So, the data must be provided in the
right form for input and the information produced must be in a format
acceptable to the user.

" A form is a tool with a message: It is a physical carrier of data of

information." A poorly designed form is a poor administrative tool.
The sufficient consideration in form design is a brief, descriptive title
that tells what the form is and what it does. The composition, color
and layouts of all forms are designed for easy reading and more
clarity. Sufficient space has been provided in all forms to avoid

72
complexity and cover crowing of data. Hence FORMS must be
attractive and graphical user interface.

User interface design

Any software product in addition to being efficient and fast in

functionality, should also be user friendly. For designing a good GUI
developer should consider the following principles:

 Clarity

 Visual feedback

 Good response

 Audible feedback

 Traceable Paths

 Control design

Process Design :

The process design gives insight into the way in which the processing
is done in the system. Here, the processing is done through menus and
application is completely event driven. Visual Basics applications are
event driven, which means they waits for an event to occur, an event
that occurs in one module triggers another module.

73
ENTITY RELATIONSHIP DIAGRAM

74
 DATA FLOW DIAGRAMS
DATA FLOW DIAGRAM

A Data Flow diagram (DFD) is a graphical tool used to describe

and analyze the movement of data through a system-manual or
automated including the process, stores of data and delay in the
system. They are central tools and basis from which other components
are developed. It depicts the transformation of data from input to
output through processes and the interaction between processes.

A DFD also known as "bubble chart", thus, has the purpose of

clarifying system requirement and identifying major transformation
that will be programmed in system design. So it is the starting point of
design phase that functionally decomposes the requirement
specification down to lowest level of detail. A DFD consists of
bubbles joined by lines. Transformation of data from input to output
through processes describes logically and independent of physical
components is called logical DFD. Physical DFD shows the actual
implementation and movement of data between people, department
and workstations.

DFD's are excellent mechanism for communicating with

the customers during requirement and are widely used for the
representation of external and top-level internal design specification.
In the latter situation, DFD's are quite valuable for establishing
naming convention and names of system components such as
subsystem, files and data links. DFD shows the flow of data. This

75
diagram helps to understand the basic working of the system. It helps
to make and recognize various parts and their interrelationships.

COMPONENTS OF DFD’s

In a DFD, there are four main components:

 Source or destination of data such as entities that interact with

system, who form the source and recipient of information are
depicted in the form of a closed rectangle.

 Data Flow is a packet of data. It identifies the flow of data in

motion. It is a pipeline through which information flows. It is
depicted in DFD as an arrow mark with the pointer pointing in
the direction of data flow. This connecting symbol is present
between an entity, process and data store. This arrow mark
specifies the sender and receiver.

 Process depicts the procedure, function or module that

transforms input data into outputs. They are depicted as circle or
a bubble with procedure name and a unique number inside the
circle.

 Data Stores are physical areas in the computer's hard disk when
a group of related data is stored in the form of files. They are a
database or data at rest or a temporary repository of data. They

76
 are depicted as an open-ended rectangle. These data stores are
used either for storing data into files or for reference purpose.

CONVENTIONS USED IN DRAWING DFD

Source or Destination

Data Flow

Process

Or

77
 0TH LEVEL (CONTEXTUAL DIAGRAM)

GroupFund
Bank

Bank Administrator
Customer’s
Officer’s

IN GroupFund Bank there is three components i.e administrator, bank officer’s &
customer’s.

1TH LEVEL (CONTEXTUAL DIAGRAM)

Administrator has all these

controls, it can be happen
78 when administrator login.
 Administrator

Create Bank Search account of Delete account Update account

Officer’s of Bank of Bank officer’s
Bank officer’s
account officer’s

79
 2TH LEVEL (CONTEXTUAL DIAGRAM)

Customer Bank Customer

Officer’s

Receive request from the customer send response acc to request of the customer

80
 3TH LEVEL (CONTEXTUAL DIAGRAM)

Send request to bankofficer

Customer
Give response to customer
Bank Officer

81
 SYSTEM SECURITY MEASURES:

On the side of security measures the following steps are taken:

Users can only edit the available information , they cannot

change the information by any means.

Only the administrator has the right to edit the information

and can add customer’s, supplier’s, product details and can
order for the purchase of the goods.

Screen Shots

82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
INTRODUCTION

Design Representation must be translated in to an artificial language that results

in to instruction that can be executed by computer. The coding step performs the
translation of design representation in to an artificial language resulting in
instructions that can be executed by the company. If thus involves programs that
meet the system specification of the design stage. If the design is performed is
detailed manner can be accomplished mechanically.

Complete Project Coding

Login
using System;
using System.Data;
using System.Configuration;
using System.Collections;

100
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;

public partial class Login : System.Web.UI.Page

{
protected void Page_Load(object sender,
EventArgs e)
{

}
protected void Button1_Click(object sender,
EventArgs e)
{
SqlConnection con = new
SqlConnection("Integrated Security=SSPI;Persist
Security Info=False;Initial Catalog=mybank;Data
Source=MY-6180A623FF7B");
con.Open();

SqlCommand cm = new SqlCommand("select

* from Login_bank", con);
SqlDataReader dr = cm.ExecuteReader();
string s =
DropDownList1.SelectedValue.ToString();

switch (s)
{
case "Admin":
{
while (dr.Read())
{

101
 if
((TextBox1.Text.Equals(dr.GetString(0).ToString
())) &&
((TextBox2.Text.Equals(dr.GetString(1).ToString
()))) && (s == dr.GetString(2)))
{

Response.Redirect("~\\Administrator\\default.as
px");

else
{

Label1.Text="invalid user name and password";

}

}
break;
}
case "Customer":
{

while (dr.Read())
{
if
((TextBox1.Text.Equals(dr.GetString(0).ToString
())) &&
((TextBox2.Text.Equals(dr.GetString(1).ToString
()))) && (s == dr.GetString(2)))
{

Response.Redirect("~\\Customer\\Ticket.aspx");

else
102
 {

Label1.Text="invalid user name and password";

}
break;
}

case "Officer":
{
while (dr.Read())
{

if
((TextBox1.Text.Equals(dr.GetString(0).ToString
())) &&
((TextBox2.Text.Equals(dr.GetString(1).ToString
()))) && (s == dr.GetString(2)))
{

Response.Redirect("~\\BankingOfficer\\ServiceDe
sk.aspx");

else
{

Label1.Text="invalid user name and password";

}
}
break;
}
}
}
103
 }
Administrator (Create acc.,search
acc.,update acc,delete acc.)

using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;

public partial class

Administrator_ServiceCounter :
System.Web.UI.Page
{
SqlConnection con;
SqlCommand com;
SqlDataAdapter adp;
DataSet ds;
SqlCommandBuilder cmd;
SqlDataReader dr;
string gender;

protected void Page_Load(object sender,

EventArgs e)
{
con = new SqlConnection();
con.ConnectionString = "Integrated
Security=SSPI;Persist Security

104
Info=False;Initial Catalog=mybank;Data
Source=MY-6180A623FF7B";

protected void btnsave_Click(object sender,

EventArgs e)
{
string name = txtname.Text;
string desk = txtdesk.Text;

if (rdmale.Checked==true)
{
gender = rdmale.Text;
}
else
{
gender = rdfemale.Text;
}
string add = txtadd.Text;
string code = txtcode.Text;
con.Open();
com = new SqlCommand("insert into
bankofficer values('" + code + " ','" + name +
"','" + desk + "','" + add + " ','" + gender +
"')", con);
com.ExecuteNonQuery();
adp = new SqlDataAdapter("select * from
bankofficer", con);
ds = new DataSet();
adp.Fill(ds, "bankofficer");
cmd = new SqlCommandBuilder(adp);
grdofficer.DataSource =
ds.Tables[0].DefaultView;
grdofficer.DataBind();
txtcode.Text = "";
txtname.Text = "";
txtdesk.Text = "";
105
 txtadd.Text = "";
rdfemale.Checked = false;
rdmale.Checked = false;

con.Close();

}
protected void btnsearch_Click(object
sender, EventArgs e)
{

con.Open();
com = new SqlCommand("select
officername, officerdesk, officeraddress,
officergender from bankofficer where
officercode ='" + txtcode.Text + "'", con);
try
{
dr = com.ExecuteReader();
dr.Read();
txtname.Text = dr[0].ToString();
txtdesk.Text = dr[1].ToString();
txtadd.Text = dr[2].ToString();
if (dr[3].ToString() == "Male")
{
rdmale.Checked = true;
}
else
{
rdfemale.Checked = true;
}

con.Close();
}
catch (Exception ex)
{
106
 Label6.Text = "" + ex.Message;
}
}
protected void btnupdate_Click(object
sender, EventArgs e)
{

string name = txtname.Text;

string desk = txtdesk.Text;
if (rdmale.Checked == true)
{
gender = rdmale.Text;
}
else
{
gender = rdfemale.Text;
}
string add = txtadd.Text;
con.Open();
com = new SqlCommand("UPDATE
bankofficer set officername='" + name +
"',officerdesk='" + desk + "',officeraddress='"
+ add + " ',officergender='" + gender + "'
where officercode='" + txtcode.Text + "'",
con);
com.ExecuteNonQuery();
adp = new SqlDataAdapter("select * from
bankofficer", con);
ds = new DataSet();
adp.Fill(ds, "bankofficer");
cmd = new SqlCommandBuilder(adp);
grdofficer.DataSource =
ds.Tables[0].DefaultView;
grdofficer.DataBind();
con.Close();
}
protected void btndelete_Click(object
sender, EventArgs e)
107
 {

con.Open();
com = new SqlCommand("delete from
bankofficer where officercode ='" +
txtcode.Text + "'", con);
com.ExecuteNonQuery();
adp = new SqlDataAdapter("select * from
bankofficer", con);
ds = new DataSet();
adp.Fill(ds, "bankofficer");
cmd = new SqlCommandBuilder(adp);
grdofficer.DataSource =
ds.Tables[0].DefaultView;
grdofficer.DataBind();
txtcode.Text = "";
txtname.Text = "";
txtdesk.Text = "";
txtadd.Text = "";
rdfemale.Checked = false;
rdmale.Checked = false;

con.Close();

Administrator(check the services

provided by the bank officer’s)

using System;
using System.Data;
using System.Configuration;

108
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;

public partial class Administrator_Services :

System.Web.UI.Page
{
SqlConnection con;
SqlCommand cmd;
SqlDataReader dr;
SqlDataAdapter da;
SqlCommandBuilder com;
DataSet ds;

protected void Page_Load(object sender,

EventArgs e)
{ con = new SqlConnection();
con.ConnectionString = "Integrated
Security=SSPI;Persist Security
Info=False;Initial Catalog=mybank;Data
Source=MY-6180A623FF7B";

if (!Page.IsPostBack)
{

con.Open();
cmd = new SqlCommand("select * from
bankofficer", con);
dr = cmd.ExecuteReader();
while (dr.Read())
{

109
ddlcode.Items.Add(dr[0].ToString());
}
con.Close();
}
}
protected void
ddlcode_SelectedIndexChanged(object sender,
EventArgs e)
{

con.Open();
string s =
ddlcode.SelectedValue.ToString();
da = new SqlDataAdapter("select *
from bankofficer where officercode = '" + s +
"'", con);
ds = new DataSet();
da.Fill(ds, "bankofficer");
com = new SqlCommandBuilder(da);
grddesk.DataSource =
ds.Tables[0].DefaultView;
grddesk.DataBind();

}
}

Bank Officer( processed a request )

using System;
using System.Data;
using System.Configuration;
110
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
using System.Text;
public partial class BankingOfficer_ServiceDesk
: System.Web.UI.Page
{
SqlConnection con;
SqlCommand cmd;
SqlDataReader dr;
SqlDataAdapter da;
SqlCommandBuilder com;
DataSet ds;

protected void Page_Load(object sender,

EventArgs e)
{
con = new SqlConnection();
con.ConnectionString = "Integrated
Security=SSPI;Persist Security
Info=False;Initial Catalog=mybank;Data
Source=MY-
6180A623FF7B;MultipleActiveResultSets=True";

if (!Page.IsPostBack)
{

con.Open();
cmd = new SqlCommand("select * from
services", con);
dr = cmd.ExecuteReader();
111
 while (dr.Read())
{

ddlcode.Items.Add(dr[0].ToString());
}

con.Close();

}
}

protected void
ddlcode_SelectedIndexChanged(object sender,
EventArgs e)
{
con.Open();
string s =
ddlcode.SelectedValue.ToString();
da = new SqlDataAdapter("select * from
ticket where typeofservices ='" + s + "'",
con);
ds = new DataSet();
da.Fill(ds, "ticket");
com = new SqlCommandBuilder(da);
grddesk.DataSource =
ds.Tables[0].DefaultView;
grddesk.DataBind();
con.Close();

}
protected void btnprocessed_Click(object
sender, EventArgs e)
{

// StringBuilder object

112
 StringBuilder str = new
StringBuilder();

// Select the checkboxes from the

GridView control

for (int i = 0; i < grddesk.Rows.Count;

i++)
{
GridViewRow row = grddesk.Rows[i];
bool isChecked =
((CheckBox)row.FindControl("CheckBox2")).Checke
d;

if (isChecked)
{
int t =
Convert.ToInt32(grddesk.Rows[i].Cells[3].Text);
con.Open();
cmd = new SqlCommand("UPDATE
ticket set IsProsseced='Y' where ticketnumber="
+ t, con);
cmd.ExecuteNonQuery();

// Column 2 is the name column

ResultInfo.Text = "Processed";
da = new SqlDataAdapter("select * from
ticket where typeofservices ='" +
ddlcode.SelectedValue.ToString()+ "'", con);
ds = new DataSet();
da.Fill(ds, "ticket");
grddesk.DataSource =
ds.Tables[0].DefaultView;
grddesk.DataBind();

con.Close();
113
 }
}

// prints out the result

Customer (send a request to bank officer)

using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
using System.Drawing;

public partial class Customer_Ticket :

System.Web.UI.Page
{
SqlConnection con;
SqlCommand com;
SqlDataAdapter ad;

114
 DataSet ds;
SqlCommandBuilder cd;
string accnumber;
string services;
SqlDataReader dr;
protected void Page_Load(object sender,
EventArgs e)
{
con = new SqlConnection();
con.ConnectionString = "Integrated
Security=SSPI;Persist Security
Info=False;Initial Catalog=mybank;Data
Source=MY-
6180A623FF7B;MultipleActiveResultSets=True";

if (!Page.IsPostBack)
{

con.Open();
com = new SqlCommand("select * from
services", con);
dr = com.ExecuteReader();
while (dr.Read())
{

ddlservices.Items.Add(dr[0].ToString());
}

con.Close();

}
}
protected void btngenrate_Click(object
sender, EventArgs e)
{

if (txtaccno.Text.Length == 16)
115
 {

accnumber = txtaccno.Text;
services = ddlservices.Text;
con.Open();
com = new SqlCommand("insert into
ticket (accountnumber,typeofservices)values('"
+ accnumber + " ','" + services +"')", con);
com.ExecuteNonQuery();
con.Close();
txtaccno.Text = "";
con.Open();
ad = new SqlDataAdapter("select *
from ticket where
accountnumber='"+accnumber+"'", con);
ds = new DataSet();
ad.Fill(ds, "ticket");
cd = new SqlCommandBuilder(ad);
grdticket.DataSource =
ds.Tables[0].DefaultView;
grdticket.DataBind();
con.Close();

}
else
{

Label3.ForeColor = Color.Red;
Label3.Text = "Please Enter Correct
16 Digit Account Number";
}

}
}

116
COMMENTS AND DESCRIPTIONS:

The comments have been used very frequently and are very
descriptive. I have used comments that are informative and
they enhance the readability of code. They will also be useful in
the maintenance of the programs.

ERROR HANDLING:

Errors are handled well and the users will get related messages
whenever they will do something wrng. Database handling
errors are also well caught. I have used VB standard error
handling techniques like On Error Goto for handling various
types of errors. In addition to this ADO library is put into
action for handling errors.

VALIDATION CHECKS:

I have used both field level validations whenever required. I

have also set procedures for validating data to be
stored/retrieved form database.

117
Sql Server2005 As A Relational Database
Management System

It would definitely make things easy for the user if software that
enables the user to create a database also allows the user to maintain
it. Maintaining a database would involve performing the vrious data
manipulation operations on the tables in the database. These
operations are :

 Adding records

 Querying

 Modifying records

 Deleting records

The operations enable the user to store, retrieve and update date in the
database. In addition to this the software should also allow the user to
create relationships between the various tabled. The software that
provides all the following facilities is called a Relational Database
Management System (RDBMS):

 Table -: In the case of tables, the tasks involved are as follow :

118
  Creating a table

o Specifying the field names.

o Specifying the data type.

o Specifying the field size.

o Specifying a field in the table that will have unique

values.

 Adding records to the tables

 Modifying data in the table

 Deleting records from the table

 Creating relationships between tables

 Queries -: In the case of queries, the tasks involves are s

follows:

 Creating queries to obtain information

o Specifying conditions on the basis of which data is

fetched from one or more tables.

o Specifying the fields on the basis of which data is to be

sorted.

 Creating queries to update data specifying the

conditions to determine which record is to be
updated.

 Creating queries to delete data specifying the condition to

determine which records are to be deleted.

119
 Reports -: In case of reports the tasks involved are as follows:

 Creating reports specifying the table or query from which

the report is to be created.

 Creating reports specifying the fields from the above those

are to be intended in the report.

 Formatting the data is done.

 Forms -: In case of forms the tasks involved are as follows:

 Creating forms specifying the table or query from which

the form is to be created.

 Crteating forms specifying the fields from the above that

are to be displayed in the form.

 Formatting of forms is done.

120
 TESTING

INTRODUCTION

Software Testing is a critical element of software quality

assurance and represents the ultimate review of specification, design
and coding. It plays a critical role in quality assurance for software.
Due to limitations of the verification methods of the previous phases,
design and requirement faults also appear in the code. Testing is used
to detect all these errors in addition to those in the code.

8.2 OBJECTIVES OF TESTING

The main objectives of the testing are :

 To execute program with intent of finding an error.

 To check the proper functioning of various modules of the

system individually and to correct errors, if any.

 To check and test the proper integration of all individually tested

modules so as to establish proper interaction.

 To check whether all the data fields in the database are

consistent or not.

 To check the accuracy and reliability of the system.

 To verify whether it fulfills the requirement of the proposed

system.
121
 The individual modules were tested and results
measured against manual calculations. Necessary corrections and
proper error handlers have been when error was detected. Suitable test
data was used. The users of the system were involved all through the
testing procedure and their suggestions are considered.

TYPES OF TESTING PERFORMED

There are various types of testing studied under the Software

Engineering course. Some of these are:

8.3.l Unit Testing

This concentrates on each unit of the software as implemented

in source code.

 Each system modules were tested individually.

 Checking the uniqueness of the key values in client interface.

 Input Output format.

 Necessary Corrections

Integration Testing

It addresses the issues associated with the dual problems of

verification and programming. Black-box test case design techniques
are the most prevalent at this stage. In this, many unit-tested modules

122
are combined into subsystems, which are then tested. The goal is to
see if the modules can be integrated properly. Hence, the emphasis is
on testing interfaces between nodules.

8.3.3 System Testing

 System tested after integration of all modules.

 Checking the module interaction and collective working.

 Necessary corrections.

Functional Testing

The goal is to see if the modules can be integrated properly.

Hence, the emphasis is on testing interfaces between nodules. The
structure of the program is not considered. Test cases were decided on
the basis of the requirements or specifications of the modules. Test
cases were first checked manually and then checked on the system.
Necessary corrections were made wherever necessary

123
Performance Testing

Performance Testing is designed to test the run-time

performance of software within the context of an integrated system.
Performance Testing was performed at each level of the software
development. Performance testing was performed on individual
modules. Performance tests are coupled with stress testing and often
require both hardware and software instrumentation.

White-Box Testing

It uses the control structure of the procedural design to derive

test cases. It is predicted on close examination of procedural design.
Providing test case that exercise specific sets of condition and loops
tests logical paths through the software.

124
 GANTT CHART:
1 5 10 15 20 25 30 35 40 45 50 55 60
TASKS

Requirement

Gathering

System

Design

Coding

Phase

Testing

Phase

FUTURE SCOPE:
Project has the great future scope it can be developed into a full fled
Groupfund software that can be used Large publically .

FUTURE ENHANCEMENT:
On the behalf of enhancement the following features can be added into the
project.

 Automatic/regular backup

 Built in/On line help capability

 Customized Reports

125
APPENDIX-A
THIS APPENDIX DEFINES THE TECHNICAL ELEMENTS
USED IN THE PROJECT.

PROCESS
NAME
NUMBER

This symbol is used to define the process’s used in the data flow
diagrams.

DATA FLOW CAPTION

This arrow is used to define the flow from source to sink or vice
versa.

SOURCE NAME

This symbol shows the sources of data in the data flow diagrams.

SINK NAME

This is standard notation used for defining the sink symbols.

ENTITY NAME

126
This rectangle is used for showing how the entities are defined in the
ER-diagram.

RELATION
NAME

This is used to describe what relation is between different entities in

the ER-diagram.

MODULE NAME

This is used to describe the system, sub system, programs, and sub
ptograms in the designs of modules.

127
APPENDIX-B

Login Form:-

128
GLOSSARY:
Algorithms: - These are the general set of statements needed for
problem solving purpose.

Attribute: - It defines the additional information about the entity.

Contextual Diagram: - It is the overview of the system data flow.

Data Dictionary: - This is the dictionary defining the purpose and

structure of each tanle attribute.

Data Structure: - Here ths defines the structure of the tables.

D.F.D:- Data Flow Diagram. It is the basic diagram showing how the
data flow occurs in the system.

Entity: - It is the person, place, thing or a concept for which we can

collect the data.

ER Diagram: - It is the diagram showing the relationship between

the entities.

Flow Chart: - This is the graphical chart depicting the steps needed
for solving a problem.

Process: - It is the function which transfers the input values into

output values.

129