Download software model in software engineering and more Thesis Software Development in PDF only on Docsity!
Faculty of Computer Science and Information Technology
SOFTWARE MODELING SSE 5303
TITLE
MOBILE PHONE ONLINE SHOPPING (MOPOS)
-FUNCTIONAL MODELING REPORT-
LECTURER
DR. NORHAYATI MOHD ALI
STUDENT
SAWALRUDIN BIN ABU HASSAN GS
EUGENE TOBORE OKOJIE GS
SHUWAIL ABOBAKR HASAN QASEM
MUHAMMAD HANIF BIN MAZLAN
Contents
1. Introduction
1. Background
2. Problem Statement
3. Objective
4. Scope
2. Requirement
2.1. Functional Requirement
2.2. Non-Functional Requirement
3. Functional Modeling
2.3. Usecase Diagram
2.4. Usecase Description
4. Structural Modeling
5. Behavioural Modeling
6. Implementation Modeling
often fail to meet even basic electrical safety standards. Also, because counterfeit phones are
not tested for compliance with industry and national standards, they suffer frequent call
dropouts and put a strain on the mobile network by degrading coverage, call quality and
mobile internet speeds. Recent cases have shown that counterfeit devices can also come
preloaded with malware that seeks to steal personal and financial information from the user.
2. Objective
Mobile Manufacturers Forum (MMF) research predicts sales of around 148 million
counterfeit or substandard mobile devices in 2013 through visible retail sites, with many
more expected to be sold in unofficial retail outlets, online auction websites and in local
black markets. With the average knock-off phone selling for around US$45, MMF estimate
of US$6 billion in illegal sales represents a massive financial loss for governments and the
mobile phone industry.
Therefore, the objective of this study is to provide an online platform that sells genuine
mobile phones to the consumers.
3. Scope
This study will focus on the development of a web-based online shopping platform that sells
genuine mobile phones to the consumers. This system will allow consumers to buy various
phone brands without worry about it's counterfeit products. every product sold has passed
tests from authorities like MCMC. the authority's approval certificate will be attached when
user reviews the product. the user may also choose to customize the product specifications
that they wish to purchase before the purchase is finalized. The development will emphasize
on online shopping consumers. The area of focus is limited to ensure good understanding of
business by grasping the behaviour of the target group to properly apply online shopping.
The prototype to be developed is based on the context of business and target users.
2. Requirement
Ecommerce also known as electronic commerce or internet commerce, refers to the buying
and selling of goods or services using the internet, and the transfer of money and data to
execute these transactions. Ecommerce is often used to refer to the sale of physical products
online, but it can also describe any kind of commercial transaction that is facilitated through
the internet. Whereas e-business refers to all aspects of operating an online business,
ecommerce refers specifically to the transaction of goods and services.
In order to capture your audience and make the sales, you have an ecommerce website. Your
e-commerce website needs to be current and implement several very important elements.
2.1. Functional Requirement
This section provides requirement overview of the system. Various functional modules that
can be implemented by the system will be:
Actor Requirements Description Objective
Customer Login Registered customer by providing user ID (email address) and password.
View Items Customer browse through the store to the items that are there in each of products. Customer can use searching mechanism for easy and quick access to particular products.
Add/Remove Item From Cart
Customer Registration
New customer providing user Id (email address) and password. Allowing customers to register will save them time when it comes to repeat purchases, they won’t have to re-enter their payment information, shipping address, and any other personal information.
2.2. Non-Functional Requirement
Quality Attribute Architecture Requirement Performance Performance shows the response of the system to performing certain actions for a certain period. This application has to response any request at normal time and peak hour. Security Security is responsible for the ability of the system to reduce the likelihood of malicious or accidental actions as well as the possibility of theft or loss of information. Security features that will use in this application are:
3. Functional Modeling
2.3. Usecase Diagram
2.4. Actor Description
Actor ID AC Actor name Customer Description
2.5. Usecase Description
Use case ID UC Use case name
View Items
Actors Customer Description Browse and/or search among products. Trigger The customer wants to browse among products or the customer would like to search for certain products. Precondition The customer opens a browser on his/her machine. Postcondition The system presents a result list of products (which meets with the given search conditions in case of searching) to the customer. Normal flow 1. The customer opens a browser on his/her machine.
- The customer types a keyword in the search field and presses the "OK" button.
- The system finds products which meets with the search conditions and presents the result to the customer.
Alternative flows
Perform Advanced Search Steps 2 is replaced with:
- The customer performs an advanced search operation. (S)He fills the input fields belonging to different attributes of products, then presses the "OK" button. Refine Search Result The following steps are added:
- The customer refines the result by typing new keywords into the search fields.
- The system executes a new search operation on the previous result list and presents a new result list to the customer. View Product Details Steps 2-4 are replaced with the following:
- The customer selects a product from the presented list.
- The customer presses the "Details" button.
- A new popup window opens containing some more information about the selected product.
Exceptions The format or number of the search keywords is incorrect.
The system cannot load products (the database is not available).
Includes None
Notes and issues
If none of the products meets the given search conditions, the system returns an empty list.
Use case ID UC Use case name
Manage Shopping Cart.
Actors Customer
Description This use case describes how an actor can modify items in the shopping cart.
Trigger Every user who visits the site or makes a purchase has a direct bearing on the revenue and hence the profitability of the shopping platform
Precondition The actor is on the cart screen and have already logged in.
Post- condition
The user successfully modifies existing items in the cart or adds new items to the cart.
Normal flow 1. The user clicks on one of the category in the frame of the screen and navigates to the item he wishes to add to the cart and clicks on the “Add to Cart” link.
- The system displays the cart screen with the all the old items and newly added item. The subtotal field displays the total cost of the shopping cart.
- The user repeats step “3 and 4” for all the items She/he wants to add to the cart.
- The user modifies the item quantity for one or multiple items and clicks “update cart”
- The system updates the new quantity and displays the modified line items totals and sub- total to the user.
- The user clicks the “Remove” link to remove any of the items in the cart.
- The system deletes the item from the cart and adjust the sub-total and quantity accordingly
Use case ID UC Use case name
Customize Product Specification.
Actors Customer, Administrator, Vendor Description This is when the item been purchased, has to be checked if it meets the customer’s requirement or specification. Trigger Customer selects item, and manage shopping cart. Precondition Customer has logged in and selected item, and an order has been placed. Post- condition
User has already accepted the displayed item.
Normal flow 1. Customer, has viewed item, and selected item.
- Customer then logs into the system to manage shopping cart.
- Customer can view “ITEM FEATURES” for example, Item Model, Functions, Specification, and Manufacturer, etc.
- Customer can ask for specific item. If item available from Vendor, “Hence item will be displayed by Administrator”. Alternative flows
- If item/product specification is not meet, order can be cancelled.
- If desired item is satisfactory to the customer after view and search, then proceed with order. Exceptions If item is not satisfactory to customer, then vendor should provide satisfactory item. Includes Vendor, Item been displayed and manufacturer. Notes and issues
Customer must agree with what item is displayed as Vendor provides the items. If not customer can cancel order.
4. Structural Modelling
5. Behavioural Modelling
6. Implementation Modelling
