DEFECT TRACKING SYSTEM
Development of a web based Defect Tracking System
- Title of the project: Defect Tracking System
- Domain: Software Industry
- Sub Domain: Testing and Quality Division
- Project Architecture: N-Tire Architecture
- SDLC methodologies: Waterfall model
- Abstract of the project:
This project is aimed at developing an online defect tracking system useful for applications developed in an organization. The Defect Tracking System (DTS) is a web based application that can be accessed throughout the organization. This system can be used for logging defects against an application/module, assigning defects to individuals and tracking the defects to resolution. There are features like email notifications, user maintenance, user access control, report generators etc in this system.
The software is fully integrated with CRM (Customer Relationship Management) as well as CMS (Content Management System) solution and developed in a manner that is easily manageable, time saving and relieving one from manual works.
A: Following tasks can be performed with the application:
- User Maintenance
- Component Maintenance
- Defect Tracking
- Report
User Maintenance: Creating, Granting & Revoking access and deleting users from application.
Component Maintenance: Creating a component (application being developed/ enhanced), Granting & Revoking access on components to Users and Marking a component as “Active” or “Closed”.
Defect Tracking: Creating, Assigning defects to users, Modifying and Closing a defect. A defect screen should at least have following details
- Defect Id and Title
- Defect priority
- Date created
- Defect description
- Defect diagnosis
- Name of originator
- Status
- Resolution
Report: Generate reports on defects.
B: Following additional tasks also can be performed by this application:
- Find User
- Find component
- Find defect
Find User: A search screen to find users and display results.
Find component: A search screen to find components and display results.
Find defect: A search screen to find defects and display results.
7. EXISTING SYSTEM:
- Defect Tracking System is a web-based application designed to help a workgroup keep track of Defects and tasks via a shared central resource. The system was designed specifically with the IT department in mind, where quick access to shared data and history is a requirement, both from an internal organizational perspective, as well as to fulfill the needs of the customers.
- It provides one roof solution for all the Defects issues in the software development. It doesn’t provide any kind of solution to any kind of problem. It only acts as a means to transmit the issues and their details to the concerned office personnel with accuracy. It is a tool that helps in providing the solution for the Employee request Log in right time.
- In addition to all these, it also maintains the preferences, customized settings, priorities, users, etc. It is very critical to solve different kind of reports at a time in the existing system. The IT departments have different Operational Administrators who were providing so many problems in each and every day. Tracking these defects is a tough job.
8. PROPOSED SYSTEM:
- The development of the new system contains the following activities, which try to automate the entire process keeping in view of the database integration approach.
- User friendliness is provided in the application with various controls. The system makes the overall project much easier and flexible to the end user. It can also be deployed over the Internet. Various classes have been used to provide file upload and mail features. There is no risk of data mismanagement at any level while the project development is under process. It provides high level of security using different protocols like https etc. The system Interface provides good environment to solve any kind of defect.
- The system capture the overall details of any defect from this user interface and send it to the particular administrator. Every defect details must be stored in the centralized data base server which can be organized by the company.
9. MODULES:
1) Administrator
2) Operational Administrator
3) Operator
4) Defect Tracking
5) Search
6) Reports
7) Registration and Authentication
10. Functionalities of the System:
1. A user should be able to:
- Login to the system through the first page of the application.
- Change the password after logging into system.
- View the defects assigned to the User.
- Find defects for components on which the user has access.
- Find components on which the user has access.
- Modify the defects by changing / putting values in fields.
- Assign defects to other users having access to the component.
- Find details of other Users.
- Generate reports of defects for components on which the user has access.
2. As soon as a defect is assigned to a user a mail should be send to the User.
3. The Application Admin should be able to do the following tasks
- Add a new component.
- Remove Component Admin privilege from a user.
- Add a new user.
- Remove a user.
11. Keywords:
- Generic Technology Keywords: Databases, User Interface, Programming
- Specific Technology Keywords: ASP.Net, C#.Net, MS SQL Server
- Project Type Keywords: Analysis, Design, Implementation, Testing
- SDLC Keywords: Presentation, Business Object, Data Access Layers
12. Environment:
- Servers:
- Operating System Server: - Microsoft Windows 2000 or Higher
- Data Base Server: Microsoft SQL Server 2000/2005
- Clients: Microsoft Internet Explorer,
- Tools: Microsoft Visual Studio .Net
- User Interface: ASP.NET with AJAX
- Code Behind: VC#.NET
13. Requirements:
- Hardware requirements:
Number | Description |
1 | PC with 2 GB hard-disk |
- Software requirements:
Number | Description |
1 | Windows 2000/ XP/ or Higher with MS-office |
2. | MS-SQL server2000/2005 |
3. | Ms-Visual Studio .Net 2005 |
4. | Ms-Internet Explorer |
14. Milestones:
No. | Milestone Name | Milestone Description
| Remarks
|
1 | Requirements Specification | Complete specification of the system including defining hierarchies constitutes this milestone. A document detailing the same should be written and a presentation on that be made. | Attempt should be made to add some more relevant functionality other than those that are listed in this document. |
2 | Technology familiarization | Understanding of the technology needed to implement the project. | The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective. |
3 | Database creation | A database of at least 10 entries of users with at least 1 should application admin. | It is important to finalize on the database at this stage itself so that development and testing can proceed with the actual database itself. |
4 | High-level and Detailed Design | Listing down all possible scenarios and then coming up with flow-charts or pseudo code to handle the scenario. | The scenarios should map to the requirement specification |
5 | Development of front end functionalities. | Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options | During this milestone period, it would be a good idea for the team to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind. |
6 | Integrating the front-end with the database | The front-end developed in the earlier milestone will now be able to update the database. Other features should be functional at this stage. In short, the system should be ready for integration testing. |
|
7 | Integration Testing | The system should be thoroughly tested by running all the test cases written for the system (from milestone 5). | Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged. |
8 | Final Review | Issues found during the previous milestone are fixed and the system is ready for the final review. | During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled |
Defect Tracking System - Screens by finalyearprojects
0 comments:
Post a Comment