sri indu 1213 it

  • 498 views
Uploaded on

sriindu it

sriindu it

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
498
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
14
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Bug Tracking System
    Welcome
  • 2. BugTracking System
    Towards
    Final Year Project
    Student Intern Project
  • 3. Bug Tracking System
    Guided By:
    K.DEEPTHI
    Submitted By:
    A.JIGNASH
    M. BHARADWAJ
    May 3, 2010
  • 4. Bug Tracking System
    Agenda :
    Shiv Prakash Amitabh Mukherjee Akshay Saraf Deepit Chaturvedi
    May 3, 2010
  • 5. Bug Tracking System
    What is a Bug ?
    May 4th ,2010
    A software Bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways.
    Most Bug arise from mistakes and errors made by people in either a program's source code or its design, and a few are caused by compilers producing incorrect code.
    Bug can have a wide variety of effects, with varying levels of inconvenience to the user of the program. Some defects have only a subtle effect on the program's functionality, and may thus lie undetected for a long time. More serious defects may cause the program to crash or freeze leading to a denial of service. Others qualify as security defects and might for example enable a malicious user to bypass access controls in order to obtain unauthorized privileges.
  • 6. BugTracking System
    What are the Types Of Bug?
    Conceptual error :
    • Code is syntactically correct, but the programmer or designer intended it to do something else
    Maths Defects
    • Division by zero
    • 7. Arithmetic overflow or underflow
    • 8. Loss of arithmetic precision due to rounding or numerically unstable algorithms
    Logic Defects
    • Infinite loops and infinite recursion
    Syntax Defects
    • Use of the wrong operator, such as performing assignment instead of equality test. In simple cases often warned by the compiler; in many languages, deliberately guarded against by language syntax (continued)
  • BugTracking System
    What are the Types Of Bugs?
    May 3, 2010
    Co-programming Bug
    • Deadlock
    • 9. Race condition
    • 10. Concurrency errors in Critical sections, Mutual exclusions and other features of concurrent processing. Time-of-check-to-time-of-use (TOCTOU) is a form of unprotected critical section.
    Team working Bug
    • Unpropagated updates; e.g. programmer changes "myAdd" but forgets to change "mySubtract", which uses the same algorithm. These errors are mitigated by the Don't Repeat Yourself philosophy.
    • 11. Comments out of date or incorrect: many programmers assume the comments accurately describe the code
    • 12. Differences between documentation and the actual product
  • Bug Tracking System
    Some Unusual Bug
    May 3, 2010
    Heisenbugs:
    • Those bugs that manifest only under certain condition . These bugs normally escape the debugger of the developers .
    Bohrbug:
    • A Bohr bug or bohrbug is a bug that manifests itself consistently under a well-defined (but possibly unknown) set of conditions
    Mandelbug
    • A mandelbug is a computer bug whose causes are so complex that its behavior appears chaotic.
    Schroedinbug
    • A schroedinbug is a bug that manifests only after someone reading source code or using the program in an unusual way notices that it never should have worked in the first place, at which point the program promptly stops working for everybody until fixed.
  • Bug Tracking System
    What is a Bug Tracking System ?
    May 3, 2010
    Defect tracking is the process of finding defects in a product (by inspection, testing, or recording feedback from customers), and making new versions of the product that fix the defects.
    Defect tracking is important in software engineering as complex software systems typically have tens or hundreds or thousands of defects: managing, evaluating and prioritizing these defects is a difficult task.
    Defect tracking systems are computer database systems that store defects and help people to manage them.
    A Defect tracking system is a software application that is designed to help quality assurance and programmers keep track of reported software defects in their work. It may be regarded as a sort of issue tracking system
  • 13. Bug Tracking System
    Why is it Necessary ?
    Software defects are expensive.
    Moreover, the cost of finding and correcting defects represents one of the most expensive software development activities. For the foreseeable future, it will not be possible to eliminate defects.
    While defects may be inevitable, we can minimize their number and impact on our projects.
    To do this development teams need to implement a defect management process that focuses on preventing defects, catching defects as early in the process as possible, and minimizing the impact of defects.
    A little investment in this process can yield significant returns
    May 3, 2010
  • 14. Cost of Defects during the Software LifeCycle
  • 15. Bug Tracking System
    What are the Components of a good Defect Tracking System ?
    A major component of a bug tracking system is a database that records facts about known defects. Facts may include the time a bug was reported, its severity, the erroneous program behavior, and details on how to reproduce the bug; as well as the identity of the person who reported it and any programmers who may be working on fixing it.
    Typical bug tracking systems support the concept of the life cycle for a bug which is tracked through status assigned to the bug. A bug tracking system should allow administrators to configure permissions based on status, move the bug to another status, or delete the bug. The system should also allow administrators to configure the bug statuses and to what status a bug in a particular status can be moved to.
    May 3, 2010
  • 16. BugTracking System
    Examples of Extreme Effects of Defects
    Defects in the code controlling the Therac-25 radiation therapy machine were directly responsible for some patient deaths in the 1980s.
    In 1996, the European Space Agency's US$1 billion prototype Ariane 5 rocket was destroyed less than a minute after launch, due to a bug in the on-board guidance computer program.
    In June 1994, a Royal Air Force Chinook crashed into the Mull of Kintyre, killing 29. It was caused by a software bug in the aircraft's engine control computer.
    May 3, 2010
  • 17. BugTracking System
    Financial Implications
    In 2002, a study commissioned by the US Department of Commerce' National Institute of Standards and Technology concluded that software defects, or errors, are so prevalent and so detrimental that they cost the US economy an estimated $59 billion annually, or about 0.6 percent of the gross domestic product.
    As per GARTNER estimates the global market for testing will be about $13 bn by 2010 . And Indian IT companies would take over 70 % of testing market.
    May 3, 2010
  • 18. BugTracking System
    Defect LifeCycle
  • 19. LifeCycle of a BugZilla Bug
  • 20. Defect Tracking Software
    May 3, 2010
    To develop a project titled “Bug Tracking Software ” which isan :
    • automated bug / issue tracking system that provides automation of keeping track of the component development processes & bug processing.
    • 21. software application that is designed to help programmers/users keep track of reported software defects in their work.
    • 22. is a web based application that can be accessed throughout the organizations
    Abstract:
  • 23. BugTracking System
    May 3, 2010
    Functionalities
    It is a database that records facts about known bugs.
    Facts may include:
    • Time a bug was reported,
    • 24. Severity,
    • 25. Assignment of Status,
    • 26. Erroneous program behavior,
    • 27. Details on how to reproduce the bug:
    • 28. Identity of the user who reported it,
    • 29. Identity of the developer/programmer working on fixing it.
  • BugTracking System
    May 3, 2010
    Functionalities
    BugTracking:
    • Creating defects,
    • 30. Assigning defects to users,
    • 31. Modifying defects
    • 32. Closing a defect.
    A defect screen should atleasthave following details
  • BugTracking System
    May 3, 2010
    Software Development Environment:
    • MS Platform
    • 41. MS-SQL Server
    • 42. Oracle 10g Database
    • 43. Visual Studio 2008
    • 44. ASP.NET 2.0
    • 45. IIS (Internet Information Services) 7.0
  • BugTracking System
    May 3, 2010
    Software Development Environment:
    MS Platform
    • contains header files, libraries, samples, documentation and tools utilizing the APIs required to develop applications for Microsoft Windows and the .NET Framework 3.0/.NET Framework 3.5.
    • 46. Application programming interface (API) is an interface in computer science that defines the ways by which an application program may request services from libraries and/or OS.
    • 47. Used to write applications that target
    • 48. Windows XP, Windows Server 2003, Windows Vista & Windows Server 2008
  • BugTracking System
    May 3, 2010
    Software Development Environment:
    • application used to create computer databases.
    • 49. environment used to generate databases.
    • 50. support businesses by online transaction processing (OLTP) and decision support system (DSS) workloads.
    • 51. DSS workloads, are highly resource intensive.
    • 52. DSS queries touch large amounts of data (often terabytes in size).
    MS-SQL Server
  • 53. BugTracking System
    May 3, 2010
    Software Development Environment:
    Visual Studio 2008
    It is a comprehensive set of tools that accelerates the process of turning the developer’s vision into reality.
  • 54. BugTracking System
    May 3, 2010
    Software Development Environment:
    Visual Studio 2008
    • LINQ Support
    LINQ essentially is the composition of many standard query operators that allows us to work with data in a more intuitive way.
    Benefits :
    • significant – Compile time checking C# language queries,
    • 55. ability to debug step by step through queries.
    • 56. Expression Blend Support
    • 57. XAML generator tool for silver light applications.
    Benefits :
    • By this we can get extensive web designer and JavaScript tool.
  • BugTracking System
    May 3, 2010
    Software Environment for Development:
    • Windows Presentation Foundation
    Visual Studio 2008 contains plenty of WPF Windows Presentation Foundation Library templates
    Benefits:
    • extensive graphic functionality.
    • 58. any visual developer who is new to .NET, C# and VB.NET can easily develop the 2D and 3D graphic applications.
    • 59. Multi-Targeting Support
    Benefits:
    • We are able to create, run, debug the .NET 2.0, .NET 3.0 and .NET 3.5 applications.
  • BugTracking System
    May 3, 2010
    Software Environment for Development:
    • Nested Master Page Support
    • 60. LINQ Intellisense and JavaScript Intellisense support for Silverlight applications
    • 61. Intellisense Filtering
    • 62. Multilingual User Interface Architecture - MUI
    • 63. Visual Studio 2008 Split View
    • 64. Debugging .NET Framework Library Source Code
    • 65. In built Silverlight Library
    • 66. Inbuilt C++ SDK
  • Bug Tracking System
    May 3, 2010
    Hardware Environment for Development:
    • PC with 20 GB hard-disk
    • 67. 1 GB RAM,
    • 68. Ethernet Card,
    • 69. Network Connectivity.
  • BugTracking System
    Timeline
    2-3
    4-5
    7-11
    12-18
    21-24
    19-20
    24-26
    26-27
    Time in Weeks
    May 3, 2010
  • 70. Flow Chart
    Flow Chart
    Overview of the Software Function
  • 71. ERD
    ERD Diagram of Bugtracking System
  • 72. BugTracking System
    THE FOLLOWING POINTS WILL COVERED UNDER DATABASE
    1.CREATION OF USER
    For creating user we have to write query as :cerate user user_name identified by password .
    The various privilege assign to user are 1) grant privilege 2)revoke privilege
    May 3, 2010
  • 73. Defect Tracking Software
    2.Creating tables
    May 3, 2010
    BTS | Final Year Project | Dept. of IT
  • 74. BugTracking System
    May 3, 2010
    BTS | Final Year Project | Dept. of IT
  • 75. BugTracking System
    May 3, 2010
  • 76. Bug Tracking System
    May 3, 2010
  • 77. Bug Tracking System
    1.CHECKING REFERANTIAL INTIGRITY
    May 3, 2010
  • 78. Thank You !!!
  • 79. Questions & Answers !!