Professional Documents
Culture Documents
eProject Document
Online Floral Delivery
<Group Name>
Nguyen Xuan Minh, C00174, 4066
- Hanoi, 01/2011 -
eProject
Document
Page 2
CONFIDENTIAL6/16/2016
eProject
Document
1. Introduction
One way of communicating wishes are by sending flowers. So our
client java florist wants to develop a website which would help people
to communicate wishes by sending flower bouquet on special
occasion.
Java
Florist
offers
professionally
designed
flower
arrangements for all occasions like Birthday, wedding, new baby, thank
you, fathers day, mothers day etc. The services that will be offered by
java florist include delivery of bouquets in Mumbai and surrounding
areas, and can even handle flower delivery nationwide through there
network of trusted florists.
2. Problem Definition
2.1. The Proposed System
One way of communicating wishes are by sending flowers. So our
client java florist wants to develop a website which would help people
to communicate wishes by sending flower bouquet on special
occasion. Java Florist offers professionally designed flower
arrangements for all occasions like Birthday, wedding, new baby, thank
you, fathers day, mothers day etc. The services that will be offered by
java florist include delivery of bouquets in Mumbai and surrounding
areas, and can even handle flower delivery nationwide through there
network of trusted florists.
The Website will have a web page which has links or option
Home, My Account, About Flower, View Cart, Florist Registration
etc.
The Home page will also have link for different occasions and
when the user clicks on any occasion the bouquets available with
Page 3
CONFIDENTIAL6/16/2016
eProject
Document
Software Requirements:
o ASP.NET 3.5 or later
o IIS 4.0 or later
o Internet Explorer 6.0 or other
Page 4
CONFIDENTIAL6/16/2016
eProject
Document
Page 5
CONFIDENTIAL6/16/2016
eProject
Document
information.
The application will show message if Username or
Password is invalid.
b. Bouquet management:
Purpose: Allow managers add new, update information and
disable bouquets.
Object used: Employee
Function requirement:
-
bouquets,
view
bouquets
Page 6
CONFIDENTIAL6/16/2016
eProject
Document
employee, customers.
c. Input provide by Client:
- Inputs for the web-bases application
- Outputs from the Web-based application
- Process involved in the Web-based application
Page 7
CONFIDENTIAL6/16/2016
eProject
Document
UC001
Search bouquet
Customer
Search bouquets information
Overview and
scope
Level
Preconditions
Post conditions in
words
Trigger
Included Use Cases
Extended Use
Cases
MAIN
SUCCESSFUL
SCENARIO
Primary
1. Customer dont need register but customer can
direct book online through the website companys
2. Customer enters keyword or choose start price, end
price.
System display details information about bouquets
contain keyword.
User clicks Search button
None
None
Actor Action
1.
Customer
System Action
enters
end
price
to
search.
2.Customer click Search
button
3. System search bouquets in
database and return records
OTHER
SUCCESSFUL
SCENARIOS
corresponding.
4. System display result
Branching Action
Step
Page 8
CONFIDENTIAL6/16/2016
UNSUCCESSFUL
SCENARIOS
eProject
Document
Conditions
2a. Keyword is null
Actions
Customer may reenter
keyword
Developer
Creation date and
last modified date
USE CASE #
USE CASE Name
ACTOR
Purpose (1 phrase)
UC002
Add new bouquet
Employee
Add new bouquet information to the system
Overview and
scope
Level
Preconditions
Post conditions in
words
Trigger
Included Use Cases
Extended Use
Cases
MAIN
SUCCESSFUL
SCENARIO
Primary
1. Employee need login before add new a bouquet
2. Employee provides bouquet information.
System display bouquet is successfully added to
database and question for employee to continue
working or not.
Employee click Add New Bouquet button
None
None
Actor Action
System Action
1. Employee redirect to
Add New Bouquet page.
2. System validate user login.
Page 9
CONFIDENTIAL6/16/2016
eProject
Document
3. Employee input
bouquet information like
bouquet name, price,
total amount, bouquet
category etc.
4. Employee click Add
New Bouquet button
5. System will add bouquet
information to the database
6. System displays a message
to employee.
Branching Action
OTHER
SUCCESSFUL
SCENARIOS
Step
UNSUCCESSFUL
SCENARIOS
Conditions
Actions
2a. System fails to authorize System redirect to Login
employee account
invalid
information missing.
Developer
Creation date and
last modified date
Page 10
CONFIDENTIAL6/16/2016
eProject
Document
UC003
Modify bouquet information
Employee
Modify bouquet information existing in the system
Overview and
scope
Level
Preconditions
Post conditions in
words
Trigger
Included Use Cases
Extended Use
Cases
MAIN
SUCCESSFUL
SCENARIO
Primary
1. Employee need login before add new a bouquet
2. Employees choose a bouquet want to edit the
information in the list of bouquets in the system.
System display bouquet is updated successfully to
the database.
Employee click Modify Bouquet Information button
None
None
Actor Action
System Action
1. Employee redirect to
Bouquets page.
2. System validate user login.
3. In the list of bouquets,
employee chooses a
bouquet want to edit.
4. Employee click Edit
button
5. System show Edit form for
bouquet
6. Employee modify
bouquet information like
bouquet name, price,
total amount, bouquet
category etc.
Page 11
CONFIDENTIAL6/16/2016
eProject
Document
7. Employee click
Update Bouquet
Information button
8. System will update bouquet
information to the database
9. System displays a message
to employee.
Branching Action
OTHER
SUCCESSFUL
SCENARIOS
Step
UNSUCCESSFUL
SCENARIOS
Conditions
Actions
2a. System fails to authorize System redirect to Login
employee account
invalid
information missing.
Developer
Creation date and
last modified date
Page 12
CONFIDENTIAL6/16/2016
eProject
Document
UC004
Disable bouquet
Employee
Hide a bouquet existing in the database
Overview and
scope
Level
Preconditions
Post conditions in
words
Trigger
Included Use Cases
Extended Use
Cases
MAIN
SUCCESSFUL
SCENARIO
Primary
1. Employee need login before add new a bouquet
2. Employees choose a bouquet want to hide in the
list of bouquets in the system.
System display bouquet is hidden successfully.
Employee click Disable Bouquet button
None
None
Actor Action
System Action
1. Employee redirect to
Bouquets page.
2. System validate user login.
3. In the list of bouquets,
employee
chooses
Page 13
CONFIDENTIAL6/16/2016
eProject
Document
8. System displays a message
to employee.
Branching Action
OTHER
SUCCESSFUL
SCENARIOS
Step
UNSUCCESSFUL
SCENARIOS
Conditions
Actions
2a. System fails to authorize System redirect to Login
employee account
Developer
Creation date and
last modified date
USE CASE #
USE CASE Name
ACTOR
Purpose (1 phrase)
UC005
Add New Occasion
Employee
Add new an occasion to the system
Overview and
scope
Level
Preconditions
Post conditions in
words
Trigger
Included Use Cases
Extended Use
Cases
Primary
1. Employee need login before add new a bouquet
2. Employees choose a bouquet want to hide in the
list of bouquets in the system.
System display bouquet is hidden successfully.
Employee click Disable Bouquet button
None
None
Actor Action
Page 14
System Action
CONFIDENTIAL6/16/2016
eProject
Document
1. Employee redirect to
Bouquets page.
2. System validate user login.
3. In the list of bouquets,
employee
chooses
OTHER
SUCCESSFUL
SCENARIOS
Step
UNSUCCESSFUL
SCENARIOS
Conditions
Actions
2a. System fails to authorize System redirect to Login
employee account
Developer
Creation date and
last modified date
Page 15
CONFIDENTIAL6/16/2016
eProject
Document
4. Design
[This section shows design of the system. This could be a part of the Developers
Manual]
Page 16
CONFIDENTIAL6/16/2016
eProject
Document
Page 17
CONFIDENTIAL6/16/2016
eProject
Document
5. System Prototype
<Put the system prototype or mock UI here. Focus on important forms and the
screen flows between forms. If you use RAD and .NET, prototyping really help you to
reach your development goals quickly>
Page 18
CONFIDENTIAL6/16/2016
eProject
Document
Page 19
CONFIDENTIAL6/16/2016
eProject
Document
7. Checklists
7.1. Check List of Validation
< Put the checklist here; describe how it is used and the resulted checklist>
8. Screenshots
<Capture some intuitive and main screens of the software and put them here>
9. Coding Convention
<Provide the coding convention for your team. If you simply want to use the existing
code standard(s) such as Java Code Convention, you can refer to it\them by name
or URL>
Page 20
CONFIDENTIAL6/16/2016
eProject
Document
Appendix
Glossary [Optional]
<Place all definitions or abbreviation used in this document >
References [Optional]
<Place all referenced materials used in this document >
Others<Optional>
Page 21
CONFIDENTIAL6/16/2016