Professional Documents
Culture Documents
Sample Assignment
Sample Assignment
Sample Assignment
Specification
for
Version 1.0
Table of Contents
Table of Contents ........................................................................................................ ii
1. Introduction...............................................................................................................1
1.1 Purpose......................................................................................................................1
1.2 Document Conventions.............................................................................................1
1.3 Intended Audience and Reading Suggestions ..........................................................1
1.4 Project Scope............................................................................................................2
2. UML Diagrams..........................................................................................................3
2.1 Use Case Diagrams.......................... .........................................................................3
3.1 Class Diagram ......................................................................................................12
1. Introduction
1.1 Purpose
Online Shopping Software main purpose is to provide customers with the possibility to
perform online purchases on products already on store. Customers are identified properly
and are able to perform online transactions using three kind of methods: either using
credit card or banking documents, but also through PayPal account. Online Customers are
divided on two categories upon user account types: basic and business.
Basic accounts beside other attributes contain a specific one named Fidelity which deals
with the number of years the user has been joining the online shop. On the other hand is
business plan which is characterized uniquely by the Volume attribute that is the total
amount of transactions performed within the online shop. The customer is able to operate
throughout the system after properly authenticated. He is able to create a cart and add
products to it or delete them as well. Then he decides whether he might go on with the
checkout operation and complete the purchase. Once the user decided upon the plan to
use: basic or business, he is given the alternatives to pay through the previously
mentioned methods accordingly. Once the purchase is confirmed by the customer and
admitted by shop commission, customer details come into use in order to define the
shipping address and other supplementary information. Customer is given the possibility
to view and print some information regarding his activity on the shop. For instance he can
print the number of purchases completed by him from eh beginning of the current year.
He can print the status of previously performed purchases and decide whether to cancel
or not a specific purchase if it is still in Not available status.
During the process of product selection and addition to cart specifying correspond
quantity the system automatically checks if the product is available within the quantity or
not. In case of negative response the system generates a request to the product supplier.
Stated in short terms this is the overall situation on hand.
2. UML Diagrams
2.1 Use Case Diagrams
Online Shop from user perspective use case
Description:
This use case provides the viewpoint for the whole process from user perspective.
Customer sees only the necessary functions that the system must define.
Actors: Online Customer
Preconditions: Customer must have a bank account.
Base Case:
1. Customer must log in and authenticate
2.
3.
4.
5.
6.
Alternative Flows
None
Post conditions: Customer performs transactions based on defined accounts.
Additional Info/Issues: None
Description:
View products use case describes the whole operations a user can perform on a product
currently on the store. It also describes an exceptional case when a product is not
available on the quantity required.
Preconditions: Customer must login and authenticate firstly
Base Case:
1. Customer can view the products
2. he can select the products
3.
4.
5.
6.
7.
Alternative Flows
None
Post conditions: Customer performs transactions based on defined accounts.
Additional Info/Issues: None
Description:
This use case defines the cycle when customer makes a purchase. When deciding to
perform a purchase the customer proceeds to the checkout operation and then to the
payment method and according verifications.
Preconditions: Customer must confirm the final form of the cart and products already in.
Base Case:
1. Customer must complete with the cart
2. he is taken to the checkout step
3. he is forwarded to a payment method based on the purchase type that he
decided beforehand.
Alternative Flows
The customer may cancel the purchase when it is in Not Available yet status.
Post conditions: Customer performs transactions based on defined account.
Additional Info/Issues: Includes third party accounts like PayPal or supporting bank
documents.
Description:
Payment use case deals with the cycle of performing a payment through on of the
methods mentioned.
Preconditions: Customer must authenticate and decide upon the type of purchase to
commit.
Base Case:
1. Customer decides on the type of method to pay using either credit card or
providing bank documents in case of basic type of purchase.
2. he decides upon PayPal method to pay if he decides on business purchase type.
3. each of the methods forward the user to the corresponding sites where he can
enter credit card info, or upload a document or confirm a PayPal account.
Alternative Flows
None
Description:
This use case describes processes when the customer can view and print information for
purchases he has already performed.
Preconditions: Customer must authenticate.
Base Case:
1. Customer can view the status of the purchases already submitted.
2. If the status is Not available yet the user has the choice to cancel such a
purchase.
3. he can list, view and print purchases from eh beginning of the year also.
Alternative Flows: None
Post conditions: None
Additional Info/Issues: None