Development of a web based Flaw
Tracking System
1. Title of the project: Flaw Tracking System
2. Abstract of the project:
This project
is aimed at developing an online flaw tracking system useful for applications
developed in an organization. The Flaw Tracking System (FTS) is a web based
application that can be accessed throughout the organization. This system can
be used for logging flaws against an application/module, assigning flaws to
individuals and tracking the flaws 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
·
Flaw
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”.
Flaw Tracking: Creating, Assigning flaws
to users, Modifying and Closing a flaw. A flaw screen should at least have
following details
·
Flaw
Id and Title
·
Flaw
priority
·
Date
created
·
Flaw
description
·
Flaw
diagnosis
·
Name
of originator
·
Status
·
Resolution
Report: Generate reports on flaws.
B: Following
additional tasks also can be performed by this application:
·
Find
User
·
Find
component
·
Find
flaw
Find User: A search screen to find
users and display results.
Find
component:
A search screen to find components and display results.
Find flaw: A search screen to find flaws
and display results.
3.
EXISTING SYSTEM:
Ø
Flaw
Tracking System is a web-based application designed to help a workgroup keep
track of Flaws 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 Flaws 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 flaws is a tough job.
4. 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 flaw.
Ø The system capture the
overall details of any flaw from this user interface and send it to the
particular administrator. Every flaw details must be stored in the centralized data
base server which can be organized by the company.
5.
MODULES:
1) Administrator
2) Operational Administrator
3) Operator
4) Flaw Tracking
5) Search
6) Reports
7) Registration and
Authentication
Administrator
Administrator can perform
these following tasks
User
Maintenance
Users of this system treated as employees. Employees can
be recruited by the administrator. Administrator is only authenticated to
assign roles to employees
Role
Management
In this system role
management can be done by the administrator. The roles can be classified into
these types
·
General
Employee
·
Net
work Administrator
·
Data
Base Administrator
·
Technical
Administrator
·
General
Administrator
Based on the employee
experience administrator can assign different roles to various employees which
are register into this system.
Component
Maintenance
Here component in the sense
of software which are using in this organization. The component can be
classified into different types and modules
1.
Operating
System Software
2.
Programming
Software
3.
Networking
Software
4.
Data
Base Software
The above all tasks should
be performed by Admin only.
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”.
Operational Administrator
In this system
who can responsible for solve any flaw in the organization is treated as
Operation administrator. For every
operational administrator we are having one target mail id. Based on this mail id employee send his flaw
report. After receiving any flaw from the employee, these administrators are
responsible for sending an acknowledgement to the employees.
After solving
the flaw the administrator can send a reply notice to the employees.
Operator
Here operator
is treated as employee only. An operator role is sending flaw report to the
concerned operational administrators.
Operator can post the completed information regarding the flaw which are
facing by him.
Additional
feature is having by an operator is he can set the priority of that flaw. Based
on the priority operational administrator can solve those flaws.
Flaw Tracking: Creating, Assigning flaws to users,
Modifying and Closing a flaw. A flaw screen should at least have following
details and this flaw report can be verified by concerned admin. After verify
he can send the status to the employees.
·
Flaw
Id and Title
·
Flaw
priority
·
Date
created Date and Time
·
Flaw
description
·
Operator
Details
·
Operational
Administrator
·
Status
Report: Generate reports on flaws. Reports can be generated by
the administrator.
Search: Search can be provided by every user of this
application. Administrator can search what types of component are used in this
organization. Employees can search their own profiles.
Registration and Authentication
Every user must
be a registered person. This registration can be approved by the administrator.
After successful completion of registration process a user can able to log in
into the system. The user credentials can be validated in this authentication
module.
Password management
like forgot password and remember password features can be added in
authentication modules.
6. Requirements:
·
Hardware
requirements:
Number
|
Description
|
1
|
PC with 2 GB hard-disk
and 256 MB RAM
|
·
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
|
No comments:
Post a Comment