Bug Tracking Project

Table of Contents
CHAPTER
CHAPTER 1 INTRODUCATION
1.1 Objective
1.2 Need
1.3 Scope
1.4 Application
1.5 Achievement
CHAPTER 2 SURVEY OF TECHNOLOGY
2.1 Windows OS
2.2 Java
2.3 Rational Rose
2.4 Netbeans
CHAPTER 3 REQUIREMENT ANALYSIS
3.1 Problem Definition
3.2 Specific Requirment
3.3 Planning and Scheduling
3.4 Software and Hardware Requirment
3.5 Preliminary product Description
3.6 Conceptual Model
3.6.1 Use Case Diagram
3.6.2 Activity Diagram
3.6.3 Class Diagram
3.6.4 Sequence Diagram
3.6.5 E-R Diagram
3.6.6 Data Flow Diagram
G.T.POLYTECHNIC COLLEGE, JAORA Page 1

CHAPTER 4 SYSTEM DESIGN
4.1 Procedural design
4.1.1 Logic Diagram
4.2 Test Cases
4.2.1 Admin
4.2.2 User
CHAPTER 5 IMPLEMENTATION
5.1 Coading
5.2 Testing Approaches
5.2.1 White Box
5.2.2 Black Box
5.3 Snapshot
CHAPTER RESULT AND DISCUSSION
6.1 Test Report
6.2 User Documentation
CHAPTER 7 CONCLUSION
7.1 Conclusion
7.2 Limitation
7.3 Future enhamncement
REFERENCES
GLOSSARY

CHAPTER-1

1. Introduction
1.1 Objective
The main objective of this system is develop flawless system, which is access real time
information from anywhere in the world, 24 hours a day 365 days in a year. Another aim is that
manage hundred of projects in multiple locations or just a few. The another main objective of this
system is track the all the defects or bugs in the project and make the project user friendly and bugs
free system.
1.2 Need
In any software development bugs are inevitable. Let it be in any kind of product bugs arise at
any phase of development. One has to take a great care in the proper maintenance and resolution of
the bugs. In the Existing system the bugs are not properly maintained and they are simply relied on
shared lists and email to monitor the bugs.
In this type of system it becomes difficult to track a bug if a bug is over looked then it may
cause tremendous errors in the next phase and can improve the cost of project whatever necessary
effort spent on the bug maintenance may not be worthy. So bug history has to be maintained
properly. And there is no efficient search technique.
One has to search the whole database for the details of particular bug which might have
occurred sometime earlier. It is both time consuming and error prone. And it is very difficult to
share the bug among several users as there is no proper maintenance of the bugs. In order to have an
efficient product bugs must be maintained properly and should be resolved in time both to reduce
time and money spent on the development.
1.3 Scope
 This system maintains the products, Bugs and bug Tracking. It has advantage of maintaining
bug history it stores all the details from bug origin to bug resolution.

 Each product can have versions for easy maintenance of the product and all the user of the
product is stored in the database. It provides the advantage of maintaining users to the bugs
and resolutions provided by them.
 Our System provides the searching based on status, priority, and operating system.
 It provides with user and bug hierarchy, which would be helpful in knowing the relation
between bugs and users allotted to the bug.
 It is provided with a fully authenticated system with password encryption. And has the
facility for storing attachments for a bug.
 One can keep a track of the bug in a product with much lower cost and effort.
 The most advantage of this system is maintaining log records which are helpful in knowing
any errors or misuse of the system by other users.
1.4 Application
This defect tracking system helps to track bug. There are three modules in this
tracking system, Administrator, Staff and Customer. The Administrator can login to
the app and can enter the details of staff, project, view bugs send from the customers.
The admin can also also assign work to staffs, view bug case flow status details, send
messages to customers using this bug tracking application. The staff can login to the
site using username and password. Then he/she can view the bugs assigned to them.
He can directly give solution message to customers or he/she 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/she is 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/she 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. This is how bug
tracking can be done with this application.

1.5 Achievement
Bug Tracking System for the bug tracking/reporting and reliability assessment. BT helps in
reporting the bug, assigning the bug to the developer for fixing, monitoring the progress of bug
fixing by various graphical/charting facility and status updates, providing reliability bug prediction
and bug complexity measurements, and distributing fixes to users/developers.

CHAPTER-2

SURVEY OF TECHNOLOGY
2.1 WindowsOS
Microsoft Windows, commonly referred to as Windows, is a group of

several proprietary graphical operating system families, all of which are developed
and marketed by Microsoft. Each family caters to a certain sector of the computing
industry. Active Microsoft Windows families include Windows NT and Windows
IoT; these may encompass subfamilies, (e.g. Windows Server or Windows Embedded
Compact) (Windows CE). Defunct Microsoft Windows families include Windows
9x, Windows Mobile, and Windows Phone.
Microsoft introduced an operating environment named Windows on November 20,

1985, as a graphical operating system shell for MS-DOS in response to the growing
interest in graphical user interfaces (GUIs).[5] Microsoft Windows came
to dominate the world's personal computer (PC) market with over 90% market share,
overtaking Mac OS, which had been introduced in 1984, while Microsoft has in 2020
lost its dominance of the consumer operating system market, with Windows down to
30%, lower than Apple's 31% mobile-only share (65% for desktop operating systems
only, i.e. "PCs" vs. Apple's 28% desktop share) in its home market, the US, and 32%
globally (77% for desktops), where Google's Android leads.
Apple came to see Windows as an unfair encroachment on their innovation in GUI

development as implemented on products such as the Lisa and Macintosh (eventually
settled in court in Microsoft's favor in 1993). On PCs, Windows is still the most
popular operating system in all countries. However, in 2014, Microsoft admitted
losing the majority of the overall operating system market to Android, because of the
massive growth in sales of Android smartphones. In 2014, the number of Windows
devices sold was less than 25% that of Android devices sold. This comparison,
however, may not be fully relevant, as the two operating systems traditionally target
different platforms. Still, numbers for server use of Windows (that are comparable to
competitors) show one third market share, similar to that for end user use.

As of October 2020, the most recent version of Windows for
PCs, tablets and embedded devices is Windows 10, version 20H2. The most recent
version for server computers is Windows Server, version 20H2. A specialized version
of Windows also runs on the Xbox One video game console.
2.2 Java
What is JAVA?
Java is an entire programming language resembling C or C++. It takes a sophisticated
programmer to create Java code. And it requires a sophisticated programmer to
maintain it. With Java, you can create complete applications. Or you can attach a
small group of instructions, a Java "applet" that improves your basic HTML. A Java
Applet can also cause text to change color when you roll over it. A game, a calendar,
a scrolling text banner can all be created with Java Applets. There are sometimes
compatibility problems between Java and various browsers, operating systems or
computers, and if not written correctly, it can be slow to load. Java is a powerful
programming language with excellent security, but you need to be aware of the
tradeoffs.
What is JSP?
Short for Java Server Page. A server-side technology, Java Server Pages are an
extension to the Java servlet technology that was developed by Sun. JSPs have
dynamic scripting capability that works in tandem with HTML code, separating the
page logic from the static elements -- the actual design and display of the page -- to
help make the HTML more functional(i.e. dynamic database queries). A JSP is
translated into Java servlet before being run, and it processes HTTP requests and
generates responses like any servlet. However, JSP technology provides a more
convenient way to code a servlet. Translation occurs the first time the application is
run. A JSP translator is triggered by the .jsp file name extension in a URL. JSPs are
fully interoperable with servlets. You can include output from a servlet or forward the
output to a servlet, and a servlet can include output from a JSP or forward output to a
JSP. JSPs are not restricted to any specific platform or server. It was orignially
created as an alternative to Microsoft's ASPs (Active Server Pages). Recently,
however, Microsoft has countered JSP technology with its own ASP.NET, part of
the .NET initiative.

What is JavaScript?
When new technologies start, they sometimes acquire names that will be confusing in
the future. That's the case with JavaScript. JavaScript is not 'Java'. JavaScript is a
simple programming language that was developed by Netscape that writes commands
to your browser when the HTML page is loaded. Note: you can have compatibility
issues with Java Script, especially in newer versions of Browsers.
What is Java?
Java is a simple, distributed object oriented programming language which provides
the security, High performance, robustness.
Java is a portable and Architectural neutral language which can be Interpreted.
Java is multithreaded and Dynamic language.
About Java
Java is a Programming language originally developed by James Gosling at Sun
Microsystems and released in 1995 as a core component of Sun Microsystems' Java
Platform. The language derives much of its Syntax from c and C++ but has a simpler
object Model and fewer low-level facilities. Java applications are typically compiled
to bytecode(class file) that can run on any Java Virtual machine (JVM) regardless of
computer architecture.
Why Software Developers Choose Java

Java with its versatilty, efficiency, and portability, Java has become invaluable to
developers by enabling them to:
• Write software on one platform and run it on virtually any other platform
• Create programs to run within a Web browser and Web services
• Develop server-side applications for online forums, stores, polls, HTML forms
processing, and more
• Combine applications or services using the Java language to create highly
customized applications or services
• Write powerful and efficient applications for mobile phones, remote processors,
low-cost consumer products, and practically any other device with a digital heartbeat.
Goals in creation of Java

There were five primary goals in the creation of the Java language
1. It should be "simple, object oriented".

2. It should be "robust and secure".
3. It should be "architecture neutral and portable".
4. It should execute with "high performance".
5. It should be "interpreted, threaded, and dynamic".
Architecture of Java
Java's architecture arises out of four distinct but interrelated technologies:
• The Java programming language

• The Java class file format
• The Java Application Programming Interface
• The Java virtual machine
When you write and run a Java program, you are tapping the power of these four
technologies. You express the program in source files written in the Java
programming language, compile the source to Java class files, and run the class files
on a Java virtual machine. When you write your program, you access system
resources (such as I/O, for example) by calling methods in the classes that implement
the Java Application Programming Interface, or Java API. As your program runs, it
fulfills your program's Java API calls by invoking methods in class files that
implement the Java API.
The Java Virtual Machine

At the heart of Java's network-orientation is the Java virtual machine, which supports
all three prongs of Java's network-oriented architecture: platform independence,
security, and network-mobility.
A Java virtual machine's main job is to load class files and execute the bytecodes they
contain. As you can see in Figure 1-3, the Java virtual machine contains a class
loader, which loads class files from both the program and the Java API. Only those
class files from the Java API that are actually needed by a running program are
loaded into the virtual machine. The bytecodes are executed in an execution engine.
Coding standard
Java suggests set of coding standard to follow while writing java program. Coding
standard helps author as well as others to better understand program. It reduce
amount of debugging time considerably. Basically coding standard suggests how to
name class, methods variables of different scope, package etc.

Writing a Java program
In the Java programming language, all source code is first written in plain text files
ending with the .java extension. Those source files are then compiled into .class files
by the javac compiler. A .class file does not contain code that is native to your
processor; it instead contains bytecodes — the machine language of the Java Virtual
Machine1 (Java VM). The java launcher tool then runs your application with an
instance of the Java Virtual Machine.
2.3 Rational Rose
Rational Rose is a software development environment for using model descriptions

and pattern languages to drive code development. Rational Rose is an IBM product.
The emphasis of the "rational" development environment is to design major software
engineering components at an abstract modeling level, initially unhindered by the
challenges of implementing components and relationships as code. Common
technologies driving rational development are APIs (Application Programming
Interfaces) to encapsulate interfaces from implementation, UML (Unified Modeling
Language) to express abstract entities and their relations, and IDEs (Integrated
Development Environments) to coordinate the various modeling and coding artifacts.
2.4 Netbeans
The NetBeans Profiler is a tool for the monitoring of Java applications: It helps
developers find memory leaks and optimize speed. Formerly downloaded separately,
it is integrated into the core IDE since version 6.0. The Profiler is based on a Sun
Laboratories research project that was named JFluid. That research uncovered
specific techniques that can be used to lower the overhead of profiling a Java
application. One of those techniques is dynamic bytecode instrumentation, which is
particularly useful for profiling large Java applications. Using dynamic bytecode
instrumentation and additional algorithms, the NetBeans Profiler is able to obtain
runtime information on applications that are too large or complex for other profilers.

NetBeans also support Profiling Points that let you profile precise points of execution
and measure execution time.
CHAPTER 3

REQUIREMENT ANALYSIS
3.1 Problem Definition
Bug Tracking System is an ideal solution to track the bugs of a product, solution or an
application. Bug Tracking System allows individual or groups of developers to keep track of
outstanding bugs in their product effectively. This can also be called as Defect Tracking System.
The Bug Tracking System can dramatically increase the productivity and accountability of
individual employees by providing a documented work flow and positive feedback for good
performance.
For many years, bug-tracking mechanism is employed only in some of the large software
development houses. Most of the others never bothered with bug tracking at all, and instead simply
relied on shared lists and email to monitor the status of defects. This procedure is error-prone and
tends to cause those bugs judged least significant by developers to be dropped or ignored.
In any software development bugs are inevitable. Let it be any kind of product bugs arise to any
phase of development. One has to take a great care in proper maintenance and resolution of the
bugs. In the Existing system the bugs are not properly maintained and they are simply relied on
shared lists and email to monitor the bugs. In this type of system it becomes difficult to track a bug
if a bug is over looked then it may be cause tremendous errors in the next phase and can improve
the cost of project what ever necessary effort spent on the bug maintenance may not be worthy. So
bug history has to be maintained properly. And there is no efficient search technique. One has to
search the whole database for the details of particular bug which might have occurred some time
earlier. It is both time consuming and error prone. And it is very difficult to share the bug among
several users as there is no proper maintenance of the bugs.
In order to have an efficient product bugs must be maintained properly and should be resolved
in time both to reduce time and money spent on the development.

3.2 Specific Requirment
The main focus of the analysis phase of Software development is on “What needs to be
done”. The objects discovered during the analysis can serve as the framework or Design. The
class’s attributes, methods and association identified during analysis must be designed for
implementation language. New classes must be introduced to store intermediate results during the
program execution.
This system maintains the products, Bugs and bug tracking. It has advantage of maintaining
bug history it stores all the details from bug origin to bug resolution. Each product can have
versions for easy maintenance of the product and all the user of the product is stored in the database.
It provides the advantage of maintaining users to the bugs and resolutions provided by them. Our
System provides the searching based on status, priority, and operating system. It provides with user
and bug hierarchy, which would be helpful in knowing the relation between bugs and users allotted
to the bug. It is provided with a fully authenticated system with password encryption. And has the
facility for storing attachments for a bug. One can keep a track of the bug in a product with much
lower cost and effort. The most advantage of this system is maintaining log records which are
helpful in knowing any errors or misuse of the system by other users.
3.3 Planning and Scheduling
PLANNING TIME(in days)

Requirement Gathering 15
Analysis 10
Designing 20
Coding 35
Testing 10

Gantt Chart
Requirement Analysis Designing Coding Testing
Gathering
0 15 25 45 80 90
3.4 Software and Hardware Requirment
3.4.1 Software Requirements
A set of programs associated with the operation of a computer is called software. Software is the
part of the computer system which enables the user to interact with several physical hardware
devices.The minimum software requirement specifications for developing this project are as
follows:
Operating System Windows 7,8,10
Designing Tools Rational Rose
Development Tools Net Beans IDE 8.0
Language Java, JSP
3.4.2 Hardware Requirement Specification
.The minimum hardware requirement specification for developing this project is as follows:
Processor : Pentium IV
RAM : 512 MB RAM

Hard Disk : 20GB
3.5 Preliminaryproduct Description
Module Description
3.5.1 Employee
Employees are of two types, developers and testers. Developers are used to develop program
and open bugs where as testers resolve the bugs and save to the database.
3.5.2 Manager
Manager takes care of recruitment of employees and the management of employees in the
project and monitors the completion of project
3.5.3 Administrator
Administrator is a person who will take care of all registration status, acceptance of new
bugs, and many other tasks to reduce burden on employee.
One has to take a great care in the proper maintenance and resolution of the bugs. In the
Existing system the bugs are not properly maintained and they are simply relied on shared lists and
email to monitor the bugs.
In this type of system it becomes difficult to track a bug if a bug is over looked then it may
cause tremendous errors in the next phase and can improve the cost of project whatever necessary
effort spent on the bug maintenance may not be worthy. So bug history has to be maintained
properly. And there is no efficient search technique.
One has to search the whole database for the details of particular bug which might have
occurred sometime earlier. It is both time consuming and error prone. And it is very difficult to
share the bug among several users as there is no proper maintenance of the bugs. In order to have an
efficient product bugs must be maintained properly and should be resolved in time both to reduce
time and money spent on the development.

3.6 Conceptual Model
3.6.1 Use Case Diagram
A use case diagram is a diagram that shows a set of use cases and actors and relationships.
Use case Diagrams represent the functionality of the system from a user’s point of view. Use
cases are used during requirements elicitation and analysis to represent the functionality of the
system .Use cases focus on the behavior of the system from external point of view.
<<include>>
Validation Login
Project
Administrator
Department
Employee
Monitor
Manager
Developer Tester
Bugs
Testplan
Overall Use case Diagram

Login
Permission
Project
Administrator
Department
Developers
Create Employee
Testers
Create Manager
Logout
Administrator Use case

Register
Login
Project
Department
Manager
Monitor
Developers
Employees
Testers
Logout
Manager Use Case

Register
Login
Project
Employee
Bugs
Testplan
Developer Tester
Logout
Employee use case

3.6.2 Activity Diagram
Activity Diagram
 An activity diagram shows the flow from activity to activity. An activity is an ongoing non-atomic
execution within a state machine.
 Activities ultimately result in some action, which is made up of executable atomic computations
that result in a change in state of the system or the return of a value.
Activity diagrams commonly contain
 Activity states and action states

 Transitions
 Objects

Like all other diagrams, activity diagrams may contain notes and constrains
Login Process
Providing
Credentials
Retry
Validation
<<No>>
<<YES>>
Services
Login Activity Diagram

Registration Process
Providing
examination
Provide
<<YES>> Credentials
admin validation
<<NO>>
Invalidate
details
Registration Activity Diagram
Manager Process
Login
Validation
Projects Monitor Department
Create/upd
ate/delete
Logout
Manager Activity Diagram

Administrator Process
Login
validation
Employee Manager Projects Department
Create/upd
ate/delete
View
Permission
Logout
Administrator Process

Employee Process
Employee
Developer Tester
Login
Bugs Testplan
validation
Projects update delete
create create update delete
select
Login
Rectify
Logout
Employee Process

3.6.3 Class Diagram
The class diagram is the main building block in object oriented modeling. They are being used
both for general conceptual modeling of the systematic of the application, and for detailed modeling
translating the models into programming code.
The classes in a class diagram represent both the main objects and or interactions in the
application and the objects to be programmed. In the class diagram these classes are represented
with boxes which contain three parts:
 The upper part holds the name of the class

 The middle part contains the attributes of the class, and
 The bottom part gives the methods or operations the class can take or undertake
An Activity Diagram shows the flow from activity to activity.
An activity is an ongoing non- atomic execution within a state machine.

Departement
ID : string
deptname : string
1..1 type : string
date : date
1..n
1..1
assigndept()
view() Manager/HR
Monitor
close() ID : string
ID : string
username : string
project : string
password : string
Projects startdate : date
dept : string
ID : string enddate : date
email : string
name : string 1..1 1..n type : string
date : date
type : string monitorreport : string
date : date create()
1..1 update()
1..n getprojects()
create() delete()
create()
update() view()
update()
delete() close()
delete()
1..1
view() view()
close() close()
1..n
1..1 1..1 1..1
Registration
1..1
1..n
Employees
ID : String 1..1
username : string Admin
1..n 1..1
password : string Permission : string
email : string Login Credentials : string
1..n dept : string Username : string
date : date password : string Create()
bugs : string 1..n 1..1 changepassword : void save()
testplan : string 1..1 update()
1..1
save() delete()
getprojects() cancel() cancel()
createbugs() close() close()
createtestplan() validation() view()
update() search()
view()
close() 1..n
1..1
Developers Testers
Class Diagram

3.6.4 Sequence Diagram
Sequence Diagram
 An interaction diagram shows an interaction, consisting of a set of objects and their

relationships, including the messages that may be dispatched among them.
 A sequence diagram is an interaction diagram that emphasizes the time ordering of
messages.
 Graphically, a sequence diagram is a table that shows objects arranged along x-axis and
messages, ordered in increasing time, along the y-axis.
Contents
 Sequence diagrams commonly contain the following:

 Objects
 Links
 Messages
Like all other diagrams, sequence diagrams may contain notes and constrains.

Login Permission Manager Employee Department Project
: Administrator
1: loginrequest()
validation
response()
2: Create()
response()
3: create()
valid()
confirmation()
4: create()
valid()
confirmation()
5: view()
6: view()
Administration Sequence Diagram

Register Login Department Project Monitor
: Manager
1: Fill up the details

submit()
verfication()
confirmation()
3: login request()
validation
response()
4: create()
5: allot department()
response()
6: Allot project()
response()
7: monitor
response()
Manager Sequence

Register Login Project Bugs Test Plan
: Employee
1:Fill up the details
Developer()
Verfication
Confirmation()
Tester()
Verification
Confirmation()
2: Login Request()
Validation
response()
3: employee selects alloted project()
response()
4: Tester identify bugs()

5: tester develop testplan
submit to developer
submit to developer
employee rectify bugs
confirmation()
Employee Sequence

3.6.5 E-R Diagram
Entity Relationship Diagrams (ERDs) illustrate the logical structure of databases. An entity-
relationship (ER) diagram is a specialized graphic that illustrates the interrelationships between
entities in a database.
ER diagrams often use symbols to represent three different types of information. Boxes are
commonly used to represent entities. Diamonds are normally used to represent relationships and
ovals are used to represent attributes.
Entity relationship diagrams are a way to represent the structure and layout of a database. It is
used frequently to describe the database schema. ER diagrams are very useful as provide a good
conceptual view of any database, regardless of the underlying hardware and software.

Employee
Department
ECode: INTEGER Project
Dept_Number: INTEGER
FName: VARCHAR(45) Project_Number: INTEGER
LName: VARCHAR(45) Dept_Name: VARCHAR(45)
Gender: VARCHAR(45) Dept_Location: VARCHAR(45) Project_Name: VARCHAR(45)
DOB: DATE Project_Description: VARCHAR(45)
Qualification: VARCHAR(45) SDate: DATE
Address: VARCHAR(100) Duration: INTEGER
Phone_Number: INTEGER Client_Name: VARCHAR(45)
Assign_Project
Mobile: INTEGER Client_Address: VARCHAR(45)
SNo: INTEGER Client_Phone: VARCHAR(45)
EMail_Id: VARCHAR(45)
DOJ: DATE Project_Name: VARCHAR(45) Client_EMail: VARCHAR(45)
Basic_Salary: INTEGER User_Id: VARCHAR(45) Project_Lead: VARCHAR(45)
DNo: INTEGER Role: VARCHAR(45) Dept_Name: VARCHAR(45)
Login_Id: VARCHAR(45)
Password: VARCHAR(45)
Marital_Status: VARCHAR(45)
Hint_Question: VARCHAR(45)
Bug_Report
Hint_Answer: VARCHAR(45)
Role: VARCHAR(45) Bug_No: INTEGER
Bug_Name: VARCHAR(45)
Bug_Type: VARCHAR(45)
Bug_Level: VARCHAR(45)
Priority: VARCHAR(45)
Project_Name: VARCHAR(45)
Tester_Code: VARCHAR(45)
Bug_Date: VARCHAR(45)
E_Code: VARCHAR(45)
Status: VARCHAR(45)
Bug_Rectified_Date: VARCHAR(45)
Stauts: VARCHAR(45)
ER-Diagram
3.6.6 Data Flow Diagram
Data Flow Diagram
A Data Flow Diagram (DFD) is a graphical representation of the “flow” of data through an
information system. It can also be used for the visualization of data processing (structured design).
There are two types of DFDs. They are:
 Context Level DFD
 Top Level DFD
Context Level DFD
In the Context Level the whole system is shown as a single process.
 No data stores are shown.

 Inputs to the overall system are shown together with data sources (as External entities).
 Outputs from the overall system are shown together with their destinations (as External
entities).
Context Level DFD
Top Level DFD
The Top Level DFD gives the overview of the whole system identifying the major system
processes and data flow. This level focuses on the single process that is drawn in the context
diagram by ‘Zooming in’ on its contents and illustrates what it does in more detail.

Top Level DFD

CHAPTER 4

SYSTEM DESIGN
4.1 Procedural design
The main focus of the analysis phase of Software development is on “What needs to be done”.
The objects discovered during the analysis can serve as the framework or Design. The class’s
attributes, methods and association identified during analysis must be designed for implementation
language. New classes must be introduced to store intermediate results during the program
execution.
Emphasis shifts from the application domain of implementation and computer such as user
interfaces or view layer and access layer. During analysis, we look at the physical entities or
business objects in the system, that is, which players and how they cooperate to do the work of the
application. These objects represent tangible elements of the business.
During the Design phase, we elevate the model into logical entities, some of which might relate
more to the computer domain as people or employees. Here his goal is to design the classes that we
need to implement the system the difference is that, at this level we focus on the view and access
classes, such as how to maintain information or the best way o interact with a user or present
information.
Design process:
During the design phase the classes identified in object-oriented analysis Must be revisited with
a shift focus to their implementation. New classes or attribute and Methods must be an added for
implementation purposes and user interfaces.
The following are some of the vies of software design life cycle. They are
 Data Flow Diagrams

 UML Diagrams
 Data Base Design

4.1.1 Logic Diagram
For our project Bug Tracking, we refer Spiral model. The Spiral Life Cycle Model is a
type of iterative software development model which is generally implemented in high risk
project .It was first proposed by Boehm in this system development method, we combine the
features of both, waterfall model and prototype model. In Spiral model we can arrange all the
activities in the form of a Spiral. Each loop in a Spiral represents a development phase (and
we can have any number of loops according to the project). Each loop has four sections or
quadrants:
1. To determine the objectives, alternatives and constraints. We try to understand the

product objectives, alternatives in design and constraints imposed because of cost,
Technology, schedule, etc.
2. Risk analysis and evaluation of alternatives. Here we try to find which other
approaches can be implemented in order to fulfill the identified constraints.
Operational and technical issues are addressed here. Risk mitigation is in focus in
this phase. And evaluation of all these factors determines future action.
3. Execution of that phase of development. In this phase we develop the planned product.
Testing is also done. In order to do development, waterfall or incremental approach can
be implemented.
4. Planning the next phase. Here we review the progress and judge it considering

Spiral Model
Advantage of Spiral Model
1) Spiral Life Cycle Model is one of the most flexible SDLC models in place. Development
phases can be determined by he project manager, according to the Complexity of
the project.
2) Project monitoring is very easy and effective. Each phase, as well as each loop,
Requires a review from concerned people. This makes the model more transparent.
3) Risk management is one of the in-built features of the model. Which makes it extra
attractive compared to other model.
4) Change can be introduced letter in the life cycle as well. And coping with these changes
aren’t a very headache for the project manager.

2. Disadvantage of Spiral Model
1. The Spiral Model is much more complex than other SDLC models.
2. Spiral Model is not suitable for small projects as it is expensive.
3. As a number of phases is unknown at the start of the project, so time estimation is
very difficult.
4.2 Test Cases
4.2.1 Admin
Levels of Testing
Module1 Module2 Module3
Units Units Units
i/p Integration o/p i/p Integration o/p
System Testing: Presentation + business +Databases
UAT: user acceptance testing
STLC (SOFTWARE TESTING LIFE CYCLE)

Test Planning:
1. Objective of testing,
2. Areas that need to be tested,
3. Areas that should not be tested,
4. Scheduling Resource Planning,
5. Areas to be automated, various testing tools used
Test Development: 1. Test case Development (check list)
2. Test Procedure preparation. (Description of the test cases)
Test Execution: 1. Implementation of test cases. Observing the result.

Result Analysis: 1. Expected value: is nothing but expected behavior
Of application.
2. Actual value: is nothing but actual behavior of the
application
Bug Tracing: Collect all the failed cases, prepare documents.

Reporting: Prepare document (status of the application)
TCD (Test Case Document)
Test Case Document Contains
 Test Scope (or) Test objective

 Test Scenario
 Test Procedure
 Test case
This is the sample test case document for the Academic details of student project:
Test scope
 Test coverage is provided for the screen “ Academic status entry” form of a student
module of university management system application

 Areas of the application to be tested
Test Scenario
 When the office personals use this screen for the marks entry, calculate the status details,
saving the information on student’s basis and quit the form.
Test Procedure
 The procedure for testing this screen is planned in such a way that the data entry, status
calculation functionality, saving and quitting operations are tested in terms of Gui testing,
Positive testing, Negative testing using the corresponding Gui test cases, Positive test
cases, Negative test cases respectively
4.2.2 User
Test Cases
 Template for Test Case
T.C.No Description Exp Act Result
1 Check Status If condition is true No template Yes
of Bug Tracking But input Wrong
Guidelines for Test Cases
1. GUI Test Cases
 Total no of features that need to be check

 Look & Feel
 Look for Default values if at all any (date & Time, if at all any require)
 Look for spell check
Example for GUI Test cases

T.C.
Actual
No Description Expected value value Result
The Bug Status screen True Yes

Check for all the features in
1 must contain all the
the screen
features
Check for the alignment of The alignment should be True Yes
2 the objects as per in proper way of
the validations Bug Tracking
2. Positive Test Cases
 The positive flow of the functionality must be considered

 Valid inputs must be used for testing
 Must have the positive perception to verify whether the requirements are justified.
Example for Positive Test cases
T.C. Description Expected value Actual Result

value
No
1 Check for the Bug date Time The date and time of the Yes True
system must be displayed
Auto Display
2 Enter the valid user id into It should accept No False
the user id field
3. Negative Test Cases

 Must have negative perception.
 Invalid inputs must be used for test.
Example for Negative Test cases
T.C. Description Expected value Actual Result
No value
1 Try to modify the information Modification should not Accept True
in date and time be allow
2 Enter invalid data in to the It should not accept Reject False
login details form, click on invalid data, save
Save should not allow

CHAPTER 5

IMPLEMENTATION
5.1 Coading
A.HomePage
<html>
<jsp:include page="./Header.jsp" />
<body><form>
<br><br><br><br><br>
<center><font face="arial narrow"><b> This is Admin Page</center>
<br><br><br><br><br><br><br>
</form>
</body>
<jsp:include page="./footer.jsp" />
</html>
B.User Login
.<html>
<head>
<title>Login.html</title>
<meta http-equiv="keywords" content="keyword1,keyword2,keyword3">
<meta http-equiv="description" content="this is my page">
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">

<script type="text/javascript" language="javascrpt">
function check()
{
if(testerForm.bug_name.value=='')
{

window.alert("Bug Name is empty !");
return false;
}
if(testerForm.bug_type.value=='')
{
window.alert("Bug Type is empty !");
return false;
}
if(testerForm.bug_level.value=='')
{
window.alert("Bug Level is empty !");
return false;
}
if(testerForm.priority.value=='')
{
window.alert("Bug Priority is empty !");
return false;
}
if(testerForm.tester_code.value=='')
{
window.alert("Tester code is empty !");
return false;
}
if(testerForm.bug_date.value=='')
{
window.alert("Bug Date is empty !");

return false;
}
if(testerForm.e_code.value=="select")
{
window.alert("Employee Code is empty !");
return false;
}
if(testerForm.status.value=="select")
{
window.alert("Select Status !");
return false;
}
}
</script>
<script LANGUAGE="Javascript" src="dateget.js">
</script>
</head>
<body bgcolor="">
<form name="testerForm" action="AssignBug" onSubmit="return check()" method="post">
<br>
<center>
<h5 align="center"><font color="red">
<%
HttpSession hs=request.getSession();
String s1=(String)hs.getAttribute("userid");
if(request.getParameter("msg")!=null)

{ %>
<%=request.getParameter("msg")%>
<%}
%>
</font></h5>
<br> <h3><font color="#FBB117">    Assign Bug</font></h3>
<table border="0" cellpadding="2" >
<tr><td align="right"><font>Bug_Name</font></td><td><input type="text"
name="bug_name"></td></tr>
<tr><td align="right"><font>Bug_type</font></td><td><input type="text"
name="bug_type"></td></tr>
<tr><td align="right"><font>Bug_level</font></td><td><input type="text"
name="bug_level"></td></tr>
<tr><td align="right"><font>Priority</font></td><td><input type="text"
name="priority"></td></tr>
<tr><td align="right"><font>Project Name</font></td><td>
<%
ServletContext sc=getServletContext();
String driver=sc.getInitParameter("drivername");
String url=sc.getInitParameter("url");
String uname=sc.getInitParameter("username");
String pwd=sc.getInitParameter("password");
try{
Class.forName(driver);
Connection con=DriverManager.getConnection(url,uname,pwd);
System.out.println(".......11........");
ResultSet rs,rs1;

PreparedStatement pstmt=con.prepareStatement("select loginid from
employee_details");
rs=pstmt.executeQuery();
PreparedStatement pstmt1=con.prepareStatement("select project_name

from project_details");
rs1=pstmt1.executeQuery();
%>
<select name="pname">
<%
while(rs1.next())
{
%>
<option><%=rs1.getString(1)%></option>
<%
}//while
%>
</select>
<tr><td align="right"><font>Tester Code</font></td><td> <input type="text"
name="tester_code" value=<%=s1%> readonly></td></tr>
<tr><td align="right"><font>Bug Date</font></td><td> <input type="text"
name="bug_date"><a href="javascript:show_calendar('document.testerForm.bug_date',
document.testerForm.bug_date.value);">date</a>
</td></tr>
<tr><td align="right"><font>Employee code</font></td><td>
<select name="e_code">
<option value="select">---select---</option>
<%
while(rs.next())

{
%>
<option><%=rs.getString(1)%></option>
<%
}//while
}
catch(Exception e)
{
e.printStackTrace();
}
%>
</select>           &nbsp
;
</td></tr>
<tr><td align="right"><font>Status</font></td><td>
<select name="status">
<option value="select">---select---</option>
<option>open</option>
<option>close</option>
</select>
</td></tr>
<tr><td align="center" colspan="2"><input type="submit"
value="submit"></td></tr>
</table>

</center>
</form>
</body>
<jsp:include page="./footer.jsp" />
</html>
<jsp:include flush="true" page="Header.jsp"></jsp:include>
<%@ page language="java" %>
<%@ page session="true" %>
<%@ page import="java.sql.*,java.io.*,java.util.Random"%>
<HTML>
<HEAD>
<LINK href="styles.css" type="text/css" rel="stylesheet">
<script LANGUAGE="Javascript" SRC="Images/validate.js"></script>
<title>Adminresponse</title>
<script language="javascript">
function Checkfiles()
{
var fup = document.getElementById('my_file_element').value;

alert(fup);
if(fup=="")
{
alert("Upload at least one file");
document.getElementById('my_file_element').focus();
return false;

}
else if(fup!="")
{
alert("Not null");
var fileName = fup;
var ext = fileName.substring(fileName.lastIndexOf('.') + 1);

alert(ext);
if(ext == "gif" || ext == "GIF" || ext == "JPEG" || ext == "jpeg" || ext == "jpg" || ext == "JPG")
{
alert("correct format");
return true;
else
alert("Upload Gif or Jpg images only");

document.getElementById('my_file_element').focus();
return false;
}
return false;
}

}</script>
</HEAD>
<body class="SC">
<form name="get ElementById">
<h3 align=center>View Project</h3>
<%
/*Declaration of variables*/
Connection con;
PreparedStatement pstmt;
ResultSet rs=null;
String pid,pname,description,date,duration,name,address,phone,email,plead,deptname;
try
{
Class.forName("com.mysql.jdbc.Driver");
con=DriverManager.getConnection("jdbc:mysql://localhost:3306/bts", "root", "igen");
pstmt=con.prepareStatement("select * from project_details");
rs=pstmt.executeQuery();
}
catch(Exception e)
{
e.printStackTrace();
}
if(rs!=null)

{
%>
<br>
<table class=notebook align=center>
<tr class=row_title>
<th align="center">ProjectName</th>
<th align="center">Submission Date</th>
<th align="center">Duration</th>
<th align="center">ClientName</th>
<th align="center">ClientAddress</th>
<th align="center">PhoneNo</th>
<th align="center">EmailId</th>
<th align="center">ProjectLead</th>
<th align="center">DeptName</th>
<th align="center">Delete</th>
<%
int DisRow=0;
/*Getting the values from the database*/
while(rs.next())
{
pid=rs.getString("project_no");
pname=rs.getString("project_name");
description=rs.getString("project_description");
date=rs.getString("sdate");
duration=rs.getString("duration");
name=rs.getString("clientname");

address=rs.getString("clientaddress");
phone=rs.getString("clientphone");
email=rs.getString("clientemail");
plead=rs.getString("projectlead");
deptname=rs.getString("deptname");
DisRow++;
%>
<tr class= <%=(DisRow%2!=0)? "row_even" : "row_odd"%>>
<td align="center"><%=pname%></td>
<td align="center"><%=date%></td>
<td align="center"><%=duration%></td>
<td align="center"><%=name%></td>
<td align="center"><%=address%></td>
<td align="center"><%=phone%></td>
<td align="center"><%=email%></td>
<td align="center"><%=plead%></td>
<td align="center"><%=deptname%></td>
<td align="center"><a href="DelProj?pid=<%=pid%>">Delete</a></td>
<%
}
rs.close();
if(DisRow==0)
{
%>
<tr><th colspan=5>No Records found</th></tr>
<%

}
}
%>
</table>
<br><br><br>
</BODY>
<jsp:include flush="true" page="footer.jsp"></jsp:include>
</HTML>
C.Admin Login Page
<html>
<body bgcolor="white">
<form>
<table width="100%">
<tr>
<td align=""><img src="./Images/header.jpeg" height="120"></img></td>
<td align=""><font face="arial narrow" size="5px" color="orange"><b> Defect Tracking
System</b></font></td>
</tr>
<tr>
<%
HttpSession hs=request.getSession();
String uname=(String)hs.getAttribute("userid");
String role=(String)hs.getAttribute("role");
%>
<td align="right" valign="bottom" colspan=2>
<b> <%if(role.equals("admin")){%>Welcome,   Admin<%} else
{%>Welcome,  <%=uname%> <%} %> </b>

<b>[ <%if(role.equals("admin")){%><a href="./AdminHome.jsp"><%} else
if(role.equals("Tester")){%><a href="./TesterHome.jsp?cat=Tester"><%} else
if(role.equals("Developer")){%><a href="./DeveloperHome.jsp?cat=Developer&uname=<
%=uname%>"><%}else if(role.equals("HRManager")){%><a href="./ManagerHome.jsp?
cat=HrManager&uname=<%=uname%>"><%} %><font
color="#FBC61">home</font></a> ]</b>
<%if(role!="user"){%><b>[ <a href="./logout.jsp"><font color="#FBC61"
size="3px">logout</font></a> ]</b><%} %>
</td>
</tr>
</table>
<script type="text/javascript">
sfHover = function() {
var sfEls = document.getElementById("nav").getElementsByTagName("LI");
for (var i=0; i<sfEls.length; i++) {
sfEls[i].onmouseover=function() {
this.className+=" over";
}
sfEls[i].onmouseout=function() {
this.className=this.className.replace(new RegExp(" over\\b"), "");
}
}
}
if (window.attachEvent) window.attachEvent("onload", sfHover);
</script>

<style type="text/css">
ul#nav, ul#nav ul {
margin: 0;
padding: 0px;
list-style: none;
ul#nav li {
position: relative;
float: left;
width:140px;
font-size: 12px;
#nav li ul {
position: absolute;
margin-left: -999em; /* hide menu from view */
top: 20;
left:0;
}

/* Styles for Menu Items */
ul#nav li a {
display: block;
text-decoration: none;
color:"black";
padding: 2px;
border: 1px solid #ccc;
min-height:0;
}
/* commented backslash mac hiding hack \*/
* html ul#nav li a {height:1%; position:relative;}
/* end hack */
/* this sets all hovered lists to black */

#nav li:hover a,#nav li.over a,
#nav li:hover li a:hover,#nav li.over li a:hover {
color: #fff;
background-color: black;}
/* set dropdown to default */

#nav li:hover li a,#nav li.over li a {
color: black;
background-color:silver; */
}
#nav li ul li a { padding: 2px 2px; } /* Sub Menu Styles */
#nav li:hover ul,#nav li.over ul {margin-left:0; } /* show menu*/

</style>
<body bgcolor="white">
<form>
<hr>
<table border=0 align=right>

<tr><td>
<font size="3px">
<ul id="nav">
<li><a href="#">Open</a>
<ul id="nav">
<li><a href="./AssignBug.jsp?cat=Tester">Bug Report</a></li>
<li><a href="./ViewBugs1.jsp?cat=Tester">View Bugs</a></li>
<li><a href="./EditProfile.jsp?cat=Tester">Edit Profile</a></li>
<li><a href="./Recchange_pass.jsp?cat=Tester">Change Password</a></li>
</ul>
</li>
</ul>
</font>
</td></tr>
</table>
<br

</form>
</body>
</html>
5.2 Testing Approaches
Software Testing is the process used to help identify the correctness, completeness,
security and quality of developed computer software. Testing is a process of technical
investigation, performed on behalf of stakeholders, that is intended to reveal quality-related
information about the product with respect to the context in which it is intended to operate. In
general, software engineers distinguish software faults from software failures. Our project"
Defect Tracking System” is tested with the following testing methodologies.
The test process begins by developing a comprehensive plan to test the general
functionality and special features on a variety of platform combinations. Strict quality control
procedures are used. The process verifies that the application meets the requirements specified in
the system requirements document and is bug free. The following are the considerations used to
develop the framework for developing the test methodologies.
The process of executing a system with the intent of finding an error. Testing is defined
as the process in which defects are identified, isolated, subjected for rectification and ensured
that product is defect free in order to produce the quality product and hence customer
satisfaction.

Testing
5.2.1 White Box
 Testing Methodologies
 Black box Testing:
 White box Testing.
 Gray Box Testing.
 Levels of Testing
 Unit Testing.
 Module Testing.
 Integration Testing.
 System Testing.
 User Acceptance Testing.
 Types Of Testing
 Smoke Testing.
 Sanitary Testing.
 Regression Testing.
 Re-Testing.
 Static Testing.
 Dynamic Testing.
 Alpha-Testing.
 Beta-Testing.
 Monkey Testing.
 Ext….
 TCD (Test Case Documentation)
 STLC

 Test Planning.
 Test Development.
 Test Execution.
 Result Analysis.
 Bug-Tracing.
 Reporting.

5.2.2 Black Box
 Microsoft Windows – Standards

 Manual Testing
 Automation Testing (Tools)
 Win Runner.
 Test Director
Testing:
 The process of executing a system with the intent of finding an error.

 Testing is defined as the process in which defects are identified, isolated, subjected for
rectification and ensured that product is defect free in order to produce the quality
product and hence customer satisfaction.
 Quality is defined as justification of the requirements
 Defect is nothing but deviation from the requirements
 Defect is nothing but bug.
 Testing --- The presence of bugs
 Testing can demonstrate the presence of bugs, but not their absence
 Debugging and Testing are not the same thing!
 Testing is a systematic attempt to break a program or the AUT
 Debugging is the art or method of uncovering why the script /program did not execute
properly.

Testing Methodologies:
 Black box Testing: is the testing process in which tester can perform testing on an
application without having any internal structural knowledge of application.
Usually Test Engineers are involved in the black box testing.
 White box Testing: is the testing process in which tester can perform testing on an
application with having internal structural knowledge.
Usually The Developers are involved in white box testing.
 Gray Box Testing: is the process in which the combination of black box and white
box techniques are used.

5.3 Snapshot
Home Page
Registration Form

Admin home
Tester Home

Developer home
Admin view employee

Tester view bugs
Edit profile

Change password
Developer bug report

Admin add department

Admin add project
CHAPTER 6
RESULT AND DISCUSSION
6.1 Test Report
Bug Name: Application crash on clicking the SAVE button while creating a new user.
Bug ID: (It will be automatically created by the BUG Tracking tool once you save this bug)
Area Path: USERS menu > New Users
Build Number: Version Number 5.0.1
Severity: HIGH (High/Medium/Low) or 1
Priority: HIGH (High/Medium/Low) or 1
Assigned to: Developer-X
Reported By: Your Name
ReportedOn: Date
Reason: Defect
Status: New/Open/Active (Depends on the Tool you are using)
Environment: Windows 2003/SQL Server 2005

6.2 User Documentation
Database design is the process of producing a detailed data model of a database. This logical
data model contains all the needed logical and physical design choices and physical storage
parameters needed to generate a design in a Data Definition Language, which can then be used to
create a database. A fully attributed data model contains detailed attributes for each entity.
The term database design can be used to describe many different parts of the design of an
overall database system. Principally, and most correctly, it can be thought of as the logical design
of the base data structures used to store the data. In the relational model these are the tables
and views.
In an object database the entities and relationships map directly to object classes and named
relationships. However, the term database design could also be used to apply to the overall
process of designing, not just the base data structures, but also the forms and queries used as part
of the overall database application within the database management system (DBMS).
CHAPTER 7
CONCLUSION
7.1 Conclusion
User comes to the search engine and makes a query, typically by giving key words, the
engine looks up the index and provides a listing of best-matching web pages according to its
criteria, usually with a short summary containing the document's title and sometimes parts of the
text.
Most search engines employ methods to rank the results to provide the “best” results first.
How a search engine decides which pages are the best matches, and what order the results should
be shown in, varies widely from one engine to another.
Search engine is technically the software and algorithms used to perform a search, the term
have become synonymous with the website itself.

Database Server
MySQL Server
Application Server
J2SE
Server
USER
Servlets
Application
Web
Browser

7.2 Limitation
 In this we are using Email-oriented approach for creating an issues it is well

suited for users reporting problems, but not it is good in Bug tracking
development issues.
 In this Interfaces are designed by programmers and they provide huge number of
features but it is difficult to implement them.
7.3 Future enhamncement

 Browsers which are being used should be supported by web based bug tracking system.
Since mostly free bug systems are Linux based, they do not work well with Windows.
 Bug tracking system should be robust, lightweight and fast.
 Should have minimal system requirements and maintenance.
 Should be easily installed and efficient to use.
 Should be platform independent and database system independent.
 File attachment should be supported
 Product and Component based
 Creating & Changing Bugs at ease
 Query Bug List to any depth
 Reporting & Charting in more comprehensive way
 User Accounts to control the access and maintain security
 Simple Status & Resolutions
 Multi-level Priorities & Severities
 Targets & Milestones for guiding the programmers
 Attachments & Additional Comments for more information
 Robust database back-end

REFERENCES
 System Analysis And Design
By William S. Davis, David C. Yen
 An Analysis and Design of Information Systems
By Simon Bell
 Software Engineering
-By Schach
 Database Management System
By Jason Price
 JSP: A Beginner’s Guide
-By Robert Brunner
 Java Server Pages Programming: A visual professional guide for Design
By Carsten Thomsen
GLOSSARY
 Bug Tracking: BT is provide a platform which help user, it professionals, and

developers for Bug Tracking and also developer and user can update their source
code
 Admin: Who is responsible to create, update, delete, add source code.
 JSP: Java Server Page
 API: Application Programming Interface
 CSS: Case Coding Style sheet
 GUI: Graphics User Interface
 Update: User can update your profile.
 Manage Source Code: User can manage source code

Bug Tracking Project

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Bug Tracking Project

Uploaded by

Copyright:

Available Formats

Table of Contents

CHAPTER 2 SURVEY OF TECHNOLOGY

2.3 Rational Rose

CHAPTER 3 REQUIREMENT ANALYSIS

3.1 Problem Definition

3.2 Specific Requirment

3.3 Planning and Scheduling

3.4 Software and Hardware Requirment

3.5 Preliminary product Description

3.6 Conceptual Model

3.6.1 Use Case Diagram

3.6.2 Activity Diagram

3.6.3 Class Diagram

3.6.4 Sequence Diagram

3.6.5 E-R Diagram

3.6.6 Data Flow Diagram

G.T.POLYTECHNIC COLLEGE, JAORA Page 1

4.1 Procedural design

4.1.1 Logic Diagram

4.2 Test Cases

5.2 Testing Approaches

5.2.1 White Box

5.2.2 Black Box

CHAPTER RESULT AND DISCUSSION

6.1 Test Report

6.2 User Documentation

7.3 Future enhamncement

G.T.POLYTECHNIC COLLEGE, JAORA Page 2

G.T.POLYTECHNIC COLLEGE, JAORA Page 3

G.T.POLYTECHNIC COLLEGE, JAORA Page 4

G.T.POLYTECHNIC COLLEGE, JAORA Page 5

G.T.POLYTECHNIC COLLEGE, JAORA Page 6

G.T.POLYTECHNIC COLLEGE, JAORA Page 7

Microsoft Windows, commonly referred to as Windows, is a group of

Microsoft introduced an operating environment named Windows on November 20,

Apple came to see Windows as an unfair encroachment on their innovation in GUI

G.T.POLYTECHNIC COLLEGE, JAORA Page 8

G.T.POLYTECHNIC COLLEGE, JAORA Page 9

Why Software Developers Choose Java

Goals in creation of Java

1. It should be "simple, object oriented".

G.T.POLYTECHNIC COLLEGE, JAORA Page 10

• The Java programming language

The Java Virtual Machine

G.T.POLYTECHNIC COLLEGE, JAORA Page 11

2.3 Rational Rose

Rational Rose is a software development environment for using model descriptions

G.T.POLYTECHNIC COLLEGE, JAORA Page 12

G.T.POLYTECHNIC COLLEGE, JAORA Page 13

3.1 Problem Definition

G.T.POLYTECHNIC COLLEGE, JAORA Page 14

3.3 Planning and Scheduling

PLANNING TIME(in days)

G.T.POLYTECHNIC COLLEGE, JAORA Page 15

3.4 Software and Hardware Requirment

3.4.1 Software Requirements

Operating System Windows 7,8,10

Designing Tools Rational Rose

Development Tools Net Beans IDE 8.0

Language Java, JSP

3.4.2 Hardware Requirement Specification

RAM : 512 MB RAM

G.T.POLYTECHNIC COLLEGE, JAORA Page 16