ONLINE BUG TRACKING AND CUSTOMER SUPPORT

SYSTEM (OBTACSS)
PROJECT REPORT
A Project work submitted in partial fulfillment of the requirement of the award
of

the degree of Master of Computer Application(2010 – 2011)

Submitted by

S.Sangeetha Vigneshwari

Reg.No : 10A7030217

Under the Guidance of

Mr.K.Perumal, M.Sc,M.Phil,Ph.d.,

Associate Professor

Department of Computer Application

Directorate of Distance Education

Madurai Kamaraj University

Madurai

June-2011
CERTIFICATE
 DIRECTORATE OF DISTANCE EDUCATION

MADURAI KAMARAJ UNIVERSITY

MADURAI

CERTIFICATE

This is to certify that the project report entitled “ONLINE BUG

TRACKING AND CUSTOMER SUPPORT SYSTEM ”Submitted
by Mrs.S.SANGEETHA VIGNESHWARI., MCA in partial fulfillment of
the requirements for the award of degree of Master of Computer Application
of Madurai Kamaraj University, Madurai from
December 2010 to may 2011.

Internal Guide External Examinar

Submitted for the project Viva-Voce Examination held on ____________

DECLARATION

DECLARATION
 I here by declare that the project entitled “ Online Bug
Tracking and Customer Support System ” is record of original
work done by me under supervision and guidance of Mr.K.Perumal,
M.Sc,M.Phil,Ph.d., Associate Professor this project work has not formed the
basis for the award of any degree or similar title to any candidate of any
university.

Place : Madurai SANGEETHA VIGNESHWARI.S

Date :
 ACKNOWLEDGEME
NT

ACKNOWLEDGEMENT
 First hand,I praise and thank God, the almighty who showered the
necessary wisdom and grace upon us to accomplish the project work at HCL
CDC in Madurai.

I record my sincere thanks to Prof.Dr.S.Kannan

M.Sc,Ph.D.,Associate professor in Madurai Kamarajar University,Madurai
for permitted me to take up the project work.

My profound thanks to Mr.K.Perumal, M.Sc,M.Phil,Ph.d.,

Associate Professor in Madurai Kamarajar University,Madurai for his valuable
advice.

My profound thanks to Mr.J.Prakash M.Sc,M.Phil.,Project head,

HCL,madurai .

Finally, I would like to thank my parents, all –well wishers and friends
without whose prayers and help I could not have scaled this height.
 SYNOPSI
S

SYNOPSIS
 In this project,we study this problem and provide
some findings.
• The project contains three main modules. These are Administrator,
Staff and Customer. The administrator logins to the application and
enters the details are Staff Entry, Project Entry, View New Bugs From
Customers, Assign Bug to staff, View Bug case flow status details,
Send message to customers.

• The staff details are username, password, category and Email Id. The
project details are name and description. The bug details are project
name, error category, error details, print screen of the bug, due date to
reply for the bug. Bug assign details include the ticket number which is
generated for the bug and other messages.

• Case flow details include bug details, which staffs are involved in
solving the bug, and the status. The message sending includes the
message details for the bug solution. The staff may login to the site
using username and password. Then he may view the bugs assigned to
them. He can directly give solution message to customers or he can
assign the bugs to other staffs if the bug is related to them. The user
may view bug case flow details with which he involved.

• The customer registers in to the applications and login to the site using
username and password, whenever a bug is raised from his software;
he sends the bug details to the administrator with print screen of the
bug generated. He may see the bug case flow details and bug status
along with remedy details at any time using the ticket number
generated during new bug entry.

TABLE OF CONTENTS
SI.NO PARTICULARS PG.NO

1. INTRODUCTION 1

1.1 ABOUT THE ORGANIZATION

1.2 PROJECT DESCRIPTION

2. SYSTEM STUDY 11

2.1 FEASABILITY STUDY

2.2 EXISTING SYSTEM

2.3 PROPOSED SYSTEM

3 SYSTEM SPECIFICATION 14

3.1 SOFTWARE REQUIREMENTS

3.2 HARDWARE REQUIREMENTS

4 LANGUAGE SPECIFICATION 15

4.1 FEATURES OF VB .NET

4.2 FEATURES OF SQL SERVER 2000

5 SYSTEM DESIGN 32

5.1 INPUT DESIGN

5.2 OUTPUT DESIGN

5.3 DATABASE DESIGN

5.4 DATA FLOW DIAGRAM

5.5 SYSTEM FLOW DIAGRAM

6 SYSTEM TESTING AND MAINTENANCE 58

6.1 UNIT TESTING

6.2 INTEGRATION TESTING

6.3 VALIDATION TESTING

7 SYSTEM IMPLEMENTATION 59

7.1 SCOPE FOR FUTURE DEVELOPMENT

8 CONCLUSION 60

9 BIBLIOGRAPHY 62

APPENDIX

• SCREEN SHOT
• DATA TABLE STRUCTURE
• SAMPLE CODING
• LIST OF ABBREVIATION
I.
 1.INTRODUCTION

1.1 ABOUT THE ORGANISATION

We present ourselves has MRV INFOTECH.A Port Blair based company provides a
complete support and solution to IT since 1997. The world shrinks with advanced
technology, MRVprovides a complete support and solution at one-stop-shop for products &
Infrastructure Solutions in the areas of IT, Communication, Office Automation, and
Enterprise Networking & VPN Services This is backed by its service support infrastructure.
MRV Infotech’s portfolio of products covers the entire spectrum of the information
technology needs of its customers.

By virtue of the immense diversity of markets and customers that it addresses, MRV
Infotech’s products offerings include everything from high end enterprise level servers for
mission critical applications to multimedia home computers.

You may be a large multi-location company exploring solutions to enable your organization
or you may be a new born rising star looking for someone for IT planning or setting up your
IT Infrastructure, MRV Infotech has a solution, a tailor-made for you.

Our motto “MRV – The Name you can Trust”. We understand the full requirement of a client
from their point of view and guide them in a proper way to fulfill their requirement and we
provide support all kind of IT related problems.

1.2 PROJECT DESCRIPTION

The project titled “ONLINE BUG TRACKING AND CUSTOMER

SUPPORT SYSTEM” is designed using Active Server Pages .NET with Microsoft Visual
Studio.Net 2005 as front end and Microsoft SQL Server 2005 as back end which works in
.Net framework version 2.0.. The coding language used is ASP.Net using C#.

The project contains the following main modules:

The project contains three main modules:

1. Administrator
2. Staff
3. Customer.
Administrator:

The administrator logins to the application and enters the following details.

1. Staff Entry.
2. Project Entry.
3. View New Bugs From Customers.
 4. Assign Bug to staff.
5. View Bug case flow status details.
6. Send message to customers

• The staff details are username, password, category and Email Id.
• The project details are name and description.
• The bug details are project name, error category, error details, print
screen of the bug, due date to reply for the bug.
• Bug assign details include the ticket number which is generated for the
bug and other messages.
• Case flow details include bug details, which staffs are involved in
solving the bug, and the status.
• The message sending includes the message details for the bug solution.

Staff:

• The staff may login to the site using username and password.
• Then he may view the bugs assigned to them. He can directly give
solution message to customers or he can assign the bugs to other staffs if the
bug is related to them.
• The user may view bug case flow details with which he involved.
Customer:

• The customer registers in to the applications and login to the site using
username and password.
• Whenever a bug is raised from his software, he sends the bug details to
the administrator with print screen of the bug generated.
• He may see the bug case flow details and bug status along with remedy
details at any time using the ticket number generated during new bug entry.
 2. SYSTEM STUDY

2.1 Feasibility System

The feasibility of the project is analyzed in this phase and business proposal is put
forth with a very general plan for the project and some cost estimates. During system
analysis the feasibility study of the proposed system is to be carried out. This is to ensure
that the proposed system is not a burden to the company. For feasibility analysis, some
understanding of the major requirements for the system is essential.

Three key considerations involved in the feasibility analysis are

 ECONOMICAL FEASIBILITY
 TECHNICAL FEASIBILITY
 SOCIAL FEASIBILITY

ECONOMICAL FEASIBILITY:

This study is carried out to check the economic impact that the system
will have on the organization. The amount of fund that the company can pour into the
research and development of the system is limited. The expenditures must be justified. Thus
the developed system as well within the budget and this was achieved because most of the
technologies used are freely available. Only the customized products had to be purchased.
TECHNICAL FEASIBILITY:

This study is carried out to check the technical feasibility, that is, the
technical requirements of the system. Any system developed must not have a high demand on
the available technical resources. This will lead to high demands on the available technical
resources. This will lead to high demands being placed on the client. The developed system
must have a modest requirement, as only minimal or null changes are required for
implementing this system.

SOCIAL FEASIBILITY:

The aspect of study is to check the level of acceptance of the system by the
user. This includes the process of training the user to use the system efficiently. The user
must not feel threatened by the system, instead must accept it as a necessity. The level of
acceptance by the users solely depends on the methods that are employed to educate the user
about the system and to make him familiar with it. His level of confidence must be raised so
that he is also able to make some constructive criticism, which is welcomed, as he is the final
user of the system.

2.2 Existing System

The call centers (technical) may attend the calls through phone and rectify
their problems. It can take lot of time and money. The client can’t describing the full details
of the problems, so to solve the problems is very difficulty.

2.3 Proposed System

 In our issue track system (call center website) clients will register their issues
(problems) .Our company employees will process the issues and give the solutions through
website. In this we are using the internet without phone. So it will reduce the cost and time.

3. SYSTEM SPECIFICATION
3.1 Hardware Specifications:
 The hardware used for the development of the project is:

PROCESSOR : PENTIUM III 866 MHz

RAM : 128 MD SD RAM

MONITOR : 15” COLOR

HARD DISK : 20 GB

FLOPPY DRIVE : 1.44 MB

CDDRIVE : LG 52X

KEYBOARD : STANDARD 102 KEYS

MOUSE : 3 BUTTONS

3.2 Software Specifications:

The software used for the development of the project is:

OPERATING SYSTEM : Windows XP Professional

ENVIRONMENT : Visual Studio .NET 2005
.NET FRAMEWORK : Version 2.0
LANGUAGE : C#.NET
WEB TECHNOLOGY : Active Server Pages.NET
WEB SERVER : Internet Information Server 5.0
REPORTS : Web Form Data Grid control
BACK END : MS-SQL-Server 2005
 4. LANGUAGE SPECIFICATION

4.1 FEATURES OF VISUAL BASIC .NET

Visual Studio .NET is the single IDE that all the .NET languages can use. It
makes everything available to all languages.

Visual Studio .NET is a great Multilanguage development environment and

offers a complete set of tools to build Windows Forms , ASP.NET Web applications , and
XML Web services.
Start Page
The Start page offers three tabs at the top of the window that enables to
modify Visual Studio.NET as well as find important information. The tabs are

HTML Server Controls versus Web Server Controls

Control Type When to use this Control Type

HTML Server Controls When converting traditional ASP 3.0 Web pages to
ASP.NET Web pages and speed of completion is a
concern. It is a lot easier to change your HTML
elements to HTML server controls than it is to
change them to Web server controls.

When you prefer a more HTML-type programming

model.

When you wish to explicitly control the code

that is generated for the browser.

Web Server Controls When you require a rich set of functionality to

perform complicated page requirements.

When you are developing web pages that will be

viewed by a multitude of browser types and that
require different code based on these types.

When you prefer a more Visual Basic-type

programming model that is based on the use of
controls and control properties.
 Projects tab: This tab is the one to start new projects and launch projects that
already exists. This tab lets you to create a new project or open an existing project.

Online Resources tab: This tab provides a number of online resources when
connected to the Internet.

My Profile tab: This tab enables to customize the Visual Studio.NET

environment to resemble the structured environment that is familiar with.

Server Explorer

This window enables to perform a number of functions such as database

connectivity, performance monitoring, and interacting with event logs.

By using Server Explorer you can log on to a remote server and view database
and system data about that server. Many of the functions that are performed with the
Enterprise Manager in SQL Server can now be executed in the Server Explorer.

Solution Explorer
This provides an organized view of the projects in the application.The toolbar
within the Solution Explorer enables to

• View code page of the selected item.

• View design page of the selected item.

• Refresh the state of the selected item.

• Copy the Web project between Web servers.

• Show all the files in the project, including the hidden files.

• See Properties of the selected item.

Class View

The Class View window can be viewed from the Start Page by clicking the
Class View tab. The Class View shows all the classes that are contained within your solution.
 The Class View shows the hierarchical relationship among the classes in your
solution as well as the number of other items including methods, enumerations, namespaces,
unions, and events. It is possible to organize the view of these items within the window by
right-clicking anywhere in the Class View area and choosing how the items are sorted.

Toolbox

The Toolbox window enables to specify elements that will be part of the
Windows Forms or Web Forms. It provides a drag and drop means of adding elements and
controls to the pages or forms. The code snippets can also be stored within the Toolbox.

Properties window

This window provides the properties of an item that is part of the application.
This enables to control the style and behavior of the item selected to modify.

Dynamic Help

This window shows a list of help topics. The help topics change based on the
item selected or the action being taken.

The Dynamic Help window shows the help items displayed when you have a
Button control on the page selected. After the item is selected, a list of targeted help topic is
displayed. The topics are organized as a list of links. Clicking one of the links in the Dynamic
Help window opens the selected help topic in the Document window.

Document window

The Document window is the main window within Visual Studio.NET where
the applications are built.

The Document window shows open files in either Design or HTML mode.
Each open file is represented by a tab at the top of the Document window. Any number of
files can be kept open at the same time, and you can switch between the open files by
clicking the appropriate tab.

Design mode versus HTML mode

 Visual Studio.NET offers two modes for viewing and building files: Design
and HTML. By clicking the Design tab at the bottom of the Document window, you can see
how the page will view to the user. The page is built in the Design mode by dragging and
dropping elements directly onto the design page or form. Visual Studio .NET automatically
generates the appropriate code.

When the page is viewed in HTML mode, it shows the code for the page. It
enables to directly modify the code to change the way in which the page is presented.

Working with SQL Server through the Server Explorer

Using Visual Studio.NET , there is no need to open the Enterprise Manager

from SQL Server. Visual Studio.NET has the SQL Servers tab within the Server Explorer
that gives a list of all the servers that are connected to those having SQL Server on them.
Opening up a particular server tab gives five options:

 Database Diagrams

 Tables

 Views

 Stored Procedures

 Functions

Database Diagrams

To create a new diagram right click Database diagrams and select New
Diagram. The Add Tables dialog enables to select one to all the tables that you want in the
visual diagram you are going to create.

Visual Studio .NET looks at all the relationships between the tables and then
creates a diagram that opens in the Document window.
 Each table is represented in the diagram and a list of all the columns that are
available in that particular table. Each relationship between tables is represented by a
connection line between those tables.

The properties of the relationship can be viewed by right clicking the

relationship line.

Tables

The Server Explorer allows to work directly with the tables in SQL Server. It
gives a list of tables contained in the particular database selected.

By double clicking one of the tables, the table is seen in the Document
window. This grid of data shows all the columns and rows of data contained in the particular
table.

The data can be added or deleted from the table grid directly in the Document
window. To add a new row of data , move to the bottom of the table and type in a new row of
data after selecting the first column of the first blank row. You can also delete a row of data
from the table by right clicking the gray box at the left end of the row and selecting Delete.

By right clicking the gray box at the far left end of the row, the primary key
can be set for that particular column. The relationships to columns in other tables can be set
by selecting the Relationships option.

To create a new table right-click the Tables section within the Server Explorer
and selecting New Table. This gives the design view that enables to start specifying the
columns and column details about the table.

To run queries against the tables in Visual Studio .NET, open the view of the
query toolbar by choosing View->Toolbars->Query.

To query a specific table, open that table in the Document window. Then click
the SQL button which divides the Document window into two panes-one for query and other
to show results gathered from the query.

The query is executed by clicking the Execute Query button and the result is
produced in the lower pane of the Document window.
Views

To create a new view , right-click the View node and select New View. The
Add Table dialog box enables to select the tables from which the view is produced. The next
pane enables to customize the appearance of the data in the view.

4.2 Features of SQL-SERVER

The OLAP Services feature available in SQL Server version 7.0 is now called
SQL Server 2000 Analysis Services. The term OLAP Services has been replaced with the
term Analysis Services. Analysis Services also includes a new data mining component. The
Repository component available in SQL Server version 7.0 is now called Microsoft SQL
Server 2000 Meta Data Services. References to the component now use the term Meta Data
Services. The term repository is used only in reference to the repository engine within Meta
Data Services

SQL-SERVER database consist of six type of objects,

They are,

1. TABLE

2. QUERY

3. FORM

4. REPORT

5. MACRO

TABLE:

A database is a collection of data about a specific topic.

VIEWS OF TABLE:

We can work with a table in two types,

1. Design View
 2. Datasheet View

Design View

To build or modify the structure of a table we work in the table design

view. We can specify what kind of data will be hold.

Datasheet View

To add, edit or analyses the data itself we work in tables datasheet

view mode.

QUERY:

A query is a question that has to be asked the data. Access gathers data
that answers the question from one or more table. The data that make up the answer is either
dynaset (if you edit it) or a snapshot(it cannot be edited).Each time we run query, we get
latest information in the dynaset.Access either displays the dynaset or snapshot for us to view
or perform an action on it ,such as deleting or updating.

FORMS:

A form is used to view and edit information in the database record by

record .A form displays only the information we want to see in the way we want to see it.
Forms use the familiar controls such as textboxes and checkboxes. This makes viewing and
entering data easy.

Views of Form:

We can work with forms in several primarily there are two views,

They are,

1. Design View

2. Form View
Design View

To build or modify the structure of a form, we work in forms design view.

We can add control to the form that are bound to fields in a table or query, includes
textboxes, option buttons, graphs and pictures.

Form View

The form view which display the whole design of the form.

REPORT:

A report is used to vies and print information from the database. The report
can ground records into many levels and compute totals and average by checking values from
many records at once. Also the report is attractive and distinctive because we have control
over the size and appearance of it.

MACRO:

A macro is a set of actions. Each action in macros does something. Such as

opening a form or printing a report .We write macros to automate the common tasks the work
easy and save the time.

MODULE:

Modules are units of code written in access basic language. We can write
and use module to automate and customize the database in very sophisticated ways.

WHAT IS “.NET”?

Microsoft .NET is a set of Microsoft software technologies for rapidly

building and integrating XML Web services, Microsoft Windows-based applications, and
Web solutions. The .NET Framework is a language-neutral platform for writing programs
that can easily and securely interoperate. There’s no language barrier with .NET: there are
numerous languages available to the developer including Managed C++, C#, Visual Basic
and Java Script. The .NET framework provides the foundation for components to interact
seamlessly, whether locally or remotely on different platforms. It standardizes common data
types and communications protocols so that components created in different languages can
easily interoperate.

“.NET” is also the collective name given to various software components

built upon the .NET platform. These will be both products (Visual Studio.NET and
Windows.NET Server, for instance) and services (like Passport, .NET My Services, and so
on).

THE .NET FRAMEWORK

The .NET Framework has two main parts:

1. The Common Language Runtime (CLR).

2. A hierarchical set of class libraries.

The CLR is described as the “execution engine” of .NET. It provides the

environment within which programs run. The most important features are:

 Conversion from a low-level assembler-style language, called

Intermediate Language (IL), into code native to the platform being executed on.
 Memory management, notably including garbage collection.
 Checking and enforcing security restrictions on the running code.
 Loading and executing programs, with version control and other such
features.

The following features of the .NET framework are also worth description:
 Managed Code - is code that targets .NET, and which contains certain extra
information - “metadata” - to describe itself. Whilst both managed and unmanaged code can
run in the runtime, only managed code contains the information that allows the CLR to
guarantee, for instance, safe execution and interoperability.

Managed Data - With Managed Code comes Managed Data. CLR provides
memory allocation and Deal location facilities, and garbage collection. Some .NET languages
use Managed Data by default, such as C#, Visual Basic.NET and JScript.NET, whereas
others, namely C++, do not. Targeting CLR can, depending on the language you’re using,
impose certain constraints on the features available. As with managed and unmanaged code,
one can have both managed and unmanaged data in .NET applications - data that doesn’t get
garbage collected but instead is looked after by unmanaged code.

Common Type System - The CLR uses something called the Common Type System (CTS)
to strictly enforce type-safety. This ensures that all classes are compatible with each other, by
describing types in a common way. CTS define how types work within the runtime, which
enables types in one language to interoperate with types in another language, including cross-
language exception handling. As well as ensuring that types are only used in appropriate
ways, the runtime also ensures that code doesn’t attempt to access memory that hasn’t been
allocated to it.

Common Language Specification - The CLR provides built-in support for language
interoperability. To ensure that you can develop managed code that can be fully used by
developers using any programming language, a set of language features and rules for using
them called the Common Language Specification (CLS) has been defined. Components that
follow these rules and expose only CLS features are considered CLS-compliant.

THE CLASS LIBRARY

 .NET provides a single-rooted hierarchy of classes, containing over 7000
types. The root of the namespace is called System; this contains basic types like Byte,
Double, Boolean, and String, as well as Object. All objects derive from System. Object. As
well as objects, there are value types. Value types can be allocated on the stack, which can
provide useful flexibility. There are also efficient means of converting value types to object
types if and when necessary.

The set of classes is pretty comprehensive, providing collections, file, screen,

and network I/O, threading, and so on, as well as XML and database connectivity.

The class library is subdivided into a number of sets (or namespaces), each
providing distinct areas of functionality, with dependencies between the namespaces kept to a
minimum.

LANGUAGES SUPPORTED BY .NET

The multi-language capability of the .NET Framework and Visual Studio

.NET enables developers to use their existing programming skills to build all types of
applications and XML Web services. The .NET framework supports new versions of
Microsoft’s old favorites Visual Basic and C++ (as VB.NET and Managed C++), but there
are also a number of new additions to the family:

Visual Basic .NET has been updated to include many new and improved
language features that make it a powerful object-oriented programming language. These
features include inheritance, interfaces, and overloading, among others. Visual Basic also
now supports structured exception handling, custom attributes and also supports multi-
threading.
 Visual Basic .NET is also CLS compliant, which means that any CLS-
compliant language can use the classes, objects, and components you create in Visual
Basic .NET.

Managed Extensions for C++ and attributed programming are just some of the
enhancements made to the C++ language. Managed Extensions simplify the task of migrating
existing C++ applications to the new .NET Framework.

C# is Microsoft’s new language. It’s a C-style language that is essentially “C+

+ for Rapid Application Development”. Unlike other languages, its specification is just the
grammar of the language. It has no standard library of its own, and instead has been designed
with the intention of using the .NET libraries as its own.

Microsoft Visual J# .NET provides the easiest transition for Java-language

developers into the world of XML Web Services and dramatically improves the
interoperability of Java-language programs with existing software written in a variety of other
programming languages.

Active State has created Visual Perl and Visual Python, which enable .NET-
aware applications to be built in either Perl or Python. Both products can be integrated into
the Visual Studio .NET environment. Visual Perl includes support for Active State’s Perl Dev
Kit.

Other languages for which .NET compilers are available include:

 FORTRAN
 COBOL
 Eiffel
 Fig1 .Net Framework

ASP.NET Windows Forms

XML WEB SERVICES

Base Class Libraries

Common Language Runtime

Operating System

INTRODUCTION TO ASP.NET

ASP.NET is the .NET framework layer that handles Web requests for specific
types of files, namely those with (.aspx or .ascx) extensions. The ASP.NET engine provides a
robust object model for creating dynamic content and is loosely integrated into the .NET
framework.

WHAT IS ASP.NET?

ASP.NET is part of the .NET framework. ASP.NET programs are centralized

applications hosted on one or more Web servers that respond dynamically to client requests.
The responses are dynamic because ASP.NET intercepts requests for pages with a specific
extension (.aspx or .ascx) and hands off the responsibility for answering those requests to
just-in-time (JIT) compiled code files that can build a response “on-the-fly.”
 ASP.NET deals specifically with configuration (web.config and
machine.config) files, Web Services (ASMX) files, and Web Forms (ASPX) files. The server
doesn’t “serve” any of these file types—it returns the appropriate content type to the client.
The configuration file types contain initialization and settings for a specific application or
portion of an application. Another configuration file, called machine.web, contains machine-
level initialization and settings. The server ignores requests for web files, because serving
them might constitute a security breach.

Client requests for these file types cause the server to load, parse, and execute
code to return a dynamic response. For Web Forms, the response usually consists of HTML
or WML. Web Forms maintain state by round-tripping user interface and other persistent
values between the client and the server automatically for each request.

A request for a Web Form can use View State, Session State, or Application
State to maintain values between requests. Both Web Forms and Web Services requests can
take advantage of ASP. Net’s integrated security and data access through ADO.NET, and can
run code that uses system services to construct the response. So the major difference between
a static request and a dynamic request is that a typical Web request references a static file.
The server reads the file and responds with the contents of the requested file.

ASP.NET uses .NET languages. ASP.NET code exists in multithreaded JIT

compiled DLL assemblies, which can be loaded on demand. Once loaded, the ASP.NET
DLLs can service multiple requests from a single in-memory copy.

ASP.NET supports all the .NET languages (currently C#, C++, VB.NET, and
JScript, but there are well over 20 different languages in development for .NET), so you will
eventually be able to write Web applications in your choice of almost any modern
programming language.

In addition to huge increases in speed and power, ASP.NET provides substantial

development improvements, like seamless server-to-client debugging, automatic validation of
form data.
 Fig2. Interoperability

ASP.NET EVENTS

.NET events and whEvery time an ASP.NET page is viewed, many tasks are being performed
behind the scenes. Tasks are performed at key points ("events") of the page's execution
lifecycle.

The most common events are:

OnInit

The first event in our list to be raised is OnInit. When this event is raised, all
of the page's server controls are initialized with their property values. Post Back values are
not applied to the controls at this time.

On Load

The next event to be raised is On Load, which is the most important event of them all as
all the pages server controls will have their Post Back values now.
Post Back Events

Next all the Post Back events are raised. These events are only raised when the
page view is the result of a Post Back. The order that these events are raised can't be defined
or relied upon; the only consistency with the order that Post Back events are raised is that
they are all raised between the Unload and OnPreRender events.

OnPreRender

This event is raised just prior to the page or server control's html output being
written into the response stream that's sent to the client web browser. This is last chance you
have to make any modifications. By this point, all the server controls on the page have the
final data applied.

On Unload

This is the last event in our list to be raised and you should destroy any un-
managed objects and close any currently open database connection at this point. It is not
possible to modify any controls on the page at this point as the response stream has already
been sent to the client web browser.

As each event of the page is raised it also automatically tells all its child
controls to raise their own implementation of the same event. In turn each of those controls
will tell its own child controls to do the same and so on down the control tree till all controls
have done so. Then execution flow is passed back to the main page class to continue onto the
next event and the process is repeated for that event.

MAIN FEATURES OF ASP.NET

 Successor of Active Server Pages (ASP), but completely different architecture

• Object-oriented

• Event-based

• Rich library of Web Controls

• Separation of layout (HTML) and logic (e.g. C#)

• Compiled languages instead of interpreted languages

• GUI can be composed interactively with Visual Studio .NET

• Better state management

NAMESPACES

ASP.NET uses a concept called namespaces. Namespaces are hierarchical

object models that support various properties and methods. For example, HTML server
controls reside in "System.web.UI.HtmlControls" namespace, web server controls reside in
“System.web.UI.WebControls" namespace and ADO+ resides in "System. Data" namespace.

LANGUAGE INDEPENDENT

An ASP.NET page can be created in any language supported by .NET

framework. Currently .NET framework supports VB, C#, JScript and Managed

ASP.NET SERVER CONTROLS

Using ASP.NET Server Controls, browser variation is handled because these

controls output the HTML themselves based on the browser requesting the page.

TYPES OF CONTROLS
 ASP.NET has two basic types of controls: HTML server controls and Web
server controls.HTML Server Controls are generated around specific HTML elements and the
ASP.NET engine changes the attributes of the elements based on server-side code that you
provide. Web server controls revolve more around the functional you need on the page. The
ASP.NET engine takes the extra steps to decide based upon the container of the requester,
what HTML to output.

Fig 3. Web Controls

ADO.NET

ADO.NET provides a set of classes which a script can use to interact with
databases. Scripts can create instances of ADO.NET data classes and access their properties
and methods. A set of classes which work with a specific type of database is known as a
.NET Data Provider. ADO.NET comes with two Data Providers, the SQL Server.NET Data
Provider (which provides optimised access for Microsoft SQL Server databases) and the
OLEDB.NET Data Provider, which works with a range of databases. The main ADO.NET
OLEDB data access classes are OLEDBConnection, OLEDBCommand, OLEDBDataReader
and OLEDBDataAdapter.
 5. SYSTEM DESIGN

5.1 INPUT DESIGN

Input design is the process of converting user-originated inputs to a

computer-based format. Input design is one of the most expensive phases of the operation of
computerized system and is often the major problem of a system.

5.2 OUTPUT DESIGN

Output design generally refers to the results and information that are generated
by the system for many end-users; output is the main reason for developing the system and
the basis on which they evaluate the usefulness of the application.

The output is designed in such a way that it is attractive, convenient and

informative. Forms are designed in VB.NET with various features, which make the console
output more pleasing.

As the outputs are the most important sources of information to the users,
better design should improve the system’s relationships with us and also will help in
decision-making. Form design elaborates the way output is presented and the layout available
for capturing information.
5.3 DATABASE DESIGN
The database design is a must for any application developed especially more for the
data store projects. Since the chatting method involves storing the message in the table and
produced to the sender and receiver, proper handling of the table is a must.
In the project, login table is designed to be unique in accepting the username and the
length of the username and password should be greater than zero. Both the company and
seeker username are stored in the same table with different flag values.
The job and question table is common to all companies. Likewise job apply details are
stored in the common ‘apply’ table. The different users view the data in different format
according to the privileges given.

The complete listing of the tables and their fields are provided in the annexure under
the title ‘Table Structure’.

5.4 DATA FLOW DIAGRAM

 LEVEL 0:

Administrator Module

User Details

Login
Authenticati
on

Project Bugs from

Staff Entry Entry Customers

Staff Details Project Details Bug Details

LEVEL 1:
Staffs Projects Bugs
Bug Tracking
Login

Administrator

Adds
Bugs
Bug
Bugs from Database Staff Details
Customers

Assigns Bugs to
Fixed Bugs respective staffs

LEVEL 2:

Response to the customer

Login
 Administrator
View
Fixed
Bugs

Bug Response to the

Customer Details
Database customer

LEVEL 3:

User Details

Bug Details
Login
Customer Response
Authenticati Projects Bugs fromAssign
Staffs Entry to Projects
on Entry Customers
Staffs Registration Customer
Customer Details StaffBugs
Bugs
Details
ER-DIAGRAM
 Projec
t
Staffs Projects
Detail
Student
Staff s
Profile
Details
Project Bugs from
Staff Entry Customer
s

Bugs
Staff
Entry
Project
Entry ADMIN
Bugs
from
Custom
ers

Customer
Bug Table Reg Tble

Employe
e Statu
Project Priorit
s
assigned y
Table Tabl
table Table
e

6. SYSTEM TESTING AND MAINTENANCE

UNIT TESTING:

Unit testing verification efforts on the smallest unit of software design,

module. This is known as “Module Testing”. The modules are tested separately. This testing
is carried out during programming stage itself. In these testing steps, each module is found to
be working satisfactorily as regard to the expected output from the module.

INTEGRATION TESTING:

Integration testing is a systematic technique for constructing tests to uncover

error associated within the interface. In the project, all the modules are combined and then the
entire programmer is tested as a whole. In the integration-testing step, all the error uncovered
is corrected for the next testing steps.

VALIDATION TESTING:

Validation testing is where requirements established as a part of software

requirement analysis is validated against the software that has been constructed This test
provides the final assurance that the software meets all functional, behavioral and
performance requirements. The errors, which were not uncovered during integration testing,
are found out and corrected during this phase.
 7. SYSTEM IMPLEMENTATION

Implementation is the stage of the project when the theoretical design is turned
out into a working system. Thus it can be considered to be the most critical stage in achieving
a successful new system and in giving the user, confidence that the new system will work and
be effective.

The implementation stage involves careful planning, investigation of the

existing system and it’s constraints on implementation, designing of methods to achieve
changeover and evaluation of changeover methods.

The project is implemented by accessing simultaneously from more than one

system and more than one window in one system. The application is implemented in the
Internet Information Services 5.0 web server under the Windows 2000 Professional and
accessed from various clients.
 8. CONCLUSION

The “BUG TRACKER” is a complex system involving many sub process.

The system overcomes the limitation of existing manual system. This project has been
designed, developed and implemented thus providing a full-fledged approach for proficient
and best of results. The project satisfies each efficient user for saving his time and also helps
him in clearing the bugs and also satisfies various organizations to use their Bug Tracker to
recruit bugs.

The Bug Tracker services can be updated with necessary enhancements in the
database. The system overheads the problem in the existing ones by capable of processing
voluminous data in a user-friendly manner.

The persons, who are involved in working the task manually, have seen this
project running and expressing satisfaction about the working procedures and the
“conversion handling” incorporated in the project.

Future enhancements can be made such as issuing user id to the user, where by
the user can use that as a reference which specifies all his previous performance, the project
work us stopped at this satisfactory level, due to time constraints.
 9. BIBLIOGRAPHY

-STEVE HARRIS AND ROBMACDONALD

Moving to ASP.NET: Web Development with VB.NET:

(Apress)

2001

-MATTHEW MACDONALD

Microsoft Visual Basic.NET Programmer’s Cookbook:

(Tata McGraw Hill Edition)

2002

-CHRIS GOODE, JOHN KAUFFMAN

Beginning ASP.NET 1.0 with Visual Basic.NET

(Wrox Programmer to Programmer)

2001

-Douglas O.Reilly

Designing Microsoft ASP.NET Applications

TataMcGrawHill Edition

2002

Web Site Reference:

http://www.asp.net

http://www.osborne.com

http://www.microsoft.com

Appendix:
SCREEN SHOTS:
DATA TABLE STRUCTURE:
BUG:
CUSTOMREG:

EMPLOYEE
PRIORITY

PROJECT ASSIGNED

STATUS

SAMPLE CODING:
Imports System.Data.SqlClient

Public Class frmLogin

Inherits System.Windows.Forms.Form

#Region " Windows Form Designer generated code "

Public Sub New()

MyBase.New()

'This call is required by the Windows Form Designer.

InitializeComponent()

'Add any initialization after the InitializeComponent() call

End Sub

'Form overrides dispose to clean up the component list.

Protected Overloads Overrides Sub Dispose(ByVal disposing As Boolean)

If disposing Then

If Not (components Is Nothing) Then

components.Dispose()

End If
 End If

MyBase.Dispose(disposing)

End Sub

'Required by the Windows Form Designer

Private components As System.ComponentModel.IContainer

'NOTE: The following procedure is required by the Windows Form Designer

'It can be modified using the Windows Form Designer.

'Do not modify it using the code editor.

Friend WithEvents Label1 As System.Windows.Forms.Label

Friend WithEvents Label2 As System.Windows.Forms.Label

Friend WithEvents Button1 As System.Windows.Forms.Button

Friend WithEvents Label3 As System.Windows.Forms.Label

Friend WithEvents Button3 As System.Windows.Forms.Button

Friend WithEvents Label5 As System.Windows.Forms.Label

Friend WithEvents txtuname As System.Windows.Forms.TextBox

Friend WithEvents txtpassword As System.Windows.Forms.TextBox

<System.Diagnostics.DebuggerStepThrough()> Private Sub

InitializeComponent()

Me.Label1 = New System.Windows.Forms.Label

Me.Label2 = New System.Windows.Forms.Label

Me.txtuname = New System.Windows.Forms.TextBox

Me.txtpassword = New System.Windows.Forms.TextBox

Me.Button1 = New System.Windows.Forms.Button

 Me.Label3 = New System.Windows.Forms.Label

Me.Button3 = New System.Windows.Forms.Button

Me.Label5 = New System.Windows.Forms.Label

Me.SuspendLayout()

'

'Label1

'

Me.Label1.Font = New System.Drawing.Font("Microsoft Sans Serif",

12.0!, CType((System.Drawing.FontStyle.Bold Or
System.Drawing.FontStyle.Italic), System.Drawing.FontStyle),
System.Drawing.GraphicsUnit.Point, CType(0, Byte))

Me.Label1.Location = New System.Drawing.Point(24, 48)

Me.Label1.Name = "Label1"

Me.Label1.Size = New System.Drawing.Size(112, 23)

Me.Label1.TabIndex = 0

Me.Label1.Text = "UserName"

'

'Label2

'

Me.Label2.Font = New System.Drawing.Font("Microsoft Sans Serif",

12.0!, CType((System.Drawing.FontStyle.Bold Or
System.Drawing.FontStyle.Italic), System.Drawing.FontStyle),
System.Drawing.GraphicsUnit.Point, CType(0, Byte))

Me.Label2.Location = New System.Drawing.Point(24, 88)

Me.Label2.Name = "Label2"

Me.Label2.Size = New System.Drawing.Size(112, 23)

Me.Label2.TabIndex = 1
 Me.Label2.Text = "Password"

'

'txtuname

'

Me.txtuname.Font = New System.Drawing.Font("Microsoft Sans Serif",

12.0!, System.Drawing.FontStyle.Italic, System.Drawing.GraphicsUnit.Point,
CType(0, Byte))

Me.txtuname.Location = New System.Drawing.Point(144, 48)

Me.txtuname.Name = "txtuname"

Me.txtuname.Size = New System.Drawing.Size(120, 26)

Me.txtuname.TabIndex = 0

Me.txtuname.Text = ""

'

'txtpassword

'

Me.txtpassword.Font = New System.Drawing.Font("Microsoft Sans Serif",

12.0!, System.Drawing.FontStyle.Italic, System.Drawing.GraphicsUnit.Point,
CType(0, Byte))

Me.txtpassword.Location = New System.Drawing.Point(144, 88)

Me.txtpassword.Name = "txtpassword"

Me.txtpassword.PasswordChar = Microsoft.VisualBasic.ChrW(42)

Me.txtpassword.Size = New System.Drawing.Size(120, 26)

Me.txtpassword.TabIndex = 1

Me.txtpassword.Text = ""

'

'Button1
 '

Me.Button1.BackColor = System.Drawing.Color.PapayaWhip

Me.Button1.Font = New System.Drawing.Font("Microsoft Sans Serif",

14.0!, CType((System.Drawing.FontStyle.Bold Or
System.Drawing.FontStyle.Italic), System.Drawing.FontStyle),
System.Drawing.GraphicsUnit.Point, CType(0, Byte))

Me.Button1.ForeColor = System.Drawing.Color.Blue

Me.Button1.Location = New System.Drawing.Point(194, 136)

Me.Button1.Name = "Button1"

Me.Button1.Size = New System.Drawing.Size(75, 32)

Me.Button1.TabIndex = 3

Me.Button1.Text = "E&xit"

'

'Label3

'

Me.Label3.BackColor = System.Drawing.Color.Transparent

Me.Label3.Font = New System.Drawing.Font("Microsoft Sans Serif",

20.0!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point,
CType(0, Byte))

Me.Label3.Location = New System.Drawing.Point(0, 0)

Me.Label3.Name = "Label3"

Me.Label3.Size = New System.Drawing.Size(352, 32)

Me.Label3.TabIndex = 6

Me.Label3.Text = "Tax Login Form"

Me.Label3.TextAlign = System.Drawing.ContentAlignment.MiddleCenter

'
 'Button3

'

Me.Button3.BackColor = System.Drawing.Color.PapayaWhip

Me.Button3.Font = New System.Drawing.Font("Microsoft Sans Serif",

14.0!, CType((System.Drawing.FontStyle.Bold Or
System.Drawing.FontStyle.Italic), System.Drawing.FontStyle),
System.Drawing.GraphicsUnit.Point, CType(0, Byte))

Me.Button3.ForeColor = System.Drawing.Color.Blue

Me.Button3.Location = New System.Drawing.Point(89, 136)

Me.Button3.Name = "Button3"

Me.Button3.Size = New System.Drawing.Size(71, 32)

Me.Button3.TabIndex = 2

Me.Button3.Text = "&Login"

'

'Label5

'

Me.Label5.BackColor = System.Drawing.Color.Transparent

Me.Label5.Location = New System.Drawing.Point(0, 128)

Me.Label5.Name = "Label5"

Me.Label5.Size = New System.Drawing.Size(352, 48)

Me.Label5.TabIndex = 13

'

'frmLogin

'

Me.AutoScaleBaseSize = New System.Drawing.Size(5, 13)

 Me.BackColor = System.Drawing.Color.FromArgb(CType(192, Byte),
CType(255, Byte), CType(192, Byte))

Me.ClientSize = New System.Drawing.Size(338, 173)

Me.Controls.Add(Me.Button3)

Me.Controls.Add(Me.Label3)

Me.Controls.Add(Me.Button1)

Me.Controls.Add(Me.txtpassword)

Me.Controls.Add(Me.txtuname)

Me.Controls.Add(Me.Label2)

Me.Controls.Add(Me.Label1)

Me.Controls.Add(Me.Label5)

Me.FormBorderStyle =
System.Windows.Forms.FormBorderStyle.FixedSingle

Me.MaximizeBox = False

Me.MinimizeBox = False

Me.Name = "frmLogin"

Me.StartPosition =
System.Windows.Forms.FormStartPosition.CenterScreen

Me.Text = "Tax Login Form"

Me.ResumeLayout(False)

End Sub

#End Region
 Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click

End

End Sub

Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button3.Click

Try

If con.State <> ConnectionState.Open Then con.Open()

cmd.CommandText = "Select count(*) From Users Where UserName='"

& txtuname.Text & "' and [Password]='" & txtpassword.Text & "'"

If cmd.ExecuteScalar > 0 Then

cmd.CommandText = "Select count(*) From Users Where

UserName='" & txtuname.Text & "' and [Password]='" & txtpassword.Text &
"'"

LoggedUser = txtuname.Text

loginsucceed = True

Me.Close()

Else

MsgBox("Invalid User...", MsgBoxStyle.Critical)

End If

Catch ex As Exception

MsgBox(ex.Message.ToString, MsgBoxStyle.Critical)
 Finally

con.Close()

End Try

End Sub

Private Sub frmLogin_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load

End Sub

End Class

LIST OF ABBREVIATIONS

HTML : Hyper Text Markup Language

DHTML : Dynamic Hyper Text Markup Language

CGI : Common Gateway Interface

ASP : Active Server Pages

CTS : Common Type System

CLR : Common Language Runtime

XML : Extended Markup Language

SQL : Structured Query Language

CLS : Common Language Specification

IL : Intermediate Language

ADO : ActiveX Data Object

COM : Component Object Model

IIS : Internet Information Server

URL : Uniform Resource Locator

JSP : Java Server Package