---

time: 2020-10-23T13:05:00
attending:

• Chris
• Conner Pierce
• Henry Dang
• Peter Mangelsdorf
• Tom Trimbur

---

Software Design Document

Concerns

Username

• Store in Text file

Database

• Not Needed

How to Identify Players

• Enum?

Local Play

• out of scope
• just focus on networked play

Which Objects Must Exist

• Player
• Piece(s)
• "Interaction defines the player"

Who Should Know Where Pieces Go

• Peter:
  • Pieces should know their logical position
  • Board should know the translation of logical position to physical position
• Conner: Board should know where pieces go

SDD

• (see example document)
• (Due Wednesday)
• Sections
• Diagrams
• Work Delegation

Sections

• Intro
• Overview
  • Definitions (Red/White, Man/King)
  • Tools/Tech (Unit Tests)
• Requirements Traceability
• Interface
• Networking
• Data Model

Diagram

• System Architecture (Deployment) (see Example SDD page 2)
• Networking/Messaging (Sequence)
• Object Dependencies (UML)
• Object Knowledge (UML)

Work Delegation

Task 1

• Intro
• Requirements
• Data Model

Task 2

• Overview

Task 3

• Networking

Task 4

• Interface

Architecture

Indicating Multiple Hops

• consider it a series of connected turns
• or a queue of actions, gets repeated

GameObject or Class

• Henry: Should put checkers logic in plain C# classes
• Conner: Everything that is rendered and has a position must be a GameObject at some point

Designing for Testing

• Peter:
  • We can run Unit Tests from inside Unity
  • Can either load in a full game environment (test gameobjects)
  • Or load only classes (test logic)
• Henry: We should be testing the logic
• Peter: Yes!

Coordinating Effort

• Conner, Henry: Sunday Morning (10:00)