introduction of the project along with the SRS,DFD and Data dictionary of the project

2. BUG TRACKING SYSTEM
Prof. VANI AGRAWAL
NEHA KAURAV
SAURABH SONI
ANKIT BOHARE
CLASS:
BCA 3rd SEM.

3. What is BUG?
• A bug is a common term used to describe an
error, flaw(flaunt), mistake, failure or fault in
a computer program or system that produces
an incorrect or unexpected result or causes it
to behave in unintended way.
• Most bugs are arise from mistakes and errors
made by people in either program’s source
code or its design, and few are caused by
compilers producing incorrect code.

4. • A bug tracking system is a software application
that is designed to help quality assurance and
programmers keep track of reported software
bugs in their work. It may be regarded as a sort
of issue[matter]tracking system.
• A major component of bug tracking system is a
database that records facts and known bugs.
• The report of database can consists of several
information which can also called facts.

5. Software Requirement Specification
(SRS)
• A software requirements specification (SRS) is a
comprehensive description of the intended
purpose and environment for software under
development. The SRS fully describes what the
software will do and how it will be expected to
perform.
• A software requirements specification (SRS) is a
document that captures complete description
about how the system is expected to perform.

6. • Administrator
 He/she can record the team, staff and project entry.
 If he/she does not find the process of project on time then it
can assign that project to another team.
 He/she can keep record of the status of all the projects along
with their bug details.
• Developer
 When he/she will login, then he/she will be able to see all
bugs details that are assigned to him/her.
 Details of the project of that bug belong.
 He/she will be able to see members of its team.
 He/she will be able to change or see the status of the bug.
 He/she can report the process of the bug to the tester.
 He/she will be able to see the status of the projects assigned
to him/her team.

7. • Tester
 When he/she login, then he/she will be able to see the
details of the project that are assigned to him/her.
 He/she can get an interface for defect log.
 He/she will be able to see members of his/her team.
 He/she should have the rights to see or change the status
of the project.
 He/she can see or change the status of the bug.
• Analyst
 He/she can generate various reports.
 He/she can allot the bug to the developer of his/her team.
 If he/she does not find work on time then it will allot the
bug to another developer of his team.
 He/she can see the members of his team.
 He/she will be able to see details of projects that are
assigned to his/her team.

8. • A data flow diagram (DFD) illustrates how data is processed by a system
in terms of inputs and outputs. As its name indicates its focus is on the
flow of information, where data comes from, where it goes and how it
gets stored.
• Process Notations. A process transforms incoming data flow into
outgoing data flow.
• Data store Notations. Data stores are repositories of data in the system.
They are sometimes also referred to as files.
• Dataflow Notations. Data flows are pipelines through which packets of
information flow. Label the arrows with the name of the data that moves
through it.
• External Entity Notations. External entities are objects outside the
system, with which the system communicates. External entities are
sources and destinations of the system's inputs and outputs.
process
data store
Data flow External entity

9. Level 0 (Context level)

10. Level 1

11. Level 2

12. • A data dictionary is structured collection
about data. It sets a exact definition of all
DFD data elements and data structures.
Staff Registration:
staff id, staff name, category, address,
contact number, e-mail id
Team entry:
team id, team name
Project Entry:
Project id, project name, price
Assigning Team to Staff:
staff id, team id, team assigning date

13. Assigning Project to Team:
project id, team id, starting date
of project, end date of project
Reporting of the bug:
Bug id, description, print screen
of bug, bug identified by, bug
identify date
Resolving of a bug:
Bug id, resolved by, resolved date
Bug assigned to developer:
Bug id, assigned date, assigned to