Design Ideas and Evaluation Template
Use this page to structure the folio document for alternative design ideas and the evaluation process used to choose a preferred design.
How to use this template
Students should document two to three genuinely different design ideas. Tiny variations of the same idea should not be treated as separate designs.
Cover Information
| Field | Student entry |
|---|---|
| Project title | |
| Student name | |
| Date | |
| Version |
1. Design Problem Summary
Write a short summary of the design problem.
Include:
- the problem, need or opportunity
- the intended users
- the most important requirements from the SRS
- the key constraints shaping the design
2. Design Idea 1
2.1 Title or label for this idea
Give the design a clear name so it can be referred to consistently later.
2.2 Overall concept
Describe the central idea of this design in one short paragraph.
2.3 How this design addresses the SRS
- key functional requirements addressed:
- key non-functional requirements addressed:
- important constraints addressed:
2.4 Appearance and interface notes
Describe the likely layout, style, screens, outputs or user interaction.
2.5 Functionality notes
Describe the main features, workflows or behaviours this design would include.
2.6 Ideation evidence
Insert the evidence used to develop this idea. This could include:
- mind maps
- brainstorming notes
- sketches
- annotated sketches
- mood boards
2.7 Strengths of this design
-
2.8 Limitations or risks of this design
-
3. Design Idea 2
Repeat the same structure used for Design Idea 1.
3.1 Title or label for this idea
3.2 Overall concept
3.3 How this design addresses the SRS
3.4 Appearance and interface notes
3.5 Functionality notes
3.6 Ideation evidence
3.7 Strengths of this design
3.8 Limitations or risks of this design
4. Design Idea 3
Use this section only if the student is documenting three design ideas.
4.1 Title or label for this idea
4.2 Overall concept
4.3 How this design addresses the SRS
4.4 Appearance and interface notes
4.5 Functionality notes
4.6 Ideation evidence
4.7 Strengths of this design
4.8 Limitations or risks of this design
5. Evaluation Criteria
Write evaluation criteria as questions.
| Criterion ID | Evaluation question | Linked SRS requirement or constraint | Type: efficiency or effectiveness |
|---|---|---|---|
| EC1 | |||
| EC2 | |||
| EC3 | |||
| EC4 |
Add more rows as needed.
Useful categories to draw from include:
- accessibility
- accuracy
- attractiveness
- clarity
- communication of message
- completeness
- maintainability
- readability
- relevance
- timeliness
- usability
- cost of data and file manipulation
- functionality
- speed of processing
- ease of use
- scalability
- compatibility
6. Evaluation Results
Use one results table so each design is judged against the same criteria.
| Criterion ID | Design 1 result | Design 2 result | Design 3 result if used | Notes or evidence |
|---|---|---|---|---|
| EC1 | ||||
| EC2 | ||||
| EC3 | ||||
| EC4 |
7. Feedback from Client or Users
Record any feedback gathered while considering the design ideas.
| Source of feedback | Design idea discussed | Key feedback received | Action taken or implication |
|---|---|---|---|
8. Preferred Design
8.1 Selected design
State clearly which design has been chosen as the preferred design.
8.2 Justification
Write a short paragraph that explains:
- why this design performed best against the criteria
- how it best meets the SRS
- why it is the most suitable design to develop into detailed designs
8.3 What will carry forward into detailed design
- key interface decisions:
- key functional decisions:
- key constraints that must still be managed:
- any feedback that must be incorporated:
Final Check Before Submission
- [ ] There are two to three genuine alternatives.
- [ ] Each design responds to the same SRS.
- [ ] Each design shows functionality and appearance.
- [ ] Ideation evidence is included.
- [ ] Evaluation criteria are written as questions.
- [ ] The results table is completed.
- [ ] A preferred design is clearly identified and justified.