Developing shooting multiplayer game with use of 3D engine

This document discusses the development of a shooting multiplayer game using a 3D engine. It covers the description of the application, tiers of the system, overall structure of implementation, class diagram, activity diagram, sequence diagram, use-case diagram, user interface design, system robustness, fault tolerance, minimal recovery time, scalability, and security.

Running head: SYSTEM ARCHITECTURE
MN611 – T2 2019 System Architecture
Name of Student-
Name of University-
Author’s Note-

1SYSTEM ARCHITECTURE
Table of Contents
Title..................................................................................................................................................1
Section 1..........................................................................................................................................1
1.1 Description of the application...............................................................................................1
1.2 Tiers of system.......................................................................................................................1
1.3 Overall structure of Implementation.....................................................................................2
Section 2..........................................................................................................................................2
2.1 Class Diagram.........................................................................................................................2
2.2 Activity Diagram.....................................................................................................................3
2.3 Sequence Diagram.................................................................................................................4
2.4 Use-Case Diagram..................................................................................................................5
2.5 User Interface Design............................................................................................................6
Section 3..........................................................................................................................................6
3.1 System robustness.................................................................................................................6
3.2 Fault Tolerant.........................................................................................................................6
3.3 Minimal Recovery Time.........................................................................................................6
3.4 Scalable..................................................................................................................................7
3.5 Security..................................................................................................................................7
Bibliography.....................................................................................................................................8

2SYSTEM ARCHITECTURE
Title: Developing shooting multiplayer game with use of 3D engine.
Section 1
1.1 Description of the application
The game that is analyzed is REA (Rescue Earth from Aliens). This game has been developed with
modern technologies including Unity 3D. The characters in REA is developed using Blender 3D. There are
many levels in this game. All the levels includes some particular strategy so that the player can fight with
the aliens. The first level of the game is easy and its level of difficulty increases with the increase in level.
There are several aliens in each of the levels and the players should some tactics so that they can
compete with the aliens and win the level. There are medals and coins provided to the players when
they wins each level and they can buy different commodities with the coins they are gaining.
1.2 Tiers of system
There are four tiers in the game application. This includes documentation layer, programming
layer and implementation layer and database layer. As this a multiplayer game, the player will have the
accessibility to choose their partners of players from their friend circle and will be able to invite their
friends to play the game.
Figure 1: Three Tier Architecture
(Source: Created by Author)

3SYSTEM ARCHITECTURE
1.3 Overall structure of Implementation
In the game development, the initial phase of development included studying the
documentation that is being developed for developing the game. The implementation of the application
is mostly done by agile methodology. The agile methodology helps to develop the game with iteration
process. This methodology also enhances coding practice of the team. Different components of the
software were assigned to different individuals as per their interest. With the agile methodology, weekly
meetings are also organized to discuss the progress of the work. In the implementation process, pair
programming was also included so that the project modules can be achieved in cohesive manner and for
ensuring that all the team member can understand the process of system development. After outlining
the team dynamics, developing of the single player was started and sequentially the double player and
squad player was developed.
Section 2
2.1 Class Diagram
Figure 2: Class Diagram
(Source: Created by Author)

4SYSTEM ARCHITECTURE
2.2 Activity Diagram
Figure 3: Activity Diagram
(Source: Created by Author)

5SYSTEM ARCHITECTURE
2.3 Sequence Diagram
Figure 4: Sequence Diagram
(Source: Created by Author)

6SYSTEM ARCHITECTURE
2.4 Use-Case Diagram
Figure 5: Use Case Diagram
(Source: Created by Author)

7SYSTEM ARCHITECTURE
2.5 User Interface Design
Figure 6: User Interface Diagram
(Source: Created by Author)
Section 3
3.1 System robustness
Robustness states the ability of the system to cope with all errors that comes during execution
and has the capability with the erroneous input. The gaming system of REA is robust because it includes
robust programming that mainly focuses on the system handling unexpected actions as well as
unexpected terminations. The system supports code for handling the termination and displays the error
messages.
3.2 Fault Tolerant
Fault tolerance includes property to continue its operating in event of failure of some of the
components. This property helps to system to do intended operation when some of the parts of the
system fails to work. The gaming system of REA does not support fault tolerance because if part of some
part of the system is not working, it will lead to stop the working of the whole system.
3.3 Minimal Recovery Time
Recovery time of a software or system includes some set of policies, procedures as well as tools
so that the recovery of the system can be done. The system supports minimal recovery process when it
is needed. The system developed has the ability to recover itself faster after failure. The recovery
function disrupts normal operations and results in loss of revenue as disaster result.

8SYSTEM ARCHITECTURE
3.4 Scalable
The gaming system that is being built includes good programing structure which indicates that
the system is scalable. The programs included are easily understandable and programs can be expanded
for supporting the new roles. This system also provides provision for many users as well as includes
concurrent access of database and editing of database. The security of the game application is also high
for all users associated with the system and includes database integrity.
3.5 Security
System security in system development includes securing the resources of the system to save
the sensitive data. There should be proper protection of the data in the system as because it includes
data of users and different system related data. The system of REA is secured as because the data in the
system are secured from the any type of attack in the system. The system is capable to deal with any
type of system security.

9SYSTEM ARCHITECTURE
Bibliography
[1] P.A. Laplante. Requirements engineering for software and systems. Auerbach Publications, 2017.
[2] F. Khan, S.R. Jan, M. Tahir, S. Khan, and F. Ullah, Survey: dealing non-functional requirements at
architecture level. VFAST Transactions on Software Engineering, 9(2), 2016, pp.7-13 .
[3] S. Al-Fedaghi, Context-aware software systems: toward a diagrammatic modeling
foundation. Journal of Theoretical and Applied Information Technology, 95(4), 2017, p.936.
[4] J. Eckhardt, A. Vogelsang, and D.M. Fernández, May. Are" non-functional" requirements really non-
functional? an investigation of non-functional requirements in practice. In 2016 IEEE/ACM 38th
International Conference on Software Engineering (ICSE), 2016, (pp. 832-842). IEEE.
[5] M.J. Decker, K. Swartz, M.L. Collard, and J.I. Maletic,. A tool for efficiently reverse engineering
accurate UML class diagrams. In 2016 IEEE International Conference on Software Maintenance and
Evolution (ICSME) 2016, October, (pp. 607-609). IEEE.