NATIONAL TECHNOLOGICAL UNIVERSITY OF LIMA

SOUTH
Teacher: Msc Jamer M. Delgado Pérez

Systems Engineering:
UML Design

Problem Description
Online bookstore
1.1 User Requirements

This is about building the UML analysis model of a software solution for a company.
that sells books over the Internet. Customers access information about the books through
the Web and search by author, title, or ISBN. As they navigate through the different pages
they find a book that interests them and add it to the shopping cart to complete the purchase at the end
corresponding order.

To place an order, a customer must be previously registered as such. This means entering
a series of personal data (first name and last name, address, locality, postal code, country), data of the
credit card (type of card, number, expiration date) and about shipping preferences (email
normal, express, international or courier). Associated with a specific order, they can be introduced
packaging options (standard or gift), card with additional message when it's a gift, or a
name and address of another person to whom an order is sent. As is customary in this type
of applications, you must choose a username and a password as a method of authentication for
carry out the usual transactions with the bookstore.

When the set of desired books (quantity, title and has been included in the shopping cart
The author must proceed to the order confirmation process, which will require a prior security step.
to ensure that the customer is who they say they are. Once all additional data has been entered, the
the client confirms the order which goes into a waiting state -90 minutes- during which it is possible
modify some of the order items (remove or change quantity) but not add new items
A new order must be created for this.

It is also intended to incorporate the '1-click' mechanism, that is, once it has been detected
the book you want to buy can be ordered by simply pressing a button labeled '1-
"click." This mechanism can be enabled/disabled by the user - who must be a client.
registered - and when used it is possible to accumulate all the desired items that will later be grouped in
a single order to optimize packaging and shipping costs. The criterion is to group all
items from an initial order made in '1-click' mode that fall within a deadline
of 90 minutes.

Any change in the client's data also requires a prior security step to
confirm that the client is the correct one.

On behalf of the bookstore, orders must be collected according to the modalities we have.
as previously described, and consolidate into a single order the isolated orders that are within the 90-day period
minutes, have already been completed with the cart option or with '1-click'. This period is the one that
it also allows for modifications, so from the moment they are reassembled
Orders to optimize packaging and shipping costs are definitively confirmed and not
they cannot be modified or canceled.
The company can make partial shipments based on item availability, but without
modify the total shipping cost due to this fragmentation of the order. As they are being
reorganizing the orders, an email is sent to the customer to confirm the order, the same as to
make the corresponding shipment.

If you believe that there is missing information in these requirements, make the necessary assumptions - in one way
logic and simple - and add them along with the corresponding diagram.

1.2 Assumptions

It is assumed that the bookstore has customers who buy books in its retail locations. It is
That is why there is already a Library Information System, with the catalogs of books and their functions.
associated (purchase of copies, search, classification, etc.) It is also assumed that the company
will request services from the credit card system (external, to validate the customer's card to
register and also to validate the electronic payment), as well as to the company's system that
makes the shipments (also external, to validate the shipping data of the order, calculate the costs of
shipping and contracting the shipping service for the order.

The format of the use case documentation follows the guidelines of the template in the Book
UML and Patterns by Craig Larman.

In the class diagram, I assume the Packages Clients and Books already exist, forming part of
of the Library's Computer System.

Use Case Diagram (2 points)

2.1 Context Diagram
2.2 Use Case Diagram

Online bookstore

Authenticate

Registrar

Add Item 1 Click

<<extend>>

Client

System
Search Books Computer System
Bookstore
<<extend>>

Add Item to Cart

System Confirm Order

Credit Card System

Change Personal Information

Modify Order
System
Business Shipping System

Send Order
Shipping Manager
2.3 Modified Use Case Diagram

Consider that there are two types of customers: the occasional customer, who can browse the news,
bestsellers or search for a specific book according to a criterion and the specialized customer
(student, researcher or teacher) who may need to see the books that deal with a topic
specific. Modify the diagram from the previous section (2.2) to take into account both types of
clients - depending on different goals - and represent in the model the relationships between actors,
the goals and—if necessary—the new use cases that are required.

Online bookstore

Authenticate

Registrar

Search for Occasional Books

Occasional Client <<extend>>

<<extend>>

Client
Add Item to Cart
Client
Specialized <<extend>> System
<<extend>> Computer System
Library
Add Item 1 Click

Search Specialized Books

<<System>> Confirm Order

Card System Créhere

Change Personal Information

Modify Order
System
Company Shipping System

Send Order
Shipping Manager
2.4 Textual description of 3 use cases

Use Case UC1: Register

Resumen:Aquí cualquier persona natural podrá registrarse como cliente de la librería llenando un
form with your data and what you want to read
Actors:
Client
Library computer system
Credit card system
Fecha de Creación:17-11-2021
Personal Involucrado y Metas:
Client: Wants to be a formal customer of the bookstore, to enjoy the store's benefits
Library computer system: Wishes to have customers with purchasing capacity as it can validate
the credit card information, which is used frequently.
Credit card system: Registers the bookstore customers and performs card authentication
in the safest way possible
Prerequisites: Not being a customer of the bookstore, being of legal age, having a valid credit card and
live in the country of origin of the bookstore.
Postconditions: Register as a customer, perform any operation that allows your card to
credit.
Main Stage:
Enter the bookstore's website and register as a customer.
The client enters their username and password to then fill in their personal data, then they choose
país, escoge preferencia de envió y si activa o no el modo“1-click”
The webpage will display a form for the place where you live and how you would like to receive your
product.
You will choose your type
The bookstore requests the bookstore's computer system if the customer is registered.
The bookstore's computer system registers the customer
The bookstore will ask for the necessary credit card information.
The customer will choose their type of card, the numbers, code, and expiration date of the card.
The bookstore will request the credit card system to validate the card data.
The credit card system accepts the card and responds with a code which remains
registered
The bookstore registers that code and gives a welcome message to the new customer.
Alternative Flows:
A1: nonexistent username
This will start at the 2nd item. The library information system will tell us that this user already
exists
A2: existing username, but invalid password
This will start in the 2nd item, The information system of the
the library will tell us that the password is invalid
A3: the system finds some failure to communicate with the SIL
This starts at item 5. The library will communicate that it exists.
inconveniences with the system
Requisitos de Interfaz de usuario:
A computer equipped with what is necessary to function basically
A compatible browser with the website
Non-Functional Requirements:
The page must work every day of the week
Be fast and efficient
It must be able to have many connected clients.
Use Case UC2: Identify
Summary: the client will be able to identify themselves with an account or with a username and password so that they can
make any type of purchase
Actors:
Client
Library computer system
Fecha de Creación:17-11-2021
Personal Involucrado y Metas:
Client: Wishes to become an authorized client as this will allow them to carry out operations such as purchasing a
fast and secure way
Library computer system: identify your customer and meet the customer's standards and their
needs
Prerequisites: Must be registered in advance
Postconditions: Know the client's data and what they want according to the provided data.
Main Stage:
The customer enters the bookstore's website
The library asks you to enter username and password.
-El cliente ingresa su usuario y contraseña
The library validates the data with the system
The system, when validating the data, indicates the personal data and other options to choose from.
Welcome the user
Alternative Flows:
nonexistent username
This starts at item 4, indicating that the user does not exist.
A2: existing username, but invalid password
This starts at the 4th item, showing a message, that the
the password is incorrect
A3: the system finds some fault in communicating with the SIL
This starts at item 4, indicating that there are failures with the system.
and that he tries again another time
User Interface Requirements:
A computer equipped with what is necessary to function basically
A compatible browser with the website
Non-Functional Requirements:
The page must work every day of the week.
Be quick and efficient
It must be able to have many connected clients.

Use Case UC3: Search for books

Resumen:El cliente podrá hacer una búsqueda de libros por filtros, como autor y titulo y aparte
show new arrivals from the bookstore.
Actors:
Client
Library information system
Fecha de Creación:17-11-2021
Personal Involucrado y Metas:
Client: Wants to quickly and easily find books with any information related to
book, also wants to take into account the news in the bookstore.
Preconditions: Being a registered and identified customer
Postcondiciones:Tener una lista de libros que se asemejen a la información brindada en el buscador
and that they can be added to the cart and enabling the 1-click option
Main Stage:
The bookstore asks you to choose what type of search you will perform from a list of options and the string.
search
The client will choose the type and the search string.
The bookstore will request the books from the system.
The system will show the books according to the data entered in the search engine and the new releases.
The bookstore will display the books sorted alphabetically by titles, with summaries.
imagen del libro, precio, autor, etc
Alternative Flows:
A1: non-existent username
There is no such alternative flow
A2: existing username but invalid password
There is no such alternative flow.
A3: the system finds some fault in communicating with the SIL
This would start at the 1st item, indicating that there are failures with the
system and try your search another time.
User Interface Requirements:
A computer equipped with what is necessary to function basically.
A browser compatible with the website
Non-Functional Requirements:
The page must work every day of the week.
Be quick and effective
It must be able to have many connected clients

Activity Diagrams (1 point)

3.1 Activity Diagrams

Show the activity diagrams for the three use cases described in Section 2.4.

Use Case UC1:

Use Case UC2:
Use Case UC3:

State Diagram (1 point)

4.1. State Diagram

Build a state diagram to show the possible changes in the order since
the client confirms it until the company confirms it at the end of the 90 minutes and it can no longer be done
make more modifications or cancellations.
 Class Diagram (2 points)

5.1. Class Diagram

Build the class diagram for the application.
 Sequence Diagram (1 point)

6.1. Sequence Diagrams

Show the sequence diagrams for the three use cases described in Section 2.4.

Use case UC1:

Use case UC2:

Use case UC5:
 Package Diagram (1 point)

7.1. Package Diagram

Build a diagram with the main packages of the application and their dependencies. Keep in mind
account that - based on the class diagram - should consider the possible associations and select
navigability so that the dependency is only in one direction
 Deployment Diagram (1 point)

7.1. Deployment Diagram

Build a deployment diagram to place the detected packages in the previous diagram and
allow a reasonable execution of the application.
 Design Class Diagram (1 point)

9.1. Design Class Diagram

Refine the class diagram of the application (Section 5.1) with some additional classes of
design (taking into account the technological solution) and expanding the detail of some of the
existing.