website bán thang máy javabean fpt aptech

REQ02: Buyer can view feedbackREQ03: Admin can view feedback REQ04: Admin can Reply feedback REQ05: Admin can Delete feedback 2.5.1 Complaints: the client provide complaints on the proje

7 Nam Quốc Cang, Q.1, Tp.Hồ Chí Minh

Elevation System-Online

Application

Development’s Guide

Faculty: Phạm Công Thành Batch No:

Group No:03 Student:

Table of contents

Table of contents 2

Review 1 3

1. Introduction Proposed System 4

2. Requirement 4

3. System Requirements 15

4. Development Software 15

5. Technology 15

Review 2 17

6. Use Case and Sequence Diagram 18

7. Entity Relationship Diagram 91

Review 3 102

8. Database Relationship Diagram 103

9. Table Definition 104

10. Site Map 112

11. Gui Design Customer 114

12. GUI Design Admin 140

13. GUI Design Project manager 141

14. Report 196

REVIEW 1

1. Introduction - Proposed System.

D’Hellas is a france company and was founded on 1987, based on the know-how and license of one of the biggest lift companies The company concerns manufacturing,

trading and maintenance of the complete lift system It is enlisted among the largest companies in the world Millions of people in the whole world recognize and rely on D’Hellas

The company already has website which is being in used since last 15 years, now the company wants a have new look and feel of the project also they wish to add newly launched features also The primary focus of the organization is to develop more user friendly website The company wants to assure the quality of the products system they are offering hence they also want to add feedback option to take valuable feedback from the customer The company wants to build a website which will enhance their

productivity

Following are the requirements criteria listed by the company which they want to be added in the website:

2.1. Home page:

Home page must be designed with user friendly template and must contain all the necessary information about the organization It must contain the entire navigational link, some success stories, some achievements, separate login section

2.2. Client Login and its functionalities:

2.2.1. Creating Account(if not be a member):

.REQ03: Customers must provide Username and Password to login into the website.

.REQ04: System must distinguish Customer type to display pages which

customers can view

.REQ05: Customers can only access to pages they have permission

2.2.3. Customers can edit their profile.

- Description:

Customer can edit their information as password, personal picture, name…

- Functional Requirements:

.REQ06: customer see his/her informations that provide to register not be correct

and self edit

REQ07: System valdates information

2.2.4. Placing Order:

- Description:

The registered client can place and online order for which they are going to fill online purchase form and after entering all the required details (quotation) the form is supposed to submit Once the order is submitted an order number must

be generated It must include fields like

• Elevation System Required:

• Type //can be decided by you

• Number of system

• Location where service required:

• Name of the place

• Address

• Telephone number to contact

• And then must click on submit button after which another form must be come with details like

.REQ09: Customers can choice accessories follow elevator if need

.REQ10: Customers must pay for order Sysstem must proccess self and return totals

.REQ11: View and print information’ order and time to start project(after one hour)

Customer checks order status and destroy order following rules of company.

• After one day of Start time : 5% cost.

• After two day of Start time : lost 20% cost.

• After three day of Start time: lost 35% cost.

• After four day of Start time: unavailable.

- Function requirements:

REQ12: Customers can see on cancel their order if being allowed

2.3. Admin Login and its functionalities:

2.3.1 Admin Login as FullRoles:

.REQ04: Admin can search the details of the project which is going on

2.3.3 Viewing Client Information:

- Description:

Admin can view all the details of all the client registered with the following information:

.Username.Full name.Gender.Email.Phone.Address Company name and address

- Function Requirements:

.REQ04: Admin can search details of clients Must be able to view the details

of all the client registered

2.3.4 Viewing Order Request:

.REQ06: Admin can search details of Order

2.3.6 Viewing Complaints Lodge:

.REQ08: Admin search order status

.REQ09: Admin must insert(add to) project and staff follows order ID

2.3.8 Report:

- Description:

View and print all report of projects, report of customers, report of finaces, report of products

- Function Requirements:

.REQ10: Admin can choice report to see

2.3.9 Checks insert and update products, news:

REQ11: Show and search all products

REQ12: Show and search all news

REQ13: Edit products and news

REQ14: Insert and update promotion

2.4. Admin Login as Project manager:

2.4.1 Creating Account(if not be a member):

- Description:

Here the staff will create the account by providing some personal and

professional details Details Such as:

REQ02: Username is unique

REQ03: System auto set level’s customer at 0

2.4.2 View Details Project:

.REQ04: Managers can view and update project information here

2.4.3 Viewing Client Information:

.REQ06:Customers must order

.REQ07:Management and is considered one of the necessary information

2.4.4 Viewing Order Request

REQ11: Management considered the feedback from your customers

REQ12Management can answer the comments or the system will respond

2.4.7 History action of manager project :

REQ13: Review the actions performed

REQ14: Can not edit

REQ15: Only store management actions

2.4.7.1 Viewing Complaints Lodge

.Satisfying level: good, average satisfactory , poor

.Problem ,if faced

- Function Requirements:

REQ16: Management considered the complains from your customers

REQ17: Management can answer the comments or the system will respond REQ18: Customers must be in their project

2.5 Feedback: here the client can provide the valuable feedback It must include

details like(follow products, projects)

- Description :

Only Buyer can feedback and only admin can Reply or Delete Feedback

Admin and Buyer can view Feedback System must provider for Buyer

feedback function They can feedback one or more product they not satisfied

- Functional Requirements :

REQ01: Buyer can feedback product

REQ02: Buyer can view feedback

REQ03: Admin can view feedback

REQ04: Admin can Reply feedback

REQ05: Admin can Delete feedback

2.5.1 Complaints: the client provide complaints on the projects that go on or

finish

- Description : Only Buyer can Complaints and only Admin can Reply or

Delete Complaints Admin and Buyer can view Complaints System must provider for Buyer Complaints function They can Complaints one or more product they not satisfied

- Functional Requirements :

REQ06: Buyer can Complaints

REQ07: Buyer can view Complaints

REQ08: Admin can view Complaints

REQ09: Admin can Reply Complaints

REQ010: Admin can Delete Complaints

2.6 Projects:

- Description :

Here the list of the projects which is completed must be shown (the data must

be updated by the admin).The client can complaints or requirements for

warraty(only owner).The client can feeback after use(only owner)

Client view:

Elevation System Required:

Type //can be decided by you

Number of system

.Location where service required:

Name of the place

Address

Telephone number to contact

And then must click on submit button after which another form must be come with details like

.REQ11: Buyer can Complaints

.REQ12: Buyer can view Complaints

.REQ13: Admin can view Complaints

.REQ14: Admin answer if required

2.7 Products: Details of the products used for elevation must be entered (static

page)

- Description :Buyer can view, add to cart to placing order or Complaints.The

admin must updates prices, pictures, model, number details of products

- Functional Requirements :

.Client view Product

.Admin view Product

.Admin Add new Product

.Admin Update Product

.Admin Delete Product

2.8 Promotion :

- Description : Buyer and Admin can view promotion Only Admin can Add

new, Update, Delete promotion

o Product name

o PromotionID

o Day start promotion

o Day finish promotion

o Cent promotion

- Functional Requirements :

.Buyer can view Promotion

.Admin can view Promotion

.Admin can Add new Promotion

.Admin can Update Promotion

.Admin can Delete Promotion

2.10. Contact Us: It must flash the contact details for the site.

The client can view position of company and represent office on goole map

The client can view information and contact staff in the nearest office

The admin must updates or change staff, office if neccessary

3.1Hardware

Web Server

Processor Core2 Duo or later

Memory 4G RAM or greater

Modem/ADSL Connecting to internet 24/24

Client

Processor Core2 Duo or later

Memory 2G RAM or greater

Monitor Super VGA (800x600) or higher resolution with 256

colors

Pointing Device Microsoft Mouse, Microsoft IntelliMouse®, or

compatible pointing device

Modem/ADSL Connecting to internet

3.2 Software

Web Server

Operation System Windows 7

Browser Internet Explorer 8.0 or higher

Database Microsoft SQL Server 2005 or higher

Software Java SDK 1.6

Jboss 5.x

Client

Operation System Windows 7 or later

Browser Internet Explorer 8.0 or higher

TASK SHEET

Project Ref No 1 Project Title Activity

Plan Prepared By

Date of Preparation of Activity Plan

Nguyen Dinh Dai 21/03/2013 22/03/2013 3 All of Team FINISH

2 Existing Scenario

Elevation System - Online Application

Nguyen Dinh Dai 21/03/2013 22/03/2013 3 All of Team FINISH

3 Customer Requirement

Specification

Elevation System - Online Application

Nguyen Dinh Dai

21/03/20 13

22/03/20

13 3 All of Team FINISH

4 Functional Requirement Specification

Elevation System - Online Application

Nguyen Dinh Dai 21/03/2013 22/03/2013 3 All of Team FINISH

5 System Requirements

Elevation System - Online Application

Nguyen Dinh Dai

21/03/20 13

22/03/20

13 3 All of Team FINISH

6 Development Software

Elevation System - Online Application

Nguyen Dinh Dai

21/03/20 13

22/03/20

13 3 All of Team FINISH

Prepared

by (Student

Nguyễn

Date

REVIEW2

6 Use Case and Sequence Diagram

Description Guests want to register with the website to become a Customer

Requirements Guest provides Guest’s information

1 Actor clicks ‘Register’ link in Home page

3 Actor clicks on to Agree button.

2 System redirects to Registration Policy page.

4 System redirects to Register page and displays Registration form with the following control :

- ‘UserName’ text field

- ‘Password’ text field

- ‘Confirm Password’ text field

- ‘Name’ text field

- ‘Birthday’ datebox

- ‘Gender’ checkbox group

- ‘Address’ text field

- ‘Phone’ text field

- ‘Email’ text field

5 Actor inputs register’s

information and click ‘Register’

button [Alternative 1]

- ‘Captcha’ textbox

- ‘Refresh image’ button

- ‘Register’ button

- ‘Back to Home’ button

6 System checks the information

2 UserName has already exists

3 Actor lefts ‘Password’ text field blank

4 Actor lefts ‘Confirm Password’ text field blank

5 Password and confirm password don’t match

6 Actor lefts ‘Name’ text field blank

7 Actor lefts ‘Birthday’ datebox blank

8 Input age to ‘Birthday’ datebox less than 16

9 Actor lefts ‘Address’ text field blank

10 Actor lefts ‘Phone’ text field blank

11 Input phone not in numeric or phone length not in range 8 – 14 character

12 Actor lefts ‘Email’ text field blank

or input an invalid email address

13 Actor left ‘Captcha’ text field blank or input an unmatch value

System displays message to Actor :

- ‘UserName cannot be blank’

- ‘This Username has already exist!’

- ‘Password cannot be blank’’

- ‘Confirm Password can’t be blank’

- ‘Confirm password not match password.’

- ‘Name cannot be blank’

- ‘Birthday is invalid’

- ‘Age must over 16’

- ‘Address cannot be blank’

- ‘Phone is invalid’

- ‘The phone number should be numeric only and must be between 8 and 14 digits’

- ‘Email is invalid’

Description Customer wants to login to the website.

Requirements Guest provides username and password

Pre-conditions

Post-conditions Success: User logged in to website.Fail: Refill information

Basic flow

1 Actor go to Login of website

3 Actor inputs UserName and Password, then click the Login button

[Alternative 1]

2 System redirects to login and displays Login form on the left with the following control:

- ‘UserName’ text field

- ‘Password’ text field

flow [Alternative 1]Actor’s Action System Responses:

1 Actor click ‘Cancel’ button 2 System will reset username,

password and focus to username

[Alternative 2]

3 Actor click ‘OK’ button, inputs UserName and Password, then click the Login button

- ‘UserName’ text field

- ‘Password’ text field

- ‘Login’ button

- ‘Back to Home’ button

System show a message box:

“Invalid Username and password”.[Alternative 2]

Post-conditions Success: Session “User” being cleared customer become a guest.

Basic flow

1 Actor clicks ‘Log out’ button on the Actor’s Home menu

2 System remove session, and then redirect to homepage page

Alternative

flow

Description Customer wants to Update his/her profile’s information

Requirements Customer provides profile information

Pre-conditions Customer must logged in

Post-conditions

Success: Profile’s information of this user has been updated

Fail: Refill information

1 Actor clicks ‘Profile’ button in Actor’s Home page menu

2 System redirects to Update Profile page and displays Update Profile form with the following

3 Actor updates information and click

‘Save’ button [Alternative 1]

control :

- ‘UserName’ text field (read only)

- ‘Old Password’ text field

- ‘New Password’ text field

- ‘New Password Confirm’ text field

- ‘Name’ text field

- ‘Birthday’ text field

- ‘Gender’ checkbox group

- ‘Address’ text field

- ‘Phone’ text field

- ‘Email’ text field

- ‘Save’ button

- ‘Back to Home’ button

4 System checks the information [Exception 1]

5 System update the account into database and then redirects

to Actor Home page

4 Actor lefts ‘Name’ text field blank

5 Actor lefts ‘Birthday’ datebox blank

6 Input age to ‘Birthday’ datebox less than 16

7 Actor lefts ‘Address’ text field blank

8 Actor lefts ‘Phone’ text field blank

9 Input phone not in numeric or phone length not in range 8 – 14 character

10 Actor lefts ‘Email’ text field blank

or input an invalid email address

System displays message to Actor :

- ‘Password cannot be blank’’

- ‘Confirm Password can’t be blank’

- ‘Confirm password not match Password.’

- ‘Name cannot be blank’

- ‘Birthday is invalid’

- ‘Age must over 16’

- ‘Address cannot be blank’

- ‘Phone is invalid’

- ‘The phone number should be numeric only and must be between 8 and 14 digits’

- ‘Email is invalid’

Post-conditions Success: Save all data to database.Fail: Orccur Error page

1 Customer click “order” button on product that liked best

3.Customer inputs information and click “Submit” button

[Alternative1]

2.System save elevator information in session and redirect to Order page and show

a form to input information.-“Weight” textfield

6 Customer click “add to cart” button.

8 Customer click “Order” button

-“Type Elevator”label -“Weight”label

1.Actor input text into “Weight”

2.Actor input number into

“Weight”not in range

3.Actor input text into “Height”

4.Actor input number into

7 Actor input text into “Telephone”

8.Actor input number into

“Telephone” not in format

-“Location not blank!”

-“ Person not blank!”

-“Telephone bust be number”-“Telephone is not match format”

-“No quantity to increase”

-“Please input card number again.”

Focus to Credit card number.-“Redirect to error page”

Post-conditions Success: Save all data to database.Fail: Orccur Error page

1 Customer click “Accessory” button

on product that liked best

3.Customer inputs information and click “Submit” button

[Alternative1]

6 Customer click “add to cart” button

8 Customer click “Order” button

[Alternative2]

2.System save elevator information in session and redirect to Order page and show

a form to input information.-“Weight” textfield

Attched accessories of elevator

-“Type Elevator”label -“Weight”label

-“Height(floor)”

-“Quantity of Elevator(as session values)” label

10 Customer input information and click

1.Actor input text into “Weight”

2.Actor input number into

“Weight”not in range

3.Actor input text into “Height”

4.Actor input number into

7 Actor input text into “Telephone”

8.Actor input number into

Display message:

-“ Weight bust be number”

-“Weight>100 and<1 ton”

-“ Height bust be number”

-“ Height >1 and<50”

-“Location not blank!”

-“ Person not blank!”

-“Telephone bust be number”-“Telephone is not match format”

“Telephone” not in format.

-“No quantity to increase”

-“Please input card number again.”

Focus to Credit card number.-“Redirect to error page”

6.2.6 Status Order and Cancel project :

Author Nguyễn Đình Đại

Use Case

Description Customer wants to cancel her/his order

Requirements Customer cancel order if allowed

Pre-conditions Customer must logged in and Placing order Successful

Post-conditions Success: Guest creates a Customer account in this websiteFail: Refill information

1.Customer click “Status Order” on Customer page

3.Customer click “Cancel ” button [alternative1]

4.Customer click “yes”

[alternative2]

2.Redirect to Status order page that show all customer’s project and status of project on a table Every row of status table have a cancel button

-OrderID

-ContentOrder

-Start date

-End date-Status(Going on, Complete, available, unavailable)

6 System set status order to unavalable and generates finished bill of order Include

-OrderID label-Cost label

-Cost available(lost fee)label.-Order Status label

Customer click “No”

Redirect to home page

Redirect to Status Order page

Author Nguyễn Đình Đại

Use Case

Description Customer wants to view history of order and project

Requirements Customer can view history of order and project

Pre-conditions

Post-conditions Success: Guest creates a Customer account in this websiteFail: Refill information

Basic flow

1.Customer click “History” on Customer page

3.Customer click “OK ” button

2.Redirect to History page that show all customer’s project and order content that ordered by date Every row of History table has follwing

-Date-Action

6.2.8 Customer Feedback :

Use Case Name Feedback

Description Customer wants to Feedback product

Requirements Actor select product actor want feedback

Pre-conditions

Post-conditions Success: Customer feedback success.

Fail: Feedback Fail

Basic flow Actor Actions:

1 Actor Login to Home page and select product want Feedback and click Feedback

System Responses:

2 System displays Feedback form with the following control:

- ‘1’ radio button-‘2’ radio button

3 Actor select the desired scale feedback, then click the Feedback button [Alternative 1]

-‘3’ radio button-‘4’ radio button-‘5’ radio button-‘Feedback’ button

4 System checks the information [Exception 1]

5 System redirects to Product page

Use Case Name Complaint

Description Customer wants to complaint project

Requirements Actor select project of actor that actor wants complaint

Pre-conditions

Post-conditions Success: Customer complaint success.

Fail: complaint Fail

Basic flow Actor Actions:

1 actor click “project” on homepage

“Complaint”

3 Actor select the project that wants

to complaint, then click the

flow [Alternative1]Actor click on “Cancel” button Redirects to Project page

Exception Actor Actions:

6.2.10 View product

Use Case Name View product

Description Customerview information product

Requirements Actor login to home page

Pre-conditions

Post-conditions

Basic flow Actor Actions:

1 Actor Login to Home page and select product want to see in home page

System Responses:

2 System displays Product Page with the following control:-‘Product Name’ text field

- ‘Product Picture’ image

- ‘Price’ text field

- ‘model’ text field-‘number details’ text area

Alternative

flow

6.2.11 Search product:

Use Case Name Search product

Description Customersearch information product

Requirements Actor login to home page

Pre-conditions

Post-conditions Success: Show product.

Fail: Can’t find product

Basic flow Actor Actions:

1 Actor Login to Home page input

‘Search’ text field and click

System Responses:

2 System displays Product Page with the following control:

’Search’button, then select field actor want to search -‘Search’text field.-‘Search’ button.

-‘Field’combo box

Alternative

flow

6.2.12 Customer view promotion:

Use Case Name View promotion

Description Customerview promotion of product

Requirements Actor login to home page

Pre-conditions

Post-conditions

Basic flow Actor Actions:

1 Actor Login to Home page and System Responses:2 System displays Product Page

select product want to see promotion in home page with the following control:-‘Product Name’ text field

- ‘Product Picture’ image

- ‘Price’ text field

- ‘model’ text field-‘number details’ text area-‘promotion’ text field

Use Case Name Login

Description Administrator wants to login to Admin page

Requirements Actor provides username and password

Pre-conditions

Post-conditions Success: Administrator logged in to website.

Fail: Refill information

Basic flow Actor Actions:

1 Actor click on link “Login” in admin home page

3 Actor inputs UserName and Password, then click the Login button [Alternative 1]

System Responses:

2 System redirects to Login page and displays Login form with the

following control:

- ‘UserName’ text field

- ‘Password’ text field

System Responses:

System displays message to Guest :

- ‘UserName’ cannot be blank’

- ‘Password cannot be blank’

6.3.2 Change Password