UNIVERSIDAD DE CÓRDOBA

GRADO DE INGENIERÍA INFORMÁTICA

ADVANCED SOFTWARE MODELLING AND DESIGN

ACTIVITY DIAGRAM, USES CASES DIAGRAM,

CLASS DIAGRAM

Author: Antonio José Sánchez Moscoso

Date: 26-03-2020
 INDEX OF CONTEXT

1 INTRODUCCIÓN....................................................... 3

2 BUSINESS CONCEPT MODEL ......................................4

2.1 BUSINESS CONCEPT MODEL ........................................................ 4

3 ACTIVITY DIAGRAM ................................................. 6

3.1 ACTIVITY DIAGRAM ................................................................. 6

4 USE CASE DIAGRAM................................................. 8

4.1 USE CASE DIAGRAM................................................................. 8

4.2 USE CASE SPECIFICATION ........................................................ 10

Apéndice A BIBLIOGRAPHY ........................................ 12

Título del documento Nombre del Capítulo

1 INTRODUCCIÓN

In this work, i am going to expose use case diagrams, class

diagram, business concept model and use case specification about
online shopping.

This is important to do so that the software design and

modeling is more understandable and easier to implement.

Next, I Will show business concept model.

 2 BUSINESS CONCEPT
MODEL

2.1 BUSINESS CONCEPT MODEL

Business Concept Model has as main purpose:

• Capture the concepts of the problema domain (classes).

• Identify its relationships.
• Classes may be stereotyped as <<concept>>
• The aim of the model to identify the knowledge of the
domain.
• There are not generalizations, nor dependencias among
classes (it is optional)
• Associations should include the role if it is not trivial, as
well as the cardinality if it is different from 1.
Título del documento Nombre del Capítulo

Okay, let’s start explaining this concept modal business.

At first, the User owns a one Shopping cart and he can also
utilize Search Product (it does not apperar in the image but the
relationship es 0* - 1). Then Search Product can find 0 * Products.
Both the user and the producto are related to the Shopping Cart.

By last, the user accepts To confirm order and then make the
Purchase payment.
Título del documento Nombre del Capítulo

3 ACTIVITY DIAGRAM

3.1 ACTIVITY DIAGRAM

Activity diagram is another important behavioral in UML diagram to

describe Dynamic aspects of the system. Activity diagram is esentially
an advanced versión of Flow chart that modeling the Flow from one
activity to another activity.

Activity diagrams describe how activities are coordinated to provide a

service which can be at different levels of abstraction.

It is also suitable for modeling how a collection of use cases

coordinate to represent business workflows
1. Identify candidate use cases, through the examination of
business workflows
2. Identify pre- and post-conditions (the context) for use cases
3. Model workflows between/within use cases
4. Model complex workflows in operations on objects
5. Model in detail complex activities in a high level activity
Diagram
Título del documento Nombre del Capítulo

I think there is no need for an explication of this diagram

because it is very similar to the block diagram that we saw in the
previous topic. If there any doubts, you can explain them to me
through the fórum.
Título del documento Nombre del Capítulo

4 USE CASE DIAGRAM

4.1 USE CASE DIAGRAM

A use case diagram is a dynamic or behavior diagram in UML.

Use case diagrams model the functionality of a system using actors
and use cases. Use cases are a set of actions, services, and functions
that the system needs to perform. In this context, a "system" is
something being developed or operated, such as a web site. The
"actors" are people or entities operating under defined roles within
the system.

¿Why Make Use Case Diagrams?

Use case diagrams are valuable for visualizing the functional

requirements of a system that will translate into design choices and
development priorities.

They also help identify any internal or external factors that may
influence the system and should be taken into consideration.
They provide a good high level analysis from outside the system. Use
case diagrams specify how the system interacts with actors without
worrying about the details of how that functionality is implemented.
Título del documento Nombre del Capítulo

Actors:

Admin: He can perform all use cases including “Manage

DataBase(Delete,Add and Modify) Product.

Registered User: Could also perform all except “Manage

DataBase Product”.

Unregistered User: He could not “confirm order and Pay” and

“Manage DataBase Product”.
Título del documento Nombre del Capítulo

4.2 USE CASE SPECIFICATION

Name Search Product

Initiator Admin, Registered User or Unregistered User

Secondary Actors None

Goal Go to the page of a product

Main Stage 1. The user wants to search a product.

2. The user writes the name of a product in the
search engine.
3. The system displays all products related that
search.
4. The user selects a product.
5. The system shows the product page.

Extension 3ª. There are no products with that search

Name Modify Shopping Cart

Initiator Admin, Registered User or Unregistered User

Secondary Actors None

Goal Add or delete product from basket

Main Stage 1. User enter to modify option

2. The user clicks on the “Add/Delete
3. The system add or delete product.
4. The system shows the shopping cart.

Extension
Título del documento Nombre del Capítulo

Name Add Product

Initiator Admin, Registered User or Unregistered User

Secondary Actors None

Goal Add producto to Shopping Cart

Main Stage 1. The user has previously searched for the

product.
2. Inside the producto page, the user clicks on
add product buttom.
3. The system adds products on the shopping
cart

Extension

Name To confirm and pay order

Initiator Admin or Registered User

Secondary Actors None

Goal Pay purchase all products of the shopping cart

Main Stage 1. The user wants to pay purchase.

2. The user selects to confirm order
3. The user selects the payment method and
the shipping address.
4. The system notifies you if you want to make
the payment.
5. The user selects confirm.

Extension 4ª. The user cancels the purchase.

 A BIBLIOGRAPHY

1. Use Case Diagram https://www.smartdraw.com/use-case-

diagram/#whatisUseCase

2. Activity Diagram https://www.visual-

paradigm.com/guide/uml-unified-modeling-language/what-is-activity-
diagram/