Online spice selling report1

Online Spice Selling

SNPIT & RC,UMRAKH Page 1

Abstract


An Online Spice Selling system that permits a customer to submit online

orders for spices and/or services from a store that serves both walk-in customers and

online customers. The Online Spice Selling system presents an online display of an

order cutoff time and an associated delivery window for items selected by the

customer. The system accepts the customer's submission of a purchase order for the

item in response to a time of submission being before the order cutoff time. The

Online Spice selling does not settle with a credit supplier of the customer until the

item selected by the customer is picked from inventory but before it is delivered.

Therefore, the customer can go online and make changes to the order. In addition,

available service windows are presented to the customer as a function of customer

selected order and service types; and further, the order picking is assigned in

accordance with a picker's preference. There is no existing system. All work is done

manually.

By developing this website we want to help our customers to buy products

online. We even provide our distributors to buy products online. We will provide the

facility of shopping cart. We will provide the visitors to see the product details. The

mode of payment is cash on delivery.

Guided By Submitted By

Mr.Sandip Tandel Kinjal Pandya (110490131030)

Pooja Patel (11049013043)

Pratik Sherdiwala (110490131038)



INDEX

Sr No. Date Topics Page

No.

Grade sign

1. 6/1/2014 Use Case Diagram

2. 20/1/2014 Activity Diagram

3. 27/1/2014 Class Diagram

4. 3/2/2014 Sequence Diagram

5. 17/2/2014 State Diagram

6. 3/3/2014 Entity-Relationship

Diagram

7. 10/3/2014 Data Flow Diagram

8. 17/3/2014 Data Dictionary

9. 31/3/2014 SRS Document

10. 7/4/2014 Timeline Chart



1. Introduction

An Online Spice Selling system that permits a customer to submit online

orders for spices and/or services from a store that serves both walk-in customers and

online customers. The Online Spice Selling system presents an online display of an

order cutoff time and an associated delivery window for items selected by the

customer. The system accepts the customer's submission of a purchase order for the

item in response to a time of submission being before the order cutoff time. The

Online Spice selling does not settle with a credit supplier of the customer until the

item selected by the customer is picked from inventory but before it is delivered.

Therefore, the customer can go online and make changes to the order. In addition,

available service windows are presented to the customer as a function of customer

selected order and service types; and further, the order picking is assigned in

accordance with a picker's preference. There is no existing system. All work is done

manually.

By developing this website we want to help our customers to buy products

online. We even provide our distributors to buy products online. We will provide the

facility of shopping cart. We will provide the visitors to see the product details. The

mode of payment is cash on delivery.



2.Usecase Diagram

Use case is used to capture high level functionalities of a system.

Actor Notation:

An actor can be defined as some internal or external entity that interacts with the system.

Actor is used in a use case diagram to describe the internal or external entities.









3.activity diagram Activity diagrams, which are related to program flow plans (flowcharts), are used to

illustrate activities. In the external view, we use activity diagrams for the description of those

business processes that describe the functionality of the business system

Activity diagrams allow you to think functionally. Purists of the object-oriented approach

probably dislike this fact. We, on the other hand, regard this fact as a great advantage, since

users of object-oriented methods, as well as users of functional thinking patterns, find a

common and familiar display format, which is a significant aid for business-process

modeling.

Activity

An activity diagram illustrates one individual activity. In our context, an activity represents a

business process (Figure 3.16). Fundamental elements of the activity are actions and control

elements (decision, division, merge, initiation, end, etc.):

Elements are connected by so-called "activity edges" and form the "control flow", which can

also be casually called 'flow'. The execution of an activity can contain parallel flows. A

border can surround the activity, meaning the entire activity diagram.

Action

An action is an individual step within an activity, for example, a calculation step that is not

deconstructed any further. That does not necessarily mean that the action cannot be

subdivided in the real world, but in this diagram will not be refined any further:

The action can possess input and output information The output of one action can be the input

of a subsequent action within an activity. Specific actions are calling other actions, receiving

an event and sending an event, and sending signals.









4. Class diagram Class Diagram provides an overview of the target system by describing the objects and classes inside the system

and the relationships between them. It provides a wide variety of usages; from modeling the domain-specific

data structure to detailed design of the target system. With the share model facilities, you can reuse your class

model in the interaction diagram for modeling the detailed design of the dynamic behavior. The Form Diagram

allows you to generate diagram automatically with user-defined scope.

The class diagram is the main building block of object oriented modelling. It is used both for general conceptual

modelling of the systematics of the application, and for detailed modelling translating the models into

programming code. Class diagrams can also be used for data modeling.[1]

The classes in a class diagram

represent both the main objects, interactions in the application and the classes to be programmed.

A class with three sections.

In the diagram, classes are represented with boxes which contain three parts:

The top part contains the name of the class. It is printed in Bold, centered and the first letter capitalized.

The middle part contains the attributes of the class. They are left aligned and the first letter is lower

case.

The bottom part gives the methods or operations the class can take or undertake. They are also left

aligned and the first letter is lower case.

In the design of a system, a number of classes are identified and grouped together in a class diagram which helps

to determine the static relations between those objects. With detailed modelling, the classes of the conceptual

design are often split into a number of subclasses.

In order to further describe the behaviour of systems, these class diagrams can be complemented b state diagram

UML state machine

http://en.wikipedia.org/wiki/Object_oriented

http://en.wikipedia.org/wiki/Conceptual_model

http://en.wikipedia.org/wiki/Conceptual_model

http://en.wikipedia.org/wiki/Programming_code

http://en.wikipedia.org/wiki/Data_modeling

http://en.wikipedia.org/wiki/Class_diagram#cite_note-1

http://en.wikipedia.org/wiki/File:BankAccount1.svg

http://en.wikipedia.org/wiki/File:BankAccount1.svg



TRANSACTION

transid

pnrno

transdate

amt

commit()

rollback()

Payment System

custno

custid

custname

creditcardno

BillingAddress

VeiwOrder()

PaymentDetails()

ONLINE SPICE CART

SYSTEM

HTTP

CartAddition

Creidtno : String

Description : String

ItemId : String

Amount : Integer

Category : String

Get_to_cart()

Check_out()

CANCELLATION

cusno : Integer

Item id : Integer

amount : Integer

retrive()

update()

CREDIT CARD HOLDER

cardno

issuedate

expirydate

verifydtls()

perform_transaction()

CUSTOMER

Number of Item : Integer

cusid : Integer

Shipnname : String

Company : String

Address : String

Payment()

CartAddition()

Cancellation()

USER

Email id : String

password : String

First name : String

Last Name : String

Street Address : String

ZipCode : Integer

City : String

State : String

Country : String

Phone : String

Login()

Registration()

Logout()

SELLER

Item name : String

Item id : Integer

Discount : Integer

Categoty : Integer



5. Sequence diagram The Sequence Diagram models the collaboration of objects based on a time sequence. It shows how

the objects interact with others in a particular scenario of a use case. With the advanced visual modeling

capability, you can create complex sequence diagram in few clicks. Besides, VP-UML can generate sequence

diagram from the flow of events which you have defined in the use case description.

Sequence diagrams describe interactions among classes in terms of an exchange of messages

over time.

Basic Sequence Diagram Symbols and Notations

Class roles

Class roles describe the way an object will behave in context. Use the UML object symbol to

illustrate class roles, but don't list object attributes.

Learn how to edit text on a symbol.

Activation

Activation boxes represent the time an object needs to complete a task.

Messages

Messages are arrows that represent communication between objects. Use half-arrowed lines

to represent asynchronous messages. Asynchronous messages are sent from an object that

will not wait for a response from the receiver before continuing its tasks.Learn how to draw

messages

.

http://www.smartdraw.com/resources/tutorials/Text-and-Tables







6. state diagram A state diagram is a type of diagram used in computer science and related fields to describe the behavior

of systems. State diagrams require that the system described is composed of a finite number of states;

sometimes, this is indeed the case, while at other times this is a reasonable abstraction. Many forms of state

diagrams exist, which differ slightly and have different semantics.

The behavior of an entity is not only a direct consequence of its input, but it also depends on its preceding state.

The history of an entity can best be modeled by a finite state diagram. State Machine diagram can show the

different states of an entity also how an entity responds to various events by changing from one state to another.

State diagrams versus flowcharts

Newcomers to the state machine formalism often confuse state diagrams with flowcharts.

The figure below shows a comparison of a state diagram with a flowchart. A state machine

(panel (a)) performs actions in response to explicit events. In contrast, the flowchart (panel

(b)) does not need explicit events but rather transitions from node to node in its graph

automatically upon completion of activities.[10]

Nodes of flowcharts are edges in the induced graph of states. The reason is that each node in

a flowchart represents a program command. A program command is an action to be executed.

So it is not a state, but when applied to the program's state, it results in a transition to another

state.

http://en.wikipedia.org/wiki/Diagram

http://en.wikipedia.org/wiki/Computer_science

http://en.wikipedia.org/wiki/State_%28computer_science%29

http://en.wikipedia.org/wiki/Abstraction_%28computer_science%29

http://en.wikipedia.org/wiki/Semantics#Computer_science

http://en.wikipedia.org/wiki/UML_state_machine#Basic_UML_state_diagrams

http://en.wikipedia.org/wiki/Flowchart

http://en.wikipedia.org/wiki/UML_state_machine#Basic_UML_state_diagrams

http://en.wikipedia.org/wiki/State_diagram#cite_note-Practical_UML_Statecharts_in_C.2FC.2B.2B.2C_Second_Edition:_Event-Driven_Programming_for_Embedded_Systems-10

http://en.wikipedia.org/wiki/File:Statechart_vs_flowchart.png





7.ER diagram

Concept Draw gives the ability to describe visually a database using the Crow’s Foot notation

icons for drawing ER diagrams - ERD.

Entity-Relationship model making possibility to describe a database in which in the tables

data can be the point to data in other tables - for instance, your entry in the database could

point to several entries.

An entity-relationship model is a systematic way of describing and defining a business

process. The process is modeled as components (entities) that are linked with each other by

relationships that express the dependencies and requirements between them, such as: one

building may be divided into zero or more apartments, but one apartment can only be located

in one building. Entities may have various properties (attributes) that characterize them.

Diagrams created to represent these entities, attributes, and relationships graphically are

called entity–relationship diagrams.

An ER model is typically implemented as a database. In the case of a relational database, this

stores data in tables, which represent the entities. Some data fields in these tables point to

indexes in other tables; such pointers represent the relationships.

The three schema approach to software engineering uses three levels of ER models that may

be developed.



CUSTOMER ADMIN

DISTRIBUT

OR

FEEDBACK

PRODUCTS

Manage

Manage

View

&

Order

Vie

w

&

Ord

er

Give

1

1

1 1

M

1

M

1

M M

M

M

Distribut

or_id

Name

Feedbac

k_id

Cust_id &

Dist_id

Custom

er_id

Manage

Name Name Admin_

id

Give

Product

_id

Product_

name



8.Data Flow Diagram

A Data Flow Diagram (DFD) is a diagrammatic representation of the information

flows within a system, showing:

how information enters and leaves the system,

what changes the information,

where information is stored.

In SSADM a DFD model includes supporting documentation describing the information shown in the diagram.

DFDs are used not only in structured system analysis and design, but also as a general process modelling tool.

There are a number of commercial tools in the market today which are based on DFD modelling.

SSADM uses DFDs in three stages of the development process:

o Current Physical DFDs. These record the results of conventional fact finding.

o Current Logical DFDs. The logical information processing of the current system

o Required Logical DFDs. The logical information processing requirements of the proposed

system.

1. The Notation

DFDs show the passage of data through the system by using 5 basic constructs: Data flows,

Processes, Data Stores, External Entities, and Physical Resources.

1.1 Data Flows

A data flow shows the flow of data from a source to a destination. The flow is shown as an

arrowed line with the arrowhead showing the direction of flow. Each data flow should be

uniquely identified by a meaningful descriptive name (caption).



Flow may move from an external entity to a process, from a process to another process, into

and out of a store from a process, and from a process to an external entity. Flows are not

permitted to move directly from an external entity to a store or from a store directly to an

external entity.

It is generally unacceptable to have a flow moving directly from one external entity to

another. However, if it is felt useful to show such a flow, and they do not clutter the diagram,

they can be shown as dotted lines.



.

(DFD level 0)

0.0

Online

Spices

Selling

DISTRIBUTOR

View feedback &

customer &

distributor

information

Manage

product detail

& customer &

distributor

Search product &

View product

detail & Receive

bill

Registration &

place order &

give feedback

ADMIN CUSTOME

R

Search product &

View product &

Receive bill

Registration &

place order &

give feedback



first level diagram for admin)



DFD 1 for customer



DFD 1 for distributor



9.DATA DICTIONARY

Table Name :- admin_mst

Table Description :- To keep details of Admin

Primary Key :- admin_id

Sr. No. Field Name Data Type Constraint Description

1 Admin_id Nvarchar (15) Primary key Store the Admin id

2 Username Nvarchar (15) Not Null Store the User Name

3 Password Varchar (15) Not Null Store the Password

4 Name Varchar (15) Not Null Store the Admin Name

5 Gender Varchar (15) Null Store the Admin Gender

6 DOB Varchar (15) Null Store the Admin DOB

7 Address Varchar (50) Not Null Store the Address

8 City Varchar (20) Not Null Store the City

9 Pincode Numeric (6) Not Null Store the Pincode

10 Mobile_no Numeric (12) Unique key Store the Mobile No

11 Email_id Nvarchar(30) Unique key Store the Email Id

12 Sec_que Varchar(30) Not Null Store the Security Question

13 Ans Varchar(50) Not Null Store the Answer



Table Name :- customer_mst

Table Description :- To keep details of customer

Primary Key :- cust_id


1 Cust_id Nvarchar (15) Primary key Store the Customer id


3 Name Nvarchar (40) NotNull Store name of customer

4 Gender Varchar (15) Null Store the Gender

5 DOB Varchar (15) Null Store the DOB

6 Password Nvarchar (15) Not Null Store the Password




10 Email_id Varchar (30) Unique key Store the Email id


12 Sec_que Varchar (30) Not Null Store the security question

13 Answer Varchar (50) Not Null Store the Answer



Table Name :- distributor_mst

Table Description :- To keep details of distributor

Primary Key :- dist_id


1 Dist_id Nvarchar (15) Primary key Store the Distributor id


3 Name Nvarchar (40) NotNull Store name of distributor

4 Password Nvarchar (15) Not Null Store the Password

5 Gender Varchar (15) Null Store the Gender

6 DOB Varchar (15) Null Store the DOB




10 Email_id Varchar (30) Unique key Store the Email id


12 Sec_que Varchar (30) Not Null Store the security question

13 Answer Varchar (50) Not Null Store the Answer



Table Name :- product_mst

Table Description :- To keep details of product

Primary Key :- product_id


1 Product_id Nvarchar (15) Primary key Store the product id

2 Product_name Nvarchar (15) Not Null Store the product name

3 Product_price Varchar (50) Not Null Store the product price

4 Product_image Varchar (20) Not Null Store the product image



Table Name :- order_mst

Table Description :- To keep details of order placed

Primary Key :- order_id

Foreign Key :- product_id


1 Order_id Varchar (20) Primary key Store the order_id

2 Cust_id Varchar (20) Not Null Store the customer_id

3 Dist_id Varchar (20) Not Null Store the distributor_id

4 Product_id Nvarchar (15) Foreign Key Store the product id

Ref:- product_mst

5 Product_name Nvarchar (15) Not Null Store the product name

6 Product_price Varchar (50) Not Null Store the product price

7 Quantity Varchar (20) Not Null Store the product quantity

8 Total Varchar (20) Not Null Store the total price



Table Name :- feedback_mst

Table Description :- To keep details of feedback

Primary Key :- feedback_id

Foreign Key :- cust_id, dist_id


1 Feedback_id Nvarchar (15) Primary key Store feedback id

2 Cust_id Nvarchar (15) Foreign key Store the customer ID

Ref:- customer_mst

3 Dist_id Nvarchar (15) Foreign key Store the distributor ID

Ref:- distributor_mst

4 Category Nvarchar (15) Not Null Store the category whether

customer or distributor

5 Feedback Nvarchar (150) Not Null Store the feedback



10.Software Requirements Specification


Version <4.0>



Table of Contents

1. Introduction 3

1.1 Purpose 3

1.2 Scope 3

1.3 Overview 3

2. Genral Description 4

3. Functional Requirements 5

3.1 Description 5

3.2 Technical Issue 5

4. Interface Requirements 6

4.1 GUI 6

4.2 Hardware & Software Interface 7

5. Performance Requirements 8

6. Design Consraint 8

7. Other Nonfunctional Attributes 8

7.1 Security 8

7.2 Reliability

7.3 Availability 8

7.4 Maintainbility 8

8. Preliminary Schedule 8



Software Requirements Specification

Introduction

1.1 Purpose

This document gives detailed functional and non-functional requirements for Online

Spice Selling. The purpose of this document is that the requirement mentioned in it should be

utilized by software developer to implement the system.

1.2 Scope

This system admin allows Admin to maintain the list of spices for selling & price of

Spices & also help to admin store record of selling easily. With the help of this software

Customer & Distributor show the detail of spices & purchase online.

1.3 Overview

This system provide an easy solution of Online Spice Selling.



2. General Description

Unjha Dhanadal Factory is a reputed business firm that deals with the selling of

Dhanadal as well as other spices. The firm produces dhanadal on its own where as the other

spices are bought from the farmers and then packed by the firm after the cleaning process.

There are in all 100 employees including the workers. Online Spice Selling System help the

firm provides advanced solution to speed up production process enhance marketing and

support customer relations management.



3. Functional Requirements

3.1 Description

FUNCTIONAL MODULES

1) Registration This module is used for the registration of different

users.

2) Login This module is used for login of the registered users.

3) Product Management Admin will manage products by its price and brand.

4) Add to Cart Customer and distributor can add the products to their

respective shopping carts.

5) Upload Product Admin can add new product.

6) Feedback Buyer and seller can give the feedback and admin can

see the feedback.

USERS

1) Admin Admin can register and manage products as well as

customers and distributors. He can view the feedback

given by the users.

2) Customer User can register as a customer and then buy products

online. He can add products to his shopping cart. He can

also give feedback.

3) Distributor User can register as a distributor and then buy products

online. He can add products to his shopping cart. He can

also give feedback.

3.2 Technical Issues

The system should be implemented in PHP.



4. Interface Requirement

4.1 GUI

GUI-1: The home screen will be displayed so that stack holder of the system will use

of this system.

GUI-2: The stack holder is registered user than he login in him account. But stack

holder is not registered than he first fill up register form & after login as customer &

Distributors.

GUI-3: The stack holder login then view products and add products in the cart.

GUI-4: The stack holder proceeds for payment.



4.2 Hardware and Software Requirements (Minimum) MINIMUM HARDWARE REQUIREMENT

Server Side Hardware Requirement

Processor 2.50GHz

RAM 2 GB

Hard Disk 4 GB Free space

Client Side Hardware Requirement

Processor 1.60GHz

RAM 512 MB

Hard Disk 2 GB Free space

MINIMUM SOFTWARE REQUIREMENT

Server Side Software Requirement

Operating System Windows XP, Windows 7, 8.

Front End Php 5.2.2

Back End MySQL 5.2.2

Tools Macromedia Dreamweaver (8.0),

WampServer (2.2).

Client Side Software Requirement

Operating System Windows XP

Web Browser Internet Explorer 6.0



5. Performance Requirement

The performance requirement defines the response time for system functionality.

The load time for the GUI should not be more than four seconds.

The log in must be verified within 7 seconds.

The search query should be processed within 3 seconds and response must be given.

6. Design Constraint The system must be design as a standalone system and must be run on window based

system. The system can develop in PHP.The database are implemented in Oracle or MySQL.

7. Other Non-Functional Attributes 7.1 Security

The system must provide password to logon the system. The password must be

changed by the administrator/Customer/Distributor.

7.2 Reliability

The system must be reliable to prevent any unauthorized access.

7.3 Availability

The system should be available during the 24 hours.

7.4 Maintainability

There should be the facility to add product in the cart by Customer and Distributor.

8. Preliminary Schedule

The System must be implemented within 6 months.



11.Timeline chart

Timeline chart:-

Timeline chart refers to user items that create a chart where a series of events are

arranged on a bar graph.Where by every event could be a single point in time or date range.

For people in the chart who have a person page entry, the chart entry links to the

person a page entry and vice-versa.Some chart colors are determined by the theme but can be

changed by the user via the properties in the Stylesheets.Theme.

Chart section.Other stylesheet options are controlled via the chart-related styles in the

Stylesheet.System section.



Time line chart for tablet distribution system:

0

1

2

3

4

5

6

Progress

6 jan 21 jan

27 jan

3 feb 17 feb

3 mar 10 mar

17 mar 31 mar

7 apri

Date post:	06-May-2015
Category:	Software
Upload:	manasvi-sarkar
View:	466 times
Download:	3 times