Bug Tracking System Provides The Job Computer Science Essay Example

bugs, as well as replicate them. When a bug is found, it is reported to the programmer for fixing and the tester is informed. The tester then checks if the bug has been fixed. If it has, the bug is marked as closed. If not, its status remains unchanged in the database. The project manager receives notifications about bugs from the system and examines the database for new and unresolved issues. They assign new bugs to programmers and request prompt resolution for those that are still not fixed.

Bug track is a reliable and secure web-based project management system and professional issue-tracking solution that supports multiple languages including English, Swedish, German, and Japanese.

Users have the option to select their desired language and there will be increased connectivity in the upcoming days. All system fields can handle Unicode for any chosen language. The bug tracking system is a convenient, secure, and dependable web-based tool that supports multiple languages. It serves as a professional system for managing projects and keeping track of issues.

The bug tracking system is user-friendly, with an intuitive user interface that eliminates the need for learning. It offers reliable performance, ensuring fast response times and 99.9% uptime. For security, the system is hosted on servers located in the Equinox datacenter in Chicago, known for its trustworthiness and protection. The information within the system is meticulously maintained with high levels of security.

Bug tracking is a web-based system available online with no need for installation or additional hardware or software purchases. The literature review focuses on bug tracking, which addresses the problem of bugs in software. These bugs are not a result of bad developers or poorly

written code, but rather the inability to anticipate all potential user actions. Users are often the cause of program crashes, not the code itself. To simplify error handling, the Debian bug tracking software is utilized to plan, manage, track, and coordinate software before its release to clients. A bug tracking system is a computer application designed to aid users in managing and tracking reported software bugs.

A bug tracking system is a type of issue tracking system that incorporates a database for storing factual information. This information, including the time of bug report, affected versions, complexity/priority, and bug-solving details, is stored within this primary component. The primary benefit of utilizing a bug tracking system lies in its capacity to provide a concise and centralized perspective on development requests. In existing systems, software development adheres to a sequence of steps wherein the project manager delegates tasks to team members upon receiving a project.

Once the analysis, design, and coding phases are completed, the software is transferred to a tester whose responsibility is to identify any bugs in the software. The tester reports these bugs to their project manager by documenting them on paper and sending them over. The project manager then evaluates the importance of each bug and assigns programmers to fix them.

The programmer fixes the bugs and gives a report to the project manager. Bugs are inevitable in the development of any software and can occur at any stage of growth in any kind of product. Proper maintenance and attention to detail for bugs is crucial.

4) Bugs have negative effects on both the software and the software development team. The current system has drawbacks, including being

effort and time consuming. Testers have to write details of bugs on paper and follow unnecessary formalities when presenting the paper. When there are many bugs, sorting them based on priority by referring to the paper becomes challenging for the project manager. This can negatively impact the project's timeline.

During a project, there may be human errors that can cause various issues. For example, if there are many bugs, the tester might not accurately report all of them. Likewise, the project manager may struggle to categorize bugs correctly based on their importance. Additionally, insufficient communication among team members can also be problematic.

Sometimes, a poor relationship between developers and their project manager can result in the creation of an ineffective product. This, in turn, hampers the achievement of optimal quality and ultimately leads to a decline in the overall quality of the product.

Not effectively managing and addressing bugs can lead to difficulties in tracking them, which can waste effort and increase project costs.

The existing method of searching the complete database for a possible bug that might have happened previously is both laborious and susceptible to mistakes.

The purpose of the proposed system is to analyze the existing system based on the problem statement, address its issues, and determine the necessary requirements.

The proposed system should possess the following qualities: 1) It should be interactive and ensure quick access with minimal time consumption. 2) There should be minimal human errors, making it error-free. 3) It should provide high security and ensure the best quality. 4) It should be user-friendly for everyone. 5) It should be cost-effective. 6) It should enhance customer satisfaction and facilitate effective communication.

The advantages of the proposed

system are that it provides product, bugs, and bug tracking. It also keeps all information from bug origin to bug resolution, including maintaining bug history. Additionally, the system stores versions of each product in a database for easy maintenance.

In the proposed system, the search is based on status, priority, and operating system, which means that this product provides efficient search techniques. The proposed system also provides a fully authenticated system with username and password encryption. This allows users to keep track of bugs in a product with lower cost and effort. Additionally, bug tracking software is a Defect Tracking System or a set of scripts that provides and maintains a database of problem reports. Bug tracking software enables individuals or groups of developers to effectively keep track of unfixed bugs in their product.

Bug tracking software enables the tracking of bugs and code changes, facilitates information sharing among teammates, allows for the submission and review of patches, and provides standard assurance. The benefits of bug tracking software include improved communication between groups of people, increased software standards, enhanced customer satisfaction with bug-free software, accountability, and overall productivity. Implementing bug tracking software in an environment can yield these benefits. With numerous bug tracking software packages available, it is important to determine specific bug tracking requirements before choosing a solution. The 2.5Bug Tracking Software for Windows assists in effectively managing developing projects by tracking bugs.

This software provides information on the number of processed bugs, pending bugs, and closed bugs, resulting in improved user response. It allows multiple users to access it simultaneously and records bug reports in a database. It offers features like auto login, attachments,

bug versions, sorting, and date. To ensure effective bug tracking, it is important to organize and protect the firm's data, as the bug reports can contain hours or even days of activity.

The backup must be recorded and maintained daily in a database. It is also crucial to have a daily build of the software in an environment where bug tracking is effective. This enables testers to test the most recent version of the software and prevents them from reporting bugs that have already been fixed.

They also quickly identify newly introduced bugs while the code is still fresh in the memory of the developers who introduced them. It is recommended to use build numbers to specify the version of software in which a bug was found, fixed, and verified. Revision numbers of modified source code modules can be helpful for developers but are not necessary for coordinating work between test and development. A process should be in place to handle bug reports and ensure that they are not closed prematurely. This process should require the person who reported the bug to verify its resolution or approve any other type of resolution. The typical bug report life cycle includes the following status values: New, Assigned, Resolved, Verified, and Closed.

Use a resolution field to specify how problems are resolved and to keep the bug report life cycle simple. Possible resolutions include: Fixed, Won't Fix, Not Reproducible, Duplicate, By Design, and External. Avoid triaging bug reports in meetings as this will waste man-hours that could be used for fixing bugs. If a triage is necessary due to schedule constraints, do not close bug reports in the meeting

as this bypasses the quality process by bypassing testers who report bugs. Instead, utilize the bug triage to reprioritize, postpone, or resolve issues as "won't fix".

It is important to handle feature requests and bug reports separately. This ensures effective triage and accurate statistics for measuring software quality.

In order to save developers time, bug reports should include a step-by-step description of how to reproduce the bug. Identifying the minimal steps needed further optimizes developer efficiency.

Keep bug reporting simple. Avoid making it complicated by asking for unnecessary data. If bug reporting becomes too burdensome, some bugs might not be reported at all or people could resort to reporting bugs through email or word-of-mouth.

Keeping records of how bugs are detected is useful in deciding how to allocate testing resources effectively. The options for the "detection method" field include Interactive Testing, Test Script Execution, Test Script Design, Unit Testing, Integration Testing, Code Review, Beta Testing, and Customer Report.

2.6 Debian: The operating system's kernel is Linux. Various other applications are necessary.

The distribution of software based on the Linux kernel is known as a distribution, and companies that produce and distribute such software are called distributors. These distributors earn revenue through the sale of packaged software and by offering support and training services. The Debian Project is a collaborative group that has developed an operating system called Debian GNU/Linux, or simply Debian, which is freely available.

Developers of Debian are currently improving the operating system to provide assistance for different OSs like Hurd, NetBSD, FreeBSD, and possibly Windows. These developers belong to a reliable internet network where GPG keys are mutually signed. Debian is an open-source and free computer OS that is

widely acknowledged as the original Linux OS with a GUI. It offers a wide range of software packages which can be freely obtained from the internet.

Debian is unique among other distributions due to its organizational structure rather than being a company. It is freely accessible under an open license and can be utilized as both a server operating system and a desktop system.

Debian is a community that includes volunteers, specifically Debian members or maintainers. These individuals do not engage in sales but instead work together towards the common goal of creating a high-quality operating system that is also affordable.

There are multiple ways to acquire free software. You can either directly download it from the internet or buy it on a CD from a distributor. The analysis phase of the project encompasses both the creation and evaluation of its feasibility.

Feasibility study is vital as it assesses a system's efficiency in managing the risks and circumstances that arise during implementation. In an ideal scenario, all projects would be feasible with ample resources and unlimited time. However, this is not achievable in reality.

The text discusses the importance of feasibility studies, which simulate future development processes to determine their worthiness. These studies focus on economic feasibility, legal feasibility, and time feasibility.

When developing this system, three factors must be taken into consideration: technical feasibility, resource feasibility, and economic feasibility. Luckily, the system does not necessitate any monetary investment and instead utilizes existing resources. Additionally, as the current scope of the system does not involve any commercial intentions, economic feasibility is unnecessary.

3.2.2 Legal Feasibility: The system development must be evaluated to determine if there are any legal violations or liabilities. It

is important to mention that the current scope of the system does not include commercial use.
3.2.3 Time feasibility: Meeting the project deadline is crucial since this is an ongoing project. Thus, it is essential to ensure that the project can be completed within the specified timeframe.

3.2.4 Technical feasibility: The technical feasibility of this project is high because there is already a developed dataflow machine in place. Therefore, there is no need to develop new technology.
3.2.5 Resource feasibility: This debian bug tracking system does not require a large amount of resources. It only needs a development center with personal computers equipped with the necessary hardware and software to build the system.
3.3 System Requirement Specification (SRS): The SRS introduction provides information about the purpose, scope, definitions, acronyms, abbreviations, references, and an overview of the document's requirements.

A good solution for tracking bugs in a product, solution, or application is the Debian bug tracking system (DBTS). DBTS allows individual developers or groups of developers to effectively keep track of unresolved bugs in their product, which is also known as a Defect Tracking System. The software requirements specification (S.R.S.) specifies the purpose and target audience of DBTS. The goal of DBTS is to create a fully automated system for tracking various elements within a software solution center, including products, product versions, users (programmers), system configuration, and product hierarchy.

These are the items that need to be tracked before the product is released for production. The scope of the SRS defines the software product that will be created, including its capabilities, objectives, and applications. The project will be implemented in a software development center where there are multiple solutions and technologies that

require manpower to develop. The system is designed to be generic and global, suitable for any client who accepts this architecture. It is considered a middle-term system that will last for five years, and it can be expanded without making significant changes to the underlying architecture and source code. This section provides an overview and roadmap for the SRS.

The remaining sections of the SRS include the product functions, constraints on the system (including assumptions and dependencies), as well as process and data requirements. The use of a Documented Business Workflow Tracking System (DBTS) can greatly enhance productivity and accountability for individual employees by providing a documented workflow and positive feedback for good performance. Section 3.5 of the SRS provides an overall description of the project's main functions, as well as the characteristics of a user for this project.

The assumptions, constraints, and dependencies presented in this section are the result of interactions with the project designer. A more advanced version of DBTS known as Wireless BTS, which is not part of this project, will be incorporated into the wireless data entry in future versions 2.0 – 2005. This will be done through decks and cards embedded in each employee's wireless devices, restricted to within the company. This section of the SRS provides a description of the observable aspects of a software system, including a description of the entire system. The interface for the DBTS system requires a combination of interactive .net computing software and MS Internet Explorer web browsers. Workstations connected to the intranet central server are also necessary for distributed and scalable data distribution to clients. The user interface for this system will be an

MS capable web browser, though it can be viewed optimally in any third party web browser.

The hardware interface for the workstation client includes the central server intranet connection as well as a mouse and mouse pad and a keyboard. The software interface requires an MS capable browser to access the intranet server, the MS developers network, and the MS Developers Kit from MS or visual studio IDE 7.0, 7.1, and 7.2. A text editor is also needed for preparing HTML files. In terms of communication interfaces, the server communicates with clients on workstations through the intranet access. There are four modules in this system, one of which is the Authenticate User module. To begin, the Bug Tracking System activates the login form.

When the user enters their username and password, our system begins the authentication process by verifying them against the username and password stored in the database. If the password is a match, the user is granted access to the main page. If not, they are notified of an invalid username and password. Once successfully authenticated, the system enables menus and logs any failures or security breaches. Additionally, the user is presented with a list of existing products, allowing them to view details and make modifications.

This project allows for the addition of new projects. All products have multiple versions to accommodate the completion of the entire project. The features needed for each product are classified into different versions with set deadlines. The versions are completed based on their respective deadline dates. Additionally, users have the capability to add new versions or make modifications to existing version details.

Product Users: Each product is assigned resources or

users in order to complete the project. First, all employees' names and qualifications are stored in the database. Each user is assigned to a product based on their rating, qualification, and designation. The effective date is also stored for each user, indicating the period they are valid for that product.

Bug Details: This module allows users to add or update bugs. As the number of bugs for a product can be significant, this system is equipped with efficient filtering capabilities.

The user has the option to filter the bugs by priority, database, operating system, and status. Once the user applies the filters, the bug list is retrieved from the database. Bug History: This section keeps track of all the solutions provided by different users for bug resolution. Given that bugs often require multiple techniques or methods for resolution, it's crucial to maintain a history of each bug.

The Bug Assignee feature shows a list of users assigned to resolve the bug. Since multiple users may need to work together to find a solution for the bug, the user can add the bug to a new user or modify existing user details. The Bug Attachments feature provides a list of attachments related to the bug, whether it's a database bug or a GUI bug.

When adding a bug, it is necessary to include the bug details. The file attachments can be in the form of a document, database file, or image file. These attachments are stored in a specific location and include information about their size and type. Users have the option to add new attachments or modify the details of existing files. The bug tracking system also includes a

hierarchy for organizing the bugs saved in the database, allowing for related bugs to be linked together.

Through this hierarchical structure, the user has the ability to add child nodes and make changes to existing node values. The hierarchy is defined by the parent-child relationship between bugs. The "Track Resolution" feature shows a list of all solutions given by users assigned to a bug, including the action type and the resolution provided.

The "Track Resources" section shows a list of resources assigned to the project. Resources are provided to resolve bugs, and these resources are assigned based on employee ratings. The "View Product Bug Hierarchy" module displays the bug hierarchy for easy reference.

Here, the bugs are presented as parent-child nodes to make it easier for users to navigate the large number of bugs in the database and understand their relationships. The Product User Hierarchy module is designed to show the users assigned to each bug, including their names and designations. Additionally, there can be a hierarchy of employees based on their designations when allocating resources.

This module simplifies the employee hierarchy by providing an advanced search feature. In general, the number of bugs for a project has increased significantly, making it time-consuming to locate specific bugs. However, with the search screen provided, users can filter bugs based on priority, product, severity, database, and operating system type. Additionally, they can list bugs within a specific time range by specifying a start date and end date.

After performing a search, a list of bugs is displayed. From this list, the user has the option to modify existing bugs or add new ones. The Admin Users module displays all users of the

system. Users can add new users or update information for existing users. For enhanced security, passwords provided by users are encrypted before being saved to the database.

This module stores information such as address, phone, and email. The configuration allows all the values used in the system to be easily adjusted. Additional values like status, priority, and others can be dynamically added on the screen. Instead of hard coding these fields and requiring the user to contact the developer for new values, this feature allows values to be added directly from the screen. Additionally, the user has the ability to change the status to In Active whenever desired.

Log View: To enable efficient tracking of system logs, they are maintained. However, as the logs can become extensive, it may be difficult for users to check the database. The Log View module allows users to search for logs based on the user and records within a specific start date and end date.

Logout: When a user clicks on "Log out", the session variable is terminated and the system is then redirected to the login page.

At every stage, whenever a user clicks a button to perform an operation, the Bug Tracking System will automatically log the activity.

4.11 System Environment
4.11.1 Hardware Specifications:
The bug tracking system is developed with the following hardware specifications:

Application Server Configuration:
- Content Type: Computer processor
- Content: Pentium 4 or later versions
- Content Type: Clock speed
- Content: 2.26 Processor
- Content Type: Hard Disk
- Content: 40GB or more
- Content Type: RAM
- Content: 256MB or more
- Content Type: Ethernet Card
- Content: 32 bit PCI
- Content Type: Modem
- Content: 56KBPS

Database Server Configuration:
- Content Type: Computer processor
- Content: Pentium 4 or later versions
-

Content Type: Clock speed
- Content: 2.26 Processor
- Content Type: Hard Disk
- Content: 40GB or more
- Content Type: RAM
- Content: 256MB or more
- Content Type: Ethernet Card
- Content: 32 bit PCI
- Content Type: Fire wall protected

Client System Configuration:
- Content Type: Computer processor
- Content: Pentium 4 or later versions
- Content Type: Clock speed
- Content: 2.26 Processor
- Content Type: Hard Disk
- Content: 40GB or more
- Content Type: RAM
- Content: 256 MB or more
- Content Type: Modem
- Content: 56KBPS

4.11.2 Software Specifications:
The bug tracking system is developed with the following software configuration:

Application Server Configuration:
- Content Type: Operating System
- Content Used: Windows 2000 Server or later versions
- Content Type: Application Server
- Content Used: IIS 5.0
- Content Type: Driver
- Content Used: Thin driver
- Content Type: Front End
- Content Used: Java / MS.Net
- Content Type: Scripts
- Content Used: VB / JavaScript

Database Server Configuration:
- Content Type: Operating System
- Content Used: Win2000 server or later versions
- Content Type: Back End
- Content Used: SQL Server 2000

5.CURRENT TECHNOLOGIES: Introduction to Java: The Java language was initially referred to as OKA but was later renamed JAVA in 1995. Initially, Java was not developed for the internet; instead, its primary purpose was to create a platform-independent language capable of functioning on various architectures. This would enable the development of new software to be integrated into different consumer electronic systems.

Java was created at Sun Microsystems in 1991 by a team of individuals including Mike Sheridan, Chirs Warth, James Gosling, Ed Frank, and Patrick Naughton. It took 18 months to develop the first working version of Java. C, a structured language known for its ease of learning and power, was widely

used by programmers. However, as programs became more complex, the need for C++ arose to address these complexities.

The problem with C and C++ languages is that they are designed for a specific target. This limitation means that C++ can only compile for a particular CPU, requiring a dedicated compiler and resulting in high costs and time-consuming development.

The need for a simple, cost-effective, and time-saving language led programmers to develop a portable and platform-independent solution that could generate code and run on any CPU in various environments. This was the initial motivation behind Java's creation. The World Wide Web (WWW) is widely known, and Java became relevant because the web required portable and platform-independent programs. The web encompasses different operating systems, central processing units, and various systems. Users want to be able to run programs from different platforms connected to the web.

The creation of Java was driven by the need for a programming language that could produce portable programs for the web. Initially a low priority issue, it became a prominent necessity as the internet grew in importance. The desire for an architecture-neutral language played a role in sparking Java's development, but it was ultimately the internet, specifically the World Wide Web, that led to Java's significant success. Java inherits many characteristics and attributes that contributed to the success of C++ and C.

Introduction to Java database connectivity (JDBC) Open Database Connectivity (ODBC): ODBC provides a consistent interface for interacting with a SQL-based database engine and accessing metadata about the database system vendor, data storage, and data location. The database management system usually provides specific drivers or "bridges" for their respective systems. ODBC and SQL can be

used to connect to a database and efficiently make changes to it. Originally a PC standard, ODBC has now become almost an industry standard. Although SQL is well-suited for manipulating databases, it is not suitable as a general-purpose application language. Programmers primarily use SQL to communicate with databases, but another language is necessary to process SQL statements, display results, or generate reports. Unfortunately, writing a program that can run on multiple platforms is not easy, despite the progress made in standardizing database connectivity.

If you were to create a database client using C++, you would need to rewrite the client for each platform. This means that the version designed for a PC would not be compatible with a Macintosh. There are two reasons for this. Firstly, C++ is not a portable language because it lacks a complete specification. For example, the number of bits that an int holds is not defined in C++. Secondly, different platforms have varying support libraries, such as network access and GUI libraries. However, Java provides a solution to these issues. Java programs can run on any Java-enabled platform without requiring recompilation.

The Java language has a complete specification and a Java-enabled platform must support specific libraries. An example of such a library is JDBC, which can be considered as the Java equivalent of ODBC and is becoming a standard. Database vendors are developing bridges that connect their systems with the JDBC API. Additionally, JavaSoft has created a bridge driver that converts JDBC to ODBC, enabling communication with older databases that are unaware of Java's existence. Usin