Report Writing, System testing and validation
With the technical developments complete – Matlab codes, Simulink model, and ThingSpeak dashboard all working. I shifted my focus towards completing the report. The goal was to document everything properly, validate all three implementations and make sure the report was structured so that all the evidenced engineering work was captured.
Report Writing
Writing started with the easiest chapters to draft first – methodology and design implementation – because all the technical decisions were fresh and documented in the blog throughout the project.
The chapter structure is:
- Chapter 1: Introduction – background, research problems, aims and objectives, scope.
- Chapter 2: Methodology – simulation approach, dataset generation, Matlab scripts, Simulink, ThingSpeak
- Chapter 3: Design and implementation – system architecture, script design, Simulink model design and Thingspeak channel setup
- Chapter 4: Results – single-turbine and multi-turbine outputs, scenario comparison, Simulink validation and IoT dashboard.
- Chapter 5: Discussion – objectives met, research problems addressed, comparison to existing projects and solutions, limitations
- Chapter 6: Conclusion and potential for future developments.
A decision made towards the end of the report writing was to include only key code parts in the main body rather than the full code. The three full Matlab code files were included in the project blog, keeping the report focused and within the page limit.
Comments
Post a Comment