Tamagotchi Project Statement

Jonathan Chiu, Yancy Hu, Vamshi Chilukamari





Project Statement

Overview

The purpose of this project is to create a virtual pet application for the Android client. The virtual pet game we are creating will be related to the Tamagotchi digital pet device that was originally released in the late 90s. After receiving much fame, newer generations of the device were created and marketed, packed with new features while still retaining the original concepts.

Customers

Our target customers are casual gamers with Android phones. Recently, the definition of a “casual gamer” has become a very broad term, especially with the introduction of Facebook games, most notably Farmville. As such, our target customer base can apply to all people who own an Android.

Goals

The primary objective of this project is to recreate a true replica of the classic Tamagotchi game device on the Android, with upgrades and features in order to benefit from the Android’s additional capabilities.

System Functions

Evident

The Tamagotchi Application should be able to take advantage of the Android’s GPS system in order to determine the current weather in the user’s location, and project that weather into the game’s environment.

The users will also be able to hold online battles with other users. Their battle levels will determine the chances of a user winning. There will also be a database that will hold all the statistics of the Tamagotch, including but not limited to, number of battles fought, number of victories, and age.

There will be an incorporated inventory system, with items that can be used to take care of a Tamagotchi, items like food and medicine. Additional items will be put in-game.

Hidden

None as of now

Frills

An Achievement System will inform the user of accomplishments made throughout the game (i.e played 10 battles, Tamagotchi survived 25 days, etc.). An additional notification system will notify the user through some media (pop-ups, email, etc.) on updates on their Tamagotchi (when its hungry, sick, etc.).

There will be minigames based around the Tamagotchi that the user can play and earn achievements.

System Attributes

Details/Constraints

During normal usage, the Tamagotchi pet will randomly walk around the map. Hunger levels will increase as the Tamagotchi remains active. It will also randomly poop on the screen.

We hope to achieve widespread usage of this application, so it will not be system intensive. All Android clients should be able to run this application.

High Priority

Inventory system, Items, Movement, Battle System, Mini games

Low Priority

Voice commands

Use Cases

Use Case ID	Use Case Name	Primary Actor	Scope	Complexity	Priority
0	Open appplication	User	In	Med	1
1	Feed Tamagotchi	User	In	Med	1
2	View backpack contents	User	In	High	1
3	Give Medicine	User	In	Med	1
4	Discard poop	User	In	Med	1
5	Initiate Battle	User	In	High	1
6	Battle (???)	User	In	High	1
7	View Item Description	User	In	Low	1
8	Prepare Tamagotchi for weather	User	In	High	1
9	Buy item from store	User	In	High	3
10	Play minigame	User	In	High	2
11	Use voice command	User	Possibly In	Med	4

Use Case Number	0
Application	Main Application
Use Case Name	Open application
Use Case Description	User opens application to begin playing
Primary Actor	User
Precondition	None
Trigger	None
Basic Flow	User opens application An egg appears on the screen where a new Tamagotchi will hatch from Tamagotchi is born User can now interact with Tamagotchi
Alternate Flows	User has already created a Tamagotchi previously Existing Tamagotchi is loaded User can interact with Tamagotchi

Use Case Number	1
Application	Main Application
Use Case Name	Feed Tamagotchi
Use Case Description	The user feeds the Tamagotchi some food.
Primary Actor	User
Precondition	User has food in his backpack.
Trigger	The Tamagotchi complains that it is hungry.
Basic Flow	User taps and drags food item from backpack User drops food item on Tamagotchi A confirmation dialog appears to confirm using item Tamagotchi smiles (or does some animation) to show that it received the item Hunger level is adjusted according to the item specifications
Alternate Flows	Item from opened backpack User opens full backpack User taps and drags food item Backpack minimizes User drops food item on Tamagotchi and Basic Flow occurs User drops food somewhere not on Tamagotchi User taps and drags food item Drops the item somewhere other than Tamagotchi The item returns to the backpack and nothing occurs Tamagotchi is full Tamagotchi refuses to eat food Item returns to backpack

Use Case Number	2
Application	Main Application
Use Case Name	View Backpack Contents
Use Case Description	User can open inventory and view all items in their possession.
Primary Actor	User
Precondition	None
Trigger	User pushes on a button on the screen
Basic Flow	User chooses to open the backpack in the application Application then displays all contents of the backpack Backpack can then be closed.
Alternate Flows	User chooses to open the backpack in the application Application fails to open backpack

Use Case Number	3
Application	Main Application
Use Case Name	Give Medicine
Use Case Description	User gives the Tamagotchi medicine to treat its illness.
Primary Actor	User
Precondition	There is Medicine in the backpack.
Trigger	The Tamagotchi alerts you that it is sick (either through text or a sick icon of some sort)
Basic Flow	User taps and drags medicine from backpack User drops medicine item on Tamagotchi A confirmation dialog appears to confirm using item Tamagotchi smiles (or does some animation) to show that it received the item Sickness level is adjusted according to the item specifications
Alternate Flows	Item from opened backpack User opens full backpack User taps and drags item Backpack minimizes User drops item on Tamagotchi and Basic Flow occurs User drops item somewhere not on Tamagotchi User taps and drags item Drops the item somewhere other than Tamagotchi The item returns to the backpack and nothing occurs Tamagotchi is not sick Tamagotchi refuses to take medicine Item returns to backpack

Use Case Number	4
Application	Main Application
Use Case Name	Discard Poop
Use Case Description	User clicks and drags poop on screen into a trash bin, also on screen.
Primary Actor	User
Precondition	There must be poop on the ground
Trigger	When the user clicks and drags the poop
Basic Flow	User clicks and drags poop into trash bin Poop object is then deleted.
Alternate Flows	User clicks and drags poop onto another part of the ground Poop object will then be moved to that location.

Use Case Number	5
Application	Main Application
Use Case Name	Initiate Battle
Use Case Description	The user connects to another user to battle their Tamagotchis.
Primary Actor	User (initiating battle)
Precondition	Initiating user and opponent must be on the same WiFi network. Both users are running the same version of the game. Both users must have living Tamagotchis.
Trigger	Initiate battle button is pressed
Basic Flow	Initiating user selects Battle Mode from menu Initiating user selects that they are acting as the server A dialog box appears displaying the initiating user’s IP address, which will be the server IP. The opponent selects Battle Mode from menu The opponent selects that they are acting as the client A dialog box appears asking the opponent for the server IP. The opponent enters the server IP and presses Enter Both players are now connected. A message will appear on each player’s screen acknowledging that they are connected and ready to battle.
Alternate Flows	Both players select server Nothing happens since no one connects to the other player. Both players select client Nothing happens since no one is acting as the server. Players are not on the same WiFi network Nothing happens. Players are running different game versions Players connect normally A dialog is displayed alerting that they are running different game versions. They are given the option to proceed anyway or quit. One player does not have a Tamagotchi Players without Tamagotchis should not be able to access the Battle option

Use Case Number	6
Application	Main Application
Use Case Name	Battle
Use Case Description	User starts battle
Primary Actor	User
Precondition	Use Case Initiate Battle must complete with both users agreeing to battle
Trigger	Use Case Initiate Battle
Basic Flow	Users will be prompted with message “Deathmatch?” If both users agree, the Tamagotchi that loses all health first will die. Tamagotchis will take turns attacking each other Battle Level will determine how much damage a Tamagotchi’s attack does. Health will decrease as both Tamagotchis take hits. Battle is over once one Tamagotchi has lost all health. Tamagotchi that loses will die. The winner gains experience towards their Battle Level.
Alternate Flows	If one or more users disagree to Deathmatch, battle will carry on normally in Basic flow, but the Tamagotchi that loses will not die. Experience gained from win will be halved. A user disconnects User disconnects Battle ends immediately

Use Case Number	7
Application	Main Application
Use Case Name	View Item Description
Use Case Description	User sees a description of an item when they tap on it.
Primary Actor	User
Precondition	An item exists in the backpack Backpack must be open
Trigger	Tapping an item in the backpack
Basic Flow	User taps (but does not drag) on item in the backpack A small panel appears at the bottom of the screen with a description of the item User can either tap somewhere else on the screen or tap the close button to close the panel.
Alternate Flows	None

Use Case Number	8
Application	Main Application
Use Case Name	Prepare Tamagotchi for Weather
Use Case Description	Because of the different weather situations as a result of GPS-based weather, the Tamagotchi needs to be prepared or it will become sick.
Primary Actor	User
Precondition	A weather situation has occurred where the Tamagotchi needs to be prepared in order to prevent illness.
Trigger	Either the weather has changed or the Tamagotchi notifies the user that it is scared (which will mean that something needs to be done)
Basic Flow	The user drags the appropriate item from the backpack onto the Tamagotchi in order to prepare it for the weather, which could be things like a blanket, umbrella, or coat.
Alternate Flows	Weather does not call for preparation Tamagotchi can be equipped with items even if weather does not call for it.

Use Case Number	9
Application	Main Application
Use Case Name	Buy item from store
Use Case Description	There is an item shop in the game where users can purchase various things.
Primary Actor	User
Precondition	None
Trigger	User presses the Enter Store button
Basic Flow	The user selects the item they wish to purchase. A description of the item appears and its cost The user buys the item Item is added to the backpack
Alternate Flows	User does not have enough money The user is alerted that they do not have enough money to purchase the item. User not allowed to purchase the item Backpack is full User is alerted that their backpack is full User not allowed to purchase the item

Use Case Number	10
Application	Main Application
Use Case Name	Play minigame
Use Case Description	The user wishes to play a minigame to earn money and/or achievements
Primary Actor	User
Precondition	None
Trigger	User selects minigame from menu
Basic Flow	The user selects a minigame to play User enters minigame If user wins, the user earns money and/or achievements Money is saved User is prompted to play again or return to the menu
Alternate Flows	User quits in the middle of game User loses minigame state, but Tamagotchi state is still saved.

Use Case Number	11
Application	Main Application
Use Case Name	Voice Command
Use Case Description	The user wants to talk to the Tamagotchi
Primary Actor	User
Precondition	None
Trigger	User presses the microphone icon
Basic Flow	User presses the microphone icon User says a voice command Tamagotchi reacts accordingly
Alternate Flows	User says an unrecognized command Tamagotchi does not respond or looks confused

Plan & Schedule

3/2	Application design finished. (Design of main game, GPS weather, mini games, database synchronization, etc)
3/9	Basic implementation of game completed and testing done. Work started on synchronizing pet stats with online database
3/16	Spring recess - Testing, bug fixes
3/23	GPS weather system finished Database created and able to sync Begin work on battle system
3/30	Demonstration I Presentation II Report I Due Working Android application that can demonstrate GPS weather system and database syncing.
4/6	Being implementation of mini games, further testing on main program Battle system working
4/13	Demonstration II Presentation III Report II Due Demonstrate battle system and anything we have done on the mini games
4/20	At least 2 mini games completed and integrated into the main game Battle system finished Start work on items and online store Possibly add voice recognition
5/4	Final Project Presentations and Demonstrations Final Report Due Individual Report Due

Deliverables

3/30 - Working Android application that can demonstrate GPS weather system and database backups. (Use cases 1-4 completed)

4/13 - Working battle system and a working mini game. (Use cases 5, 6, and 8 completed, possibly UC-10)

5/4 - Item store finished and at least 2 mini games added. (Use cases 9 and 10 version 2 completed)

Glossary

Tamagotchi - A virtual pet device first released in the late 1990s.

Facebook - A social networking service and website launched in February 2004

Farmville - a farming simulation social network game developed by Zynga in 2009

Website

http://tamacapstone.blogspot.com/

Friday, May 4, 2012

Thursday, May 3, 2012

Thursday, April 26, 2012

Thursday, April 12, 2012

Friday, April 6, 2012

Friday, March 30, 2012

Monday, March 26, 2012

Monday, March 12, 2012

Monday, March 5, 2012

Friday, March 2, 2012

Thursday, March 1, 2012