The final project may be software that supports or analyzes curation. It may be an interactive system. It may be a study, qualitative or quantitative. It is generally expected to involve iterative cycles of conceptualization, design, data gathering, analysis, and synthesis.
The final project may be undertaken individually. It may also be undertaken collaboratively.
The final project cycle is flexible. A structure will be presented, essentially, a dyed-in-the-wool human-computer interaction iterative design process. This structure includes weekly deliverables. Design and development alternate with data gathering, on various scales.
Sufficiently advanced students may propose alternative final project specifications. For example, if you wish to work on your thesis in the context of the course, inasmuch as this makes sense thematically, you are welcome. The final project does not have to burden your overall workload.
The key is that if you do wish an alternative final project specification, you will need to work closely with your professor. Engage me in discussion early on. Assuming that we come to consensus on principles, the student(s) is responsible for providing a clear and explicit alternative deliverables structure, and securing my approval, up front!