Defect Tracking Database Term Project, Essay Example

Abstract

Since the recent launch of online content delivery systems, software development teams have been overwhelmed with reported discrepancies, or bugs. Currently, most developers tracking their bugs in an Excel spreadsheet that is located on a centrally located share drive. However, this requires that only one user can enter information into the spreadsheet at any one time. Therefore, using a Microsoft SQL Server 2014 as the back-end database with a .NET front-end could resolve this problem. Once the database design is finalized the database will be imported into the SQL Server database.  The SQL Server will be hosted at the company’s existing web hosting company, Hosting.com. Bugs will be entered into the database and be assigned a tracking number.  This number will be the primary key of the “Discrepancy” table.  Bugs will have an initial status of “Open” until it is updated by a developer.  Once assigned to a developer, the ticket status is automatically to “Assigned”.  A developer can update the status to, “In-Work” or “Resolved”. A status page will be created to display the status of all bugs and a system of database tables will be used to track this information. Last, ongoing maintenance will be conducted. Since the database will be a stored in a Microsoft SQL Server 2014, a SQL Server database administrator will be hired to maintain it.

Purpose and Goal of the Project

Since the recent launch of the companies online content delivery system the software development team (developers) has been overwhelmed with reported discrepancies, or bugs. Currently, the developers are tracking their bugs in an Excel spreadsheet that is located on a centrally located share drive. While this method is easy and has been the one conventionally used, it is not practical in the modern setting. Only one user may enter information into the spreadsheet at any one time. Even with current file sharing technology, this aspect of this data entry methodology makes it challenging for all workers to see information at the same time if the information is actively being entered. Therefore, it is necessary to find a resolution to this problem.

To resolve this issue, management teams have assembled a dedicated team of Tier I support to answer customer calls and enter the bugs into the excel spreadsheet. This process is time consuming and can be considered as waste of resources as well. This has caused concurrency problems and the Tier I support manager has asked the developers to create a central database to manage the bugs. The database should allow multiple users to access and update information at the same time. The database should also be accessible from the internet so remote developers can also access the bug tracking database. By optimizing this type of application, both customers and business professionals will be able to access information both rapidly and concurrently, independent of their physical location. Eventually, the customer will also have access to the database to view the status of the bugs they report. The goal of the project is therefore to create a database that meets these requirements.

Users and Administrators

Software development teams will benefit from this work, while project managers and business professionals with be able to use this software solution in order to enhance their business practices. Bug checking is considered to be a challenging task to complete if codes are sorted manually for bugs and then recorded by using an inefficient recording platform. Therefore, this method is expected to save the time of the individuals that are willing to use it.

Proposed Solution

The project manager has decided to use Microsoft SQL Server 2014 as the back-end database with a .NET front-end.  The first deliverable for this project will be to construct a prototype Access database as a proof of concept and a template for the production database design.  The database will mirror the functionality of the SQL Server.  Once the database design is finalized the database will be imported into the SQL Server database.  The SQL Server will be hosted at the company’s existing web hosting company, Hosting.com.

Data Elements

Bugs will be entered into the database and be assigned a tracking number.  This number will be the primary key of the “Discrepancy” table.  Bugs will have an initial status of “Open” until it is updated by a developer.  Once assigned to a developer, the ticket status is automatically to “Assigned”.  A developer can update the status to, “In-Work” or “Resolved”.

A status page will be created to display the status of all bugs.  Bugs can be filtered by status, developer and Bug number.  Any bug that has not been assigned to a developer within 3 days will be displayed at the top of the status page with a red background.  Also, any bug that has not been set to “Resolved” within 10 days will be displayed at the top of the status page with a red background.  Bugs that have been set to “Resolved” will be displayed in the report with a green background.

Platform to be Used

Microsoft SQL Server 2014

Database Tables

Developers

• DeveloperID (Primary Key)
• DeveloperName (Text)
• DeveloperEmail (Text)

Bugs

• BugID (Primary Key)
• CustomerID (Foreign Key from Customers table)
• StatusID (Foreign Key from Status table)
• StatusDate (Date)
• DeveloperAsssigned (Foreign Key from Developers table)
• BugTitle (Text)
• BugDate (Date)
• BugDescription (Text)

Status

• StatusID (Primary Key)
• StatusName (Text)

Customers

• CustomerID (Primary Key)
• CustomerName (Text)
• CustomerEmail (Text)
• CustomerPhone (Text)

Ongoing Maintenance

Since the database will be a stored in Microsoft SQL Server 2014 and SQL Server database administrator will be hired to maintain it.  The company will be transitioning more of its data storage to SQL Server. Periodic examinations will be conducted to determine whether the solution is effective and necessary interventions will be applied to the system as deemed necessary. It will be necessary to constantly review the system to see if it is meeting the needs of individuals and business professionals. Optimization of the system may become necessary over time. Furthermore, for the functionality of the system to be effective, it will be necessary for it to be updated with new records of errors over time. The system will continue to act as a reasonable resolution to the problem as long as the team continues to work with it to ensure that it is relevant. Furthermore, training on this system should be provided to non-information technology professionals so that they feel fully comfortable using in in place of Excel spreadsheets to achieve the same purpose. The system will be used as long as its utility remains.

References

Codd, Edgar F (1970). A Relational Model of Data for Large Shared Data Banks. Communications of the ACM, 13(6): 377–87.