Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
OUYA Game Development by Example

You're reading from   OUYA Game Development by Example An all-inclusive, fun guide to making professional 3D games for the OUYA console

Arrow left icon
Product type Paperback
Published in May 2014
Publisher
ISBN-13 9781849697224
Length 268 pages
Edition Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
John Donovan John Donovan
Author Profile Icon John Donovan
John Donovan
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

OUYA Game Development by Example Beginner's Guide
Credits
About the Author
Acknowledgments
About the Reviewers
www.PacktPub.com
Preface
1. Experiencing the OUYA FREE CHAPTER 2. Installing Unity and the OUYA ODK 3. Diving into Development 4. Moving Your Player with Controller Input 5. Enhancing Your Game with Touch Dynamics 6. Saving Data to Create Longer Games 7. Expanding Your Gameplay with In-app Purchases 8. Polishing and Prepping Your Game for Deployment 9. Blazing Your Own Development Trail Pop Quiz Answers Index

Popular game development methodologies


Planning and organizing your project can be as much of an art as actually developing it. In this section, you'll learn a few different methodologies that you can follow to ensure that your game follows a logical development pattern suited for you or your team.

The Waterfall model

One of the most popular and oldest development patterns is the Waterfall model, dating back to 1970. The Waterfall model takes its name from its cascading stages of development, with each stage flowing into the next until the final stage is reached. These stages are outlined in a basic Waterfall model as follows:

The Waterfall model has been lauded and criticized alike for its idealistic nature. Some developers argue that it's irresponsible to begin the next stage of a project before finishing the current one because a lot of early planning can be more advantageous than on-the-fly development. Others believe that every stage of a project is interconnected, and that they should...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image