CSE 3902 Project: Design, Development, and
Documentation of Interactive Systems

 

 

 

 

 

This is moved to: http://web.cse.ohio-state.edu/~boggus/3902/index.html

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

This is a Junior-level (or advanced Sophomore) course on Professional Software Development. You will learn through hands-on activities, large team-based software development and processes. Our goals are to build a simple 2D platformer game. Not! Our goals are to craft high-quality software, understand the process of Agile software development, become familiar with advanced tools for software development, testing plans and tools, and how to work in a small sized team (4-5 people). There will be a large amount of critiquing of code and interactive feedback. This will lead to refinement and improvement of your software (for future expansion and maintenance).

Grader: James Balata (balata.4 -at- osu.edu)

Grading Policy: Grading plan

Sprints

• Sprint 1 - Requirements Gathering and Planning with TFS
• Sprint 2 - Mario States and controllers
• Sprint 3 - Mario transistions, collissions and World 1-1 level.
• Sprint 4 - Kinect controller and World 1-1 level.
• Sprint 5

Google Calendar for sprint planning sessions and feedback. Please pick a team when the instructors and grader can meet with your group. At the beginning of your weekly meetings would be good.

Google Calendar

Notes for class:

Official Syllabus

Reading Resources

C# and .NET

Super Mario

XNA

Sprites

ALM

Team Rubrics (Word) (Pdf)

Final Exam: Friday, April 26 from 4:00-5:45pm (in the same classroom).

Autumn 2012 Schedule

Groups

Super Coding Bros.

• Brandon Patridge: patridge.8@osu.edu  
  
• Duy Bui: bui.55@osu.edu
  
• Kevin Gannon: gannon.85@osu.edu
• Matthew Demarest: demarest.7@osu.edu

Bullet Bills

• Hector Medina-Fetterman (.1)
• Jesse Tenorio (.4)
• Chase Plante (.8)
• Kyle Donavan (.156)
• Mitch Cooley (.198)

BroGamers

• Kyle Hanneman (.21)
• David Hazlett (.206)
• Emilio Cantu (.20)
• Maya Sugembong (.1)

CodeFuNinjas

• Zack Hall hall.1502@osu.edu
• Chris Sedar sedar.2@osu.edu
• John Schroeder (Trey) schroeder.556@osu.edu
• Aaron Benson benson.307@osu.edu

Team Terabyte

• Michael Steen: steen.25@osu.edu
• Abby Hahn: hahn.151@osu.edu
• Chris Hartman: hartman.362@osu.edu
• Eric Mathews: mathews.211@osu.edu

Team Name

• Andersen Jang (.145)
• Wesley Stover (.180)
• Neal Hanigan (.6)
• Ahmad Farag (.4)

Sonic The Hedgehog

• Chris Deliz(.7)
• Stephen Erickson(.123)
• William Nash(.172)
• Derek Visner(.2)
• Matthew Radosavljevic (.1)

Running Schedule Winter 2013

1. Lecture 1 (M): Overview of class
2. Lecture 2 (W): Demo of Visual Studio / C# language / arrays
• Reading Assignment: First 5 chapters of C# in a Nutshell.
3. Lecture 3 (F): Presentation on C# Classes and interfaces (powerpoint)
• Homework #1 assigned
4. Lecture 4 (M): Group Formations
   • Sprites and colors
   • Group meeting time
   • Reading Assignment: Read Chapters 1 and 2 of Solid Code
5. Lecture 5 (W): Presentation on Classes and Inheritance (powerpoint)
   • Homework #1 discussion
   • TFS Cloud services (https://tfs.visualstudio.com/) and set-up.
   • Assignment for Friday: Watch TFS video on Backlog items
6. Lecture 5 (F): Use Case and Requirements Gathering
• Sprint1 assigned
• Requirements gathering and Use Cases
• Non-functional requirements
• The problem with requirements / people:
• Readings:
  • Blog on being organized like a Chef.
  • Wikipedia on Use Cases
7. Lecture 6 (W):
   • Sprint 1 due / discussion.
   • Review of Work Items, TFS, tasks.
   • Stand-up Meetings
   • Schedule weekly group meetings
8. Lecture 7 (F):
   • Sprint 1 redo due
   • Sprint 2 assigned
   • Mario states
   • Block states
9. Lecture 8 (M):
   • Sprint 2 check-in
   • Discussion of Design Patterns for Sprint 2
   • Create Code and checking it into TFS
10. lecture 9 (W):
    • Code quality, please read before class:
      • All Software Sucks, but I care.
      • Constructive Criticism
      • Software Craftmanship + first few responses
    • Comments and readability
11. Lecture 10 (F): Quality Software Foundations
• How not to program: http://www.dreamincode.net/forums/topic/194878-xna-animated-sprite/
  • Note, this code is not bad by current practices. There is much worse code.
• Cohesion and Coupling
• Dependency graph example (originally from here)
  • Discussion: Good, bad highly coupled, low coupling?
• Code Metrics - Note, the link is to Software metrics which includes management, testing, estimations, etc.
  • #Lines of Code
  • Cyclomatic complexity
• Random Blog -Arrays considered harmful
12. Lecture 11 (M): Code Metrics continued
• Dependency graph example (originally from here)
  • Discussion: Good, bad highly coupled, low coupling?
• Sample Code metrics reports
  • NDepend
• Tools for static code analysis.
  • Code Analysis in Visual Studio
    • Code Clone
    • Code Metrics
  • StyleCop
  • FxCop
  • NDepend
  • Resharper
  • Source Monitor
• Read The first 5 chapters of Refactoring by Martin Fowler
• Random Blog - Developer Achievements (coming soon to VS 2012?)
• Some random blog and the lack of intelligent thought when commenting on it.
13. Lecture 12 (W): Code Smells and Refactoring
    • Code Smells
    • Nice Synopsis and break-down
    • Taxonomy of Code Smells
    • Read CodeProject article
    • (not-so) Random Blog
    • Best practices for naming conventions
14. Lecture 13 (F): State Design Pattern for Mario
    • Sprint3 assigned
    • Blog on SOLID
15. Lecture 14 (M): Collision Detection
• Bounding boxes
• Collision detection algorithms.
16. Lecture 15 (W): Collision Detection
    • Software structure
    • Collision response
17. Lecture 16 (F): Finite-State Tables and Debugging in VS 2012
    • Finite-State Tables
      • Wikipedia
      • Tutorial and obscure C++ code
      • Mario States
      • Heirarchical?
    • Breakpoints and Conditional Breakpoints
    • Watch window, Local Window
    • Call Stack and Threads
    • Immediate Window
    • Looking at memory
    • IntelliTrace in VS 2012 Ultimate
    • Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.
      • Brian Kernighan

    • 

      "LISTEN, KID, HOW MANY TIMES DO I HAVE TO EXPLAIN IT TO YOU...BUGS DON'T BECOME PROGRAMMERS."

18. Lecture 17 (M): Sprint 3
19. Lecture 18 (W): More Design Patterns
• Observer design pattern
• Decorator design pattern
• Builder (Appendix A - see also Design Patterns by Gamma, et. al.)
• Crawfis Collections
• Read the following patterns in the Head First Design Patterns book:
  • Strategy
  • State
  • Observer
  • Decorator
  • Adaptor
  • Facade
  • Template Method
  • You should have read (and understood) the first 10 chapters in this book by now, plus some of the Appendix.
  • Reinforce your understanding using the following resources:
    • Design Patterns by Gamma, et. al.
    • http://www.dofactory.com/Patterns/Patterns.aspx
    • other web resources as you see needed.
20. Lecture 19 (F): Code Smells and Refactoring continued
• 
  • from: http://www.irregularwebcomic.net/comic.php?comic=687
• Additional Code Smells
  • Purists vs. Pragmatists
  • Should we define Wiki smells?
• Technical Debt
  • Wikipedia
  • Martin Fowler
  • Quadrants
• What is Refactoring?
• Why Refactor:
  • Refactoring improves the design of software
    • without refactoring, a design will "decay" as people make changes to a software system
  • Refactoring makes software easier to understand
    • because structure is improved, duplicated code is eliminated, etc.
  • Refactoring helps you find bugs
    • Refactoring promotes a deep understanding of the code at hand, and this understanding aids the programmer in finding bugs and anticipating potential bugs
  • Refactoring helps you program faster
    • because a good design enables progress
• CSE 2221 Example (RSS feed) (open with Programmer's Notepad)
  • Initial Java
  • Refactoring 1 (extract methods for long method)
  • Refactoring 2 (remove duplicate code)
  • Class discussions
• Lecture 20 (M): Cameras
• Window coordinate systems
• level coordinate systems
• Camera placement and coordinate system

Lecture 21 (W): Camera software and controls?

• Camera Constraints and Controls
• random blog on polymorphism

Lecture 22 (F): HUD and depth layers.

Data driven applications (also called Table-Driven or Metadata-Driven)

• Read Table-driven Approach
  • Also read the comments
• Table-based State Machine and Literate Programming for the Adventure Game