•Authors: Kazeev Danil, Begasilov Amirzhan

Project theme: •Group: IT2-2411SE

Freelance •Revieved by: Yemberdiyeva A. B.
platform
Freelance Platform
Project description
• This project is an online freelance exchange platform
designed for interaction between customers and freelancers.
The main idea is to create a convenient, secure and intuitive
space where customers can post tasks, describing their
needs and budget, and freelancers can independently search
for and respond to orders they are interested in. Unlike some
other exchanges, where the invitation of freelancers by the
customer dominates, the emphasis here is on the initiative of
the performers, which allows them to choose projects based
on interest, skills and deadlines. The goal of the project is to
bring together specialists and customers on one platform,
promote effective and transparent interaction between
them, simplify job search for freelancers and solve problems
for clients.
Project Requirements and
Key Features

User Roles Key Features Technology Stack

Freelancers: create profiles, find orders, Secure transactions Backend/frontend: Python, HTML, CSS,
perform work, get paid JavaScript, django

Customers: publish tasks, select Rating system with reviews Database: noSQL
freelancers, pay for services

Administrator: platform control Offline order publishing Payments: Kaspi KZ, PayPal,
cryptocurrencies

Tech Support: dispute resolution and Smart skill-based search

assistance
 Why Agile? Advantages:
Agile SDLC Agile offers •High flexibility to changing requirements.
flexibility to adapt to •Faster delivery of functional components.
Model for changing
requirements, quick
•Continuous feedback and improvement.
Developm MVP releases, and Disadvantages:
continuous feedback •Requires active collaboration.
ent for improvement. •Difficult to predict final costs and timeline.
•Documentation may be less detailed.
 Identifying Potential Risks
Risk Category Description
Server Downtime Technical Risk Unexpected server failures may disrupt platform
availability, causing user dissatisfaction.

Cybersecurity Threats Security Risk The platform may be vulnerable to hacking, data
breaches, or phishing attacks.

Unclear Requirements Operational Risk Changing or unclear requirements from

stakeholders can delay development.

Missed Deadlines Schedule Risk Development tasks may take longer than
planned, delaying the launch.
Payment Processing Issues Technical Risk Integration with payment systems (Kaspi KZ,
PayPal) may fail, leading to payment delays.

Low User Adoption Operational Risk Freelancers and customers may not actively join
the platform, requiring better marketing.

Scams and Fraud Security Risk Fake freelancer or customer accounts may attempt
to scam users, harming platform trust.
Risk • High Priority Risks
• Cybersecurity Threats - High
•Medium Priority Risks
•Unclear Requirements -
Prioritizati likelihood & impact. Medium likelihood & impact.
•Payment Processing Issues -
• Server Downtime - Medium
on likelihood, high impact. Medium likelihood, high
impact.
• Low User Adoption - High
likelihood & impact.
• Missed Deadlines - High
likelihood, medium impact.
• Scams and Fraud - High
likelihood, medium impact.
Risk Mitigation Strategies

Server Downtime – Use Cybersecurity Threats – Unclear Requirements –

Missed Deadlines – Use
backup servers, store the Protect user data with Write clear plans, talk to
planning tools, set realistic
platform in the cloud, and strong passwords, use two- customers often, and work
goals, and work in short
check everything regularly step login, and check the in small steps to stay on
time blocks (sprints).
to keep it working. system for problems often. track.

Payment Processing Issues Low User Adoption – Scams and Fraud – Check
– Work with trusted Advertise the platform, give user identities, watch for
payment systems, test them users bonuses to try it, and strange actions, and let
well, and give users more make sure it’s easy and users report problems
than one way to pay. comfortable to use. easily.
 Actors and
Their Main Use
Cases
Sequence Diagram:
Freelancer
Responds to Order
• The sequence diagram shows
how a freelancer responds to a
job order. The freelancer sends a
response through the user
interface, which is forwarded to
the server. The server saves the
response in the database and
sends a confirmation back. The
process includes four
components: freelancer,
interface, server, and database.
This diagram helps understand
how data flows through the
system and supports future
development and testing.
UML-state machine
diagram: order
processing
• The status diagram shows the
order lifecycle on the freelance
platform. It starts with "Created"
after the customer posts the task,
then moves to "Contractor
Selected" when a freelancer is
chosen, and "In Progress" when
work begins. After the freelancer
completes the task, the order
becomes "Completed", and once
the customer confirms payment,
it reaches the final "Paid" state.
Each step reflects a stage in the
process triggered by user or
system actions.
Сomponent diagram
The component diagram shows the freelance platform’s
architecture, divided into three layers: client interface,
server (backend), and databases.
The Web Interface allows users to log in, manage
orders, make payments, and receive notifications.
The server includes four services:
• Auth Service – handles user registration and login
• Order Service – manages task flow
• Payment Service – processes transactions
• Notification Service – sends updates
• Each service connects to its own database. This
modular design makes the system scalable, easy to
maintain, and flexible for future updates.
UML-activity
• This UML activity diagram shows the full user
journey on the freelance platform. It starts
when a user opens the website and logs in or
registers. Based on the role, a freelancer
selects and works on an order, while a
customer creates a task and chooses a
freelancer. After the task is completed, the
customer reviews the result, makes payment,
and leaves feedback. The diagram outlines key
actions for both roles and helps visualize
system logic and user flow.
UML Class Diagram