Design and Implementation of an Android Mobile Social Game (360 Last Man Stand)

TABLE OF CONTENTS

DECLARATION

APPROVAL

ACKNOWLEDGEMENT

ABSTRACT iv

LIST OF ABBREVIATIONS & ACRONYMS v

LIST OF FIGURES

LIST OF TABLES

LIST OF APPENDICES

Chapter 1 1

Introduction

1.1 Introduction 1

1.2 Background

1.3 Statement of the Problem 2

1 .4 Objectives 3

1.4.1 Main Objective 3

1 .4.2 Specific Objectives 3

1.5 Scope of the study 3

1.5.1 System scope 3

1.5.2 Geographical scope 3

1.6 Significance of the project 3

Chapter 2 5

Literature Review s

2.1 Introduction 5

2.2 Mobile Environments 5

- vi -

360 Last Man Stand Project Report

2.3 Mobile Platforms and Application Environments 6

2. 4 Market Shares 6

2.5 Mobile Gaming 7

2.5.1 Successfully Mobile Game Genres 7

2.6 The Future of Mobile Game Development 9

2. 7 Android 9

2.7.1 Advantages of Android 10

2.7,2 General Android architecture 10

2.8.2 Deployment of Android 11

2.8JavaME 12

2.8.1 General J2ME architecture 12

2.8.2 JME Deployment 13

2.8.3. Future of Java ME 14

2.9 comparison of the Development Environments 15

2.9.1 Comparing the final product 15

2.10 Summary 16

Chapter 3 17

Methodology 17

3.1 Introduction 17

3.1.1 Agile Methodology 17

3.1.2 Reasons for using Agile Methodology 18

3.2 Mobile Application Development Methodology V3 18

3.3 Mobile Application Development Methodology V3 phases 19

3.3.1 Requirements Analysis Techniques 19

3.3.2 Prototyping 20

3.3.3 Advantages of Prototyping’ 20

3.3.5 Weaknesses of the Prototype model 20

3.3.6 Storyboarding 20

-vii360

Last Man Stand Protect Report

3.3.7 Advantages of Storyboarding 21

3.3.8 Application Building 22

3.3.8.1 Support API’s 22

3.5 Conclusion 23

Chapter 4 24

System Requirements Analysis and Design 24

4.1 Functional requirements 24

4.2 Non-functional requirements 24

4.3 Hardware Requirements 24

4.4 Software requirements 24

4.5 Use Case for 360 Last Man Stand Game 25

4.6 Sequence Diagram 26

4.7 Class diagram 26

4.8 Data modeling 27

4.8.1 Entity Relationship Diagram 27

4.8.2 Database schema 28

4.9 Interface Design 28

4.10 Summary 29

Chapter 5 30

Results 30

5.1 360 Last Man Stand Project Results 30

Chapter 6 35

Recommendations and Conclusion 35

6.1 Project Overview 35

6.2 Project Accomplishments 35

- viii -

360 Last Man Stand Project Report

6.3 Limitations 35

6.4 Project Future Extensions 35

6.3.1 ‘360 Last Man Stand’ Player Accounts 35

6.3.2 User Interface Improvements 36

6.4 Conclusion 36

References

Appendices 40

Appendix A: Evidence of System Functionality 40

Appendix B: User (Player) Guide 42