2013

Project Documentation

Developed In StarUML
An Online Shopping System
Date Of Submission:5/3/2013

Online Shopping System A detailed approach

System Specification Document
Prepared By1. Pradipta Roy Chowdhury(RollNo.10200210012)
2. Nilanjana Roy(RollNo.10200211063)
3. Dipak Das(RollNo.10200210033)
4. Pabitra Sarkar(RollNo.10200210007)
Department- IT 3rd Year

Untitled

Table of Contents
1. ............................................................................................ INTRODUCTION
.............................................................................................................................................. 6
1.1.

OBJECTIVE ................................................................................................................................... 6

1.2.

OVERALL DESCRIPTION .............................................................................................................. 6

2.

USE-CASE DIAGRAM ..................................................................................................................... 7

2.1.

3.

MAIN DIAGRAM ........................................................................................................................... 7

ACTOR SPECIFICATION ............................................................................................................... 8

3.2.

USER ............................................................................................................................................. 8
3.2.1.

4.

Description ........................................................................................................................... 8

USE-CASE SPECIFICATION .......................................................................................................... 9

4.1.

ADD TO CART ............................................................................................................................... 9

4.1.1.

Description ........................................................................................................................... 9

4.3.

BUY ITEMS ................................................................................................................................... 9

4.4.

CHOOSE PAYMENT MODE............................................................................................................ 9

4.4.1.
4.5.

CONTINUE SHOPPING ................................................................................................................ 10

4.5.1.
4.6.

Description ........................................................................................................................... 9

Description ......................................................................................................................... 10

ENTER DELIVERY DETAILS ....................................................................................................... 10

4.6.1.

4.7.

Description ......................................................................................................................... 10

EXIT............................................................................................................................................ 10

4.7.1.
4.10.
4.10.1.
4.11.
4.11.1.
4.12.
4.12.1.
4.13.
4.13.1.
4.14.
4.14.1.

Description ......................................................................................................................... 10
LOG IN .................................................................................................................................... 11
Description ......................................................................................................................... 11
OTHER SPECIFICATIONS ........................................................................................................ 11
Description ......................................................................................................................... 11
REGISTER ............................................................................................................................... 11
Description ......................................................................................................................... 11
SELECT BRAND ...................................................................................................................... 12
Description ......................................................................................................................... 12
SELECT CATEGORY................................................................................................................ 12
Description ......................................................................................................................... 12

Untitled

4.15.
4.15.1.
4.16.
4.16.1.

SELECT ITEM ......................................................................................................................... 12

Description ......................................................................................................................... 12
SELECT PRICE RANGE ........................................................................................................... 13
Description ......................................................................................................................... 13

Untitled

List of Figure
FIGURE 1 USE-CASE DIAGRAM OF MAIN ................................................................................. 7

Untitled

USE CASE DIAGRAM AND DETAILED DOCUMENTATION

1. Introduction
1.1. Objective

1.2. Overall Description

This document describes.
Use Case Diagram and detailed documentation.

Untitled

2. Use-Case Diagram
2.1. Main Diagram

System
Continue Shopping
<<extend>>

Register
Select Brand
1..*

Add to Cart

<<extend>> <<include>>
<<extend>> <<extend>> <<include>>
<<extend>>

1..*

1..*

<<include>>
<<extend>>
Select Category
1..*

User
<<extend>>

1..*

Buy Items
Select Price Range Select Item
<<extend>>
<<include>>

<<include>>

Choose Payment Mode

1..*

Exit
Log In

Other Specifications

<<include>>

<<include>>

Enter Delivery Details

Figure 1 Use-Case Diagram of Main

Untitled

3. Actor Specification
3.1. User
3.1.1.

Description

Untitled

4. Use-Case Specification
4.1. Add to Cart
4.1.1.

Description

4.2. Buy Items

4.2.1.

Description

4.3. Choose Payment Mode

4.3.1.

Description

Untitled

4.4. Continue Shopping

4.4.1.

Description

4.5. Enter Delivery Details

4.5.1.

Description

4.6. Exit
4.6.1.

Description

10

Untitled

4.7. Log In
4.7.1.

Description

4.8. Other Specifications

4.8.1.

Description

4.9. Register
4.9.1.

Description

11

Untitled

4.10. Select Brand

4.10.1. Description

4.11. Select Category

4.11.1. Description

4.12. Select Item

4.12.1. Description

12

Untitled

4.13. Select Price Range

4.13.1. Description

13

Untitled

Sequence Diagrams for all Use Cases

1. Register:-

2. Log In:-

14

Untitled

3.Select Category:-

4.Select Brand:-

15

Untitled

5.Select Price Range-

6.Select Items:-

16

Untitled

7.Add To Cart:-

8.Buy Items:-

17

Untitled

Class Diagram for the System

Class Diagram for the online shopping portal

DescriptionIn software engineering, a class diagram in the Unified Modeling Language (UML) is a type
of static structure diagram that describes the structure of a system by showing the
system's classes, their attributes, operations (or methods), and the relationships among
the classes.

18

Untitled

Documentations about the classes and the relationships

1.User ClassA user-class is here abstracts those all functions that a
user is capable to do here and also holds those attributes
that a user can hold atmsot.We need to keep in mind that
here we are not dividing users into registered and non
registered.A user has LoginID(private
attribute),Password(private attribute),Address and Phone
number.there could be many more attributes too.It
depends upon the system designer that what he will
keep.A user can normally performregister(),login(),changePassword(),cancelOrder() these attributes.All
attributes are normally public properties they are known to everyone.
2.Item ClassItem is a class abstracted for all the types of items that are in
the databse of a shoppping portal.Every item has a particular
ItemID,Brand,Price and Specifications ofcourse.These are the
key or minimum requirements to identify an item.Now It must
be said that detials of an item is stored in the database i.e
Itemdatabse(a class to replicate a database to store all details
about an item).an item has some attributes like getBrand(),getPrice and there
can be much more to show.
3.User DatabaseUserDatabase is an abstraction which holds the properties of a
database used to keep details about the users registered
already in the shopping portal.UserDatabase class has
attributes like UserID,Password,Address,Phone Number and all
other details we can integrate in the registration webpage.A
databse normally has some follwing operations like
addNewUser().loginValidation(),updateDetails() and maybe
other advanced options.

19

Untitled

4.Item DatabaseItemDatabase is a database for keeping the details of all

items that is displayed in the shopping portal.It has those
attributes which ensures a smoother functioning of the
whole shopping portal e.g
ItemId,Brand,Price,Type,Itemcount,ItemRequest etc.This
itemdatabse class also can perform several operations like
addItem(),updateStock(),removeItem() etc. but this
operations do need help from the administrator himself.
5.CartCart is the class where the user temporarily stores the item
he/she bought in the shopping portal.This cart has several
properties like CartID,No.of Items,UserId and may be some other
properties optionally.It is related to the Item class through a
added to replation and multiplicity of many at item end and 1 at
cart end;as many items can be put into the cart.A cart has several
operations to perform like
addItem(),discardItem(),confirmation().We must say that none of this operation
is independent of other classes.It certainly requirs invoking of other classes.
6.Order DatabaseOrderDatabase class is an abstraction of the OrderDatabase
where placed orders are stored for proper records.It may have
many attributes e.g
OrderID,UserID,ItemID,Quantity,Orderamount.Like other
databases it has various functions like
addOrder(),removeOrder(),updateOrder().

20

Untitled

7.AdministratorAdministrator is the main adviser or maintainer of the

system.He checks evrything and confirms the orders,check
the orders,finalize them,conforms delivery and also
continuously check databses so that the system can be at
its proper state always.It must be noted that Admin class
does not mean a representaion of a human whho does
this.Admin can be a sofware intelligence too for
performing all this opertaions.Admin has AdminID and Password as attributes
and
loginValidation(),checkOrders(),finalizeOrders(),deliveryConfirmation(),checkStoc
k() as operations.

Relationships Between Classes

1. Login/RegistrationUser class and UserDatabase class is related to each other through association
relation as their objects are interrelated.We have named this relation as
login/registration as only during this two operations interact with the database
class.We can mention the multiplicity here also.At any instance there can be
more than one user and there can be more than one registration instances.
2. SelectsUser class and Item class is interelated with an association relation as an
instance of user class chooses one or many items(instances of item
class).Therefore the multiplicity at user-end is 1 and multiplicity at item class
end is 1 to many.
3. AddedToItem class and cart class are related to each other thorough this added to
relation.Now as to build a cart completely there are objects of item class
needed.So the relation is aggregration.Now aggregration being a stronger form

21

Untitled

of association defines a whole part relationship between two classes.It is also

applicable here.Noe to talk about the multiplicity there is 0 to many at item end
and 1 at cart end as many items can be put into a cart.
4. Order requestCart class and Admin class are connected through order request association
relation.When items are put into a cart before buying and finalizing the cart
sends a order request to the admin who checks to finalize the order.Now to talk
about the multiplicity in this case,the user can also cancel order or disacrd items
if he/she wants,so at cart end the multiplicity is 0 to many and the request form
any items can be one so at the admin end it is 1.
5. CheckorderDetailsAfter recieving the request of order from the cart admin sends a request too to
the ItemDatabse so that a check is performed and the order can be finalized
properly.This association is known as the checkstockdetails(as we named
it).Multiplicity details can be abstracted here for being unnecessary.
6. FetchItemDetailsNow when admin class interacts with the OrderDatabase class and checks the
orderdetails it has to finalize orders with the help of ItemDatabase class.This
association relation is named as FetchItemDetails.
7. FetchUserDetailsTo finalize the order and store it in OrderDatabase, the Orderdatabase must
fetch the user detials from the UserDatabase ot avoid all kinds of data
redundancy.This association relation is named as fetchuserdetails.
8. GetPriceItem class is related to ItemDatabase through association relation as when
choosen an instance of the item class interacts with the ItemDatabse class.This
getPrice association fetches the price from the itemDatabase.And to talk about
the multiplicity of this relation,Many items can fetch their price from the databse
class;so the multiplicity at both ends will be 1 to many.

22

Untitled

9. CheckAvailabilityWhen an item or some items is(are) put into the cart the cart needs to perform a
check that whether the item(s) is in the database.Thus the cart class and
ItemDatabase classes are related with an association relation named as added
to.Now multiplicity cannot be determined here properly.As it can be left upon
the system designer that if individual requests will be sent form individual items
or a composite query will be there.

23