Database Design

1. TBL_PRODUCT_DETAILS
No 1 2 3 4 5 6 7 Field Name PRODUCTID CODE TITLE DESCRIPTION DEVELOP_ENVIRON SUPPORT_ENVIRON RELEASEDT Data Type Integer String String String String String Date Size 15 150 300 150 150 Constraint Primary Notes

Contains information regarding Product developed by the organizations Generally products are equivalent to the projects developed all the details like supporting environments, code and Release dates are stored in this table. 2. TBL_PRODUCT-VERSION
No 1 2 3 4 5 6 7 8 Field Name PRODUCT_VER_CODE PRODUCTID TITLE DESCRIPTION VERSION_HISTORY RELEASEDT STATUS NOTES Data Type Integer Integer String String String Date Character String Size 150 300 300 1 300 Constraint Composite Foreign Check Notes {11-1}

A|I|S

This table consists of versions for a project. ProjectID in this table has 1 to many relationships with the productId in the Product Details table. Product should not have more than one version active at a time. For efficient maintenance of a product version maintenance is and important module. 3. TBL_PRODUCT_USERS
No 1 2 3 4 5 6 7 8 9 10 11 Field Name UID PRODUCTID ROLE FROMDT TODT IMPORTANCE PARENTID POSITION INDENT DESIGNATION STATUS Data Type Long Integer String Date Date String Integer String Integer String Character Size 15 100 100 1 Constraint Foreign Foreign Check Notes {1-1} {11-1} Admin|User

Foreign Foreign Check

A|I|S

This table consists of details of users of the product. Users can be programmers, Team Leaders. Each user is valid only between fromdt and todt. UID is foreign key and has 1 to 1 relationship with TBL_AUTHENTICATION 4. TBL_USERS
No 1 2 3 4 5 6 7 8 9 Field Name UID FNAME LNAME ADDRESS1 ADDRESS2 PHONE EMAIL MOBILE STATUS Data Type Long String String String String Integer String Integer Character Size 150 150 300 300 15 50 15 1 Constraint Foreign Check Notes

Validate email A|I|S

This table contains details of users like name, phone, email etc. UID maintains 1 to 1 relationship with TBL_AUTHENTICATION. 5. TBL_AUTHENTICATION
No 1 2 3 Field Name UID UNAME PASSWORD Data Type Long Character Character Size 8 8 Constraint Primary Check Notes Unique

This table contains all the users for this bug tracking system. Here the userid is unique for each user. Both Username and password can be either numeric or string. 6. TBL_CONFIGURATION
No 1 2 3 Field Name KEY VALUE STATUS Data Type String String Character Size 15 30 1 Constraint Notes Unique A|I|S

Configuration table consists of all the values, which are configurable in this project. Values like Role, Priority, Platform etc can be configured in this table. Key value consists of the name of the configuration. 7. TBL_LOG
No Field Name Data Type Size Constraint Notes

1 2 3 4 5

UID ACTIVITY ACTIVITYDTTM IPNUMBER PHONE

Long String Date String String

150 100 15

Foreign Date & time of operation -

This table is used to maintain the log history of the users who has logged in. All the activities done by the user from his login to logout are stored in this table. 8. TBL_BUG_DETAILS
No 1 2 3 4 5 6 7 8 9 10 Field Name BUGID CODE TITLE DESCRIPTION PRODUCTID COMPONENT CATEGORY SEVERITY STATUS STATUSDTTM Data Type Long String String String Integer String String String Character Date Size 15 150 300 30 30 15 1 Constraint Primary Foreign Notes

{11-1}

Check Check

High|Low {A|I|S} Date & time of operation

This table consists of details of bugs that occurred in the product development. Both the component and severity are obtained from configuration table. 9. TBL_BUG_ORIGIN
No 1 2 3 4 5 7 Field Name BUGID OS DATABASE IMPACTBY REPORTEDBY REPORTDTTM Data Type Long String String Integer Integer Date Size 15 15 Constraint Foreign Foreign Foreign Check Notes {1-1} {11-1} {1-1} {1-1} Date & time of operation

This table consists of origin details of bugs that occurred in the product development. Both the OS and DATABASE are obtained from configuration table. This table contains the fields Responsible for the bug origin. 10. TBL_BUG_ASSIGN
No 1 2 3 4 5 Field Name BUGID TYPE UID STATUS ASSIGNEDBY Data Type Long String Integer Character Integer Size 15 1 Constraint Foreign Foreign Check Foreign Notes {1-1} {1-1} A|I|S {1-1}

ASSIGNDTTM

Date

Check

Date & time of operation

This table consists of details of assignee to the bug and stored the assigned date time. This table has relation ship with the bugs table. 11. TBL_BUG_RESOLUTION
No 1 2 3 4 5 6 7 Field Name BUGID ACTIONTYPE ACTION DESCRIPTION RESOLVEDBY RESOLVEDTTM STATUS Data Type Long String String String Integer Date Character Size 15 150 300 1 Constraint Foreign Notes {11-1}

Foreign Date & Time of operation A|I|S

This table consists of resolution details for a bug. This stores the necessary action to be taken for resolution, Status and Status date time. 12. TBL_BUG_RESOURCES
No 1 2 3 4 5 6 7 Field Name BUGID TITLE DESCRIPTION RATING RESOURCEBY RESOURCEDTTM UID Data Type Long String String String Integer Date Integer Size 150 300 15 Constraint Foreign Notes {11-1}

Foreign Foreign Date & Time of operation {1-1}

This table consists of resources allotted to a bug. This stores title, description, rating and resource date time. 13. TBL_BUG_FILEATTACHMENTS
No 1 2 3 4 5 6 7 8 9 Field Name BUGID TITLE DESCRIPTION FILEID FILEPATH FILETYPE SIZE ATTACHEDBY RESOURCETTM Data Type Long String String Integer String String Integer Integer Date Size 150 300 300 15 Constraint Foreign Notes {11-1}

Primary

Foreign Date & Time of operation

This table consists of file attachments for a bug. This stores the file type, file path, attached by. The attachments can be a screen shot or a word document.

14. TBL_BUG_HIERARCHY
No 1 2 3 4 5 6 7 Field Name BUGID PARENTID HIERARCHYBY IMPACT POSITION INDENT STATUS Data Type Long Long Integer String String Integer Character Size 300 300 1 Constraint Foreign Foreign Foreign Check Notes {11-1} {1-1} {1-1} A|I|S

This table consists of hierarchy details of a bug. This ParentId in this table represents the origin bug id and the impact specifies the effect of bug on the over all project. 15. TBL_BUG_HISTORY
No 1 2 3 4 5 Field Name BUGID HISTORYBY REMARKS HISTORYDTTM STATUS Data Type Long Integer String Date Integer Size 300 1 Constraint Foreign Foreign Check Notes {11-1}

Date & Time of operation A|I|S

This table consists of history of a bug. This stores history by, Status and history date time.