PRE2019 3 Group13: Difference between revisions

From Control Systems Technology Group
Jump to navigation Jump to search
Line 79: Line 79:
* Week 2: It is clear who the the users are, the research is finished and also the requirements are decided.
* Week 2: It is clear who the the users are, the research is finished and also the requirements are decided.
* Week 3: Research into design prototype and costs.  
* Week 3: Research into design prototype and costs.  
* Week 4: Research into software prototype andlList of parts and estimation of costs.  
* Week 4: Research into software prototype and a list of parts and estimation of costs is made.  
* Week 5: Building prototype.  
* Week 5: Building prototype.  
* Week 6: The prototype has been made.  
* Week 6: The prototype has been made.  

Revision as of 12:27, 9 February 2020

Group members

Student name Student ID Study E-mail
Yara Daamen 1337157 y.f.daamen@student.tue.nl
Heather Hanegraaf 1330454 Biomedische Technologie h.e.h.hanegraaf@student.tue.nl
Mayke Scheffer 1234784 Electrical Engineering m.scheffer1@student.tue.nl
Wouter Haneveer 1300334 Computer Science w.haneveer@student.tue.nl
Gijs van Bakel 1239472 Applied Physics g.v.bakel@student.tue.nl

Problem Statement

Objectives

Users

Approach, Planning, Milestones and Deliverables

Approach

The aim of this project is to help people with nerve diseases such as tremor to become more independent. We are going to do this by making special cutlery, which makes it possible to eat independently for this target group. We want to acchieve this goal by delivering a prototype and model on how the cutlery can be implemented. The approach to reach those two goals contains multiple steps.

1. Research

Firstly, we will be going through research papers and other sources which describe the state of art of such cutlery and its respective components. This allows our group to get a grasp of the current technology of such a system and introduce us to the new developments in this field. This also helps to create a foundation for the project, which we can develop onto. The state of art also gives valuable insight into possible solutions we can think and whether their implementation is feasible given the knowledge we possess and the limited time. The Research has to be done with use of literature, survey(s), personal interview(s), recent reports from research institutes and the media and analyzing patents which are strongly connected to our project.

2. USE aspects

Furthermore, we will continue to analyze the problem from a USE – user, society, enterprise – perspective. An important source of this analysis is the state of art research, where the results of these cutlery systems in different stakeholders is discussed. The USE aspects will be of utmost importance for our project as every engineer should strive to develop new technologies for helping not only the users but also the society as a whole and to avoid the possible consequence of the system they develop. This analysis will finally lead to a list of requirements for our design.

3. Product shaping

Finally, we hope to develop a prototype in which the product will be conceptualized and programmed. In this process the RPC's are used to chose the program, hardware and the approach of the programming language itself.

4. Documentation

The wiki have to be updated and look like a report at the end of the project. To accomplish this someone will be assigned to check and edit the page every week. Besides the wiki, a presentation have to be made in anticipation of the last few weeks. Together with the prototype, the wiki page and the presentation are our final deliverables for the project.

Below the summary of the main steps in our approach of the project.

  • Doing research on our chosen project using SotA literature analysis
  • Analyzing the USE aspects and determining the requirements of our system
  • Choose the Hardware and Software for the prototype
  • Work on the prototype
  • Create a demo of the tracking functionality
  • Evaluate the prototype

Milestones

Here the major milesones can be found for every week. :

  • Week 1: The subject is chosen and also the Plan for the project has been made.
  • Week 2: It is clear who the the users are, the research is finished and also the requirements are decided.
  • Week 3: Research into design prototype and costs.
  • Week 4: Research into software prototype and a list of parts and estimation of costs is made.
  • Week 5: Building prototype.
  • Week 6: The prototype has been made.
  • Week 7: The tracker demo will be finished in order to be at the presentations.
  • Week 8: The wiki page is finished and updated with the results that were found from testing the prototype. Also, future developments are looked into and added to the wiki page.

Deliverables

Within this project there are four final deliverables.

  • This wiki page, which contains all of our research and findings
  • A presentation, which is a summary of what was done and what our most important results are
  • A prototype
  • A video of the tracker demo

Planning

Name Week #1 Week #2 Week #3 Week #4 Week #5 Week #6 Week #7 Week #8
Research RPC's and USE Analysis + start prototype research Hardware Design Software Design Prototype / Concept Proof Reading Future Developments Conclusions
Heather Hanegraaf Write approach, milestones and deliverables
Brainstrom subject ideas
Make the planning
Yara Daamen Research 12 or more papers
Add the research papers to the wiki page
Mayke Scheffer Write problem statement and objectives
Wouter Haneveer Research 12 or more papers
Add the research papers to the wiki page
Gijs van Bakel Write User part
Group Work Brainstorm about the subject during meeting
Online meeting (Whatsapp) about subject

Literature Study