Bug reporting system

Báo cáo kỳ 2 Aptech Đồ án làm về Hệ Thống Báo Cáo Lỗi

Bug Reporting System

Documentation

Group 120Group Member

Trần Thanh Tùng

Vũ Hải Đăng Trần Ngọc Ảnh Hoàng Trung

Hanoi, <10>/<2009>

1.Problem Definition 3 3.Architecture & Design of Project 5 4.Checklists 21

Sales 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

1.2 The Current System

Currentlyif 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

1.3 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

1.4 Boundaries of the System

1.5 Hardware and Software Requirements

• Microsoft Windows 2000/XP/ Vista/ Windows7.

2. Customer Requirements Specification

2.1 Users of the System

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

3. Architecture & Design of Project

3.1 Data Flow Diagram

Level 0:

Level 1:

Bug Reportin g

Admin

Order managements

Account Department Technical Support

Dispatch team

Admin

Call Center Order managements

Authentcatio n

1

Complaint 4

User

5

Manage Order 2 Dispatch team

Account Department

Order managements

Call Center Admin

User Level 2:

User, pass

User

Login 1.1

Logout 1.2

Chang

e info 1.3

Custormer

Complaint

View 2.1

Add 2.2

Edit 2.3

Admin

Account Department

Call Center

View 3.1

Edit 3.3

Add 3.2

Add 4.1

View 4.1 Admin

Technical Support

Call Center

Order managements

Delete 3.4

View 5.1

Edit 5.1

Add 5.1 Admin

3.2 Entity Relationship Diagram (Table Design)

3.3 Database Structure

3.3.1 Custormer: store customer information

No Column name Data type Size Binding Notes

1 CusID Int Primary key

Identity(1,1)

Custormer code

2 CusName varchar 50 Not null Custormer name

3 CusAddress Varchar 500 Not null Custormer address

4 CusPhone Varchar 15 Not null Custormer phone

5 CusEmail Varchar 50 Not null Custormer email

6 CusStatus bit Not null Custormer status

7 DispatchNo Varchar 20 Not null Dispatch number

3.3.2 Order: Store billing information

No Column

name Data type Size Binding Notes

1 OrdID Int Primary key

Identity(1,1)

Order code

2 CusID int Not null, Foreign key References

Custormer

3 OrdDate DateTime Not null Order date

4 OrdAddress varchar 500 Not null Receive

payStatus Bit

Not null Order status

0-Order checked; 1-Order uncheck

8 disStatus bit null Dispatch

status

3.3.3 Category: Store Category information

No Column name Data

type Size Binding Notes

1 CateID int Primary key,

identity(1, 1) Category code

2 CateName varchar 50 Not null Category name

3 CateStatus bit Not null Category Status

3.3.4 Complain: Store complain information

No Column name Data type Size Binding Notes

1 ComID Int Primary key

Identity(1,1)

Complain code

2 ComDescription varchar 500 Not null Complain description

3 CusID int Not null,

foreign key

Custormer code, references Custormer table

4 ProID int Not null,

foreign key

Product code, references Product table

5 ComDateReceive datetime Not null Receive date

complain

6 ComDateFixed datetime Not null Fixed date

3.3.5 OrderDetails: Store order detail information

No Column name Data type Size Binding Notes

1 OrdID Int

Primary key Foreign

key

References Order table

Product table

4 Price Money Not null Price

5 Quantity int Not null Quantity

3.3.6 Payment: payment method

No Column

name Data type Size Binding Notes

1 PayID int Primary key

Identify(1,1)

Payment code

2 Amount Money Not null

3 Date Datetime Not null Payment date

4 UserName Varchar 30 Foreign key,

references Users table

Employee name up payment

5 OrdID Int Foreign key,

References Order table, Not null

Order code

No Column name Data type Size Binding Notes

1 ProID Int Primary key

Identity(1,1)

Product code

2 CateID int Foreign key,

not null References Category table

4 ProPrice money Not null Product price

5 NumberMonthWar

ranty int Not null Number of month waranty

6 WarrantyDescripti

on

Varchar max Not null described warranty

7 ProStatus Bit Not null Status product

3.3.8 Users: Store users information.

No Column name Data type Size Binding Notes

1 UserName varchar 30 Primary key

Identity(1,1)

User name

2 Password varchar 30 not null Password account user

3 Type tinyint Not null Type user

4 FullName Varchar 50 Not null Fulll name user

5 Status bit Not null Status user

3.4 Screen Design

3.4.1 Form login

3.4.2 Form Admin

3.4.3 Order Management

3.4.4 Account department

3.4.5 Call center

3.4.6 Dispatch department

3.4.7 Technical support

4 Task Sheet

.Doc

Start Time

4. Checklists

4.1 Check List of Validation

4.2 S u b m i s s ion Checklist

1 All pages are active yes

2 All links are working properly Yes

3 The form will not spell Yes

4 The colors used in the color pages are

popular

Yes

5 Components are added to form active Yes

6 Incorrect data to be reminded Yes

Product name, product group is unique Yes

The page has links to other sites Yes