book life.docx

GAME

BOOK LIFE

FOR ANDROID+IOS

SOFTWARE DESGIN SPECIFICATION

_____________________________________________________________________________________BOOK LIFEDOCUMENTATION REVISION 1.0 1 MUHAMMAD ZIA

TABLE OF CONTENTS

TABLE OF CONTENTS iiRevision History............................................................................................................................iiiApproved By.................................................................................................................................iii1. Introduction..............................................................................................................................1

1.1 Purpose.........................................................................................................................................11.2 System Overview..........................................................................................................................11.3 Design Map...................................................................................................................................11.4 Supporting Materials....................................................................................................................11.5 Definitions and Acronyms............................................................................................................1

2. Design Considerations.............................................................................................................12.1 Assumptions.................................................................................................................................12.2 Constraints....................................................................................................................................22.3 System Environment.....................................................................................................................22.4 Design Methodology....................................................................................................................22.5 Risks and Volatile Areas..............................................................................................................2

3. Architecture..............................................................................................................................23.1 Overview......................................................................................................................................23.2 Subsystem, Component, or Module 1 …N...................................................................................23.3 Strategy 1…N...............................................................................................................................3

4. High Level Design....................................................................................................................44.1 View / Model Element 1…N........................................................................................................4

5. Low Level Design.....................................................................................................................45.1 Module 1…N................................................................................................................................4

6. User Interface Design..............................................................................................................46.1 Application Controls.....................................................................................................................46.2 Screen 1… N................................................................................................................................4

Appendix A: Project Timeline......................................................................................................5

REVISION HISTORY

Version Name Reason For Changes Date

1.0 Muhammad Zia Initial Revision 22/03/2015

APPROVED BY

Approvals should be obtained for project manager, and all developers working on the project.

Name Signature Department Date

Moe Android Development 22/03/2015

Game Developer Android Development 22/03/2015

1. INTRODUCTION

1.1 PURPOSE

This document's purpose is to provide a high-level design framework around which to build our project Book Life. It also provides a list of requirements against which to test the final project and determine whether we were able to successfully implement the system according to design.

1.2 SYSTEM OVERVIEW

In Book Life, the player solves 2d puzzle and do some fight to get out the second level of game. As the game start player start jumping to get user attention, after clicking the player, user can see the pain level in user. This pain cause due to his girl friend lost somewhere. Player performs physiological achievements to decrease the user pain. But before doing this exercise, player performs the lovely emotion to impress his friend, which lead him to feel too much love about her.

1.3 DESIGN MAP

SUE - Summarize the information contained within this document or the family of design artifacts. Define all major design artifacts and/or major sections of this document and if appropriate, provide a brief summary of each. Discuss any significant relationships between design artifacts and other project artifacts


S/No MAJOR COMPONENT Functionality

01 LOADING PAGE First page is Loading screen having icon and description and copyright message.

02 MAIN PAGE Main Page contains different Activates like New game, Single player, Extras.

03 NEW GAME By clicking this new page open Game play screen

3.1 FREE MODE In free mode, user is bound to perform every stage in series.

But user can change any time free user into paid user.

3.2 PAID MODE Paid mode user can play any stage and is able to decrease pain for 30 seconds to perform task with speed and without emotion drama.

3.3 ARCADE MODE Also available is an Arcade mode in which players have only sixty seconds to achieve a high score. Special task appears to achieve the love lost goal.

4 MULTIPLAYER In multiplayer mode, couples play this game at same time to check his/her lover attention towards and set specific task to achieve.

4.1 CLASSIC PROBLEM Breakup,date,gifts

4.1.1 GAME SPEED In Game speed three modes are available Slow, Medium, Fast.

4.2 ZEN DUEL

4.2.1 GAME TIME Game Time also increased from 30, 60, 90, 120, 180 second.

1.4 DEFINITIONS AND ACRONYMS

Play Store: iOS and Android Applications Market, Unity 3D: Unity 3D is tool for development 3D android gameEclipse IDE: Integrated Development Environment (A programming Editor used for coding)Android SDK: The Android SDK provides the API libraries and developer tools necessary to build, test, and debug apps for Android.) ADT: Android Development Tools is a plug-in for the Eclipse IDE that is designed to give you a powerful, integrated environment in which to build Android applications.JDK: Java Development kit,

2. DESIGN CONSIDERATIONS

All design considerations were handled in Binder Release Phase 1.

2.1 ASSUMPTIONS

Metrics and Task View reports will be handled in the workflow reporting project.

2.2 CONSTRAINTS

None that we are aware of.

2.3 SYSTEM ENVIRONMENT

The Book life project is build using Unity 3D with Android SDK, ADT, JDK.The Book Life project will be available on Play Store. User can download it from there. Its first version is for Android (An Open Source Mobile Platform/Operating System) phones only.

2.4 DESIGN METHODOLOGY

The Design of this product utilizes an object Oriented Approach.

2.5 RISKS AND VOLATILE AREAS

None have been identified.


3. ARCHITECTURE

The software capabilities and requirements specified in the book life Requirements Specification are transformed into programs that will execute on an android Phone, Tabs. Software items are partitioned into classes and packages using Object Oriented methodology to maximize encapsulation and minimize interfaces. Packages are then built (compiled and linked) into executable programs.

3.1 OVERVIEW

Project is designed with extensibility and scalability in mind. We are taking great care in designing a framework which can be updated easily. Many of the anticipated changes to our system in future phases will only require adding new types of data and changing the user presentation code to make use of these new data.

5 USER INTERFACE DESIGN:5.1 SCREEN:

5.1.1 LOADING SCREEN:Here is the first loading screen when games are loading.

5.1.2 MAIN SCREEN:Here is the Main Page of Book life game

5.1.3 GAME MODE SCREEN:

After clicking new game the Game Mode screen appear. There is different type of game mode available in this page like Classic mode, Zen mode, and arcade mode.Opening sce ne


http://www.shutterstock.com/pic-191834291/stock-photo-open-book-with-hand-drawn-landscape-on-wooden-deck.html?src=pp-same_artist-190542464-1&ws=1

5.1.6 EXTRA:After clicking the option extra in main screen below screen appear. In this screen there are different option about page, rewards, follow up, become a fan on Facebook, more games.

5.1.4 ABOUT PAGE:

Here is about page.


book life.docx

Documents

level of game

user pain

new game

user attention

paid user

game speedin game speed

time free user

design methodology22