Добавил:
Upload Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
Final_diplom.docx
Скачиваний:
0
Добавлен:
01.07.2025
Размер:
14 Мб
Скачать
☆

Figure 2.21 - Example of a use case diagram

3 THE SYSTEM DESIGNE AS A TECHNICAL OR MODEL EXPERIMENT

This section is the most important part of the graduation project. In this section will detailed described all of the classes, methods, variables, application, scripts and database. UML diagrams are drawn. And in this part written a “how to use instructions”.

3.1 Aim of experiment

The plan in my game (see figure 3.1, figure 3.2):

1) registration

2) Introduction

3) loading

4) information about history of Kazakhstan

5) scenario

6) the animated card

7) to begin level

8) to construct towers

9) to improve towers

10) to expose soldiers

11) to use additional force

12) to win against enemies

13) to stop the boss

14) to earn money

15) to move to the following level

16) to see achievements

17) to get points

18) to buy the hero

19) to improve the hero

20) to improve additional forces

21) to see credits

Figure 3.1 - Steps

Figure 3.2 - Class diagram

In my game, I used 12 classes: Boss.as, Bullet.as, C.as, Enemy.as, Placing.as, preloader.as, Tower_Fire.as etc.

Game at me begins with Nazarbayev's words (see figure 3.3):

"If not to consider Altyn Orda and of Turkic peoples, then the Kazakh khanate our direct roots", after game begins.

Figure 3.3 - Kazakh khanate

My project aim – is create game for people who want play game and learn Kazakh language and Kazakh history.

Some parts of my projects (see figure 3.4, figure 3.5, figure 3.6, figure 3.7, figure 3.8, figure 3.9, figure 3.10, figure 3.11, figure 3.12, figure 3.13, ):

Figure 3.4 – Hans

Figure 3.5 – Otrar

Figure 3.6 – Girl

Figure 3.7 – Tower1

Figure 3.8 – Tower2

Figure 3.9 – Tower3

Figure 3.10 – Boss

Figure 3.11 – Enemy

Figure 3.12 – Dragon

Figure 3.13 – Soldier

Thank you for reading my project. Have a great day!

3.2 Choice and explanation of the experiment methodology (see figure 3.14):

Figure 3.14 – Methodology

Development methodology

Planning

  • Storyboarding, Game Analysis, and Game Rules

  • User Experience

  • Game Level Design

  • Platform Identification

  • Identification of Game Type

  • Identify Technical Constraints and Implement Approach

  • Design

  • Art Assets and Graphics

  • Identify Color Scheme

  • Game Layout

  • Graphics and Animations

  • Image and File Formats

  • Audio and Sound Effects

  • Game framework

  • Prototypes

  • Use cases

  • Design Signoff

  • Programming

  • Game Programming

  • Level Implementation

  • Game Architecture Implementation

  • UI and UX integration

  • Unit Testing

  • Peer Code Reviews and Functional Reviews

  • Alpha, Beta, and Gold Release Cycles

  • Testing

  • Functional Testing

  • Game Play and Logic Testing

  • Rule Adherence Testing

  • Graphics Testing

  • Issue Reporting

  • QA Signoff and Final Release for UAT [23].

Flash game development has become increasingly popular over the years. Mostly in everybody’s life games play an important part. Gaming industry is continuously being boosted with the rapid and the latest innovations in Flash Game Development technology. The latest trend in the gaming industry is that of the games based on flash due to their exceptional graphics, animations, highly interactive and user friendly interface which virtually creates a real-time environment.

Our flash game developers constantly look for coming up with fresh and new concepts for flash game design. The developers are well versed with the blend of high end skill sets and enthusiasm of innovative creation with constant hard work.

Our Flash Game development Methodology

  • Analyze your gaming requirements

  • Create an effective game story and plot

  • Create game characters and icons

  • Design right game environment

  • Add suitable graphics and animations and carry out logical implementation in the game

  • Create different gaming levels

  • Bug fixing and trial run

  • Final deployment

Our expert developers can develop games accompanying all types of categories for Flash such as:

  • Action and thrilling games

  • Adventure games

  • Entertainment games

  • Sports and racing games

  • Puzzle and arcade games

  • Multiplayer games

  • 2D and 3D games

Why Dotsquares?

  • Eye-catching flash banners

  • Robust, scalable, reliable and innovative games with on time project delivery.

  • Cost effective Flash based game development

  • Attractive landing pages

  • Powerful and attractive games that keep the audience engrossed.

  • Customized high-end gaming solutions [24].

3.3 Experiment findings

Architecture of application

In figure 3.15, the diagram of the use case drawn. Where USER - the user can interact with the application. It can send contacts in the application, the request contacts, update your contacts. SERVER - plays its role as a store contacts, gives an account name in the application, if required. The Application - acts as a buffer between the user and the server. The interaction with the user is prompted to store and edit contacts.

Figure 3.15 - The use case diagram

In figure 3.16 the sequence diagram is drawn. Here you can see the sequence of actions as the action happens.

1: User presses registration button

2: Application asks for login and password

3: User gives that information

4: Application approves user information

5: If the USER identification is valid THEN application displays a welcome message to User

6: User presses send contacts button

7: Application gets contacts and sends to server

Figure 3.16 - The sequence diagram.

In figure 3.17 is drawn database. The database contains two tables: Users and Contact. Table Users is designed to store information about the user. Table Users contains columns id, login and password. Column id’s type is “int (255) serial” Primary key. When you add user to database id is automatically increased by one unit. Column login’s type is “varchar (50).” Longest password can be 50 characters. Column password’s type is «varchar (50)." Longest login can have 50 characters.

Table Contacts is designed to store telephone contact person. Table Contacts contains columns id, name, surname, userId, number. Column id’s type is “int (255) serial” Primary key. When you add one contact id is automatically increased by one unit. Type of name column is «varchar (50)." The longest name of a contact can have 50 characters. Type of column surname is «varchar (50)." The longest name can have 50 characters. Type of column userId is «int (255) serial» Foreign key. Used to know who owns this contact. Type of column number is «varchar (50)." This column is used to store phone number.

Соседние файлы в предмете [НЕСОРТИРОВАННОЕ]