Mobile Robot Control 2020 Group 8: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
Welcome to the page of group 8 of the course Mobile Robot Control! | |||
== Group Members == | == Group Members == | ||
| Line 25: | Line 27: | ||
|} | |} | ||
== | == Introduction == | ||
== Meeting Summaries == | == Meeting Summaries == | ||
Revision as of 14:30, 3 May 2020
Welcome to the page of group 8 of the course Mobile Robot Control!
Group Members
| Name | Student Number |
|---|---|
| J.J.W. Bevers | 0904589 |
| J. Fölker | 0952554 |
| B.R. Herremans | 0970880 |
| L.D. Nijland | 0958546 |
| A.J.C. Tiemessen | 1026782 |
| A.H.J. Waldus | 0946642 |
Introduction
Meeting Summaries
In this section, a brief summary of the meetings will be given.
| Content | |
|---|---|
| 29-04-2020 | This was an introductory meeting during which the group met with the tutor, Wouter Houtman. We briefly discussed with him what he expected of us and how we were planning to make progression. Also, we discussed the contents of the design document. We had a general discussion about the expectations of the course and the two challenges. As a group we agreed to have at least two meetings per week, one with our tutor to discuss progression and to ask questions and one without him. We agreed that every group member should watch the lectures and make the tutorials. If one does not do so, he will fall behind and will not be able to help the group progess. Moreover, since none of the group members has experience with C++, every group member is advised to practice in the programming language. For next meeting, every group member should, apart from watching the lectures and finishing the tutorials, get some inspiration for the design document. Sources of inspiration are the wiki pages of groups of previous years and the general wiki page with the description of the challenges. |
| 01-05-2020 | In order to remember what is agreed upon during the meeting, we assigned someone to take minutes. Next time, he will lead the meeting to improve the structure and someone else will be taking the minutes. A role division scheme will be made. During this meeting, we discussed the five items that should be included in the design document. First, we agreed that we should first focus on the requirements and specification. By further specifying the requirements and specifications, functions will follow. Once the functions are known, they can be divided among the components of PICO. The components will on its turn be included in an software architecture with the corresponding interfaces. We decided to roughly follow the scheme of lecture 2.1 for the requirements and specification. Next, we divided tasks. Two persons will work on the requirements and specifications, two on the functions and two on the interfaces and components. Since the deadline for the design document is 04-05-2020, we set a deadline on 03-05-2020 for a first draft of the different tasks. This gives us sufficient time to process feedback from others and finalize the design document. |
Design Document
Requirements
Functions
Components
Specifications
Interfaces