Purpose
Making a paper prototype before writing any code is an important step in building software.
It helps you plan how the system will work and look, focusing on the user’s experience.
A paper prototype uses sketches and descriptions to show what the app or program will do and how users will interact with it.
This makes it easier to spot problems and make changes early, without wasting time writing code.
It also helps everyone on the team understand the plan and work together.
By starting with a clear prototype, you can save time and create a better, more user-friendly program.
Requirements
Author a paper prototype to describe additional features that could be added to the LCS Check-In app.
These could be exclusively student-facing features, or, they could be a combination of teacher and student-facing features.
Thinking through and prototyping any portion of the additional functionality required in this application will be helpful.
Rubric
Your work, together with your partner’s, will be evaluated according to the following criteria:
| Criteria | Level 1 (Developing) | Level 2 (Approaching) | Level 3 (Proficient) | Level 4 (Advanced) |
|---|---|---|---|---|
| Clarity of User Flow | User flow is unclear or incomplete; significant gaps in describing user actions and results. | User flow is partially clear but has some gaps or inconsistencies in describing user actions and results. | User flow is mostly clear and logical; most user actions and results are described in detail. | User flow is exceptionally clear, logical, and comprehensive; all user actions and results are detailed. |
| Detail in Descriptions | Descriptions of user actions and results are vague or missing. | Descriptions of user actions and results are present but lack sufficient detail to fully communicate intent. | Descriptions of user actions and results are detailed enough to convey intent for most interactions. | Descriptions of user actions and results are highly detailed and leave no ambiguity about user intent or system behavior. |
| Interface Sketches | Sketches are missing or too rough to communicate intent; major elements of the interface are unclear. | Sketches are present but lack clarity or detail; some key elements of the interface are ambiguous. | Sketches are clear and include most key elements of the interface, effectively communicating intent. | Sketches are highly clear, well-organized, and include all key elements; they effectively and creatively communicate intent. |
| Integration of User Flow and UX | User flow and interface sketches are poorly integrated; it is difficult to understand how they work together. | User flow and interface sketches are somewhat integrated but have gaps or inconsistencies. | User flow and interface sketches are well-integrated, with clear connections between user actions and UX. | User flow and interface sketches are seamlessly integrated, providing a cohesive and intuitive representation of the UX. |
| Consideration of User Experience | Little to no consideration of user experience; interface and flow do not account for usability or user needs. | Some consideration of user experience; usability and user needs are partially addressed but with room for improvement. | Clear consideration of user experience; usability and user needs are well addressed for most interactions. | Exceptional consideration of user experience; usability and user needs are fully addressed with creative and thoughtful solutions. |
Due Date
End of class on Friday, January 17, 2025.