Scribd
Upload
9 views9 pages

Week-6 DOC 318

The document outlines an experiment conducted by a team at SRM IST focused on designing a system architecture, use case, and data flow diagram for a TRADES application. It details the components of the system architecture, the interactions in the use case involving single and multi-player modes, and the data flow between users, clients, servers, and databases. The experiment was completed successfully, as indicated by the results section.

Uploaded by

s.pream2003
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
9 views9 pages

Week-6 DOC 318

The document outlines an experiment conducted by a team at SRM IST focused on designing a system architecture, use case, and data flow diagram for a TRADES application. It details the components of the system architecture, the interactions in the use case involving single and multi-player modes, and the data flow between users, clients, servers, and databases. The experiment was completed successfully, as indicated by the results section.

Uploaded by

s.pream2003
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

School of Computing

SRM IST, Kattankulathur – 603 203

Course Code: 18CSC206J

Course Name: Software Engineering and Project Management

Experiment No 6

Title of Experiment Design a System Architecture, Use Case and Data flow Diagram

Name of the candidate S.PREAM KOUSHIK

Team Members P.C NARENDRA , D.AKSHAY , M.NITHIN , S.PREAM

KOUSHIK

Register Number RA2111026010318

Date of Experiment 06/03/2023

Mark Split Up

S.No Description Maximum Mark Mark Obtained

1 Exercise 5

2 Viva 5

Total 10
Staff Signature with date

Aim
To Design a System Architecture, Use case and Class Diagram

Team Members:
Sl No Register No Name Role

1 RA2111026010318 S . PREAM KOUSHIK Member

2 RA2111026010319 D . AKSHAY Member

3 RA2111026010329 M . NITHIN REP

4 RA2111026010326 P . C NARENDRA Member


System Architecture
Explaination:

● User Interface (UI): This component provides the graphical user interface to the
users. It communicates with the API gateway to send and receive data.
● API Gateway: The API Gateway is the entry point for all requests made to the
application. It is responsible for authenticating requests, routing them to the
appropriate microservices, and managing the rate of requests.
● Authentication: This component handles user authentication and authorization. It
verifies user credentials, issues access tokens, and maintains user session state.
● User Management: This component manages user accounts, including registration,
profile management, and social networking features. It communicates with the
database to store user data and with the cache to retrieve frequently accessed data.
● TRADES Management: This component manages TRADES-related functionality,
including TRADES lobbies, matchmaking, and scoring. It communicates with
TRADES servers to start and manage TRADES sessions.
● Communication: This component manages communication between different
components of the application. It uses message queues, REST APIs, WebSockets, and
other communication protocols.
● TRADES Server: These components manage TRADES sessions, including
TRADES rules, scoring, and TRADES-state management. They communicate with
the database to store TRADES data and with the cache to retrieve frequently accessed
data.
● Matchmaking: This component is responsible for matching players with appropriate
opponents
USE CASE DIAGRAM

Explaination:

In this particular use case, there are three actors involved:

User: This actor refers to a person who plays the TRADES alone. They interact with the
TRADES application to achieve their gaming goals.

TRADES storage: This actor refers to a storage system that is responsible for storing the
TRADES data, such as the TRADES state, player progress, and other relevant information.
The use case involves the interaction between these three actors to achieve specific goals. A
use case scenario is as follows:

● The single player user launches the TRADES application and selects the single player
mode.
● The TRADES application retrieves the TRADES data from the TRADES storage
system and presents it to the single player user.
● The single player user plays the TRADES and progresses through the levels.
● The TRADES application updates the TRADES data in the TRADES storage system
to reflect the progress made by the single player user.
● The multi player user launches the TRADES application and selects the multi player
mode.
● The TRADES application retrieves the TRADES data from the TRADES storage
system and presents it to the multi player user.
● The multi player user connects with other players and together, they play the
TRADES.
● The TRADES application updates the TRADES data in the TRADES storage system
to reflect the progress made by the multi player user and the other players.
● The TRADES storage system stores the updated TRADES data for future use.
DATA FLOW DIAGRAM

Explaination
● User: Interacts with the TRADES client to play TRADES and access TRADES
features.
● TRADES Client: Sends user actions and receives TRADES updates from the
TRADES server.
● TRADES Server: Receives user actions from the TRADES client, updates the
TRADES state in the database, sends TRADES updates to the TRADES client, and
communicates with the payment gateway and email service as needed.
● Web Server: Serves static assets (HTML, CSS, JavaScript) for the TRADES client
and handles API requests from the TRADES server.
● CDN: Delivers TRADES assets (images, audio, video) to the TRADES client from a
geographically distributed network of servers to improve load times and reduce
latency.
● Database: Stores persistent data such as user profiles, TRADES records, and
TRADES state.
● TRADES Statistics: Collects and analyzes TRADES data to generate TRADES
statistics and insights.

Result:
Thus, the system architecture, use case and class diagram created successfully.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy