My Profile
Active Members
TodayLast 7 Days
more...
Awards & Gifts
Online Exams
Fresher Jobs
Our fresher job section is exclusively for fresh graduates! Find jobs for freshers in major Indian
cities including Bangalore, Chennai, Hyderabad, Pune or Kochi
Resources
Find educational articles, blogs, discussion threads and other resources.
Colleges
Find details about any college in India or search for courses.
|
Development of DTS
Posted Date: 19 Mar 2008 Resource Type: Articles/Knowledge Sharing Category: General
|
Posted By: Deepu Member Level: Diamond
Rating:  Points: 5
|
|
|
Development of a Defect Tracking System (DTS)
Abstract
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.
Keywords
Generic Technology keywords
Databases, Programming, Network and Middleware
Specific Technology keywords
HTML, Active Server Pages, VB, MS SQL Server
HTML, Javascript, JSP, Servelets, Oracle
Unix Shell, Java, SQL
Project type keywords
Analysis, Design, Implementation, User Interface.
Functional components of the project
Following is a list of functionalities of the system. More functionalities that you find appropriate can be added to this list. And, in places where the description of a functionality is not adequate, you can make appropriate assumptions and proceed.
Following three tasks can be performed with the application :
(a)User Maintenance: Creating, Granting & Revoking access and Deleting users from application.
(b) Component Maintenance : Creating a component (application being developed
/ enhanced), Granting & Revoking access on components to Users and Marking a component as “Active” or “Closed”.
(b)Defect Tracking : Creating, Assigning defects to users, Modifying and Closing a defect. A defect screen should at least have following details
Defect Number and Title
Defect priority
Date created
Defect description
Defect diagnosis
Name of originator
Name of Assignee
Status
Resolution
(c) Find User: A search screen to find users and display results.
(d) Find component: A search screen to find components and display results.
(e) Find defect : A search screen to find defects and display results.
(f) Report: Generate reports on defects.
Accordingly there would be following levels of user privileges :
Application admin having all privileges.
Component admin having privileges (b),(d),(e),(f) for the components they own.
Users having privileges for (b),(d),(e),(f) for components they have access to.
All should have privileges for (c).
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. A Component Admin should be able to do the following tasks in addition to 1:
Add an User to the component for creating and modifying defects against that component.
Remove a user from the component.
Mark a component as “Active” / “Closed”. No new defects can be created against a “Closed” component. A component cannot be closed until all defects against the component are also closed.
4. The Application Admin should be able to do the following tasks in addition to 1 & 3:
Add a new component.
Add an user to a component as Component Admin.
Remove Component Admin privilege from a user.
Add a new user.
Remove a user.
Steps to start-off the project
There are couple of alternatives to implement such a system.
A. Microsoft platform: The system is developed using Active Server Pages as the
front end and SQL Server as the back end.
B. Unix-based platform: HTML and JSP/Javascript as front end,
Servelet programming in Java, any relational database (eg Postgress / Oracle /
My SQL), and tools in Unix
The following steps will be helpful to start off the project.
1. Study and be comfortable with technologies such as
Active Server Pages/HTML and SQL server.
Unix commands, Shell programming, Java Programming, SQL.
Some links to these technologies are given in the ‘Guidelines and References’
section of this document.
2. Create a user database with different access levels.
3. Assign a mail-admin who will create mail-ids for the people in the intranet of your lab
or in the internet. These mail-ids will be used for sending automatic notifications and
reports. The mail-admin will also take care of assigning the logins to the users of the
application.
4. Create the front-page of the application giving a brief description and a login box.
5. Create the help-pages of the application in the form of Q&A. This will help you also
when implementing the application.
|
Responses
|
No responses found. Be the first to respond and make money from revenue sharing program.
|
|
Watch TV Channels
|