2nd presentation UML

[Virtual Presenter] Good morning everyone. Today I would like to talk to you about how our company provides innovative and creative marketing strategies that help businesses grow and excel in their marketing endeavors. We will discuss the specific tactics and practices that our company offers and how they can benefit your business. Let's get started!.

[Audio] This slide demonstrates the range of diagrams and information related to the team who are responsible for the creative marketing strategies we offer. To begin we have a UML Use Case Diagram followed by Use Case Descriptions which provide a text-based description of the user interactions. UML Class Diagrams provide a visual representation of the structure of our system and Sequence Diagrams show the flow of activities between different parts of the system. Finally a UML Deployment Diagram demonstrates how the components that make up our system are distributed across different locations. The slide also lists the names of all the team members who have contributed to our creative marketing strategies..

[Audio] UML Use Case Diagrams are an effective way to illustrate the interactions between different users and a system to achieve their desired outcomes. This diagram is an accessible way to identify and organize the procedures related to the system and their connections to one another..

UML USE CASE DIAG Adminnistrator.

3 SAMPLE OF USE CAS DESCRIPTIONS.

[Audio] Creating an account on an online packing service requires vendors and packers to enter personal information and credentials which the system then verifies and validates. On successful creation the users gain access to account features and services. The system prompts users to make corrections if they provide invalid or incomplete information. The platform also notifies the user if the email address or phone number is already associated with an existing account so they can either log in or use a different one. In addition the chosen password must meet a certain level of security to be accepted by the system..

[Audio] For this use case the Vendor and the Packer are the main actors. When a customer finishes interacting with the system or application they can leave feedback in the corresponding input field. The system will then save and show a confirmation message. If the customer does not fill out the field an error message will appear asking them to provide feedback. If an issue with submission arises an error message is displayed and the customer is advised to retry. Lastly if the customer is not logged in they will be re-directed to the login page before giving feedback..

[Audio] The use case for payment is discussed in this slide. The vendor is the primary actor in this online packing service whose objective is to view job pricing details and facilitate payment. After viewing payment details the vendor starts the payment process. Job pricing details and payment method are the input data whereas status and receipt are the output data. The normal process consists of the vendor reviewing job pricing details selecting a payment method and then the system processing the payment and creating confirmation and receipt. Exceptional flows include prompting the vendor to correct errors suggesting alternative payment methods in case of technical issues and informing the vendor of any transaction decline and providing guidance to resolve it..

UML CLASS DIAGRAM.

[Audio] The slide shows a number of U-M-L class diagrams representing different entities in the system. The User entity for example includes attributes like type id username and password while Feedback and Payment have their own specific fields. Each entity has its own method for User this might be getUserId getUsername and getPassword. The System Administrator has its own method like train and approvePackages and the Trainer Packer includes fields like name chooseTask and taskId. All of these fields and methods help to represent the entities in the system and how they interact with one another..

3 SAMPLE OF SEQUENC DIAGRAMS.

SEQUENCE DIAGRAM Create Account Actninistrater RecBRsV_checkOwne ,citizenID) return check check = true I send (Actor.account„data) Actor = Vendor [ Actor Packer store_Vendo B(file) Approve Ack c.

[Audio] A Sequence Diagram is presented illustrating the payment process for a job. It illustrates the steps of job pricing review authentication payment process initiation payment confirmation and receipt creation. In the case of a payment decline the diagram suggests an alternative payment method or corrections..

[Audio] We can observe from the sequence diagram the system's feedback mechanism with the different actors Vendor and Packer and the steps it entails. It begins with the Login and Ack Login then giveFeedback message eventually ending with an Ack Feedback. This diagram illustrates an overview of how the system works to provide feedback..

UML DEPLOYMENT DIAGRAM.

[Audio] The PackStack App technical architecture consists of several user devices servers and databases connected in chain. It begins with a user device followed by an app with a user interface and style. The app is then linked to a bank server and a script for deploying the U-M-L diagram. An application server is connected to a socket server and to a DB interface. Following this an A-P-I server an A-P-I gateway and user servers are connected to a packing service review service and workload service. Finally the account database vendor DB Packer DB packing DB review DB workload DB Payment Gateway log server and log system provide the technical architecture required for the App to function properly..

GROUP MEMBERS 10922780070 Phattanant Wongprechasawad 6922782472 6922782670 "22782720 "22782993 Yotsawat Vasavat Chayawat Yossawin Leethochavalit Limnanthasin Yuwaboon Khositanon.

THANK'S FOR WATCHING.