Overview
There are three main rubric categories that are detailed in the following sections for 145 points (subject to change)
Design Document (55)
Phase 1 (20 pts)
- 80% of your grade for Phase 1 will be determined by providing all sections completed on time.
- 20% will be provided once you have approval on your phase 1 to move to phase 2.
The approval may be graded after the due date and will not be late. However, you must get this signed off and complete well before phase 2 is due to be graded without deduction.
| Category | Criteria | Points |
|---|---|---|
| Project Description | - Provides a clear and concise overview of the project (2-4 paragraphs). - Describes the project’s functionality in sufficient detail for another developer to understand and potentially implement. - Specifies the use of Java Swing for graphical development. | 5 |
| MVP, Core, Stretch Features | - Clearly defines the essential features that constitute the MVP. - Features are realistic and achievable by the project’s midpoint. - Demonstrates understanding of MVP’s role in project development. - Shows progression and clear distinction between different feature levels (e.g. tabular like this) - MVP features focus on initial validation and essential functionality. - Core features encompass broader functionalities aimed at enhancing user experience and product value. | 5 |
| Purpose & Motivation | - Explains the rationale behind choosing the project. - Articulates learning objectives and goals. - Reflects personal or educational significance. | 3 |
| Learning Targets and Challenge Goals | - Lists at least three Learning Targets of sufficient scope for the project. | 2 |
| High Level Timeline | - Lists High Level Milestones for the 10-11 weeks the project will fun for. - 7 Development milestones are demonstrable pieces of functionality that can be checked off each Friday. - Milestones are formatted correctly with no time estimates or individual assignments. | 5 |
Phase 2 (15 pts)
| Category | Criteria | Points |
|---|---|---|
| Detailed Schedule (baseline) | - All weekly goals have a subset of at least 4 tasks that will be individually assigned and estimated (assignments not required) - All tasks have reasonable initial estimates - Initial estimates with multiplier fits within a reasonable range of a weeks work in class. - Actual times can be recorded to calculate the teams velocity each week to adjust future work estimates. | 5 |
| User Experience | - Develop Wireframes and Mockups. - At least 5 different screen layouts - Screen Layouts show connections and annotations to explain how transitions or changes are effected by mouse or keyboard input. - Includes every possible screen you plan to create for your core features - Nice to have but not graded: Show where your stretch UI features will go or change the UI | 10 |
Phase 3 (20 pts)
| Category | Criteria | Points |
|---|---|---|
| Detailed Design | - Class Design & Data Structures are well-structured with appropriate attributes, methods with key parameters and return types. - Explains how classes communicate, share data, and interact within the system. - Describes important algorithms with step-by-step logic or pseudocode. - User Interface & External Libraries (if applicable): Outlines key UI components, interactions, and any third-party libraries used with justification. - Satisfies requirements in the Detailed Design Template (design diagrams, user stories etc) | 15 |
| User Stories | - Each tasks on the schedule has at least 1 user story referenced writted per the definition provided. | 5 |
| Testing Strategy | - Provided a description of the different test strategies you will use (e.g. Manual, UI testing, Automated/Junit testing). You convinced me that your program will behave as you expect by having sufficient details on the testing. For manual testing you provided some detailed steps on the tests you will run through. | 3 |
| Algorithms | - Clearly documents key algorithms (If your project has approval for no algorithms, your detailed design will be weighted with these points) | 2 |
Project Completion (60)
The following rubrics break out the assessment by different areas.
Updates (10 Pts)
There will be 10 points awarded for submitting your updated Design Document to match your finished project.
Functionality (40 Pts)
| Criteria | Exemplary (100%) | Satisfactory (80%) | Not Yet (60%) | Unassessable (0%) |
|---|---|---|---|---|
| Quality (Bugs) | No major bugs or glitches. Program does not crash. All basic use cases work as advertised. Only minor bugs present. | Few major bugs. Program does not crash. Behavior is mostly correct. | Some major bugs. Program seldom crashes. | Major bugs prevalent. Important behavior malfunctions. |
| Polish/User Design | Appearance is clean and professional. No visual or audio bugs. Great attention to detail and creativity. | Appearance is mostly well-organized and neat. No usage issues. | Appearance is somewhat organized. Usage is somewhat difficult. | Appearance is poor. Usage is difficult. |
| Quantity (Features) | Completed all MVP features and then some. Code demonstrates many hours of focused work (6+ hours per week). | Completed all MVP features. Appropriate number of hours is evident (5 hrs/week). | Completed some MVP features. Shows a lack of effort and dedication (3-4 hrs/week). | A long way from appropriate effort and completion. |
| Difficulty | Difficult technology, algorithms, UI, and/or library integration. | Appropriate difficulty. | Lack of apparent or significant learning. | No demonstration of learning. |
| Data Structures | Appropriate in all cases. | Mostly good. | Some poor choices. | Poor choices abound. |
| Class Design | Strong use of all: abstraction, encapsulation, inheritance, polymorphism. | Use of inheritance and encapsulation is good. Reasonable set of classes. | Classes used, but not encapsulated well. Over or under-designed. | Few classes. Bad design. |
Presentation (10 Pts)
| Criteria | Exemplary (100%) | Satisfactory (80%) | Not Yet (60%) | Unassessable (0%) |
|---|---|---|---|---|
| Formal Presentation | Thorough presentation of project: functionality, learnings, and experience. Professional slides and/or presentation. | Demonstrates functionality and some insight into the development experience. No slides necessary. Reasonable quality of presentation. | Falls short of sharing functionality or experience. Presentation lacks quantity or quality. | Missing or woefully disorganized, lacking details. |
Ongoing (30)
Professionalism (30 pts)
This section will be ongoing through the entire project lifecycle and count towards the final grade.
| Criteria | Exemplary (100%) | Satisfactory (80%) | Not Yet (60%) | Unassessable (0%) |
|---|---|---|---|---|
| Demo Days | Clear achievements made during each demo. Shared learning along with functionality. Tasklist is completely up to date. | Some progress is demonstrated. Task List has some updates. | Progress is missing or too small. Worksheet is missing important information. | No progress is discernible. Worksheet is inadequate. |
| Independence | No instances of being off task. Asks for hints occasionally, independently researches, demonstrates problem-solving abilities. | 1 or 2 reminders needed to be on task. Needs help with difficult issues but demonstrates ability to debug and grow independently. | 3+ reminders to get back on task. Consistently unable to resolve (minor) issues without assistance. | Frequently off task. Cannot make progress without assistance. |