Embedded Motion Control 2015 Group 4: Difference between revisions
Jump to navigation
Jump to search
Line 6: | Line 6: | ||
==Requirements== | ==Requirements== | ||
A (draft) list of the requirements contains the following points: | |||
* Exiting the maze in minimal time. | |||
* Avoiding damage of the robot and the environment. | |||
* Robustness of pathfinding algorithm with respect to maze layout. | |||
* Design software using modular approach. | |||
* Implement algorithm using only available hardware and software API's. | |||
* Manage code development with multiple developers. | |||
==Existing hardware interfaces== | ==Existing hardware interfaces== | ||
==Unknown design constraints== | ==Unknown design constraints== | ||
==Main focus point in the first two weeks== | ==Main focus point in the first two weeks== | ||
==Software design strategy== | ==Software design strategy== |
Revision as of 10:17, 29 April 2015
Authors: T. Cornelissen, T van Bommel, J. H. de Kleuver, M. Oligschläger, B. Hendrikx, P. Rooijakkers, T. Albers
Requirements and function specifications
Problem statement
The software design process starts with a statement of the problem. Although all the details of the assignment are not yet knwon at this point, we can best summarize the statement with the following sentence:
- Design the software in C/C++ for the (existing) Pico/Jazz robot that enables to find the exit of an unknown and dynamically changing maze in minimal time.
Requirements
A (draft) list of the requirements contains the following points:
- Exiting the maze in minimal time.
- Avoiding damage of the robot and the environment.
- Robustness of pathfinding algorithm with respect to maze layout.
- Design software using modular approach.
- Implement algorithm using only available hardware and software API's.
- Manage code development with multiple developers.