Newsrs

Software Requirements Specification issue tracker Page i
Table Of Contents
1. Introduction...............................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................... 1
2. Overall Description...................................................................................................................3
2.1 Product Perspective............................................................................................................................. 3
2.4.1 HARDWARE SPECIFICATION .............................................................................. 7
2.4.2 SOFTWARE SPECIFICATION................................................................................... 7
2.5 Design and Implementation Constraints............................................................................................ 8
3. System Features........................................................................................................................ 8
4. External Interface Requirements.................................................................................. 18
4.1 User Interfaces................................................................................................................................. 18
4.2 Hardware Interfaces.......................................................................................................................... 18
4.3 Software Interfaces............................................................................................................................ 18
4.4 Communications Interfaces............................................................................................................... 19
5 Other Nonfunctional Requirement......................................................................................... 19
Performance Requirements...................................................................................................... 19
Security Requirements........................................................................................................................... 19
Software Quality Attribute..................................................................................................................... 20
Quality Attributes of an Issue Tracker are:............................................................................................ 20
25
Appendix B: Analysis Model......................................................................................................25
Software Requirements Specification for issue tracker Page 1
1. Introduction
1.1 Purpose
An Issue Tracking system manages and maintains a list of project issues. It is an ideal
tool for resolving issues in a timely manner. Issue Tracking systems are commonly used in an
organization to create, update and resolve issues reported by the organization's employee such
as to report an issue, track program towards its resolution, and know who is responsible for
resolving the issue. Tracker can be used to discuss and exchange ideas instead of having to get
everyone into a meeting at the same time and place.
1.2 Document Conventions

All the main titles are written in bold. Unless otherwise mentioned, all requirements specified
here are of high priority and committed for release 1.0.
This document is prepared in the following format:
• Font Style : Times New Roman
• Headings : 18 size
• Sub-Headings : 14 size
• Description : 12 size
• Line Spacing : 1.5
1.3 Intended Audience and Reading Suggestions
Project coordinator, Project leader and each employee of an organization, who have a
login id and a password given by the administrator within the organization.
1.4 Project Scope

Tracker can be used by the employees to coordinate their work, and to make sure that
project issues get resolved in a timely manner. The built-in workflow automatically
routes that issues to the appropriate individuals. Everyone involved can obtain status,
automatic notification, reports, and share knowledge and information. An issue tracking
system often also contains a knowledge base containing information on each customer,
resolutions to common problems, and other such dates.
References
• Elias M. Awad, “System Analysis and Design”, Second Edition,
Galgotia Publications
• IAN Sommerville, “Software Engineering”, third edition, BPB
Publication.
• Elmasri Navathe, “Fundamentals of database system”, sixth edition.
• Ivan Bayross, “Oracle 10g Developer Suite (DS)”, BPB Publications
2. Overall Description
2.1Product Perspective
Some benefits of Web based Issue Tracking systems are:
 All Issues can be viewed in One Place --->An issue tracking system serves as a repository
for all project information, allowing workers and managers to refer to the system for all
project assignments and updates.
Information is contained in a consistent format ---> tracking software offers a consistent

presentation format that allows project participants to instantly locate needed information.
Clearly defined assignments --->With issue tracking software, every project participants
remains aware of his or her tasks at all times.
Easy organization of issues --->Tracking software allows issues to be categorized under

the proper heading and assigned to the right workers ensuring that issue reports never get
lost or unaddressed.
2.2 Product Features
With easy-to-use and intuitive interface, Issue Tracking for bug tracking is convenient, effective and
professional in tracking and managing both business and technical issues.
• Web-based Architecture
Issue Tracking is 100% web based application. This Application is built on ASP.NET with c#.
It supports all major browsers which is available to access.
• Easy, Efficient and Flexible User Interface:

This application is very easy to use even very efficient to user. It is also very flexible and can
be used very effectively. The interface is designed to make it efficient . It is intuitive, easy-to-use and
yet powerful.
• Powerful Query:
Another feature of the application is that it is very powerful. With the powerful query
designer, it can get instant and deep insight of the data
• Highly Customizable:
This application has Field, field rule, screen, data form, email and workflow can be customized
according to your needs.
• Process-driven and Role-based workflow:
The application Issue Tracking workflow is adaptive to all unique process which is happening
within the organization.
• Automatic Email Notification:
Automatic email notification is another feature of issue tracker. It keeps to informed issue
anywhere at any time. Automatic email is carried on effectively.
• Audit Trail:
Audit is one another feature of issue tracking system. It is used to maintain change history for
issues which is occurred within organization.
• Security
The security is another very important feature within organization. This application support
HTTPS protocol. It is assign to access permissions to user/group globally and within projects.
• Reporting
This application is also generate report. It displays current status and other aspects of projects
and issues which is occurred within the organization.
2.3 User Classes and Characteristics
Issue Tracking can be used for reporting and tracking work items, bug tracking, defect
tracking, issue tracking, task tracking, tracking feature requests, etc. In Issue Tracking , all issues
are instantly searchable and traceable, making it easy to manage these issues through to
resolution.
Project Management
In Issue Tracking , all issues are organized by projects. Issue Tracking helps companies to
manage the projects by enforcing rigorous development process at each stage of issue
resolution.
Customer Support
Issue Tracking enables to collaborate with the customers by allowing them to submit
issues, obtain status and cooperate with in resolving problems and developing new features
via the Web, which helps build a streamlined and satisfying customer support. With easy-to-
use and intuitive interface, Issue Tracking for bug tracking is convenient, effective and
professional in tracking and managing both business and technical issues.
The following are the characteristic of issue tracker:-
• Ability to Accommodate Multiple Projects
If company has been in business for a while, chances are that it works on more than one
project at once, which means that a tracking system that doesn't accommodate multiple
projects at once is rather useless. The best software allows tracking an endless number of
projects using the same system.
• Customizable User Permissions

This application have different roles that allows user’s access to project information and
commands appropriate to their role can be a key management tactic. Project management
software often advertises that it offers a way "to keep everyone on the same page", and it
does. But limiting workers' access to the information and Commands appropriate to their
function is crucial for preventing confusion and the misuse of system commands, such as the
command to delete a task.
• Ability to Create Detailed Statistics and Reports
If there is a good portion of project meetings trying to convey how a project is progressing
in general and specific terms, the best tracking systems will allow to create customized reports
or use ready-to-use report formats to produce detailed information on every aspect of a
project, including: workers time sheets, estimated task time versus actual task time, and
quality of performance ratings. With the aid of targeted reports, it can let hard numbers do the
talking while the suggest improvements will be available.
• Customizable Issue Tracking
This tracking providers offer pre-designed, ready-to-use tracking systems, but not
customized systems that address a company's unique tracking needs or business process. A
first-rate tracking provider will offer both. Sometimes, a company's needs are indeed met by a
pre-designed system. But in the event that its tracking needs change, receiving new tracking
options through the same provider will prove more difficult than receiving them through a
provider that offers customized tracking options.
• Messaging Forums
A great tracking system always includes a messaging forum where project members can share
information and collaborate on strategies. The best tracking systems will allow creating a
message forum for each task and creating as many message forums as needed. In addition to
facilitating collaboration, message forums also allow project managers and project workers to
keep track of all task discussions.
2.4 Operating Environment
This product will be operating in any windows environment. Also it will be compatible
with all compatible browsers. The main requirement to use this online product would be the
internet connection. This system needs the following specifications.
2.4.1 HARDWARE SPECIFICATION
Processor : Intel Pentium IV

Memory : 512 MB RAM
Hard Disk Drive : 40 GB
2.4.2 SOFTWARE SPECIFICATION
Server Side:
 Programming Language - C#
 Operating System - Windows NT, Windows 2000/XP.
 Database Used - SQL Server
 IDE -Visual Studio
Client Side:
Browser - Any Compatible browser

2.5 Design and Implementation Constraints
• If the Userid and Password are correct then only log in is possible.
• The employee have id and password can have the provision for creating, updating and
Resolving issues.
• Task Posting can be done only by Project Manager.
• Project information can viewed by the Project Members.
•
2.6 User Documentation
The issue tracking system is used for providing the functional support to the users
within the organization. It provides user to report an issue, track progress towards its resolution, and
know who is responsible for resolving the issue.
2.7Assumptions and Dependencies

N.A.
3. System Features
The Issue Tracking system consists of several modules such as Login Module, Employee
Module, Project Module, Task Posting, Setting Module, Reporting Module, Technical Forums,
Mail Facility, Global Tracking, Audit Trail, FAQ, Context Sensitive Help, Alerts and Export to
Excel.
3.1 Login Module
Description
This module is used to enter into the project. Login contains “user id” and
“password” for each authorized users. It checks the authority of the person using the user id and
the password. If the id and the password are valid then the user is given access to rest of the
modules else the access is denied.
Stimulus/Response Sequences
It checks the authority of person who is using user id and the password. If the id and
password are valid than the user is given access to rest of the modules else the access will be
denied.
Functional Requirement
Purpose To check authority
Inputs User id and password
Check from database and

Processing
respond accordingly
Outputs authentication
3.2 Employee Module
Description
This Module deals with the manipulation of employee information in an

organization. In this module we can add new employee, update employee in formations
etc
It add new employee, update employee information, and perform an action
according to input.
Purpose To add, edit , update employee
Inputs User id and password
Check Database and respond

Processing
according
Outputs Response to the input
3.3 Project Module
Description
This module deals with the project information. In this module we can
add, edit, delete project information.
In this module project information is carried on. This module also deals
with add, edit, delete project information, its complexity, mapping etc.
Purpose To add, edit, update project.
Project issue which is required

Inputs
for update.
Processing
according
Outputs Responding to the input
3.4 Task Posting
Description:
This module deals with the ticket posting by employee. Typically the ticket will
have a unique reference number, which is used to allow the user or support staff to
quickly locate, add to or communicate the status of the user's issue or request.
Ticket posting is done by employee. The ticket will have a unique reference number,
which is used to allow the user or support staff to quickly locate, add to or communicate
with user's issue.
Purpose Ticket Posting
Reference number is given to

Inputs
post task.
Processing
according
3.5 Setting Module
Description:
This module is typically used by administrators to perform administrative
functions. This has the ability to move the tasks which is already posted, to the
history, set user privileges. This enables us to add, edit or delete project settings and
allows the customization of Email.
Here Administration is used to perform administrative functions. It is used to
move the tasks which are already posted, to the history, set user privileges.
Purpose Setting
Set a task which is already

Inputs
posted for resolving bug.
Check Database and
Processing
respond according
3.6 Reporting Module
Description:
This module is used to generate different status level reports. It also produces a
human readable report.
To generate different status level reports. Report is generated this module. It
produces a human readable report.
Purpose report
Inputs Data to which report be generated

Processing
according
3.7 Global Tracking
Description:
The software should be able to locate, track and communicate with the
issues in various branches of the same organization.
Stimulus/Response Sequences:
This module is used to locate, track and communicate with the issues in various
branches of the same organization.
Functional Requirement:
Locate, track and

Purpose
communicate issue.
Project data to which it
Inputs track, locate and
communicate
Check Database and
Processing
respond according
3.8 Technical Forum
Description:
Use the Technical Forum to report/post issues. When reporting an issue, it
include relevant details such as error messages, browser version etc.
This module is used to report/post issues. It also include relevant details such as
error messages, browser version etc.
Purpose Report and post issue.

Inputs Issue to report or post

Processing
according
3.9 Mail Facility

Description:
The system sends e-mail notification to users when new issues are raised.
This module is used to sends e-mail notification to users when new issues are
raised within the organization.
Purpose Send email notification
Inputs Description of issue
Check Database and

Processing
respond according
Outputs Mail is posted
3.10 Audit Trail
Description:
In an Issue Tracker, an audit trail is a record which showing how many
issues get resolved or unresolved etc.
This module is used to show how many issues get resolved or
unresolved etc within the organization.
Show how many issue resolved,

Purpose
unresolved
Processing Check Database and respond according
Outputs Number of issue resolved or unresolved
3.11 FAQ, Context Sensitive Help, Alerts
Description:
FAQ:
FAQs are listed questions and answers
Context Sensitive Help:
Context-sensitive help is a kind of online help that is obtained from a

specific point in the state of the software, providing help for the situation
that is associated with that state.
Alerts:
Whenever an issue has been occurred and if the problem has been
resolved alert the relevant people to the solutions found .
This module is used to list the question and answers. Context sensitive is a kind of
online help. Whenever an issue occurred or resolved it give an alert message.
Purpose FAQ, online help and alert
Inputs Query which is occur.
Check Database and

Processing
respond according
3.12 Exports to Excel
Description:
Export to Excel is one of the most common functionality. It needs to export data
to excel spread sheet.
This module is used to export the data in Excel spread sheet.
Purpose Export to excel
Inputs Data to be exported
Check Database and

Processing
respond according
4. External Interface Requirements
4.1 User Interfaces
The user interface will be a GUI. User friendly menus and screens will be provided.
Screens have to be popped up based on user operational level. The screens are designed
using the Visual Studio 2008 with C#. The Necessary buttons and menu controls and
other controls have been used to make the system more users friendly.
4.2 Hardware Interfaces
In this Application Issue Tracker, all the end users within the organization
are connected through Local Area Network.
4.3 Software Interfaces
The Application is developed using the following tools
o Visual Studio with C#

o SQL Server 2005
4.4 Communications Interfaces
The Communication interface is in electronic forms in Issue Tracker

Application. It has various buttons, menu controls and other controls have been used
to make the system more users friendly. All controls has its features to perform the
task accordingly.
5 Other Nonfunctional Requirement
Performance Requirements
There are three classes of performance requirements. They are, good response times,
maximum throughput and concurrency.
Response time: How fast the system handles the individual requests
Throughput: How many requests the system can handle
Concurrency: How many users or threads works simultaneously
Security Requirements
Security is typically based on user accounts, user groups and user group permissions.
Issue Tracker can be able to:
 Control whether users can edit or view fields.
 Control access to bugs by users.
 Control access to specific features, such as reporting or user account administration.

 Determine which users can access which project or databases.
Software Quality Attribute
Quality Attributes of an Issue Tracker are:
 Reliability: It is measured in terms of working of project under different working

environment and different conditions.
 Maintainability: For development it should be easy to add code to existing
system, should be easy to upgrade for new features time to time..
 Portability: This can be measured in terms of costing issues related to porting,

technical issues related to porting, behavioral issues related to porting.
 Correctness: Application should be correct in terms of its functionality,

calculations used internally and the navigation should be correct.
 Efficiency: It is measured in terms of time required to complete any task given to

the system.
 Integrity or Security: System integrity or security should be sufficient to prevent

unauthorized access to system functions, preventing information loss, ensure that
software is protected from virus.
 Testability: System should be easy to test and find defects
 Flexibility: Should be flexible enough to modify

 Reusability: Software reuse is a good cost efficient and time saving development
Data Flow Diagram:-
Context Level:-
Request
User
Issue Tracker
Response
Level 1:-
Username & password
Admin Login
Login successfully
Login
Level 2:-
Add, edit, delete store employ detail

EMPLOYEE
ADMIN MODULE EMPLOYE
Store employ details return store employ details
Add, edit, delete
Store project
detail
Add,edit,delete
PROJECT PROJECT
Store project
Detail
Level 3:-
ADMIN
Add Assign
Task Task
Add Task
TASK
Assign Task TASK
Level 4:-
Generating excel report Generating excel report
ADMIN ISSUE
ISSUE
View report view report
Level 5:- Post issue
Post issue,search issue & search issue

USER ISSUE
View issue& report ISSUE
Request for task View issue & report
View task
Request for view task
Search for help TASK view task list TASK
Return help
Request for help
HELP HELP
Return help
Appendix A: Glossary
 SRS :Software Requirement Specification
 FAQ :Frequently Asked Questions

Newsrs

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Newsrs

Diunggah oleh

Hak Cipta:

Format Tersedia

Software Requirements Specification issue tracker Page i

1.2 Document Conventions

This document is prepared in the following format:

• Font Style : Times New Roman

• Line Spacing : 1.5

1.3 Intended Audience and Reading Suggestions

1.4 Project Scope

Information is contained in a consistent format ---> tracking software offers a consistent

Easy organization of issues --->Tracking software allows issues to be categorized under

2.2 Product Features

• Easy, Efficient and Flexible User Interface:

2.3 User Classes and Characteristics

The following are the characteristic of issue tracker:-

• Ability to Accommodate Multiple Projects

• Customizable User Permissions

• Ability to Create Detailed Statistics and Reports

• Customizable Issue Tracking

2.4 Operating Environment

2.4.1 HARDWARE SPECIFICATION

Processor : Intel Pentium IV

2.4.2 SOFTWARE SPECIFICATION

Browser - Any Compatible browser

2.5 Design and Implementation Constraints

2.7Assumptions and Dependencies

3.1 Login Module

Purpose To check authority

Inputs User id and password

Check from database and

3.2 Employee Module

This Module deals with the manipulation of employee information in an

Purpose To add, edit , update employee

Inputs User id and password

Check Database and respond

3.3 Project Module

Purpose To add, edit, update project.

Project issue which is required

Outputs Responding to the input

3.4 Task Posting

Purpose Ticket Posting

Reference number is given to

3.5 Setting Module

Set a task which is already

3.6 Reporting Module

Inputs Data to which report be generated

Check Database and respond

3.7 Global Tracking

Locate, track and

3.8 Technical Forum

Purpose Report and post issue.

Inputs Issue to report or post

Check Database and respond

3.9 Mail Facility

Purpose Send email notification

Inputs Description of issue

Check Database and

3.10 Audit Trail

Show how many issue resolved,

Processing Check Database and respond according

Outputs Number of issue resolved or unresolved

3.11 FAQ, Context Sensitive Help, Alerts

Context Sensitive Help:

Context-sensitive help is a kind of online help that is obtained from a