PRE2018 3 Group5
General info
Group members
| Name | Student ID |
|---|---|
| Ruben Haakman | 0993994 |
| Stan Latten | 1257196 |
| Tom Mulders | 1008890 |
| Jasper Stam | 1006240 |
| Mathijs Vastenhouw | 1269496 |
Problem
To keep residential areas clean and neat, lots of tools are used. Most of the tools are operated by humans, but some new tools can do some tasks autonomous. Can't this be done by one autonomous robot? We think the most common tasks can be performed by an autonomous robot.
Problem statement
How can tasks of maintaining residential areas be combined into one (modular) robot?
Objectives
- The system must have the ability to do tasks, like lawn mowing and trash picking
- The system must be able to go autonomous to the place, where the task has to be performed
- The system has to give a warning to the owner in case of technical disorder
- The system has to ask for help of human if needed
Users and other stakeholders
- Municipalities: responsible to maintain the residential area
- Citizens: clean and safe neighborhood
- People that are maintaining the neighborhood: can focus on other tasks, that currently would not be done
- Society as a whole
- Enterprises that specialize in maintenance of public grounds
Project setup
Approach
After reviewing the literature, we will determine the requirements for the robot. Based on these requirements we will design a robot to maintain the sidewalks, which will include a detailed physical design and a design of the software running the robot. We will analyse the effects of the use of the robot on the stakeholders and determine the costs of building, deploying and maintaining the robot. The design process will be iterative and each cycle ends with a prototype, which we will analyse and improve if needed.
Milestones
- State-of-the-art analysis
- Requirements Document
- Design Documents
- Use analysis
- Prototype (1)
- Analysis of prototype (1)
- Updated requirements and design
- Prototype (2)
- Cost analysis
Deliverables
- Requirements document
- Design document
- Use analysis
- Cost analysis
- Prototypes (2)
Who's doing what
- Ruben: Design(electronics), cost analysis, prototype.
- Stan: Design(general), Requirements, Use analysis, prototype.
- Tom: Design(general), Requirements, Use analysis, prototype.
- Jasper: Design(software), STOA analysis, Requirements, Use analysis.
- Mathijs: Design(general), STOA analysis, cost analysis, prototype.
State of the art
The literature study can be found on the page State of the art
Planning
For each week, there are points what we plan to do in that week. Planning can change over the weeks, dependent on the progress in the project. Final versions of the documents will be delivered at the end of the quartile, but concept versions will be delivered earlier.
Week 1
- Introduction to course
- Brainstorming about problem
- Make problem statement
- First idea on plan for project
- Literature study on problem
Week 2
- Updated problem description
- Concrete planning for project
- Make plan more clear with introduction
- Analysis of literature found in week 1
- First idea on requirements
- Start on USE stakeholder analysis
Week 3
- Concrete decisions on prototype
- USE stakeholder analysis
- Make requirements ready to start on prototype
- Start on prototype
Week 4-6
- Work on prototype
- Analysis of requirements based on prototype and update if needed
- Analysis of decisions made for prototype and update if needed
- Update other documents if needed
Week 7
- Finalize prototype
- Prepare presentation
Week 8
- Presentation