website bán thang máy javabean fpt aptech

TRƯỜNG ĐẠI HỌC FPT
FPT Aptech Computer Education
FPT-APTECH
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:
No Full Name Roll No
1 Nguyễn Đình Đại Student596863
2 Lữ Phúc Quốc Vinh Student579451
3 Phan Quang Bảo Khoa Student600196
4 Nguyễn Tuấn Anh Student601114
5 Nguyễn Trung Hiếu Student596923
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
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
Project Team: 03 Prepared by: All members Page 2 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
REVIEW 1
Project Team: 03 Prepared by: All members Page 3 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
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.
2. Functional Requirement Specification
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):
- Description:
Here the client will create the account by providing some personal and
professional details. Details Such as:
• Client Name
• Client User Name(must be checked for uniqueness)
• Password
• Email Address
• Contact Details
• Address
• Company or Firm Name
- Requirements:

.REQ01: GUESTs must enter their information above
.REQ02: System valdates information’s Client User Name(must be checked for
uniqueness)…
2.2.2. Login:
- Description:
The system must provide a page to allow guest login a. The system must
distinguish accounts.
- Functional Requirements:
Project Team: 03 Prepared by: All members Page 4 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
.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
. Order Name
. Cost
.Order Status.
.Payment (Type of Payment).
- Functional Requirements:
.REQ08: Customers must provide their information as above. Systems provide
form to enter information.
.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).
2.2.4. Order Status:
- Description:
Once the order is processed it must show the status as completed. It must show
the details like
• Order Number:
Project Team: 03 Prepared by: All members Page 5 of 182

Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
• Order Status:
• Start.
• Finish.(expectation).
- Function requirements:
.REQ 12: Customers can see their Status order.
2.2.5. Destroy Order:
- Description:
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:
- Description:
The system must provide a page to allows admin login. The system must
distinguish accounts and specify type of admin(master or projects manager).
- Functions Requirements:
.REQ01: Customers must provide Username and Password to login into the
website.
.REQ02: System must distinguish Customer type to display pages which
customers can view.

.REQ03: Customers can only access to pages they have permission.
2.3.2 Project Details:
- Description:
Admin must be allowed to enter the details of the project which is going on
with the following information:
.Project ID
.Order ID(and the following information: elevation ID, name , price , quantity )
.Staff ID(and the following information: name , email , address, phone)
- Function Requirements:
.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
Project Team: 03 Prepared by: All members Page 6 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
- 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:
- Description:
Admin can view the order requested with the following information:
.Order ID
.Elevation ID
.name
.price
.Quantity
.Company name and address
.Warranty(Years).
- Function Requirements:
.REQ05: Admin can search details of Order.
2.3.5 Viewing Feedback:
- Description:
Admin can view all the feedback given the clients with the following information:
.Elevation ID
.Username
.Description
.Satisfying level: good, average, satisfactory, poor
.Day of feedback.
- Function Requirements:
.REQ06: Admin can search details of Order.
2.3.6 Viewing Complaints Lodge:
- Description:
Admin can view all the complaints of project with the following information:
.Order number.
.ComplaintsID.
.Problem faced
.Day complaints

- Function Requirements:
.REQ07: Admin can search details of Complaints.
2.3.7 Delegation:
- Description:
Separate some project will going on to a project manager who will monitor
projects untill done. With the following information:
.StaffID
.Name
.Project Id
- Function Requirements:
.REQ08: Admin search order status.
.REQ09: Admin must insert(add to) project and staff follows order ID.
2.3.8 Report:
Project Team: 03 Prepared by: All members Page 7 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
- 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:
- Description:
Checks and apudates price, quantity promotion to products; Updates news on
home page; updates new products. Enter information such as.
• Products:

.Elevation ID
.Name
.Price
.Quantity
.Category
.Promotion(ID)
.Warranty(Years)
.Picture.
• News:
. Short news.
.Long News.
.Pictures.
.Date issue.
- Function Requirements:
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:
• FullName
• User Name(must be checked for uniqueness)
• Password
• Confirm Password (must be verified)
• Email Address
• Contact Details(cell phone)
• Address

• ID number.
- Functional Requirements
.REQ01: User must provide Username, Password, Name, Address, Phone
Number, Email to create an account.
Project Team: 03 Prepared by: All members Page 8 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
.REQ02: Username is unique
.REQ03: System auto set level’s customer at 0.
2.4.2 View Details Project:
- Description:
They must be allowed to enter some specify details of the project which is
going on.
.Project ID
.Customer Name
.Installation location
.Completion time
.Status
.Complain (if had)
- Functional Requirements
.REQ04: Managers can view and update project information here .
2.4.3 Viewing Client Information:
- Description:
Must be able to view the details of all the client registered
.Customer Name
.Email Address

.Contact
.Project ID
- Functional Requirements
.REQ05: Management can see their customer information to get in touch to
discuss and provide information on the progress of work
.REQ06:Customers must order
.REQ07:Management and is considered one of the necessary information
2.4.4 Viewing Order Request
- Description:
Must be able to view the order requested and must updated their order once
done.
Order ID
Customer ID
Customer Name
Project ID
Cost
Payment.
- Functional Requirements
REQ08:Management can see all information review above.
2.4.5 Order Status:
- Description:
See all order that being given.
Project Team: 03 Prepared by: All members Page 9 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
- Function Requirements:

.REQ09: Management view of the existing bill. Check the update status of bills
.REQ10: Pending bill will be taken up first
2.4.6 Viewing Feedback:
- Description:
It must note down all the feedback given the clients
.Customer Name
.Project ID
.Contents
.Day ‘s Feedback
- Function Requirements:
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 :
- Description:
Save the management actions that have dealt .
.Action
.Day’s Action
.Name’s Manager
- Function Requirements:
REQ13: Review the actions performed
REQ14: Can not edit .
REQ15: Only store management actions .
2.4.7.1 Viewing Complaints Lodge
- Description:
Note down all the complaints and must update once
.Customer Name
.Project ID
.Day ‘s Feedback
.Email
.Decripstion

.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
Project Team: 03 Prepared by: All members Page 10 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
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
. Order Name
. Cost
.Order Status.
.Payment (Type of Payment).
.Complaints
- Requirements:
.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).
Project Team: 03 Prepared by: All members Page 11 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
- 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 System Requirements
3.1
Hardware
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
Project Team: 03 Prepared by: All members Page 12 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
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.
4 Development Software
• Microsoft Windows 7Ultimate
• Netbeans 6.9.1
• Java SDK 1.6
• Microsoft SQL Server 2005 or higher
• Internet Explorer 8.0
• Jboss 5.0
5 Techonology
• J2EE
• JSP, Servlet
• EJB
Project Team: 03 Prepared by: All members Page 13 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
TASK SHEET
Project Ref. No 1 Project Title Activity

Plan
Prepared
By
Date of Preparation of Activity Plan
Sr.
No
Task
Start
Date
End
Date
Actual
Days
Member’s name Status
CRS document
1 Introduction
Elevation
System -
Online
Application
Nguyen Dinh
Dai
21/03/20
13
22/03/20
13
3 All of Team FINISH
2 Existing Scenario
Elevation
System -

Online
Application
Nguyen Dinh
Dai
21/03/20
13
22/03/20
13
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/20
13
22/03/20
13
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
)
Approved by (Faculty)
Signatur
e
Team
leader
Nguyễn
Đình Đại Phạm Công Thành
Date
REVIEW2
Project Team: 03 Prepared by: All members Page 14 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
Project Team: 03 Prepared by: All members Page 15 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
6 Use Case and Sequence Diagram
6.1

Guest
6.1.1 Register as Customer:
Author Nguyen Tuan Anh
Use Case
Name
Register as Customer
Actors Guests
Description Guests want to register with the website to become a Customer.
Requirements Guest provides Guest’s information
Pre-conditions
Post-
conditions
Success: Guest creates a Customer account in this website
Fail: Refill information
Basic flow Actor’s Action System Responses:
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
Project Team: 03 Prepared by: All members Page 16 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
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
[Exception 1]
7. System inserts the account
into database, show message:
‘Your account has been created!’
and then redirects to Login page.
Alternative
flow
Actor’s Action System Responses:
[Alternative 1]
1. Actor click ‘Back to Home’
button.

2. System returns to Home
page.
Exception
Actor’s Action System Responses:
[Exception 1]
1. Actor lefts ‘UserName’ text field
blank.
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’.
Project Team: 03 Prepared by: All members Page 17 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
Project Team: 03 Prepared by: All members Page 18 of 182
Project Elevation System-Online
Application
Document:

Development Guide
Approved by:
Faculty
6.2
Customer:
6.2.1 Login :
Author Nguyen Tuan Anh
Use Case
Name
Register as Customer
Actors Customer
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
Actor’s Action System Responses:
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
- ‘Login’ button

4. System checks the information
[Exception 1]
5. System redirects to Actor’s
Home page.
Alternative
flow
Actor’s Action System Responses:
[Alternative 1]
1. Actor click ‘Cancel’ button. 2. System will reset username,
password and focus to username
Project Team: 03 Prepared by: All members Page 19 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
[Alternative 2]
3. Actor click ‘OK’ button, inputs
UserName and Password, then click
the Login button.
textfield.
4. System checks the information
[Exception 1]
Exception
Actor’s Action System Responses:
[Exception 1]
1. Actor input invalid username and
password.
- System redirect to Login page

with the following controls:
- ‘UserName’ text field
- ‘Password’ text field
- ‘Login’ button.
- ‘Back to Home’ button.
System show a message box:
“Invalid Username and
password”.[Alternative 2]
6.2.2 Logout :
Author Nguyen Tuan Anh
Use Case
Name
Logout
Actors Customer
Description Guest wants to log out of the System
Requirements
Pre-conditions Customer logged in
Project Team: 03 Prepared by: All members Page 20 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
Post-
conditions
Success: Session “User” being cleared customer become a guest.
Basic flow
Actor’s Action System Responses:
1. Actor clicks ‘Log out’ button on the

Actor’s Home menu.
2. System remove session, and
then redirect to homepage page.
Alternative
flow
Actor’s Action System Responses:
Exception
Actor’s Action System Responses:
6.2.3 Change profile :
Author Nguyen Tuan Anh
Use Case
Name
Change profile
Actors Customer
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
Basic flow Actor’s Action System Responses:
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
Project Team: 03 Prepared by: All members Page 21 of 182
Project Elevation System-Online
Application

Document:
Development Guide
Approved by:
Faculty
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.
Alternative
flow
Actor’s Action System Responses:
[Alternative 1]

1. Actor click ‘Back to Home’ button. 2. System returns to Home page
Exception
Actor’s Action System Responses:
[Exception 1]
1. Actor lefts ‘New Password’ text
field blank.
2. Actor lefts ‘New Confirm
Password’ text field blank.
3. New Password and New Password
Confirm don’t match.
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’.
Project Team: 03 Prepared by: All members Page 22 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
Project Team: 03 Prepared by: All members Page 23 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
6.2.4 Placing Order :
Author Nguyễn Đình Đại
Use Case
Name
Placing order
Actors Customer
Description

Customer wants to buy elevator one or more and attached accessories if
need .
Requirements
Customer provides placing information, construction information, credit
card
Pre-conditions Customer must logged in and choose elevator in product page
Post-
conditions
Success: Save all data to database.
Fail: Orccur Error page.
Basic flow Actor’s Action System Responses:
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
-“Number of loor”textfield
- “Location” textfield.
- “Person to contact”tetfield.
- “Telephone”textfield.
-“Submit”button.
-“Cancel”button.
4. System checks the information
[Exception 1].
5. System save all information in

form to session and redirect to “
Accessories choosen page”. This
Project Team: 03 Prepared by: All members Page 24 of 182
Project Elevation System-Online
Application
Document:
Development Guide
Approved by:
Faculty
6. Customer click “add to cart” button.
8. Customer click “Order” button.
[Alternative2].
10. Customer input information and
click
“Buy” button.
[Alternative3]
[Alternative4]
page will show all
Attched accessories of elevator
on the bove.
7. System save accessories that
he/she choosen in session.
9.Redirect to “Total page” and all
elevator and accessories that
choosen in “payment form”
include.
-“Type Elevator”label
-“Weight”label.
-“Height(floor)”.
-“Quantity of Elevator(as session

values)” label.
-“More”button.
-“Type of Accessories”label
-“Quantity of Acessories”(as
session values) label.
-“More”button.
-“Promtion”label(percent).
-“Credit card number”textfield.
-“Total in US” label.
-“Buy”button.
-“Another”button.
11. Checks and Proccess
information.
[Exception2]
12.Save All information to
database, reduce quantity of
product and generate Bill of
Order.
[exception4]
Alternative
flow
Actor’s Action System Responses:
[Alternative1]
Customer click “Cancel” button.
[Alternative2]
Customer click “Cancel” button.
[Alternative3]
Customer click “More” button.
[Alternative4]
Customer click “Another” button.

Redirect to Homepage.
Redirect to Homepage.
Add one element to subject.
[ exception3]
System save all to session and
redirect to Product page.
Exception Actor’s Action System Responses:
Project Team: 03 Prepared by: All members Page 25 of 182