documentation) unaltered

8/4/2019 Documentation) Unaltered

1/93

ONSCREEN KEYBOARD

PROJECT REPORT

Submitted in partial fulfillment of the requirements

For the award of the degree of

MASTER OF SCIENCE

(SOFTWARE SCIENCE)

Submitted By

N.GOWRI

REG.No:07BEE1029

Under the Guidance of

Mr.R.RAMANKUMARAMANGALAM, B.E., M.Sc.,

DEPARTMENT OF COMPUTER SCIENCE

VIVEKANANDHA COLLEGE FOR WOMEN

(Affiliated to Periyar University, Salem)

TIRUCHENGODE-637205

APRIL2010


2/93

VIVEKANANDHA COLLEGE FOR WOMEN

(Affiliated to Periyar University, Salem)

ELAYAMPALAYAM, TIRUCHENGODE-637205

This is to certify that the project entitled BUG TRACKING is a bonafide record done

by N.GOWRI (REG.No:07BEE1029), during the academic year 2009-2010 in partial

fulfillment for the award of the degree ofMaster of Science(Software Science)

Internal Guide Head of the Department

Submitted for the VivaVoce Examination held on -------------------

Internal Examiner External Examiner


3/93

DECLARATION

I hereby declare that the project work entitled BUG TRACKING,

submitted to Periyar University in partial fulfillment of the requirements

for the award of the degree of MASTER OF SOFTWARE SCIENCE, is a

report of original work done by me under the supervision

of Mr.R.Ramankumaramangalam, BE., M.Sc., Head of the Department of

Computer Science, Vivekananda College for Women, during the period of study

2009-2010.

Place: Signature of the candidate

Date: (N.GOWRI)

Reg.No: 07BEE1029


4/93

ACKNOWLEDGEMENT

First and foremost I thank the almighty god for showing his grace and blessing on me to

finish this project in a nice manner.

I express my gratitude and sincere thanks to Chairman, Mr.M.Karunanidhi B.Pharm.,

M.S., Ph.D., D.litt., of Vivekanandha Educational Institutions, Elayampalayam, Tiruchengode

for having granted me the permission to undertake the project work.

I extend my heartfelt thanks to our Principal, Mr.N.Rajendran, M.C.A., M.Phil., of

Vivekanandha College for Women for his immense support in all manners.

I extend my gratitude and respect to our Head of the Department,

Mr.R.Ramankumaramangalam, BE.,M.Sc., Department of Computer Science, Vivekananda

College for Women, for his encouragement and support in doing this project work.

I express my profound thanks and gratitude to my internal guide,

Mr.R.Ramankumaramangalam, BE.,M.Sc., for giving me concrete ideas and full support for

the overall design of the system. His timely help and invaluable support

I also thank my company guide, Mr.S.Savariraj, M.C.A, TREC-STEP and all the staff

members of the organization.

Last but not the least I thank my beloved family members and friends for the moral

support and inspiration given to me during my project work.


5/93


6/93

SYNOPSIS

BUG TRACKING system acts as an interface between the Project Manager, the

Developer and the Tester in a software company.

Using this system the project manager assigns projects to the developers. The developer

develops the project as per customer requirements. The project manger itself assigns the

developed applications to the Testers for testing.

When the tester encounters n no bugs during testing, he generates a unique id number

for each individual bug. The bug information along with its id is mailed to the project manger

and the developer. This is called Bug Report. After viewing the bug report the developer

resolves the bugs. This makes that no error will go unfixed in the projects. These are stored in the

database for future reference.


7/93


8/93

CONTENTS

SNO DESCRIPTION PAGE NO

1 INTRODUCTION

1.1PROJECT DESCRIPTION1.2ORGANISATION PROFILE

2 SYSTEM CONFIGURATION

2.1 HARDWARE CONFIGURATION

2.2 SOFTWARE CONFIGURATION

2.3 SOFTWARE DESCRIPTION

3 SYSTEM STUDY

3.1 EXISTING SYSTEM

3.1.1 DRAWBACKS

3.2 PROPOSED SYSTEM

3.2.1 AIM

3.2.2 OBJECTIVES

4 SYSTEM DESIGN AND DEVELOPMENT

4.1 FILE DESIGN

4.2 INPUT DESIGN

4.3 OUTPUT DESIGN

4.4.CODE DESIGN

4.5 DATA DESIGN


9/93

SNO DESCRIPTION PAGE NO

5 SYSTEM TESTING AND IMPLEMENTATION

6 CONCLUSION

7 BIBLIOGRAPHY

8 APPENDICES

8.1 DATA FLOW DIAGRAM

8.2 TABLE STRUCTURE

8.3 SAMPLE CODINGS

8.4 SAMPLE INPUT/OUTPUT


10/93


11/93

1.1PROJECT DESCRIPTIONWhen a customer puts request or orders for a product to be developed. The project

manager is responsible for adding users to Bus Tracking System and assigning projects to the

users.

The project manager assigns projects to the developers. The developer develops the

projects as per customer requirements. The project manager itself assigns the developed

applications to the Testers for testing. The tester tests the application and identifies the bugs in

the application.

When the tester encounters n no. of bugs, he generates a unique id number for each

individual bug. The bug information along with its id is mailed to the project manager and

developer. This is Bug Report. These are stored in the database. This is useful for further

reference.

Bug information includes the bug id, bug name, bug priority, project name, bug location,

bug type.

This whole process continues until all the bugs are got fixed in the application.

The bug report is mailed to the project manager and the developer as soon as the bug is

identified. This makes that no error will go unfixed because of poor communication. It makes

ensure that anyone who needs to know about a bug can learn of it soon after it is reported.

Bug Tracking System plays a vital role in the testing phase. But it supports assigning

projects for the developer, tester by the project manager. The Bug Tracking System maintains

the different users separately i.e., it provides separate environments for project manager,

developer and tester.


12/93

The project has the following modules:

Project Manager Developer Tester

Module 1: Project Manager

The project manager has the options to access user information, project information,

assign information, report, self details.

1) User Information:

The project manager will access the user information. In this the, the project manager can

Add user details into the database. Delete user from the database. Modifying the existing user.

2) Project Information:

The project manager will access the project information. In this, the project manager can

Add the project into the database by gathering the information like project name,status, project id, description.

Delete project from the database by specifying the project name. Modify the project details by specifying the project name


13/93

3) Assign Information:

This can be accessed by the project manager to assign the projects to the other users like

developer, tester. Assign information has the following options like view, assign and project.

The project manager can

View all the projects. Assign the projects to the developer and tester by gathering the information like

user name, project id, assigned date, date of completion.

Search a particular project details by specifying corresponding project id.4) Report:

This is used to view the bug report after specifying the project id.

5) Self:

This option is used to view the self details. It has option to change password. This

gathers the information like old password, new password. This makes to store the changed

password to the database.

Module 2: Developer

The developer has the options to view projects, bug details and self details.

1) View Projects:

This option will make the developer to view all his assigned projects. It displays the

project name, project id, assigned date, expected date of completion.


14/93

2) Bug Details:

This option will make the developer to view all the bug details sent by the tester

3) Self:


gathers the information like old password, new password. This makes to store the changed

password to the database.

Module 3: Tester

The tester has the options to his projects, post bugs and self details.

1) View Projects:

This option will make the tester to view all his assigned projects. It displays the project

name, project id, assigned date, expected date of completion.

2) Post Bugs:

This option will make the tester to

Add the bug information along with bug id, project id, bug type, location etc., tothe database for future reference

Mail the bug id and some other details regarding the bug to the project managerand developer.

3) Self:


gathers the information like old password, new password.


15/93


16/93

2.SYSTEM CONFIGURATION

2.1HARDWARE CONFIGURATION:

Processor : Intel Pentium IV

Hard disk : 80 GB

Ram : 512 MB

Speed : 2.66 GHz

Monitor : SAMSUNG

Mother Board : Intel

Mouse model : ps/2

Keyboard : SAMSUNG, 108 Keys

2.2SOFTWARE CONFIGURATION:

Operating System : Windows XP Professional with SP2

IDE : Microsoft Visual Studio .Net 2005

Database : MS-SQLSERVER 2005

Web Technology : Asp.Net

Code Behind : VB

Framework : Version 3.5


17/93

2.3 SOFTWARE DESCRIPTION

FRONT-END: ASP.NET

ASP.NET is a new way to program dynamic and interactive Web applications. ASP.NET

is a compiled environment that makes extensive use of the Microsoft.NET framework, and the

entire .NET platform is available to any ASP.NET application.

About ASP:

Microsoft Active Server Pages (ASP) is a server-side scripting technology .Any scripting

or programming language that is compliant with the Component Object Model (COM) can be

used to create Web server application.

Take a pure HTML file and add scripting code to it, so that one file contains both HTML

and, for example, Microsoft Visual Basic Scripting Edition (VBScript).That file has the file

extension .asp (instead of .html) and is accessed via HTTP request.

In the browser, a user enters the URL for the file. When the server receives the request, it

recognizes the extension; Microsoft Internet Information Services (IIS) treats the .asp file

differently from an .html file. Normally, a standard HTML document will be generated and sent

to the browser as a response; but other data, such as images or binary data, can be returned.

Fortunately we are not limited to dynamically generating and presenting date and time

information in the client browser or performing computations. We can also access COM

components to extend the functionality of our Web site.

With ASP we can use client-side scripts as well as server-side scripts. May be we want to

validate user input or access a database.ASP provides solution for transaction processing and

managing session state.


18/93

While ASP should not be used for implementing business logic, we can easily and

quickly create simple Web applications.

About ASP.Net

ASP.NET is a new way to program dynamic and interactive Web applications. There is

more in it than just a few new features. It is much more than ASP 4.0. ASP. NET is a new

programming framework for Web application. It is a compiled .NET-based environment that

makes extensive use of the .NET Framework.

Because it has evolved from ASP, ASP.NET looks very similar to its predecessor-but

only at first sight. Some items look very familiar, and they remind us of ASP. But concept like

Web Forms, Web Services, or Server Controls gives ASP.NET the power to build real Web

applications.

The .NET Framework Architecture

To really understand what makes ASP.NET more than just ASP 4.0we need to have a

look at the underlying .NET Framework architecture.

The .Net Framework is a managed, type-safe environment for developing and executing

applications. The .NET Framework manages all aspects of program execution like allocation of

memory for the storage of data and instructions, granting and denying permissions to the

application, managing execution of the application and reallocation of memory for resources that

are not needed. The .NET Framework is designed for cross-language compatibility.

The .NET Framework consists of two main components:

Common Language Runtime (CLR) Class Libraries


19/93

Common Language Runtime (CLR):

The CLR is described as the Execution Engine of .NET. It provides the environment

within which the programs run. Its this CLR that manages the execution of programs and

provides core services, such as code compilation, memory allocation, thread management and

garbage collection. Through the Common Type System (CTS), it enforces strict type safety and

it also ensures that the code is executed in a safe environment by enforcing code access security.

The software version .Net is actually the CLR version.

Working of the CLR

When the .NET program is compiled, the output of the compiler is not an executable file

but a file that contains a special type of code called the Microsoft Intermediate Language

(MSIL), which is a low level set of portable instructions that are independent of any specific

CPU. Its the job of the CLR to translate this Intermediate code into a executable code when the

program is executed making the program to run in any environment for which the CLR is

implemented. And thats how the .NET Framework achieves portability. This MSIL is turned

into executable code using JIT (Just in Time) compiler. When .NET programs are executed, the

CLR activates the JIT compiler. The JIT compiler converts MSIL into native code even though it

is compiled to native code but achieves the portability benefits of MSIL.

Class Libraries

Class library is the second major entity of the .NET Framework which is designed to

integrate with the CLR. This library gives the program access to runtime environment. The class

library consists of lots prewritten code that all the applications created in ASP.NET and Visual

Studio.Net will use. The code for all elements like forms, controls and the rest in ASP.NET

applications actually come from the class library.


20/93

BACK-END: Microsoft SQL Server

Microsoft SQL Server 2005 is a full-featured relational database management system

(RDBMS) that offers a variety of administrative tools to ease the burdens of database

development, maintenance and administration. The more frequently used tools are

Enterprise Manager Query Analyzer SQL Profiler Service Manager Data Transformation Services

Enterprise Manager is the main administrative console for SQL Server installations. It provides

you with a graphical "birds-eye" view of all of the SQL Server installations on your network.

You can perform high-level administrative functions that affect one or more servers, schedule

common maintenance tasks or create and modify the structure of individual databases.

Query Analyzer offers a quick and dirty method for performing queries against any of your

SQL Server databases. It's a great way to quickly pull information out of a database in response

to a user request, test queries before implementing them in other applications, create/modify

stored procedures and execute administrative tasks.

SQL Profiler provides a window into the inner workings of your database. You can monitor

many different event types and observe database performance in real time. SQL Profiler allows

you to capture and replay system "traces" that log various activities. It's a great tool for

optimizing databases with performance issues or troubleshooting particular problems.


21/93

Service Manager is used to control the MSSQLServer (the main SQL Server process), MSDTC

(Microsoft Distributed Transaction Coordinator) and SQLServerAgent processes. An icon for

this service normally resides in the system tray of machines running SQL Server. You can use

Service Manager to start, stop or pause any one of these services.

Data Transformation Services (DTS) provide an extremely flexible method for importing and

exporting data between a Microsoft SQL Server installation and a large variety of other formats.

The most commonly used DTS application is the "Import and Export Data" wizard found in the

SQL Server program group.

SQL Server Architecture

In Microsoft SQL Server, data is stored in databases. The data in a database is

organized into the logical components visible to users. A database is also physically

implemented as two or more files on disk.

When using a database, you work primarily with the logical components such as tables,

views, procedures, and users. The physical implementation of files is largely transparent.

Typically, only the database administrator needs to work with the physical implementation.

Each instance of SQL Server has four system databases (master, model, tempdb, and

msdb) and one or more user databases. Some organizations have only one user database,

containing all the data for their organization. Some organizations have different databases for

each group in their organization, and sometimes a database used by a single application. For

example, an organization could have one database for sales, one for payroll, one for a document

management application, and so on. Sometimes an application uses only one database; other

applications may access several databases.


22/93

It is not necessary to run multiple copies of the SQL Server database engine to allow

multiple users to access the databases on a server. An instance of the SQL Server is capable of

handling thousands of users working in multiple databases at the same time. Each instance of

SQL Server makes all databases in the instance available to all users that connect to the instance,

subject to the defined security permissions.

When connecting to an instance of SQL Server, your connection is associated with a

particular database on the server. This database is called the current database. You are usually

connected to a database defined as your default database by the system administrator.

SQL Server allows you to detach databases from an instance of SQL Server, then

reattach them to another instance, or even attach the database back to the same instance. If you

have a SQL Server database file, you can tell SQL Server when you connect to attach that

database file with a specific database name.


23/93


24/93

3.SYSTEM STUDY3.1EXISTING SYSTEM:

In the existing system, the project manager assigns the projects to the developers. The

developers develop the projects as per customer requirements. The project manager itself assigns

the developed applications to the tester for testing. In the testing phase, when the tester

encounters no. of bugs then he reports to the project manager and developer about the bug

information.

3.1.1DRAWBACKS:

The tester report which is called Bug Report is in the form of physical document. If thedocument is damaged then the total information about the bug will be lost.

The bug information is not stored in the database for future reference.


25/93

3.2PROPOSED SYSTEM:

3.2.1AIM:

The purpose of the Bug Tracking System is to test the application for the bugs and report

it to the project manager and developer. The main intention behind the Bug Tracking System is

that to track bugs and report them. Store the bug information with a unique id in the database for

future reference. So, this makes the job of handling the bugs easy.

3.2.2 OBJECTIVES:

The main objectives of the Bug Tracking System are:

Identifying the bugs in the developed application. No bug will be unfixed in the developed application. Not merely identifying the bugs but also providing the bug information. As soon as the bugs are identified. They are reported to the project manager and

developer.

To ensure that who needs to know about the bug can learn soon after it is reported.


26/93


27/93

4.SYSTEM DESIGN AND DEVELOPMENT

4.1FILE DESIGN:

While developing the software product we not only develop the executable files and the

source codes but also various types of documents such as user manual, software requirements

specification document, design document, test document. File design is the process for creating

such documents.

4.2INPUT DESIGN:

Input design is the process of covering the useroriented description of the input to

computer based business system. Input design is to create an input layout that is easy to flow and

does not induce operated error. Validation checks are to be built in the system to avoid any error

entities. The goal of designing the input data is to make the data entry as easier and free from

error as possible. An input design should specify to the user what to write and where to write.

4.3OUTPUT DESIGN:

The normal procedure is to design the outputs and in detail first and then work back to

the inputs. The outputs can be in the form operational documents or lengthy reports. The inputs

have to be validated, edited, organized and accepted by the system before producing the outputs.

The next stage is to determine the most appropriate medium for output consideration with the

suitability of the device to the particular application.


28/93

4.4CODE DESIGN:

Code is a group of characters used to identify data. Codes used in the system are essential

to improve the process efficiency and to produce correct input and output. The coding method

and standards are used in such a way that codes are easily expandable. The code has to be

designed with the uniform size and format simplicity meaningfulness. The code has to be

adequate for present and anticipated data processing for machine and human use.

4.5DATABASE DESIGN:

The purpose of database design is to identify the major modules in the software and

describe its components and interfaces for each major module for the users to understand.

Database design is a crucial factor in the performance of a package, both in terms of system

timings and in the case with which the system can be maintained or modified. The database has

been designed based upon the entity relationship model. The database has different tables in

which each table contain various data needed for the package.


29/93


30/93

5.SYSTEM TESTING AND IMPLEMENTATION

SYSTEM TESTING:

System testing is the stage of implementation, which is aimed at ensuring that the system

works accurately and efficiently before live operation commences. Testing is vital to the success

of the system. An elaborate testing of data is prepared and the system is tested using this test

data. While testing errors they are noted and corrections are made. The users are trained to

operate the developed system. Both hardware and software securities are made to run the

developed system successfully in future.

TESTING STEPS

Unit Testing Integration Testing Validation Testing Output Testing User Acceptance Testing

1) UNIT TESTINGUnit testing focuses verification efforts on the smallest unit of software design, the

module. This is also known as Module Testing. The modules are tested separately. This testing

is carried out during programming stage itself. In this testing step each Module is found to be

working satisfactorily as regard to the expected output from the module.


31/93

2) INTEGRATION TESTINGIntegration testing is a systematic technique for constructing tests to uncover errors

associated within the interface. In this project, all the modules combined, and then entire

program is tested as a whole. Thus in the integration testing step, all the errors uncovered are

corrected for the next testing step.

3) VALIDATION TESTINGValidation 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 are uncovered during integration testing, are corrected during this phase.

4) OUTPUT TESTINGAfter performing the validation testing, the next step is output testing of the proposed

system since no system could be useful if it does not produce required output in this specific

format. The output generated or displayed by the system under consideration is tested asking the

users about the format required by them. Here, the output is consideration into two ways: one is

on the screen and the other is in printed format.

The output format on the screen is found to be correct as the format designed according

to the user needs. For the hardcopy also the output comes out as specified by the user. Hence

output testing doesnt result in any connection in the system.


32/93

5) USER ACCEPTANCE TESTINGThe testing of the software began along with coding. Since the design was fully object-

oriented, first the interface was developed and tested. Then unit testing was done for every

module in the software for various inputs, such that each line of the code is at least once

executed. User acceptance of a system is key factor for the success of any system. The system

under consideration is tested for user acceptance by constantly keeping in touch with the

prospective system users, at time of developing and making for PROXY SERVER.

After all modules were coded the integration test was carried out. Some minor errors

were found in the output at the earlier stage and each of them was corrected. In the

implementation of user interface part no major errors was found. After the software was

completely developed, the testing was done. The outputs of the software were correct and

accurate during the time of demonstration after that no errors were reported.

MAINTENANCE

This phase of the software life cycle is time period in which the software performance

useful work. Maintenance activities involve making enhancement to software products, adopting

products to new environment and solving current problems. The software product enhancement

may involve producing new functional capabilities, improving user displays and modes

extraction, upgrading external documents or upgrading the performance characteristics of a

system.


33/93

In order to enhance the maintainability, various types of standards and guidelines are

developed during analysis phase. During architectural design, emphasis is done for clarity,

modularity and ease of modification. Also, during implementation care is taken for producing

software that is easy to understand and easy to modify. Maintenance can be done by

development member or any separate person. A person who developed will be familiar with

system so that maintenance actually will be easier than done by other person. The software is to

develop that enable further modification in the future to suit the changing work condition in the

organization.

The software maintenance is the important one in the software development process,

because more amount of money is spent for maintenance. All maintenance request s are through

a single or a group who will be familiar with the production program. Thus reporting must be

done where if an error is encountered, a complete description of circumstances leading to error

must be included.

Reporting is an important phase. It is unable to occur the effectiveness of the

maintenance techniques quality of production really costs. Coding style effects range from

nuisance errors detected and cleared during testing that can cause software failure, data side

effects can be limited through design documentation side effects can be reduced for the entire

configuration is reviewed.


34/93

SYSTEM IMPLEMENTATION:

The implementation of the system in the organization comes as the steps of the system

developed in general. This phase of the system consists of:

1. The developed program is tested with sample data.

2. Any error identified is corrected.

3. The files of the system are checked with the actual data.

4. A parallel run of the system is performed and if any calculation error is

present, it would be corrected

5. The user personals are trained.

6. Verified every required data in the database.

7. Checked out the time taken for each process.

The implementation is done in the correct or in the formal method to user satisfaction.

Such an implementation precedes the system for efficient and fast, which the developers like

most.

Implementation is a stage in the project where the theoretical design is turned into a

working system. If the implementation stage is not properly planned and controlled, it can cause

chaos. Thus it can be considered to be the most crucial stage in achieving a successful new

system and giving the users confidence that the new system will work and be effective and acc


35/93


36/93

6.CONCLUSION

The BUG TRACKING project has been successfully implemented using ASP.Net and

SQL Server. I am sure that this application will be very useful in maintaining the

communications between the employees of a software company. It plays a vital role in

maintaining the bug details identified during testing for future reference.


37/93


38/93

7.BIBLIOGRAPHYBOOKS REFERED:

1. Maxim Gurevich, System Analysis and Design.2. Richard Fairley, Software Engineering Concepts.3. Mridula Parihar, ASP.Net Bible.4. Bill Hamilton, Programming SQL Server 2005.5. Jeffrey R. Shapiro, SQL Server 2005.

WEBSITES REFERED:

www.vb.netheaven.com www.programmersresource.com www.dotnet.com www.123aspx.com


39/93


40/93

8.1DATA FLOW DIAGRAM

A Data Flow Diagram (DFD) is a graphical technique that depicts information flow and

the transforms that are applied as data move from input to output.

Data flow diagram is a logical model of a system. The model does not depend on

hardware, software, and data structure or file organization. It only shows the data flow between

modules to module of the entire system. Data flow diagrams can be completed using only four

notations as follows,

Data Flow: Data move in a specific direction from an origin to destination. The data flow is a

packet of data.

Process: People, procedures or devices that produce data. The physical component is not

identified.

Source or Destination of Data: External sources or destinations of data, which may be people

or organizations or other entities.

Data Source: Here a process references the data in the system


41/93

Context Level DFD for BTS

BTS

Tester

Projectmanager Developer


42/93

A1: User id, Password, Designation

First Level DFD for BTS

User Login

Process

File

Handler

D1 Userinfo

Projectmanager

Developer

Tester

A1

Pass

Fail


43/93

Second Level DFD for Project Manager

Projectmanager

Project info

Assigninfo

Change

passwordD1 Userinfo

NewPassword

User info

Display

Bugreport

D4 BuginfoBugid


44/93

Second Level DFD for Developer

Developer

Display

Assigned

Display

Buginfo

D4 Buginfo D1 Userinfo

Details Bugid

Change

Password

D2 Assigninfo


45/93

A2: Bug id, Details

Second Level DFD for Tester

Tester

Track

Bugs

D4 Buginfo

D1 Userinfo

View

Assign

projects

D3 Assigninfo

Change

Password

A2 NewPassword


46/93

Third Level DFD for Project Manager

Userinfo

Adduser

Delete

User

D 1 Userinfo

Userdetails

User

id UserDetails

Modify

User


47/93


Add

Project

Delete

Project

Modify

Project

Project

Details

Project

IdProjectDetails

D2 Projectinfo

Project

info


48/93


Assign

info

Assigning

Projects

Display

Projects

D3 Assigninfo

D2 Projectinfo


49/93

8.2TABLE STRUCTURE

1. Table Name: login

Field Name Type

USERNAME nvarchar(25)

PASSWORD nvarchar(25)

DESIGNATION varchar(25)

MAILID nvarchar(50)

2. Table Name: add1

Field Name Type

EMPLOYEE NAME varchar(25)

ADDRESS nvarchar(100)

PHONENO numeric(25)

GENDER varchar(25)

QUALIFICATION varchar(25)


PASSWORD nvarchar(25)



50/93

3. Table Name: add2

Field Name Type

PROJECTNAME nvarchar(25)

STATUS varchar(25)

LOCATION nvarchar(50)

DESCRIPTION nvarchar(200)

4. Table Name: assign

Field Name Type




SDATE Datetime

CDATE Datetime


51/93

5. Table Name: send1

Field Name Type

TOID nvarchar(50)

FROMID nvarchar(50)

MESSAGE nvarchar(500)

6. Table Name: buginfo

Field Name Type



BUGLOCATION nvarchar(100)

BUGDESCRIPTION nvarchar(500)

BUGSTATUS nvarchar(25)

OPERATINGSYSTEM nvarchar(25)

BUGID numeric(10)


52/93

8.3 SAMPLE CODINGSImports System.Data.OleDb

PartialClass Default2

Inherits System.Web.UI.Page

Dim con AsNew

OleDbConnection("Provider=SQLOLEDB.1;Password=123TRECstep;Persist Security

Info=True;User ID=sa;Initial Catalog=bugtracking;Data Source=192.168.2.2")

Dim cmd AsNew OleDbCommand

Dim re As OleDbDataReader

Dim ds As DataKey

Dim ad AsNew OleDbDataAdapter

ProtectedSub Button1_Click(ByVal sender AsObject, ByVal e As System.EventArgs)

Handles Button1.Click

Dim i As Int16

IfTextBox1.Text ""And TextBox2.Text ""Then

con.Open()

cmd = New OleDbCommand("select *from login", con)

re = cmd.ExecuteReader()While (re.Read())

IfTextBox1.Text = re.GetString(0) And TextBox2.Text = re.GetString(1) And

DropDownList1.Text = re.GetString(2) Then

IfDropDownList1.SelectedIndex = 0 Then

i = 1

ExitWhile

ElseIfDropDownList1.SelectedIndex = 1 Then

i = 2

ExitWhile

ElseIfDropDownList1.SelectedIndex = 2 Then

i = 3

ExitWhile

EndIf

Else


53/93

i = 0

EndIf

EndWhile

Ifi = 1 Then

Response.Redirect("projectmanager.aspx")

ElseIfi = 2 Then

Response.Redirect("developer.aspx")

ElseIfi = 3 Then

Response.Redirect("tester.aspx")

ElseIfi = 0 Then

TextBox1.Text = ""

TextBox2.Text = ""MsgBox("Invalid Username or Password", MsgBoxStyle.OkOnly)

EndIf

re.Close()

con.Close()

Else

MsgBox("Enter All The Details", MsgBoxStyle.Information, "ENTER ALL THE

DETAILS")

EndIf

EndSub



TextBox1.Text = ""

TextBox2.Text = ""

EndSub



Response.Redirect("welcome.aspx")

EndSub

EndClass


54/93

Imports System.Data.OleDb

Partial Class Default12


Dim con As New



Dim cmd As New OleDbCommand


Dim ds As DataKey

Dim ad As New OleDbDataAdapter

Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs)

Handles Button1.ClickIf TextBox1.Text "" And TextBox2.Text "" And TextBox3.Text "" And

TextBox4.Text "" Then

con.Open()

Dim i As Int16


re = cmd.ExecuteReader

While (re.Read())

If TextBox1.Text = re.GetString(0) And TextBox2.Text = re.GetString(1) Then

i = 0

Exit While

Else

i = 1

End If

End While

If i = 0 Then

cmd = New OleDbCommand("update login set PASSWORD='" & TextBox3.Text & "'

where USERNAME='" & TextBox1.Text & "'", con)

cmd.ExecuteNonQuery()

MsgBox("Password Changed", MsgBoxStyle.OkOnly, "PASSWORD CHANGED")

Else


55/93

MsgBox("Invalid Username & password", MsgBoxStyle.OkOnly, "INVALID

USERNAME & PASSWORD")

End If

re.Close()

con.Close()

Else

MsgBox("Enter All The Details", MsgBoxStyle.OkOnly, "ENTER ALL THE

DETAILS")

End If

End Sub


Handles Button2.ClickResponse.Redirect("projectmanager.aspx")

End Sub



TextBox1.Text = ""

TextBox2.Text = ""

TextBox3.Text = ""

TextBox4.Text = ""

End Sub

End Class


56/93

Imports System.Data.OleDb

Partial Class send1


Dim con As New



Dim cmd As New OleDbCommand


Dim ds As DataKey

Dim ad As New OleDbDataAdapter



TextBox1.Text = ""

End Sub



con.Open()

If TextBox1.Text "" Then

cmd = New OleDbCommand("insert into send1 values('" &

DropDownList1.SelectedValue & "','" & DropDownList2.SelectedValue & "','" &TextBox1.Text & "')", con)

cmd.ExecuteNonQuery()

MsgBox("Message sent", MsgBoxStyle.OkOnly, "MESSAGE SENT")

Else


57/93

MsgBox("Enter the Message", MsgBoxStyle.OkOnly, "ENTER THE MESSAGE")

End If

con.Close()

End Sub

Protected Sub LinkButton1_Click(ByVal sender As Object, ByVal e As System.EventArgs)

Handles LinkButton1.Click

con.Open()

DropDownList1.Items.Clear()

DropDownList2.Items.Clear()


re = cmd.ExecuteReader()

While (re.Read())

DropDownList1.Items.Add(re.GetValue(3))

End While

re.Close()

con.Close()

con.Open()


re = cmd.ExecuteReader()

While (re.Read())

DropDownList2.Items.Add(re.GetValue(3))

End While

re.Close()


58/93

con.Close()

End Sub



Response.Redirect("projectmanager.aspx")

End Sub

Protected Sub TextBox1_TextChanged(ByVal sender As Object, ByVal e As

System.EventArgs) Handles TextBox1.TextChanged

End Sub

End Class


59/93

8.4 SAMPLE INPUT/OUTPUT

WELCOME


60/93

ABOUT BUG TRACKING SYSTEM


61/93

PROJECT MANAGER LOGIN


62/93

PROJECT MANAGER


63/93

USER INFORMATION


64/93

ADD USER


65/93

MODIFY USER


66/93

DELETE USER


67/93

PROJECT INFORMATION


68/93

ADD PROJECT


69/93

MODIFY PROJECT


70/93

DELETE PROJECT


71/93

PROJECT ASSIGN INFO


72/93

SELF


73/93

INBOX


74/93

SEND


75/93

REPORTS


76/93

USER DATA


77/93

PROJECT DATA


78/93

BUG DATA


79/93

DEVELOPER LOGIN


80/93

DEVELOPER


81/93

VIEW PROJECT


82/93

BUG DETAILS


83/93

CHANGE BUG STATUS


84/93

.

SELF


85/93

INBOX


86/93

SEND


87/93

TESTER LOGIN


88/93

TESTER


89/93

VIEW PROJECT


90/93

POST BUGS


91/93

SELF


92/93

LOGIN


93/93

SEND

documentation) unaltered

Documents