- Three or four possible applications are considered.
- The proposal supports at least three design patterns and explains their role.
- The planned application meets the stated SOLID, input/output, UI, and code-quality requirements.
9.3 Final Project Check In
Work through the stories in order. Use the acceptance criteria to check each feature, and complete the nested tasks using the specified names, values, and scenarios.
Using this pattern arbitrarily will be looked for. If you intend to use this pattern it must have a purpose in your design.
Since this check-in takes place before the State and Command patterns, look into them to see if they are something you might want to use. Consider this check-in a rough draft; your design could incorporate these patterns later on.
How complicated will it be? We aren't looking for polished. We are looking that you understand the concepts of patterns and where it is appropriate to use them.
What if I can't think of anything? Talk to some of your peers and do a brainstorming session (remember, brainstorming means no bad ideas). Talk to some of the leadership (other instructors, tutors, IAs) to get an idea of what they've done or some other past student projects.
Can it incorporate 3 patterns? This is going to be the toughest part of the rough draft process because generally patterns emerge while writing code and not before. Do an outline to help you think of where patterns might fit in.
Reach out to an instructor on Slack AT LEAST A WEEK BEFORE the final project timeframe begins. Failure to do so will result in a point reduction. Be prepared to discuss:
Return to each story and verify its acceptance criteria. Preserve the submission format and destination stated in the activity; a reading, setup guide, lab, video demonstration, and oral final may require different evidence.
Plan a project that meets the design requirements Discuss the proposal before the final-project period