IntroTo game Architecture

IntroTo game Architecture - IntrotoGameArchitecture Jeff...

Info iconThis preview shows pages 1–11. Sign up to view the full content.

View Full Document Right Arrow Icon
    Intro to Game Architecture Jeff Ward Associate Programmer Bethesda Game Studios
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
My Talk Your first engine Why architect? Principles of OOP Design Patterns Best Practices
Background image of page 2
Your Talk How can architecture help us with: Concurrency Maintainability Code ownership Usability Performance Stability
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
    Disclaimer Sorry.
Background image of page 4
AI Your First Engine psst… this isn’t real UML… Renderer 3DObj 2DObj Player Creature Sound 3dSnd Input Items Bullets File Loader
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Why is that bad? Bad architecture creates problems Produces side effects Hard to follow Hard to debug Hard to reuse Spend more time finding a way around the architecture than fixing the problem OMG HAX!
Background image of page 6
Why Architect (Design)? Stability Reusability Cohesion Orthogonally
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
    A well architected system is  easy to understand, change,  debug, and reuse.
Background image of page 8
Principles of OOP Basics Encapsulation Inheritance Polymorphism Principles of good design Reduced coupling Increased reliability Increased reusability $10 word - orthogonality
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
“Encapsulation is a programming mechanism that binds together code and the data it manipulates, and that keeps both safe from outside interference and misuse.” – Schildt Encapsulation is not just data hiding!
Background image of page 10
Image of page 11
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 01/27/2012 for the course IT 101 taught by Professor Php during the Summer '11 term at University of Mumbai.

Page1 / 29

IntroTo game Architecture - IntrotoGameArchitecture Jeff...

This preview shows document pages 1 - 11. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online