Final Project Overview
The domain of the final project is outdoor digital photography taken at Indiana State Forests, State Parks, and similar locations. The photographs come from a variety of times and seasons, and they feature different subjects and aesthetic considerations. Within this context, you may choose to narrow your focus in various ways, such as considering collections taken by an individual over many trips, those taken by an interest group or organization, those posted publicly on the Internet with appropriate metadata to identify them as salient, or those curated by administrators. Regardless of whether or how you focus your effort, you should consider the rich connections among chronology, geography, subject, and theme.
A sample collection of photographs taken by an individual over several trips will be provided for your use. These are not licensed for public distribution, and so the link will be provided via Canvas. You may use them to demonstrate your project, such as to potential employers, but you may not publicly post them without prior permission of the copyright holder.
The final project will commence on March 12, after Spring Break; teams will be formed on March 12 as well. We will use the context described above to deepen our understanding of the Double Diamond model. We will spend roughly one week each on the Discover and Design phases. There will then be roughly three weeks to iterate on the development process. Your final delivery will consist of your original software system, a project report, and a final presentation.
The delivery deadline is April 27, 1:00 PM via Canvas.
Non-functional Software Requirements
The following items are required in the strictest sense; projects that do not meet these will receive a failing grade.
- You may complete this project individually or in a team of up to four students enrolled in this course (CS345 and/or CS545).
- Your solution will include an original software component.
- You must have legal rights to use all copyrightable components incorporated into your project for the purposes of academic display of your work. Copyright terms on any third-party resources you incorporate must be documented within the project.
Assuming the non-functional requirements are met, then the software component of your system will be evaluated as described on the evaluation page.
Project Report Requirements
Numbers in square brackets indicate the relative value of the corresponding element to your final report score.
- Include an executive summary, not to exceed one page in length. [6]
- Clearly state the problem being solved and your proposed solution. Situate this discussion within the double-diamond design process that you followed, contextualizing and justifying your claims using relevant design artifacts. Be sure to include a justification for the tools and platforms selected for development. [15]
- Describe how your solution manifests the seven universal principles of design established by Norman in the class reading. Clearly label the discussion of each principle to facilitate evaluation. [3 each]
- Document the methods and results of end-user evaluation. This should be a mixed-methods presentation, including both quantitative and qualitative consideration. [15]
Presentation Requirements
Numbers in square brackets indicate the relative weight of each item in determining your final presentation score.
- Summarize the problem being solved, how it was identified, and your solution strategy. Keep your audience in mind; you do not need to pretend that you are speaking to someone who has never heard of your project before. [3]
- Demonstrate your software system. [3]
- Give an overview of the software architecture, focusing on boundary between model- and view-layer components. [3]
- Summarize the acceptance testing method and results. [3]
- Reflect on the most significant challenges faced on the project. [3]
Final Project Score
Your final project score is a weighted average as computed in the following table.
Software System | 35% |
Project Report | 55% |
Presentation | 10% |