Level 4 Diploma in Computing

Student Guidelines: Software Engineering Mini Project

Word Limit: Max. 3,000 words
Weighting: 100% of module marks
Deliverables: A word-processed report including:
• Answers to Tasks 1–6
• Work Breakdown Structure (WBS)
• Gantt Chart
• Use Case Diagrams
• Class Diagrams
• Harvard-style citations and references

General Tips to Succeed:

• Use clear headings for each task (Task 1, Task 2, etc.)
• Stick to the word limit and manage your word count wisely
• Use visuals (diagrams, tables, charts) where needed
• Ensure your work is original – no plagiarism or AI-generated content
• Cite all sources in Harvard Style
• Think like a software engineer – apply practical thinking, structure, and logic

Task 1 (15 Marks)

What You Should Include:
1. Problem Identification:
o Describe a real-world issue your project addresses.
o Use data or examples if possible.
2. Aims and Objectives:
o Define what your project hopes to achieve.
o Must be clear and well-defined aims – no confusion.
o Objectives are specific and easy to follow.
o Use bullet points or short paragraphs for clarity.
3. Scope of the Project:
o Deliverables: What the project will deliver (e.g., working prototype, UML diagrams,
user guide).
o Exclusions: What it won’t cover (e.g., no mobile app version).
o Constraints: Budget, time, tech limitations, etc.
o Assumptions: Things you’re assuming (e.g., internet is available, users are
trained).
4. Development Methodology:
o Strong evaluation of different approaches.
o Clear explanation of your chosen method.
o Full justification for why it’s the best fit.
5. Project Plan:
o Well-documented and realistic timeline.
o Comprehensive list of all needed resources.
o Assign roles and estimate time/resources.
o Use a Work Breakdown Structure (WBS) to show key tasks.
o Create a Gantt Chart to visualize timelines.

Prepared By – Nazrana Haque Page 1 of 3

 Level 4 Diploma in Computing

Tips for High Marks:

✔ Use project management tools like MS Project, or Excel
✔ Be realistic – don’t overpromise features you can’t deliver
✔ Justify why each element of your plan is included

Task 2: Requirements Specification (10 Marks)

What You Should Include:
• A list of Functional Requirements (what the system should do)
e.g., “Users can log in using email and password.”
• A list of Non-Functional Requirements (how the system performs)
e.g., “System must respond within 3 seconds.”
• Methods used to gather requirements (e.g., interview, survey, observation)
• Justify why you used that method
• Summary of information and requirements gathered through each method
Tips for High Marks:
✔ Separate functional vs. non-functional requirements
✔ Use stakeholder input or research to support your choices
✔ Explain how these requirements affect your design

Task 3: UML Diagrams (40 Marks)

What You Should Include:
1. Use Case Diagram(s):
o Show actors and their interactions with the system
o Include "include" and "extend" relationships if needed
o Cover the entire system scope
2. Class Diagram(s):
o Identify key classes with attributes and methods
o Show relationships: inheritance, association, composition, etc.
o Ensure your diagram matches the requirements from Task 2
Tips for High Marks:
✔ Use proper UML notation
✔ Keep diagrams clear, labeled, and consistent
✔ Include a short explanation as assumptions under each diagram
✔ Use tools like [Link], Lucidchart, or StarUML
✔ Validate diagrams against your requirements

Task 4: Prototype (10 Marks)

What You Should Include:
• A working prototype (front-end or functional parts)
• Screenshots
• Map each feature to its original requirement or UML element
Tips for High Marks:
✔ Prototype should be based on your design
✔ Include key features (e.g., login, search, view results)
✔ Show traceability – how design led to this prototype
✔ Explain why it’s suitable for early testing

Prepared By – Nazrana Haque Page 2 of 3

 Level 4 Diploma in Computing

Task 5: Testing (10 Marks)

What You Should Include:
• A Test Plan outlining:
o Acceptance tests
o System tests
o Unit/component tests
• A Test Case Table with:
o Test ID
o Feature being tested
o Input data
o Expected result
o Actual result
• Document any changes made based on test outcomes
Tips for High Marks:
✔ Cover both positive and negative test cases
✔ Be thorough – aim to test each function at least once
✔ Use real test data or edge cases
✔ Reflect on what worked and what didn’t

Task 6: Evaluation & Conclusion (15 Marks)

What You Should Include:
1. Evaluation of Tools & Techniques:
o Tools used (e.g., VS Code, [Link], GitHub)
o Techniques (e.g., prototyping, user testing)
2. Lessons Learned Report:
o What went well
o What you’d do differently next time
o Obstacles and how you overcame them
3. Recommendations for Future Work:
o How can the project be improved?
o Are there extra features you didn’t have time for?
4. Reflection:
o Did the system meet its goals?
o Consider productivity, quality, and personal/team performance
Tips for High Marks:
✔ Be honest and professional – self-reflection is valuable
✔ Justify every point with examples
✔ Avoid generic statements – make it project-specific

Final Submission Checklist

✅ Report follows the structure of Tasks 1- 6 ✅ Diagrams are neat and labeled
✅ References are in Harvard style ✅ Prototype is traceable to design
✅ Word count is within 3,000 words ✅ Test cases are clearly written and mapped
✅ WBS and Gantt chart are included ✅ Evaluation includes reflections and future improvements

Prepared By – Nazrana Haque Page 3 of 3