ONLINE VEGETABLE SALES

• Introduction• Purpose of the System• Scope of the System• Current System• Proposed System• Functional Requirements• Non Functional Requirements• UML Diagrams• Design goals• Implementation screens• Testing• Conclusion

INTRODUCTION

Online vegetables sales is the process where the user can avail

the services like viewing, searching and purchasing the products

through internet. It provides a better platform for the attraction of

customers. Unlike a store, online shopping has friendly customer

service available for Metropolitan Areas.

The customers who want to purchase the products need to

register themselves in the site. Loyal customers are given delivery

within a given period of time. The administrator maintains the site,

manages the products, updates database if an order is placed,

delivers them and as a whole provides better customer services.

•We provide a cart which can hold the selected items. The

customers can add their selected products to the cart,

modify them and finally place the order and make payment.

•The administrator sends products to the specified location

of the customer.

PURPOSE OF THE SYSTEM

Main theme behind this project is to

make buying easier without wasting time. We are engaged in

various of vegetables to all classes of people with great deals.

Online vegetable tries to enhance access to care and improve

the continuity and efficiency of services.

SCOPE OF THE SYSTEM

Secure registration and profile management facilities for users

so that unauthorized users cannot use your account.

Maintenance of data effectively by Admin.

Browsing through our website shop easy provides information

regarding availability and cost of the desired products for

users.

CURRENT SYSTEM

Current system is a manual system. It is completely

paper based and not reliable. These are the drawbacks of the

existing system.

Users time and money is wasted if they did not get the desired

vegetables after going to the market.

The customer then place the order to supplier and must get the

vegetables or items and intimate to the customer to take his

items and pay the bill by going to shop.

PROPOSED SYSTEM

Due to rapid changing society people are leading busy lives

having no time to go to shops and buy necessary things. So

purchasing products through internet is preferred. The online shopping

(ONLINE VEGETABLE SALES) is an easy to maintain, ready to run,

scalable, affordable and reliable cost saving tool from Software

Associates suited for small, medium, and large markets and Daily

markets.

The proposed system can be used even by the naive users

and it does not require any educational level, experience, and

technical expertise in computer field but it will be of good use if the

user has the good knowledge of how to operate a computer.

FEATURES AND BENIFITS:

• To shop while in the comfort of your own home ,without

having to step out of the door.

• sell at lower rate due to less over head.

• provide home delivery free of cost.

• No wait to see the products if someone else is taking

that.

• Takes care of security aspects like user authentication.

• Features of this site include admin services like adding,

deleting, updating products and user services like

shopping cart, browsing catalog and deleting from shop

cart.

FUNCTIONAL REQUIREMENTS

Functional requirements describe the interaction between

the system and its environment independent of its implementation.

Administrator:

He is provided with the information of users and products and he

can update the system software to meet the requirements.

User:

The user can view the details of products by entering URL of the

website.

He should be able to search for a particular product.

He can just view the details but cannot manipulate them.

• Homepage:

It is used to register and login for the customers.

• Login:

It specifies username and password to the

customer and enter into system.

• Registration:

It is used for the customers to register

themselves.

• Products list:

It shows type of products.

• Cart:

It is used to put the selected items.

• Update cart:

It specifies the modification of the selected list.

• Payment:

It provides payment details to be filled.

NON FUNCTIONAL REQUIREMENTS

Non functional requirements describe user visibility

aspects of the system that are not directly related to the

functional behavior of the system.

1. User interface and human factors

Our system provides a good graphical user interface with various

forms for viewers.

If user is on internet, the interface between user and software

product is web browser and any operating system.

Any person who has the basic knowledge of system and web can

use this.

2. Documentation:

• User manual is provided with product which contains

software requirements, hardware requirements to use this

software product and also detailed description of how to use the

product.

• The manual also contains the information about technical

problems and their solutions.

3. Hardware Considerations

RAM : 1 GB

Processor : Intel Pentium 3.1.0 GHz

Hard disk space : 120 GB

Operating system : windows XP / Vista7

4. Performance Characteristics

Scalability: Any number of users can be able to access

at a time. All the details of the users should be stored securely.

It’s response to the user should be very fast and

accurate.

5. Error Handling and Extreme Conditions

• System can work in low memory and processor speed

environments.

• System handles exceptions by notifying them to the users.

• Administrator should continuously check flaws and

maintains it.

6. Quality Issues

• Reliability: The proposed system which the developer

designs is reliable as it efficiently interacts with user. Secure

access of confidential data.

• Availability: 24*7 availability will be provided if there is

an internet connection and sever is available.

• Robustness: In the event of failure system cannot loose

any data. System can handle exception such as invalid

contents, incomplete fields using JSP.

7. System Modifications

This system is flexible but the only thing is that all the

modifications are done by administrator only.

8. Physical Environment

It can be developed anywhere. It works at room

temperature. It can be accessed by anyone anytime.

9. Security Issues

The database in which all the information stored is

secured. Second person cannot access the details of a shop

other than the owner.

10. Resource Issues

Resources of the computer should meet the

hardware considerations. Anything less than this is not

sufficient for proper functioning of the system.

 

 

UML DESIGN

The Unified Modeling Language (UML) is a general

purpose visual modeling language that is used to specify, visualize,

construct, and document the artifacts of a software system. It is used

to understand, design, browse, configure, maintain, and control

information about such systems. The Unified Modeling Language is

very important parts of developing object oriented software and the

software development process. The Unified Modeling Language uses

mostly graphical notations to express the design of software projects. 

Using the Unified Modeling Language helps project teams

communicate, explore potential designs, and validate the architectural

design of the software.

UML diagrams commonly created in visual modeling

tools include.

• Use Case Diagram

• Class Diagram

• Sequence Diagram

• Collaboration Diagram

• State Chart Diagram

• Activity Diagram

USE CASE DIAGRAM

Use-case diagrams graphically depict the system behavior

(use cases).These diagram’s present a high level view of how the

system is used as viewed from an outsider’s(actor’s) perspective.

A use-case diagram can contain:

Actors (“things” outside the system)

Use cases (system boundaries identifying what the system should

do).

Interactions or relationships between actors and use cases in the

System include the associations, dependencies, and generalizations.

Visit site

search products

choose products

Register

User

Alter cart

buy products

confirmation

logout

fill the form

<<includes>>

system failure

<<extends>>

Cash on delivery

<<include>>

authentication

check for orders

send products

Admin

login

<<includes>>update products

database track report

Registered user

CLASS DIAGRAM

Object model describes the structure of the

system in terms of objects, attributes, associations, and

operations. During requirements and analysis the object model

starts as the analysis object model and describes the

application concepts relevant to the system.

Administrator

nameIdPwd

Add()Delete()Update()Verify()Receive()Deliver()

Registered User

User namePassword

Select Vegetables()Add to cart()Update cart()Make Order()Payment()

Database

IdPwdPin

Login details()Stock Details()

Useruidpwd

Login()Logout()

Login

UidPwd

Submit()

Registration

NameEmailPhnoCityUidPwd

Submit()

Stock Details

Product NameProduct IdPriceQuantity

Add()Delete()Update()

Products

Product IDQuantity

Status()

Cart

Product IdQuantity

Add()Delete()Update()

Payment

AddressPin

Transfer()

SEQUENCE DIAGRAM

A Sequence diagram is a graphical view of a

scenario that shows object interaction in a time-based

sequence what happens first, what happens next. Sequence

diagrams establish the roles of objects and help provide

essential information to determine class responsibilities and

interfaces.

Sequence diagram for Registration:

:user

:sitepage :Products :Registration :Database

1.Connect to the site

2.Search products

3.Registration

5.Store details

6.Successfully registered

4.fill the form

7.login

Sequence diagram for purchasing:

: Registered user

:site page :login :data base :products :cart :payment : Admin

1.connect to the site

2.enter user id & password

4.verification

7.select products()

8.Add to cart()

9.Update cart()

14.Logout

5.Enter proper details

6.Successfully logged In

3.maintains database

10.place order()

11.make payment()

12.submit details()

13.confirmation()

Sequence diagram for managing:

:Database

: Admin

:sitepage :login :deliveries:products

1.Connect to the site

2.Give User ID & Password3.Verification

6.Update products

7.Delivers Products

8.Logout

4.Enter proper details

5.Successfully logged In

COLLOBORATION DIAGRAM

Collaboration diagrams use the layout to indicate how

objects are statistically connected. The Create Collaboration

Diagram Command creates a collaboration diagram from information

contained in the sequence diagram. The Create Sequence Diagram

Command creates a sequence diagram from information contained

in the interactions collaboration diagram.

Collaboration diagram for managing:

admin :sitepage :login

:deliveries

:Database

:products

4: 4.Enter proper details

3: 3.Verification5: 5.Successfully logged In

1: 1.Connect to the site8: 8.Logout

6: 6.Update products

7: 7.Delivers Products

2: 2.Give User ID & Password

Collaboration diagram for Registration:

:sitepage:user:Products

:Registration

:Database

1: 1.Connect to the site

2: 2.Search products

3: 3.Registration

4: 4.fill the form

5: 5.Store details

6: 7.login

6: 6.Successfully registered

Collaboration diagram for purchasing:

:site page :login :data base

:products

:payment

: Registered user:cart

: Admin

4: 4.verification

5: 5.Failed to login

6: 6.successfully logged in

1: 1.connect to the site12: 12.Logout

3: 3. enter user id & password

7: 7.select products

10: 10.make payment

8: 8.Add to cart9: 9.Update cart

11: 11.confirmation

2:

STATE CHART DIAGRAM

State chart diagrams model the dynamic

behavior of individual classes or any other kind of object. They

show the sequences of states that an object goes through the

events that cause a transition from one state to another and

the actions that result from a state change. Each state

represents a named condition during the life of an object

during which it satisfies some conditions or waits for an event.

State chart diagram typically contains one start state and end

states. Transition connect the various states the diagram.

State chart diagram for registered user:Homepage

Login

Search products

Add to cart

Update cart

Make payment

Submit details

Place order

State Chart diagram for user: Homepage

Search products

Add To cart

Registration.

Fill the form

login

updatecart

place order

make payment

submit details

State Chart diagram for admin:

Homepage

Login

Update/Add/Delete products

ACTIVITY DIAGRAM

Activity diagrams provide a way to model the

workflow of a business process. An activity diagram is typically

used for modeling the sequence of workflows. A software

company could use activity diagrams to model a software

development process.

Activity diagram: Start

Homepage

search products

admin login

Add to cart check for

orders

Registration Login

Alert cart

Create Order

Make payment

Cash delivery

Track order

Logout

valid

not valid

new usersuccess

send products

update cart

Track report

Stop

user admin

DESIGN GOALS

Design goals are qualities that enable us to prioritize the

development of the system. Design goals originate from the non

functional requirements specified during requirements elicitation and

from technical and management goals specified by the project.

Design goals are organized into 5 groups:

performance

dependability

Cost

maintenance

end user criteria.

Design goals are based on performance criteria:

• Response time: Ability to respond to the user within 5

seconds.

• Throughput : Ability to accomplish the designed tasks

within given period of time.

• Memory : We can not specify how much space is required

for the system to run.

Design goals based on dependability criteria:

• Robustness : Ability to survive invalid user input.

• Reliability : The system should be reliable.

• Availability : The system is available on the earliest

request of the user.

• Fault Tolerance: Ability to operate under erroneous

conditions.

• Security : Ability to withstand malicious attacks.

Design goals based on cost criteria:

• Development cost : Cost of developing the initial

system.

• Deployment Cost : Cost of installing the system.

• Maintenance cost : Cost required for bug fixes and

enhancements to the system.

Design goals based on maintenance criteria:

• Extensibility : We can easily add functionalities or new

classes to the system.

• Modifiability: Administrator can easily modify the

functionalities of the system.

• Adaptability : It is easy to port the system to different

application domains.

• Portability : The system is platform independent.

Hence it is easy to port the system to different platforms.

• Readability : Users can easily understand the

system. It is user friendly system.

Design goals based on end user criteria:

• Utility : The system well supports the work of the

user.

• Usability : It is easy for the user to use the system.

IMPLEMENTATION SCREENS

HOME PAGE

ADMIN LOGIN PAGE

ADMIN MANAGEMENT PAGE

NEW REGISTER

USER LOGIN PAGE

ADMIN VIEWS PRODUCTS

PRODUCT DETAILS

SYSTEM TESTING

A primary purpose of testing is to detect

software failures so that defects may be uncovered and

corrected. This is a non-trivial pursuit. Testing cannot establish

that a product functions properly under all conditions but can

only establish that it does not function properly under specific

conditions. The scope of present software testing includes

examination of code as well as execution of that code in

various conditions as well as examining the quality aspects of

code: does it do what it is supposed to do and do what it needs

to do.

Software testing methods are traditionally divided into white-

box, black-box.

• White box testing: It focuses on the internal structure of

the component.

• Black box testing: It focuses on input/output behavior of

the component.

Testing levels:

• Unit testing

• Integration testing

• System testing

• System Integration testing

• Regression testing

• Acceptance testing

Test Case 1: Preventing empty fields in registration form of user.

Test Case 2: Validating registration of a user.

Test Case 3: Preventing empty fields in login form of Admin.

Test case 4: Validating Login account of user

CONCLUSION

Online shopping has friendly customer service available 24

hours a day, 7 days a week to assist you with purchasing and

shipping your merchandise. Online shopping allows you to

browse through endless possibilities, and even offers

merchandise that's unavailable in store. The user can get the

ordered product by home delivery and collect the product if

wanted. The registered user can book the products even before

their arrival in the market. Authentication is done for all

registered customers who wish to login.

The goals that are achieved by the software are:

• Optimum utilization of resources.

• Efficient management of records.

• Simplification of the operation.

• Less processing time and getting required information.

• User friendly.

• Portable and flexible for future enhancement.

The web pages are developed by using HTML and JSP in

Windows environment. Database is created by using ORACLE.

Future Enhancements:

It is not possible to develop a system that makes all the

requirement of the user. User requirement keep changing as the

system is being used. Some of the future enhancements that

can be done to this system are:

• As the technology emerges, it is possible to upgrade the

system and can be adaptable to desired environment.

• Because it is based on object-oriented design, any future

change can be easily adaptable.

• Based on the future security issues can be improved using

emerging technologies.

THANK YOU