Design Exercises

An important design skill is to be able to think about, discuss, and change how a program is organized before writing code and without worrying about exactly how it will be implemented. Thus, without writing any actual implementation code, these exercises will help you explore the trade-offs between several designs and describe the best one in enough detail that other programmers could implement it for you using any data structures, file format, or UI display they want.

Submitting Work

Design Exercises are due each week by 3:07am ET in the morning on the day after that given on the course Calendar (so it is effectively a few extra hours grace time past midnight).

• You will be graded only on what is in the master branch of the individual portfolio_NETID repository provided for you in the course's Gitlab group
• Each entry must be in a separate file, named for the number of the week and topic (e.g., design01_PROJECT_TOPIC.md)
  Templates to start each entry are given below that are named correctly using this convention.
• You must use the Markdown format for your entries, whose specific prompts are detailed below
• You are responsible for ensuring that all files are correctly pushed to the repository on time

Markdown is an industry standard, simple, plain text format for providing style guidelines that can be transformed into any other document format. IntelliJ includes a Markdown editor that provides a preview or there is a web-based editor that provides similar functionality.

Deliverables

1. Objects (template)
2. Use Cases (template)
3. Changes (template)
4. Analysis (template)