0% found this document useful (0 votes)
6 views18 pages

Course Project Presentation

The document outlines the design of an Online Shopping System using a service-oriented architecture, detailing components such as catalog, inventory, and customer account services. It includes use case modeling, static and dynamic modeling, and design modeling that emphasize the layered architecture and service interfaces. The system facilitates customer interactions for browsing and purchasing items while integrating various services through coordinator objects and object brokers.

Uploaded by

Nghi Nguyen Van
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views18 pages

Course Project Presentation

The document outlines the design of an Online Shopping System using a service-oriented architecture, detailing components such as catalog, inventory, and customer account services. It includes use case modeling, static and dynamic modeling, and design modeling that emphasize the layered architecture and service interfaces. The system facilitates customer interactions for browsing and purchasing items while integrating various services through coordinator objects and object brokers.

Uploaded by

Nghi Nguyen Van
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 18

SOFTWARE DESIGN (SWD392)

TEMPLATE BÁO CÁO ĐỒ ÁN MÔN

NỘI DUNG BÊN DƯỚI LÀ SAMPLE


Table of contents
• Problem Description
• Use Case Modeling
• Static Modeling
• Dynamic Modeling
• Design Modeling

2 / 20
Problem description
The Online Shopping System
• The Online Shopping System case study is a highly distributed
World Wide Web–based system that provides services for
purchasing items such as books or clothes.
• The solution uses a service-oriented architecture with
multiple services; coordinator objects are used to facilitate
the integration of the services. In addition, object brokers are
used to provide services which include:
• a catalog service o a delivery order service
• an inventory service o an email service
• a customer account service o a credit card authorization service

3 / 20
Use Case Model

• Actors
– Customer: browses a catalog and requests to purchase items
– Supplier: provides the catalog and services customer purchase requests
4 / 20
Use Case Model
Browse Catalog
In the Browse Catalog use case, the customer
browses a World Wide Web catalog, views
various catalog items from a given supplier’s
catalog, and selects items from the catalog.

5 / 20
Activity diagram for Make Order Request use case

6 / 20
Make Order Request
Use Case Model

Use Case Description for Make Order Request


Use Case Model
Other Use Cases

View Order

Confirm Shipment and


7 / 20 Process Delivery Order Bill Customer
Static Modeling

Conceptual static model for Online


Shopping System entity classes
8 / 20
Static Modeling
The classes include customer classes (Customer and Customer Account),
supplier classes (Supplier, Inventory, and Catalog), and classes that deal
with the customer’s order such as Delivery Order, which is an aggregation
of Item.

Entity classes for the Online Shopping System

9 / 20
Object and Class Structuring

Service and entity classes for the Online


Shopping System

10 / 20
Dynamic Modeling

Communication diagram for the Make Order


Request use case
11 / 20
Dynamic Modeling

Communication diagram for the Process


12 / 20 Delivery Order use case
Design Modeling
The components are structured into the layered architecture such that each
component is in a layer where it depends on components in the layers below
but not the layers above. This layered architecture is based on the Layers of
Abstraction pattern. Applying the component structuring criteria, the
following components and services, organized by layer, are determined

13 / 20
Design Modeling

Concurrent communication diagram for


14 / 20 Online Shopping System
Design Modeling
• Each service has one provided interface through
which the service operations are accessed.
• The clients of the service invoke the appropriate
operations provided by the interface synchronously.
The service operations are designed by considering
how each individual service is accessed on the use
case–based interaction diagrams. Typically, each
service is accessed in different ways corresponding
to requests for different service operations.
• The interaction diagrams depict the messages
arriving at the service (corresponding to service
operation invocation and possible input parameters
to the service) and the service response
(corresponding to data returned by the service),
which is either synchronous (as a synchronous
message reply) or asynchronous (in a separate
asynchronous message.
Component ports and interfaces
15 / 20 for services
Design Modeling

Service interface for Customer Account


Service interface for Service
Catalog Service

16 / 20
Design Modeling

Service-oriented software architecture for Online


Shopping System
17 / 20

You might also like