2. Features

3. INTERFACE  Bug/issue view – the main window for working with separate bugs;  Search view – used for ad-hoc full-text search and narrowing search criteria;  “My Stuff” view – lists all open bugs/issues assigned to the user;  Filter view – allows to customize and use standard bug list filters;  List and statistics views – provide an overview of the situation in selected projects  Reports view – gives access to viewing and customizing reports  Preferences view – lets users quickly customize personal interface settings  Admin view – administrators’ cockpit for managing projects, users, roles, and bug attribute sets etc.

4. WORKFLOW LOGIC  Project – specifies which project the entry belongs to.  Area – shows which area of the project the issue corresponds to (e.g. code, interface, upgrades etc.).  Title – a short description of the problem.  Type – specifies whether the entry is a bug, a suggestion, etc.  Priority – an attribute used for queuing entries.  Version – identifies the version and/or the deadline for which the issue must be resolved.  Category – used as an additional classification attribute.  Phase – shows the phase of the project to which the entry is relevant.  Assigned to – displays the user who is responsible for the issue.  Linked bugs/issues – the area where all linked (“subordinate” or related) bugs are referenced as hyperlinks with numbers and titles.  Time estimate – used for tracking planned and actual resolution time.

5. ACCESS PERMISSIONS –Roles –Users –Records –Fields.  Role-based permissions allow you to control how users from different groups can access different projects in your system.  User-based permissions restrict individual users access to separate projects and ways to handle (view, edit, reassign, resolve) bugs  within these projects.  Record-level permissions allow restricting access to separate entries within a project.  Field-level permissions allow administrators to specify hidden, read- only or change access levels to any particular field or action button on user level.

6. OBJECTIVE  To track and fix the Bug in Software applications and develop it in Microsoft.NET platform. The application is to handle all bugs which arise in the Software applications and are reported by some client or anyone else related to that particular project.  The process requires the application to communicate with the clients through login and then reporting that bug.   The interface must be open so that customers can integrate with Bug tracking system.  The interface must be open to provide review and feedback to improve the interface

7. MODULES  COMMUNICATION MODULE  MAINTAINANCE MODULE  SUMMARY MODULE  ADMIN MODULE

8. COMMUNICATION MODULE  DISCUSSION  HELP  HISTORY  SEARCH

9. MAINTAINANCE MODULE  ADD BUG  DELETE BUG  UPDATE BUG

10. SUMMARY MODULE  It simply shows the summary of BUGS in particular project

11. ADMIN MODULE  CREATE USER  EDIT USER  UPDATE USER

13. BUG Table ConventionData TypeActual Name USR_N_USERIDnumericUSERID USR_C_LOGINIDcharLOGINID USR_V_PASSWORDvarcharPASSWORD USR_V_LASTNAMEvarcharLASTNAME USR_V_FIRSTNAMEvarcharFIRSTNAME USR_V_MIDDLENAMEvarcharMIDDLENAME USR_C_INITIALcharINITIAL USR_V_EMAILADDvarcharEMAILADD USR_C_USERTYPEcharUSERTYPE USR_V_COMPANYNAMEvarcharCOMPANYNAME USR_D_STARTDATEdatetimeSTARTDATE USR_D_EXPIREDATEdatetimeEXPIREDATE USR_C_STATUScharSTATUS USR_C_UPDATEUSERcharUPDATEUSER USR_D_UPDATETIMEdatetimeUPDATETIME

14. ConventionData TypeActual Name BUG_N_PROJECTIDnumericPROJECTID BUG_V_PROJECTNAMEvarcharPROJECTNAME BUG_V_PROJECTCODEvarcharPROJECTCODE BUG_N_PROJECTBUDGETnumericPROJECTBUDGET BUG_C_PROJECTTYPEcharPROJECTTYPE BUG_V_CLIENTNAMEvarcharCLIENTNAME BUG_C_DISCLOSE_SCHEDcharDISCLOSE_SCHED BUG_C_DISCLOSE_EFFcharDISCLOSE_EFF BUG_C_DISCLOSE_SIZEcharDISCLOSE_SIZE BUG_C_DISCLOSE_EOQcharDISCLOSE_EOQ BUG_C_STATUScharSTATUS PRJ_C_UPDATEUSERcharUPDATEUSER PRJ_D_UPDATETIMEdatetimeUPDATETIME

15. *

26. Improve general project organization; Promote online cross-functional cooperation within company; Enhance resource planning; Speed up bug/issue resolution times; Ensure the necessary quality levels at every project stage and functional area; Implement collaborative development scenarios with substantial customer input and feedback; Increase transparency of development and support processes; Efficiently employ international taskforce and development teams; Capitalize on best practices across projects