Software Engineering Mini Project Brief
Software Engineering Mini Project Brief
Task 1: Project Description: the problems, aims and objective of the project, scope of
the project, project plan. (15 marks)
1. Identify Problems: Students should identify the main issues or challenges that their
project aims to address. These could be problems in a specific industry, community,
or field of study.
2. Define Aims and Objectives: Next, students should clearly state the goals they want
to achieve through their project. These could be specific outcomes, improvements, or
advancements they hope to make.
3. Scope of the Project: Students need to outline the boundaries of their project,
including what will be included and what will be excluded. This helps to define the
project's focus and prevents scope creep.
4. Project Plan: Finally, students should develop a detailed project plan that outlines the
tasks, timelines, resources, and responsibilities required to complete the project
successfully. This plan should be realistic and achievable within the given timeframe.
Students should use a Gantt chart or/and WBS to illustrate project plan.
Requirements Specifications: Students should gather and document all the requirements for
their project, including functional and non-functional requirements. This involves conducting
interviews, surveys, and research to understand the needs of stakeholders. Students should
document identified.
Task 3: Design: Class diagrams and Use case diagram (30 marks)
1. Class Diagrams: Students should create class diagrams to illustrate the relationships
and attributes of the various classes within their project. These diagrams help to
visualise the overall structure of the system and how different components interact
with each other.
2. Use Case Diagrams: Using the gathered requirements, students should create use
case diagrams to illustrate the interactions between users (actors) and the system.
These diagrams help to visualise how users will interact with the system to achieve
specific goals or tasks.
Overall, Task 3 challenges students to translate their project requirements into a well-
organised system architecture and a user-friendly interface, demonstrating their design skills
and understanding of software engineering principles.
Page 1 of 2
Task 4: Implementation: Prototype (10 marks)
In Task 4, students should focus on building a prototype of their project. This involves
translating the design specifications into a functional prototype that demonstrates key features
and functionalities of the system. The prototype should serve as a proof of concept and allow
for testing and refinement before full-scale development.
In Task 4, students are not required to code the prototype. They can utilise simulation software
like Sketch or Adobe XD to design interactive prototypes without writing code. Alternatively,
for web-based projects, students can use website builders such as Wix to create functional
prototypes without coding. Students could only focus on front-end development.
In Task 5, students will develop test cases to evaluate the functionality and performance of
their project. Test cases should cover various scenarios to ensure the system behaves as
expected and meets the defined requirements.
Task 6 involves summarising the project's key findings, lessons learned, and
recommendations for future improvements. Students should reflect on the project's successes
and challenges, drawing conclusions about its overall effectiveness and significance.
Page 2 of 2