[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!. 

Scene 1

GROUP PROJECT
PACKSTACK
CROUP 8: CSS323-2 SOFTWARE ENGINEERING

[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.. 

Scene 2

01
02
03
04
05
06
CONTENT
UML USE CASE DIAGRAM
USE CASE DESCRIPTIONS
UML CLASS DIAGRAMS
SEQUENCE DIAGRAMS
UML DEPLOYMENT DIAGRAM
GROUP MEMBERS

[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.. 

Scene 3

UML USE CASE DIAGRA
A UML use case diagram shows how users (vendors
and packers) interact with a system to achieve goals
(use cases).

Scene 4

Scene 5

[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.. 

Scene 6

USE CASE DESCRIPTI
Use case ID
UC03
use case name
Create Account
Objective
to gain access to personalized services or resources on a platform or website
System or Application
Online Packing Service
1. Primary actor: Vendor
Stakeholders/actors
2. Secondary actor: Packer
Input Data
name, username, password, citizen D, resident registration, address, profile picture
Output Data
User credentials (username/email and password) to access the platform's services and features
Trigger
Select "create account" menu on the screen
1. The user must completely fill in the forms
Pre-conditions
2. Having a valid delivery address within the platform's service area
Post-Condition
Account confirmation email
Actor: Vendor and Packer
1. User enters personal information and credentials.
2. Platform verifies and validates the provided data.
3. User gains access to account features and services upon successful creation.
Normal flow
System
1. System processes and stores the user credentials.
2. Confirmation message is displayed, email confirmation is sent
System
1. Input validation failure: If the user provides invalid or incomplete information, the platform prompts them to correct
the errors before proceeding.
Exceptional flows
2. Email or phone number already in use: The platform notifies the user if the provided email address or phone number
is already associated with an existing account, prompting them to either log in or use a different email/phone number.
3. Password strength requirements: If the user's chosen password does not meet the platform's security standards
(e.g., minimum length, inclusion of special characters), they may be prompted to choose a stronger password.

[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.. 

Scene 7

USE CASE DESCRIPTI
Use case ID
UC05
Give feedback
Use case name
Objective
To allow users to provide feedback on their experience with the system or application.
System or Application
Online Packing Service
1. Primary actor: Vendor
Stakeholders/actors
2. Secondary actor: Packer
Input Data
Feedback Message
Output Data
Confirmation message
Trigger
Customer completes an interaction with the system or application
I . The vendor must have interacted with the system or application.
Pre-conditions
2. The system must be operational.
3. The vendor must be logged in
Post-Condition
The feedback provided by the customer is stored in the system's database
Actor: Vendor
I . Vendor accesses the "Give Feedback" feature from the system or application interface.
2. Vendor provides feedback in the designated input field.
3. Vendor submits the feedback.
System
I . System processes and stores the feedback.
2. Confirmation message is displayed
Normal flow
System
I . If the input field is left blank, an error message is displayed prompting the user to provide feedback.
Exceptional flows
2. If there is a technical issue during submission, an error message is displayed, and the customer is prompted to try again.
3. If the customer is not logged in, they are redirected to the login page before they can give 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.. 

Scene 8

USE CASE DESCRIPTI
Use case ID
Use case name
Objective
System or Application
Stakeholders/actors
Input Data
Output Data
Trigger
Pre-conditions
Post-Condition
Normal flow
Exceptional flows
UC06
Payment
To view job pricing details and facilitate payment.
Online Packing Service
Primary actor: Vendor
Job pricing details, Payment method
Status, Receipt
The vendor initiates the payment process after viewing payment details.
I. The vendor has accessed the job pricing details provided by the packer.
2. The vendor has selected payment method.
Payment is successfully processed and confirmed.
Actor
I. The vendor reviews job pricing details.
2. The vendor selects payment method.
System
3. The system processes payment.
4. The system generates confirmation and receipt.
System
1. Prompt vendor for correction if errors detected.
2. Suggest alternative payment methods if technical issues arise.
3. Notify vendor of transaction decline and provide guidance for resolution.

Scene 9

[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.. 

Scene 10

UML CLASS DIAGRA
Image Type
•tybkNarm: String
•useriD: String
• usernanw
-password:
•citizenlD:
•res&nt:
-address: String
•profile Picture:
-getuser1DO
-getusernarne()
•getpassword()
-getResidentO
-getAddressO
*acca e ate()
•accEditO
back()
•feedtHzkID:
-teedbackBT, Strng
•descriptim: String
•qetNarne0
*review' D: String
•revimvBy: String
•rating; DouWe
•descriptor': String
• getRevtewI DO
•getName()
-get
•paymentID:
*paidBy: Stnng
•qetP aymentl DO
+getPaidgyO
•payment( arnount
DouWe
String
enameEnvbyee: Sring
-address:
String
*status: Strmg
*get Em'*oyeeID0
•getNameO
-oetAaaress()
-getRoIe()
•getStatus()
taccEditO
System Achinistrator
•trainVm: String
•ap prove Packer()
•train()
Train packer
-creditCardInto: String
Info()
-create Task O
4 paymertO
+WveRevÉw()
•name Packer: String
•get Narne()
-choose Task()
•tasklD: String
• taskNanw Strfvg
•taskDescription: string
•geuo()
-get Name 0

Scene 11

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. 

Scene 12

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.. 

Scene 13

SEQUENCE DIAGRAM
Payment
Review Job pricing Detail By packer
Pricing
Request payment
autenticati on
Initiate payment process
Notify Autentication
Process proceecl-- -
(Payment
Confirmation and receipt--
[Else]
-Prompt for correction 
-Suggest A It paymern method
- -Transaction Decline-

[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.. 

Scene 14

SEQUENCE DIAGRAM
Give feedback
login
Ack login
giveFeedback(message)
[ Actor = Vendor ]
[ Actor = Packer ]
Ack feedback

Scene 15

[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.. 

Scene 16

User Device
PackStack App
User Interface
Styles
Bank Server
Scripts
UML DEPLOYMENT DIAGR
Application Server
Socket Server
DB Interface
API Server
API Gateway
Server
User Server
Packing Service
Review Service
Workload Service
Account Database
vendor DB
Packer DB
Packing DB
Review DB
Workload DB
Payment Gateway
Log Server
Log System

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

Scene 17

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

Scene 18

2nd presentation UML 

Scene 0

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.

avatar

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.

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.

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.

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.

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.

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.

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.

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.