Objectives
- Turn your approved idea into clear functional requirements
- Model the system with a use case diagram and an activity diagram
- Choose and justify an architecture / design pattern
- Plan persistent data storage
- Implement the first UI screens
Requirements
- At least 5 functional requirements. Login and sign-up are not counted.
- At least 9 screens: 3 per member. Sign-in and registration screens are not counted.
- Code on the team GitHub repo, with each member committing on their own branch
- A contribution table on the first page of the report
Tasks
- 01
System requirements
At least 5 relevant functional requirements (login/sign-up excluded).
- 02
Use case diagram
At least 1 primary actor and 5 relevant use cases. Use include/extend where appropriate.
- 03
Activity diagram
The app's workflow: start node, end node, activities and logical flow. It must match your use cases.
- 04
UI prototype & implementation
9 working screens: 3 per member.
- 05
Architecture / design pattern
Choose one (e.g. MVC, MVVM, Provider/Context), justify it, and reflect it in your folder structure.
- 06
Data storage plan
Data items and their types, local or cloud storage, and a preliminary data model diagram.
Deliverables
- Typed report (one per team), with a contribution table on page 1
- UI implementation code (GitHub repo link)
Submission
- Upload the report and code to the e-learning system by the deadline
- Hand in a printed copy of the report as well
- Include a signed Coursework submission form and a Statement of Academic Honesty
- Late submission follows faculty regulations
Grading
| Criterion | Marks |
|---|---|
| Use case diagram (group) 1 actors · 1 correct logic · 3 mapping to requirements. Wrong notation = 0. | 5 marks |
| Activity diagram (group) 2.5 covers the requirements · 2.5 correct flow. −0.5 per missing or incorrect component. | 5 marks |
| UI design & implementation (individual) 1 per screen. Missing screen −1 · incorrect screen −0.5. | 9 marks |
| Architecture / design pattern (group) 2 selection · 2 applied in project structure · 2 reasoning. | 6 marks |
| Total | 25 marks |
Warning
The items listed add up to 25 of the 30 Phase 1 marks. See the official coursework document on e-learning for the full criteria.
Resources
FAQ
Do login and sign-up screens count?
No. They count toward neither the 9 screens nor the 5 requirements.
Can we use AI?
Yes, for code, as long as every significant interaction is documented. The report itself must be written by you. No AI.
How are individual marks decided?
UI marks are individual: your 3 screens and your commits on your branch.