flower and gift

MCSP - 060

Online Flower and Gift Shop

byStudent’s Full Name

Enrolment No:0000

Under Guidance of

Mr.

Submitted to the School of Computer and Information Sciences, IGNOU in

partial fulfillment of the requirements

for the award of the degree

Master of Computer Applications (MCA)

Year of Submission 2010

Indira Gandhi National Open UniversityMaidan Garhi

New Delhi – 110068.

1

Table of Contents

Title of the project.

Introduction and objectives of the Project. Project category.

Tools/Platform,Hardware and Software Requirement specifications.

Problem Definition , Requirement Specification,Project Planning and Sheduling

Analysis (DFDs, ER Diagrams, Class Diagrams etc.)

A complete structure Which includes :

(i) Number of modules and their description to provide an estimation of the student’s effort on the project.

(ii) Data Structures as per the project requirements for all the modules.

(iii) Process Logic of each module.

(iv) Implementation methodology

(v) Report generation.

Implementation of security mechanisms at various levels

Scope of future application.

Bibliography

2

Project Title

Title:

Online flower and Gift shop

3

Project Introduction and Objective

This is a project to create an electronic system that will provide the Web interface for potential customers can buy online flowers and gifts.

View and select the items such as roses, bouquets, blooming and green plants, and fruit and goodies baskets as for sale they are interested to buy.

To register users to become members.

Customer can create account to store address information.

View order history and to receive notice of promotions and new products.

It will be able to manage the flower and gift items by adding, deleting and modifying details

It should also be able to automatically generate emails to be sent to members .

New System will be help user to shop flower and Bonquets on line and it Help client to

increase the sale of the flowers. System Consist of the following features:

1. Online Flower and Gift Interface

a. Home.

b. By Occasion (customer can shop by occasion).

c. By Product (customer can shop by product).

d. Get Catalogue.

e. Our Services.

f. Enquires.

g. Contact us.

h. About us.

i. Customer Login.

j. New Customer Registration and Services.

k. Admin Login

i. Add/delete/modify flowers.

l. Other Features

i. Express Services.

ii. FAQ.

4

iii. Polices.

iv. Privacy.

v. Sitemap.

vi. Contact us.

vii. Disclaimer.

viii. Search by Price.

Purpose:

This is a project to create an electronic system that will provide the Web interface for potential

customers can buy online flowers.

View and select the items such as roses, bouquets, blooming and green plants, and fruit and goodies

baskets as for sale they are interested to buy.

To register users to become members.

Customer can create account to store address information.

View order history and to receive notice of promotions and new products.

It will be able to manage the flower items by adding, deleting and modifying details

It should also be able to automatically generate emails to be sent to members

5

Tools/Platform,Hardware and Software Requirement specifications

Software:

Major software tool will be ASP. Net for coding and programming to make the website.

SQL server database to hold a large number of transaction record, customer details, payment details, order

details etc.

Web server IIS (Internet information server) to upload the website.

Other software:

MS Word for documentation, MsProject for project plan that is assigning different t

tasks to the individual team member.

We will also be using Microsoft Excel software to calculate the cost /budget for the

project. Dream weaver for web interface, adobe Photoshop for graphics etc.

Hardware

Server Side

Operating System: Windows 2000 Advanced Server/ 2003 advanced server

Processor: Pentium 4 3.0 GHz or higher

RAM: 512 Mb or more

Hard Drive: 200 GB or more

Client side

Operating System: Windows 9x or above, MAC or UNIX (Windows XP Preferred)

Processor: Pentium III 2.0 GHz or higher

RAM: 256 Mb or more

Graphics card to view the pictures

6

Problem Definition:

Almost every activity in the world today is controlled by computer driven software

programs. His trend was first accommodated by engineering applications in the past. However,

as the life style became more and more complex, every area of human interactions was invaded

by various software systems, such as real time, business, simulation, embedded, web based,

personal and more recently, artificial intelligence software etc.

According to the above facts, managing and maintaining a online flower and Gift shop

could also be controlled by efficient software. This project focuses attention on designing

efficient and reliable software which controls the transactions of a flower and Gift shop.

In real world, it tends to associate with automated systems as they provide many benefits

than doing the same thing in manually. As above mentioned, here we have introduced a system

which can be used to maintain a flower and Gift shop.

When we are concerning the manual process of a flower and Gift shop, the major

problem is the waste of time. A customer has to waste his/her valuable time when he needs to

buy a flower and Gift shop as all the events such as searching, purchasing are done by members

of the staff .In briefly, the manual process is very slow. But automation will reduce the time

taken in the whole process.

Scenario: -

Person: - Mrs Banerjee is a Business person of a multinational company from Calcutta, India and

She is on the business tour on Australia.

Steps: - 1. She wants to give flower to her boy friend in Kolkata on the Eve of Valentine day.

2. She decides to give red roses on this occasion.

3. She is new in the cities and doesn’t know much about the shopping palaces.

4. She is busy too with the meeting with the clients.

7

5. She don’t has time to go shop and buy flower and ordered it for deliver to overseas.

6. She decided to buy flowers online to avoid all the frustration.

7. She visits on our website i.e India flower online .

8. She selects the beautiful flower bookie with gift items.

9. She buy it and odered it for deliver to Kolkata; India.

10. She was happy after shopping with us its too easy and she save her time as well.

8

SRS

Product Function analysis

Functional

The Functional requirements for the product have been discussed below:

Home Page

This page will contain an overview of the whole site which will include different selling flowers and

products with little description. Also

Shop name and logo

A search engine for browsing purpose

Login for already users and signup for new user

Link to the other pages of the site

And a site navigation bar.

Flower Order form

Functionality: -

User will go to the website. Browse Through and select flower after that fill up order

form providing their address, name, payment details etc.

Occasion selection

Functionality: -

User will be choosing one or several specific occasions such as mother’s day or

valentine day, birthday, marriage etc. The website will take the user to the flowers available for that

specific occasion.

9

Bouquets or baskets

Functionality: -

User could be choosing different flowers and can ask to make a bouquet. There will be

some sample provided for the baskets and bouquets from which customer can pickup.

Customer registration:

Functionality: -

Customer visit the site, there will be some promotional offers and discounts for the

registered users and regular buyers. User might like to make a log in account for them and will

receive free news about special price discount and promotions.

Customer Log-In

Functionality: -

Customer will log-in by using their personal account information and will get

different prices for flowers.

Customer order

Functionality: -

Customer will select one product and will click the ‘add to list’ button beside the

product website will contain button and options like this after code implementation], customer can

also choose more than one product and make a list of their shopping. After finishing selection total

price will be generated on the screen. Customer can then add/delete from their shopping list.

10

Password and account management:

Functionality: -

User can log-in using their unique account name and password and change their

personal information such as address, contacts, password etc.

Functionality: -

Administrative and authorized people such as the client for this project and

employee can log-in with their account and will be able to remove, add and / or change details for

the selling product. Put new promotional offer .make mailing list etc. Again while maintenance

Sahara software will also be able to modify the website such as colours, fonts putting new flowers

pictures etc.

Payment process

Functionality: -

Customer will provide how they will be paying for the flowers. There will be four

credit cards accepted i.e Visa, Master card, AMEX and Dinears for the payment by online. Customer

can pay cash only at the shop at visit. Or customer will provide credit card details and get a unique

receipt number generated by the system.

Delivery Service (time, fees and charges)

Functionality: -

If the delivery is going to the same city or near areas fees and charges will be

different. Customer can view the price for delivery for different location. Local delivery will take less

time and less money. If the customer asks for delivery during a public holiday then extra delivery fee

will apply.

Functionality: -

If the delivery is global then prices will be bit higher than the usual while not the same

for every location. There will be a list of the global deliveries as well as time and cost for that. Our

client is more focused on local delivery at present. But he might increase his requirements with time.

11

Help

Functionality: -

If the user cannot navigate the site then they can go for the help option provided. This

option will also guide them how to make the best use of this site

FAQ

Functionality: -

User wants to know what the policy and procedure for buying and selling of the

products from this site. If user cant download pictures for the flower then what they need to do, etc

information will be provided in this section.

Customer Service

Functionality: -

Customer want to buy one product but he/she thinks there is not enough information for

them or they want some recommendation from some staff related to this business then they can contact

to the customer service number through telephone.

News Letters

Functionality: -

Regular buyers and other users who are willing to be added to the mailing list will get

weekly news letters containing new flower arrivals, promotional offers, discounts etc via e-mail.

Log-out

Functionality: -

Customer will finish their shopping using their account and simply click log-out button.

This will enable them to keep their personal information safe.

12

User interface

Regular users:

This software will be viewed by a large number of people of different ages, experience

and educational level. This software does not need a vast knowledge of computer and Internet. The

users just need to know how to connect to the Internet, how to open a browser and how to go to a

particular URL and now they are ready to use the product

Executive and Administration:

Executive and Administrative users will be able to login by

using their own username and password to modify the site. They will be able to add or delete any

item, their price and other features for the site.

Communication Interface:

13

Administration and staffOf Angelic’s Onlineflowers

CustomersSuppliers

On-Line Flowers and Gift Shop

NON –Functional

Data Safety Requirement

Because all the information is stored in the database, the database of the system must be stable, and the

data structure of the database must allow for the hardware failure or operating system failure at any

time. In addition, the database backup and data lose recovery needed to be planed for this situation.

Security Requirement

Because this system will run on the Internet, the security issue must take into account to prevent

unwanted access from other people from the Internet. Option like paypal or Secure HyperText Transfer

Protocol (HTTPS) will be provided to the customers so they can be safe and secure while paying online.

All the internal staff will have different level of access to this system according his/her role.

Software Quality Attributes

This system is intended to be used by any technical or non-technical person over the internet so it

should be It should be easy to access in term of technical issues, easy to browse, easy to administrate.

Other Non-Functional Requirements :

Performance requirements:

The software will be reliable for the client and customer to use, and should perform the task it is

designed for.

14

Maintain ability

The software will be reliable for the client and customer to use, and should perform the task it is

designed for.

Consistency

The website should be consistent such as same type of fonts in every page and reasonable

match of colours.

Project planning and Scheduling:

All the project tasks have been divided into smaller tasks and have been sequenced in a time line. The purposed starting date and finishing date have also been set. As discussed before all the tasks have been divided in to weeks and task has been allocated with the tasks and there is a weekly time sheet have been developed and will be fill up that every week. This time sheet includes the tasks which have been done.

Quality of the project will be taken seriously and all the documentation and code will be done according to the professional standards. Each document will be containing the Project name, Version Info, and the company name. There are special coding standards discussed in this document.

All the documents will be double checked before the final presentation. Scheduling is an important activity of any project management. Scheduling a software

project involves first breaking down an entire problem into a logical set of tasks which would

be assigned to developers.

In order to Schedule the project Online HRManagement Systems(Recruitment Process) we have to do the following:

Identify the tasks needed to complete the project.

Determine the dependency among different tasks.

Establish the most likely estimates for the duration of the identified tasks.

Plan the starting and ending dates for various tasks.

Determine the critical path i.e. the chain of tasks that determine the duration of the project.

Work Breakdown Structure:

Work Breakdown Structure (WBS) provides a notation for representing the major tasks

needed to be carried out in order to solve a problem. We represent the major activities needed

to solve the problem as nodes of a tree. The root of the tree is labeled by the problem name.

15

Each node of the tree is broken down into smaller components that are designated as the

children of the node."

PERT CHART

(Program evaluation review technique) :

A PERT charts consists of a network of boxes and arrows. It is organized by events &

activities or tasks. The boxes represent activities and the arrows represent task dependencies.

The boxes of PERT charts are usually annotated with the pessimistic, likely, and optimistic

estimates for every task. It is a scheduling device that showed us graphically which tasks

must be completed before others were begun. PERT controlled time and costs during the

project and also facilitated us in finding the right balance between completing our project on

time and completing it within the budget. PERT recognized that project was complex, that

some tasks must be completed before others could be started, and that the appropriate way to

manage the project was to define and control each task. Because projects often fall behind

schedule, PERT was designed to facilitate getting our project back on schedule. To build a

PERT chart for our project, we first listed all the activities required for the completion of the

project and estimated how long each will take. Then we determined the dependence of the

activities on each other. The PERT chart gave us a graphical representation of this

information, This technique did not help in deciding which activities were necessary or how

long each would take, but it did force the administrator to take the necessary planning steps

to answer these questions.

Figure below shows a PERT chart of our project. The arrows show the new information that

was not available in the work breakdown structure. The chart shows clearly that the project

consist of the activities of analysis" design, coding and testing phases. The figure shows that

the project was started on 1st May,2010 . System analysis work started on 15th May, 2010

followed by system designing work started on 15th Jun,2010. Since the design activity was

estimated to take 31 days, any activity that followed the design will be started on 15th Jul,

2010 at the earliest. The dependency arrows helped us compute these earliest start dates

based on our estimates of the duration of each activity.

The chart shows that the path through the project that consist of the analysis, design, coding

and integration and testing activities is the critical path for the project. Any delay in any

16

activity in this path would have caused a delay in the entire project. The administrator

monitored the critical path regularly in order to complete the project within the time frame.

PERT Chart for Online Flower and Gift Shop Some advantages of PERT chart is as follows

It forces the manager to plan.

It shows the interrelationships among tasks in the project and, in particular clearly identifies.

The cost of hardware and software for class of application being considered.

The benefits in the form of reduced costs or fewer costly errors. The cost if nothing changes

the critical path of the project thus helping to focus on it. The fact that the PERT chart has

exposed the critical path allows us the opportunity to consider alternative approach to cope

potential problem.

It exposes all possible parallelism in the activities and thus help in allocating resources.

It allows scheduling and simulations of alternative schedule.

It exposes all possible parallelism in the activities and thus help in allocating resources.

It allows scheduling and simulations Of alternative schedules

17

Start Analysis Design Coding Integration & testing

Maintenance / finish

1 may 2010 15 may 2010 2 June 2010 2 July 2010 25 Aug 2010

2 Sep 2010

Scope

Project will enable user to engage in:

1. buy the flower and Gifts

2. check the selected items and cost

3. delivery of product

4. add and remove flower and Gift items.

The Online flower and Gift shop project will provide these services through a simple and user

friendly web interface.

18

Online Flower Shop ER-Diagram

have can have

of

Can have

Belongs to

Ordered

Belongs to

Can have

Is

Is Can have

25

Product

ProductId

NameDescriptionPrice

Cart

CartId

ProductId

Category

CategoryIdCategoryName

Delivery

DeliveryIdCustomerIdOrderNumTypeMessageStatusCreditCardCardType

Roles

RoleId

Role

Users

LoginName

FirstNameLastNameEmailAddress

CurrentUs

er

RoleIdLoginName

OrderOrderNumCartId

Category (CategoryID, CategoryName)Product (ProductId, Name, Description, Price, CategoryId)Cart (CartId, ProductId, Name, Price, Quantity, LoginName)Delivery (OrderNum, CustomerId, DeliveryId, Type, message, Status, Credit Card, Card Type)Users (LoginName, FirstName, LastName, Email, Address)Roles (RoleId, Role)CurrentUser (RoleId, LoginName

Assumptions

1. One category can have one or several products but one particular product can belong to one category only

2. One product can be present in one or many carts at a time but one cart can have many products

3. One user can have more than one roles and one role belong to only single user4. One User can have ordered more than one orders but one order belongs to single user5. User can login once at a time hence he/she is current user once 6. Also current user can have only one role either admin or simple user

26

Database Design

Tables Relation with Relation Type

Customer Product and order M:M

Product Customer&order&supplier&

delivery

1:M

Order Customer and product M:M

Delivery Order and customer 1:1

Payment Order and customer 1:M

Customer Table

Customer tables will include fields such as name , address e-mail etc.

Product table

Product table will include data field such as product description , how many that specific types of flower we have in stock and what’s the price for that etc.

27

Order Table

Delivery Listing

28

Payment Tracking

Supplier information

Use cases

Use Case: New CustomerActors: Customer (Initiator), database systemPurpose: To add a new customerOverview: a new customer visit the website and register

Alternate: a customer visit the site and exit without sign up

29

Use Case: Search for flowersActors: online userPurpose: To search for a flower in the website eventually the databaseOverview: a user is looking for specific type of flower and browsing the whole site . if he

/ she finds it and like it they will buy

Alternate: user found the flower but was not satisfied with the price and exits.

Use Case: order a flowerActors: online userPurpose: user will buy a flowerOverview: user will visit the site , choose a flower and order it through fiiling up the

order form.

Alternate: user may change his mind and add some more flowers with the order or may cancel order before a certain time.

Use Case: update product informationActors: Admin flowers employee and administrationPurpose: updating the flower information in the website Overview: Admin doesn’t sell that particular flower anymore. Or admin got a new type

of flower to put in the website

30

Module and their Description:

Home: it will display home page where user can go to various links.

By Occasion: this button will link to the different type of flowers according to

their search criteria of different Occasion (valentine day, Mother Day etc.)

By product: - This will link to the page where can shop by products like

Romantic roses, baby bouquets, birthday bouquets etc.

Get Catalogue: Customer can request a catalogue through this option by enter

his/her own mail address.

Our Services: - This will tell about the various services and term provided by the

company.

Enquires: - Customer will able to Enquires about the delivery by enter the

receipt number and order no.

View Cart: -this will link to page where user can look how many flower he\she

orders and what is the cost and shipping price.

Customer Login: - the existing user can log on directly and there will be

different prices for the regular user.

Register and service: - This option will help to the new users to become the

member of the shop.

About us: It will display information about the shop, history and more about it.

Contact us: It will display the information to contact flower shop.

Sitemap: To make user easy to go to definite page.

31

PROCESS LOGIC OF IMPORTANT MODULES

Customer Crea

32ADD THE DEPOSIT AMOUNT IN BALANCEUPDATE DATABASE

GET NET AMOUNT AS CURRENT BALANCESTOP YES

Accept New User Data

Accept New User Data

STARTSTART

Member Registration Screen

Member Registration Screen

User ID

Exists?

User ID

Exists?

YesYes Error Message Screen

Error Message Screen

NoNo

Process and Store Data

Process and Store Data

DatabaseDatabase

Confirmation ScreenConfirmation Screen

STOPSTOP

Catalog Search

Place Order

33

Search CatalogSearch Catalog

STARTSTART

Catalog Search Screen

Catalog Search Screen

Listing exists for

the criteria?

Listing exists for

the criteria?

YesYes

Regret Message Screen

Regret Message Screen

NoNoDatabaseDatabase

Listing ScreenListing Screen

STOPSTOP

Search again?Search again?

YesYes

NoNo

34

Catalog Search Process

Catalog Search Process

STARTSTART

Login ScreenLogin Screen

ValidUserId &

Password ?

ValidUserId &

Password ?

YesYes

Login Fail Message

Login Fail Message

NoNo

DatabaseDatabase

Order ScreenOrder Screen

STOPSTOP

NoNo

YesYes

Accept User ID & Password


Login ProcessLogin Process

Process OrderProcess Order

Qty,Price, Item ID, Buyer ID

Qty,Price, Item ID, Buyer ID

Order meets acceptance

criteria

Order meets acceptance

criteria

Accept OrderAccept Order

Order Acceptance Failed

Order Acceptance Failed

Confirmation, Seller Details etc.

Confirmation, Seller Details etc.

Product Creation

35

STARTSTART

Login ScreenLogin Screen




ValidUserId &

Password ?

ValidUserId &

Password ?

Seller Or Buyer Selection Process

Seller Or Buyer Selection Process

Listing CreationListing

Creation

Seller ID, Category ID, Prod Dets, Listing Details,

Payment options etc.

Seller ID, Category ID, Prod Dets, Listing Details,

Payment options etc.

Listing meets acceptance

criteria

Listing meets acceptance

criteria

Create ListingCreate Listing

Listing Successful

Listing Successful

STOPSTOP

Listing Create Failed

Listing Create Failed

DatabaseDatabase

Login Fail Message

Login Fail Message

No

Yes

Support

36

STARTSTART

Input Search Category

Input Search Category

Search Category Available

Search Category Available

Search Context Not Found

Search Context Not Found

Seek Help

Screen

Seek Help

Screen

Input HelpProcess (Transaction, Payment etc)

Input HelpProcess (Transaction, Payment etc)

Help Creation Proc.Help Creation Proc.

Help ScreenHelp

Screen

STOPSTOP

NoNo

YesYes

Customer Care

37

STARTSTART

User DataUser Data

User Data available

User Data available

Session Expiry Message

Session Expiry Message

NoNo

YesYes


Feedback ScreenFeedback Screen

Input Feedback, User ID, Time,

Topic etc

Input Feedback, User ID, Time,

Topic etc

Record FeedbackRecord Feedback

Ticket Number &

Status

Ticket Number &

Status

STOPSTOP

Database

Database

New Feedback

New Feedback

YesYes

NoNoTrack Feedbac

k Screen

Track Feedbac

k Screen

Accept Ticket Number

Accept Ticket Number

Get Feedback Status

Get Feedback Status

Data Availab

le

Data Availab

le

NoNo YesYes

TYPES OF REPORT GENERATION

Reports are needed for internal housekeeping & maintenance action.

FOLLOWING TYPES OF REPORT WILL BE GENERATED :

1. Report on items for price sell.2. Report on items for only advertising purpose.3. Feedback report.4. Report on queries submitted in Support section.5. Report on order placing.6. Report on Items.

Beside these other reports can also be generated as per requirement in future.

Implementation Methodology

To implement a web application client-server architecture is required. The most popular client-server architectures are the two - tier and the three-tier architecture. The choice of architecture affects the development time and the future flexibility and maintenance of the application. While selecting the architecture most suitable for an application, many factors including the complexity of the application, the number of users and their geographical dispersion are considered. This system is designed based on a traditional three-tier architecture used by many web applications. Three-tier architecture includes a presentation layer, business rules/ logic layer, and the data layer. The three-tier architecture is shown in Figure

38

Waterfall Development-based Methodology

40

Implementation of security mechanisms at various levels

Security Issues

Some of the security issues with web site will be

Hackers: By breaking into the website without permission

Virus attacks:

Recommendations:

Use of Firewalls

Installation of Anti - virus software to protect the system from attack.

Backup copies of the website.

Future Scope

1.The SMS Alert to the user on purchase and on any new item added to the site.2.The user can buy all the product not only flower and Gifts.3.Add Bidding 4.Seller and buyer to sell and buy old products.

41

BIBLIOGRAPHY

Articles :1. Chen, L. (2000). Enticing Online Consumers: A Technology Acceptance

Perspective Research- in-Progress. ACM Proceedings, SIGCPR.2. Diwakar, H., Marathe, M. (2000). The architecture of a one-stop web-window shop.

December, ACM SIGecom Exchanges, Volume 2 Issue 1.3. Morrison, M., Morrison, J., and Keys, A. (2002). Integrating Web Sites and

Databases. Communications of the ACM, September, Volume 45, Issue 9.4. Kubilus, N. J. (2000). Designing an e-commerce site for users. September 2000,

Crossroads, Volume 7 Issue 1.5. Norman, D.A. The Design of Everyday Things. Doubleday, New York, 1994.6. Tilson, R., Dong, J., Martin, S., Kieke, E. (1998). A comparison of two current e-

commerce sites. September, Proceedings of the 16th annual internationalconference on Computer documentation.

Books :7. Anderson, R., Francis, B., Homer, A., Howard, R., Sussman, D. and Watson.

(2001) Professional ASP.NET. Wrox Press Ltd.8. Brown, S., Burdick, R., Falkner, J., Galbraith, B., Johnson, R., Kim, L., Kochmer, C.,

Kristmundsson, T. and Li S (2001). Professional JSP. Wrox Press Ltd.9. Walther, S. (1998) Active Server Pages. SAMS Net.10. Wagner, R., Daniels, K., Griffin, G., Haddad, C. and Nasr, J. (1997) JavaScript

Unleashed. SAMS Net.11. Wiley, Y. M. J. & Sons. (1997) Creating the Virtual Store: Taking Your Web Site from

Browsing to Buying.

42

flower and gift

Documents