Bug Reporting System

Hanoi-Aptech Computer Education
Group 120
Bug Reporting System Documentation
Group 120
Group Member Trn Thanh Tng V Hi ng Trn Ngc nh Hong Trung
- Hanoi, <10>/<2009> -
Bug Reporting System
Page 1 of 21
Group 120
INDEX
Problem Definition.................................................................................................................................3 Architecture & Design of Project...........................................................................................................5 2.Checklists...........................................................................................................................................21
Page 2 of 21
Group 120
Problem Definition
Problem Abstraction To day, with special development of information technology, management as more easily. Information Technology helps a lot in the management of information, access information quickly to help us save time, costs, and improve management effectiveness. With some retail product of companies, Due to some arrears in the delivery of the product, or due to some failures occurred for the product, they want to start up a front end business (like the AfterSales support system of the firm), where the customers can lodge their complaints, or reports regarding their concerns either by calling to the help desk lines or through the mail ids as provided in the product menu and on the bill receipt of the product. Applications Bug Reporting System meet the requirements as: it is a standalone application, it was built to record the complaints/reports lodged and their status, so as track the service provided and as to ensure that there will be the timely service. The Current System Currently if a product is corrupt, Customers must bring companies directly for warranty. employees must complete warranty information warranty customers. it is time consuming, and labor. sometimes the customer data is lost or confused. management of documents related to warranty customers is also very complex and difficult. The Proposed System The software we build really will bring many benefits to enterprises. Warranty registration scanning solution quickly, easily managed. Help corporate employees work easier, less error occurs. bring the trust of customers for companies Boundaries of the System Hardware and Software Requirements
Minimum Requirements
Hardware Requirements: Pentium III 2.6Ghz or over. Ram 512MB Hard disk require over 1 GB free Software Requirements:
Windows 2000 hoc phin bn mi hn
Page 3 of 21
Group 120
Recommended Requirements
Hardware Requirements: Pentium IV 2.6Ghz or over. Ram over 512MB Hard disk require over 1 GB free Software Requirements: Microsoft Windows 2000/XP/ Vista/ Windows7. 1. Customer Requirements Specification Users of the System Admin Users System functions Users functions: Order managements: o View list of the custormer, order details. o Update status of order, address change. Acount department: o View order details, custormer details. o View/Update/Delete account detail. Dispatch team: o View order details, custormer details. o Update orders status. Call center: o Search. o Lodge and update complaint. o Check complain status. Technical support: o Track comlaint o Update complaint status o View complaint Admins function: o View details order, custormer, and uers o Update/Delete/Cancel users
Page 4 of 21
Group 120
Architecture & Design of Project

Data Flow Diagram
Level 0: Dispatch team Call Center
Admin
Bug Reportin g
Order managements
Technical Support
Account Department
Level 1: Admin Authentcatio n 1 Order managements
User 5
Dispatch team
Call Center
Complaint 4
Account Department
Technical Support
Order managements Dispatch team Admin Account Department Manage Order 2 Call Center
Page 5 of 21
Group 120
Admin Manage Account 3
Order managements
Dispatch team
Call Center
Account Department
User Level 2: User, pass Admin Dispatch team Login 1.1 Logout 1.2 Order managements
Call Center
Account Department
Technical Support
User Admin Order managements
Dispatch team
Chang e info 1.3
Call Center
Account Department
Technical Support
Page 6 of 21
Group 120
Dispatch team Admin View 2.1 Add 2.2 Edit 2.3 User
Order managements
Account Department Call Center
Admin Order managements
View 3.1
Dispatch team Custormer
Add 3.2
Account Department
Edit 3.3
Delete 3.4
Admin
View 4.1 Complaint Add 4.1
Technical Support
Call Center Edit 4.1
Page 7 of 21
Group 120
View 5.1
Admin
Add 5.1
User
Edit 5.1
Page 8 of 21
Group 120
Entity Relationship Diagram (Table Design)
Page 9 of 21
Group 120
Database Structure
1.1.1. Custormer: store customer information
No. Column name Data type
Size
Binding Primary key Identity(1,1)
Notes Custormer code
CusID
Int
2 3 4 5 6 7
CusName CusAddress CusPhone CusEmail CusStatus DispatchNo
varchar Varchar Varchar Varchar bit Varchar
50 500 15 50
Not null Not null Not null Not null Not null
Custormer name Custormer address Custormer phone Custormer email Custormer status Dispatch number
20
Not null
1.1.2. Order: Store billing information

No.
Column name OrdID
Data type Int
Size
Notes Order code
2 3
CusID OrdDate
int DateTime
Not null, Foreign key Not null
References Custormer Order date
4 5 6
OrdAddress OrdPhone OrderName
varchar Varchar Varchar
500 15 50
Not null Not null Not null
Receive address Receive phone Receive name

Page 10 of 21
Group 120
7 payStatus Bit
Not null
Order status 0-Order checked; 1-Order uncheck
disStatus
bit
null
Dispatch status
1.1.3. Category: Store Category information

No.
Column name CateID CateName CateStatus
Data type int varchar bit
Size
Binding Primary key, identity(1, 1)
Notes Category code Category name Category Status
1 2 3
50
Not null Not null
1.1.4. Complain: Store complain information.

No.
Column name ComID
Data type Int
Size
Notes Complain code
2 3
ComDescription CusID
varchar int
500
Not null Not null, foreign key Not null, foreign key Not null Not null Not null
Complain description Custormer code, references Custormer table Product code, references Product table Receive date complain Fixed date Status complain
ProID
int
5 6 7
ComDateReceive ComDateFixed ComStatus
datetime datetime bit
Page 11 of 21
Group 120
1.1.5. OrderDetails: Store order detail information

No.
Column name OrdID ProID Price Quantity
Data type Int Int Money int
Size
Binding
Notes References Foreign Order table key References Product table Price Quantity
1 2 4 5
Primary key
Not null Not null
1.1.6. Payment: payment method

No.
Column name PayID
Data type int
Size
Binding Primary key Identify(1,1)
Notes Payment code
2 3 4
Amount Date UserName
Money Datetime Varchar 30
Not null Not null Foreign key, references Users table Foreign key, References Order table, Not null Payment date Employee name up payment Order code
OrdID
Int
1.1.7. Product: Store product information.

Bug Reporting System Page 12 of 21
Group 120
No.
Column name ProID
Data type Int
Size
Notes Product code
2 3 4 5 6 7
CateID
ProName
int varchar money int Varchar Bit max 200
Foreign key, References Category not null table Not null Not null Not null Not null Not null Product name Product price Number of month waranty described warranty Status product
ProPrice NumberMonthWar ranty WarrantyDescripti on ProStatus
1.1.8. Users: Store users information.

No.
Column name UserName
Data type varchar
Size 30
Notes User name
2 3 4 5
Password
Type
varchar tinyint Varchar bit
30
not null Not null
Password account user Type user Fulll name user Status user
FullName Status
50
Not null Not null
Screen Design
1.1.9. Form login
Group 120
1.1.10.Form Admin
1.1.11.Order Management
Page 14 of 21
Group 120
1.1.12.Account department
Group 120
1.1.13.Call center
Page 16 of 21
Group 120
1.1.14.Dispatch department
Group 120
1.1.15.Technical support
Group 120
Page 19 of 21
Group 120
4. Task Sheet
Start Time 26/10/09 .Doc 26/10/09 26/10/09 26/10/09 Design Database 01/11/09 01/11/09 01/11/09 01/11/09 07/11/09 07/11/09 07/11/09 07/11/09 12/11/09 12/11/09 12/11/09 12/11/09 Finish Time 20/11/09 20/11/09 20/11/09 20/11/09 06/11/09 06/11/09 06/11/09 06/11/09 12/11/09 12/11/09 12/11/09 12/11/09 25/11/09 25/11/09 25/11/09 25/11/09 Implemented by Trn Ngc nh Trn Thanh Tng Hong Trung V Hi ng Trn Ngc nh Trn Thanh Tng Hong Trung V Hi ng Trn Ngc nh Trn Thanh Tng Hong Trung V Hi ng Trn Ngc nh Trn Thanh Tng Hong Trung V Hi ng Evaluation 50% 30% 20% 0% 40% 40% 20% 0% 40% 40% 20% 0% 30% 50% 20% 0%
Sytem designs
Coding
Page 20 of 21
Group 120
2. Checklists Check List of Validation Option

Form fields are not empty Input match Product name, product group is unique The page has links to other sites Links are working well
Validate Yes Yes Yes Yes Yes
Submission Checklist No 1 2 3 4 5 6 Particulars

All pages are active All links are working properly The form will not spell The colors used in the color pages are popular Components are added to form active Incorrect data to be reminded
Yes No NA yes Yes Yes Yes Yes Yes
Comments
Page 21 of 21

Bug Reporting System

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Bug Reporting System

Uploaded by

Copyright:

Available Formats

Hanoi-Aptech Computer Education