___________________________________________

<Team Name>
___________________________________________

Defect Tracking for Improving

Product Quality and Productivity

Revision History

Date Version Descripti Author

on
<date> <version number> <team members
names>
Defect Tracking for Improving Product Quality and Productivity Version: 1.0
Software Requirements Specification Date: <Date>
<Team>/<Title>/<leadId>

Table of Contents
1. Introduction
1.1 Purpose 3
1.2 Scope 3
1.3 Reference 3
1.4 Technologies to be used 4
1.5 Overview 4

2. Overall Description 4
2.1 Existing System 6
2.2 Proposed System 6

3. Specific Requirements 6

3.1 Functional Requirements 7

<Team>,<year> Page 2 of 7
Defect Tracking for Improving Product Quality and Productivity Version: 1.0
Software Requirements Specification Date: <Date>
<Team>/<Title>/<leadId>

1. Introduction

This system can be used as an application for the product based

company to reduce the defects in product’s quality and productivity.
User logging should be able to upload the information of the user.

1.1 Purpose
The purpose of Defect Tracking for Improving Product Quality and
Productivity is to provide better service to the administrator or useful
for applications developed in an organization.

1.2 Scope

The Defect Tracking for Improving Product Quality and Productivity is a

web based application that can be accessed throughout the
organization. This system can be used for logging defects against an
application/module, assigning defects to individuals and tracking the
defects to resolution. There are features like email notifications, user
maintenance, user access control, report generators etc in this system.

1.3 References

(1) Java Complete Reference By Herbert Shield

(2) Database Programming with JDBC and Java By George Reese
(3) Java and XML By Brett McLaughlin
(4) Wikipedia, URL: http://www.wikipedia.org.

(5) Answers.com, Online Dictionary, Encyclopedia and much more, URL:

http://www.answers.com

(6) Google, URL: http://www.google.co.in

<Team>,<year> Page 3 of 7
Defect Tracking for Improving Product Quality and Productivity Version: 1.0
Software Requirements Specification Date: <Date>
<Team>/<Title>/<leadId>

1.4 Technologies to be used

 HTML, CSS (Web Presentation )

 JavaScript (Client-side Scripting)
 Java (as programming language)
 JDBC, JNDI, Servlets, JSP (for creating web applications)
 Eclipse with MyEclipse Plug-in (IDE/Workbench)
 Oracle/SQL Server/Access (Database)
 Windows XP/2003 or Linux/Solaris (Operating System)
 BEA WebLogic/JBoss/WebSphere (Server Deployment)

1.5 Overview

Overall description consists of background of the entire specific

requirement. It also gives explanation about actor and function which
is used. It gives explanation about architecture diagram and it also
gives what we are assumed and dependencies. It also support specific
requirement and also it support functional requirement, supplementary
requirement other than actor which is used. It also gives index and
appendices. It also gives explanation about any doubt and queries.

2. Overall Description

1. A user should be able to

• Login to the system through the first page of the application.

• Change the password after logging into system.

• View the defects assigned to the User.

• Find defects for components on which the user has access.

<Team>,<year> Page 4 of 7
Defect Tracking for Improving Product Quality and Productivity Version: 1.0
Software Requirements Specification Date: <Date>
<Team>/<Title>/<leadId>

• Find components on which the user has access.

• Modify the defects by changing / putting values in fields.

• Assign defects to other users having access to the component.

• Find details of other Users.

• Generate reports of defects for components on which the user

has access.

2. As soon as a defect is assigned to a user a mail should be send to

the User.

3. A Component Admin should be able to do the following tasks in

addition to 1:

• Add a User to the component for creating and modifying defects

against that component.

• Remove a user from the component.

• Mark a component as “Active” / “Closed”. No new defects can be

created against a “Closed” component. A component cannot be
closed until all defects against the component are also closed.

4. The Application Admin should be able to do the following tasks in

addition to 1 & 3:

• Add a new component.

• Add a user to a component as Component Admin.

• Remove Component Admin privilege from a user.

• Add a new user.

<Team>,<year> Page 5 of 7
 Defect Tracking for Improving Product Quality and Productivity Version: 1.0
Software Requirements Specification Date: <Date>
<Team>/<Title>/<leadId>

• Remove a user.

2.1 Existing System

The Current System is a computerized system but which is maintained

at individual databases. The system doesn’t provide complete online
services like online reports, and centralized database.

2.2 Proposed System

The Proposed system is a browser which is completely related to online

system, which provides the centralized database. It stores defects data
and description of the particular defect data. It can also create Excel
reports and PDF documents based on the information in its database.

3. Specific Requirements

The specific requirement gives the expected behavior of the

System

 The system behaves like opera browser in multiple accessibility

 The system can also used for local area network connections
 It should work with all platforms.

3.1 Functional Requirements

Following tasks can be performed with the application:

Modules:
(a) User Maintenance: Creating, Granting & Revoking access
and deleting users from application.

<Team>,<year> Page 6 of 7
Defect Tracking for Improving Product Quality and Productivity Version: 1.0
Software Requirements Specification Date: <Date>
<Team>/<Title>/<leadId>

(b) Component Maintenance: Creating a component

(application being developed / enhanced), Granting &
Revoking access on components to Users and Marking a
component as “Active” or “Closed”.
(c) Defect Tracking: Creating, Assigning defects to users,
Modifying and Closing a defect. A defect screen should at
least have following details
• Defect Number and Title
• Defect priority
• Date created
• Defect description
• Defect diagnosis
• Name of originator
• Name of Assignee
• Status
• Resolution
(d) Find User: A search screen to find users and display results
(e) Find component: A search screen to find components and
display results
(f) Find defect: A search screen to find defects and display
results
(g) Report: Generate reports on defects

<Team>,<year> Page 7 of 7