Project plan¶
As part of the course, a short project plan must be created for the project. These plans are not shown publicly to others; the purpose is to help yourselves in completing the final project. Creating a plan might seem unnecessary, but based on previous student feedback, it really helps to get your thoughts organized and to think about what actually needs to be done in the project! It also helps in scheduling the work.
The plan does not need to go into great detail; a high level of abstraction is sufficient. You can use bullet points to describe the items briefly. The plan should be a maximum of one A4 page. The plan is not binding, meaning it will likely evolve as the project progresses. An example plan is provided below.
Contents:
- A brief description of the functionalities in the program.
- State machine that implements the project. It is easiest to present this as a diagram.
- The state machine should cover the main tasks of the program; lower levels of abstraction are not necessary.
- Define the number of tasks and the role of each one .
- Outline of the peripherals to be used (buttons, sensors, etc.) and their purpose in the program.
- Identify global data structures and variables.
- Preliminary schedule, including milestones and distribution of work.
- Define the tier you are aiming to. You can change your opinion later.
The plan must be submitted by 2025-10-20 23:59. The plan is a mandatory part of the project. It is sufficient for one student from the project group to submit the plan to Lovelace. However, if you have questions, it is best to ask the assistants directly during the exercises.
Note! You are allowed to start the implementation of the project work before presenting a plan!
Note! The plans might be used as a reference material in academic research at a later time, in which case they will be anonymised. If you want to, you can decline the usage of your plan as research material by stating that in your plan.