Your goal for this sprint is to expand on your prototype. You should have a list of goals set in your planning documentation/system. Choose a set of those items to commit to and finish before the sprint’s end.

Planning

  1. Create a new document that describes the architecture of your project. Store this file in /doc/architecture.md with Markdown formatting and include any external resources necessary. For example:

    • Are you writing a game? Record how the various components/objects in your system will interact.

    • Are you writing a website? Record a sample database schema, diagram of how the MVC components interact, or sequence diagram of the actions that happen with the website.

      Make liberal use of diagramming utilities to accomplish this task. There is not a requirement to have perfect UML structures, but UML utilities may aid in this task.

    • Example 1 of a SAD

    • Example 2 of a SAD

Code

  1. You should continue to create a detailed plan recorded in your work management system. There should be a recorded history of your finished tasks. Do not delete things when they are done. Mark them as accomplished!

  2. You should expand your prototype and begin writing some actual code that you expect to work towards your goal. This should match your Github Projects documentation.

Deliverables

  1. A marked set of tasks to be finished in this sprint.

    • A set of the tasks finished last sprint and the ones you are creating for this sprint in your GitHub Projects tab.

  2. Delivered code that meets those tasks

  3. New architecture planning documentation.

  4. Responses and fixes to issues posted in your GitHub repository

Scoring

Out of 20:

  • (-[0,5]) Any outstanding issues from previous sprints are worth up to 5 points (25%!) off regardless of current cumulative score. You must fix outstanding issues.

  • (8) Architecture document

    • (1) doc/architecture.md exists

    • (4) has a reasonable amount of information

    • (1) is formatted in markdown

    • (2) SAD diagrams exist within the document

  • (4) GitHub Projects is up to date

  • (8) Work towards the items changed in Github Projects has been accomplished.

    • (4) There should be a reasonable amount of code written

    • (4) The pull request system has been used properly