PRE2018 3 Group4: Difference between revisions

From Control Systems Technology Group
Jump to navigation Jump to search
(→‎Enterprise: Added text 3)
No edit summary
 
(105 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<link rel="shortcut icon" href="https://www.tue.nl/favicon-64.ico" type="image/x-icon">
<div style="font-family: 'Georgia'; font-size: 15px; line-height: 1.5; max-width: 800px; word-wrap: break-word; color: #333; font-weight: 400; box-shadow: 0px 25px 35px -5px rgba(0,0,0,0.75); margin-left: auto; margin-right: auto; padding: 70px; background-color: white; padding-top: 30px;">
<link rel=http://cstwiki.wtb.tue.nl/index.php?title=PRE2018_3_Group4&action=edit"stylesheet" type="text/css" href="theme.css">
<div style="width:calc(100vw - 175px);background-color:#EFEFEF;padding-bottom:35px;position:absolute;top:0;left:0;">
<div style="font-family: 'q_serif', Georgia, Times, 'Times New Roman', serif; font-size: 14px; line-height: 1.5; max-width: 750px; word-wrap: break-word; color: #333; font-weight: 400; box-shadow: 0px 25px 35px -5px rgba(0,0,0,0.75); margin-left: auto; margin-right: auto; padding: 70px; background-color: white; padding-top: 25px;">


= 0LAUK0 - 2018/2019 - Q3 - group 4 =
<div style="display: block; position: absolute; right: 8%;">
; Page navigation
# [[PRE2018_3_Group4 | Root]]
# [[Notes - Group 4 - 2018/2019, Semester B, Quartile 3|Notes from meeting]]
# [[Initial ideas - Group 4 - 2018/2019, Semester B, Quartile 3|Initial ideas]]
# [[Project setup - Group 4 - 2018/2019, Semester B, Quartile 3|Project setup]]
# [[General problem - Group 4 - 2018/2019, Semester B, Quartile 3|General problem description]]
# [[State of the Art - Group 4 - 2018/2019, Semester B, Quartile 3|State of the Art]]
# [[Specific problem - Group 4 - 2018/2019, Semester B, Quartile 3|Specific problem description]]
# [[Present situation - Group 4 - 2018/2019, Semester B, Quartile 3|Present situation]]
# [[Drones - Group 4 - 2018/2019, Semester B, Quartile 3|Drone analysis]]
# [[Solutions - Group 4 - 2018/2019, Semester B, Quartile 3|Solution analysis]]
# [[Airports under a microscope - Group 4 - 2018/2019, Semester B, Quartile 3|Airport analysis]]
# [[Types of Decision Models - Group 4 - 2018/2019, Semester B, Quartile 3 | Decision Model investigation]]
# [[Decision Model - Group 4 - 2018/2019, Semester B, Quartile 3 | Decision Model implementation]]
# [[Decision Model validation - Group 4 - 2018/2019, Semester B, Quartile 3|Decision Model validation]]
# [[Categorizing solutions - Group 4 - 2018/2019, Semester B, Quartile 3|Categorising solutions]]
# [[Web_Application_-_Group_4_-_2018/2019,_Semester_B,_Quartile_3 | Web Application]]
# [[Future - Group 4 - 2018/2019, Semester B, Quartile 3|Future]]
# [[Conclusion - Group 4 - 2018/2019, Semester B, Quartile 3|Conclusion]]
# [[Discussion - Group 4 - 2018/2019, Semester B, Quartile 3|Discussion]]
</div>


<!-- Think
= 0LAUK0 - 2018/2019 - Q3 - Group 4 =
    twice
On this page, we provide a hierarchical overview of the project done by Group 4 in Q3 2018/2019 for 0LAUK0 (Project Robots Everywhere). We start with the formalities where we introduce the group members, provide a small introduction to the project, and talk about the project setup, et cetera. Then, we consider a `Literature Research' and a `Decision Model' section that both provide many new and exciting insights. The hierarchical structure provided below is given in chronological order.
    before
 
    copy
<h3>[[One_page_-_Group_4_-_2018/2019,_Semester_B,_Quartile_3|Single page variant]]</h3>
    pasting
'''Important:''' For the convenience of the reader and in order to adhere to the standards used by all other groups, we also have a single page that consists of the whole project. This page then depicts the complete process in chronological order. When using this page for the final evaluation, one does not have to visit any other pages. It is up to the reader to decide which page to use. The single page can be found [[One_page_-_Group_4_-_2018/2019,_Semester_B,_Quartile_3|here]].
    parts
 
    of
== Formalities ==
    this
 
    work
=== Group members ===
    :)
The group members of Group 4 are as follows:  
            -->


== Group members ==
{| class="wikitable" style="border-style: solid; border-width: 1px;" cellpadding="3"
{| class="wikitable" style="border-style: solid; border-width: 1px;" cellpadding="3"
!style="text-align:left;"| Name
!style="text-align:left;"| Name
Line 36: Line 52:
|}
|}


== Introduction ==
=== Introduction ===
 
The goal of this wiki page is to show a study/analysis/design/prototype of a robotic subject. This research is an assignment of the course Robots Everywhere (0LAUK0). For this project, students work in a group of 5 choosing a subject in the core of robotics to work on, thereby making sure the USE aspects are leading.
 
== Notes ==
In this section, we refer to the [[Notes - Group 4 - 2018/2019, Semester B, Quartile 3|notes]] made during the meeting with the professors.
 
== Initial ideas ==
 
We first present some initial ideas. These ideas can be found [[Initial ideas - Group 4 - 2018/2019, Semester B, Quartile 3|here]].
 
== General problem description ==
Between 19 and 21 December 2018, hundreds of flights were canceled at Gatwick Airport, following reports of drone sightings close to the runway<ref name="BBC News airport">[https://www.bbc.com/news/uk-england-sussex-46623754 "Gatwick Airport: Drones ground flights"], 20 December 2018. Retrieved on 2019-02-06.</ref>.
A total of 760 flights were disrupted on the 20th of December due to the drone. Naturally, this angered many people whose flight was delayed. Not only does it anger people, but it is also a financial worry for the airport organization as all of these people with delayed flights have to be compensated.
The airport did not have any `good' measures to prevent this issue. Gatwick chief operating officer Chris Woodroofe said: `The police are looking for the operator and that is the way to disable the drone'<ref name="BBC News airport">[https://www.bbc.com/news/uk-england-sussex-46623754 "Gatwick Airport: Drones ground flights"], 20 December 2018. Retrieved on 2019-02-06.</ref>.
Woodroofe further elaborates that the police had not wanted to shoot the devices down because of the risk from stray bullets. This is, of course, not something that is to be repeated as this caused a lot of inconvenience for many travelers.
The airport itself only had detection and tracking devices, but no real effective counter mechanisms available.
This issue is not limited to the setting of airports, but it can be further extended to any hot spot, such as the centre of cities, special events that involve important figures, and more.
With the ever-increasing possibilities of technology, it should in the future not be unexpected for an ''unmanned aerial vehicle'' (UAV) to suddenly show up and wreak havoc.
This havoc can range from taking pictures of people in public places to spy or stalk them to terrorists that use UAVs to drop bombs in highly populated areas. 
These occurrences are more likely to appear as the technology we possess increases.
 
We think that we should not sit idle and passively wait for the worst-case scenarios to occur before starting to think about countermeasures.
The recent incident between 19 and 21 December 2018 at Gatwick Airport should already sound an alarm that we should take an active attitude and develop mechanisms that counter UAVs in effective ways.
These mechanisms should be able to deal with much more than mere birds and should consider any form of terrorism that can be caused through the airspace.
 
== Objectives ==
 
=== Objectives of the project as a whole include: ===
* Gaining insight into accidents and incidents involving various forms of drones.
* Identify and specify the currently existing countermeasures and counter mechanisms against drones and UAVs in general.
* Identify and specify the USE stakeholders of the problem space and their interests regarding possible solutions.
* Propose multiple possible solutions to the problem.
* Identify the advantages and the disadvantages centred around user interests for each provided solution.
* Validate and verify that our proposed solutions solve the discussed problems with respect to the USE stakeholders and their interests.
 
== State of the Art ==
 
We now consider the State of the Art regarding the general problem description.
We take a look at numerous distinct papers and patents.
The State of the Art can be found [[State of the Art - Group 4 - 2018/2019, Semester B, Quartile 3|here]].
 
== Project setup ==
 
=== Approach ===
We now take a look at how we will approach this project. As is customary with open projects, we will start our approach by doing an extensive study into the current state of the problem. We will do this by studying the literature of different forms. We will look at papers where this problem has been discussed before, but also at what the current solutions are at the moment and what their flaws are. Furthermore, we also look at studies and research of institutes that have made investigations into this phenomenon.
 
After we as a group have a good grasp on the problem, we analyse the problem ourselves from a USE (User, Society, Enterprise) point of view. These three components will be central in our study and the development of our design as the users of the technology always need to be the main focus. Following this study into the USE aspects surrounding our problem space, we expect different categories of subproblems to arise. For example, when considering two distinct incidents involving UAVs, they might be categorized by the type of failure that occurred, be it human failure or technical failure. We expect that many of these distinctions can be made, and as different categories of subproblem might involve different USE aspects, they might require different solutions.
 
After this, we will provide possible solutions for a number of distinct problem categories. First, we set up a list of requirements and functionalities centred around the user. For each discussed problem category, we will then present multiple implementations of these requirements and functionalities, which will be our first drafts. These draft solutions will be further discussed and analyzed based on their advantages and disadvantages. We will also provide research into the feasibility of these proposed solutions.
 
As the discussed subproblems heavily integrate with various aspects of society, we are also interested in the ethical aspects of the evolution of the proposed technologies of counter-drones. We will investigate the ethical and regulatory consequences of these developments. We might also provide insight into which areas of the problem space have not been sufficiently discussed by previous research and falls outside the scope of ours. For future reference, we also look ahead and shortly discuss improvements or otherwise changes to our proposed solutions, that are not currently possible due to technical or other limitations. Finally, we will wrap up with completing the wiki and our documentation of the project.
 
=== Planning ===
We now take a look at the [https://docs.google.com/spreadsheets/d/1WyOdatUQELl1FZiSwcJMECZ4LAajeBZCeK_Gs31QYe4/edit?usp=sharing planning] of the project.
The planning is presented in the form of an excel sheet that clearly states the tasks that need to be carried out, by whom these tasks will be carried out, an estimation of the time that it takes to carry this task out, if the task has been completed or not, and when it needs to be completed.
Furthermore, an orange cell indicates that this will be done during a group meeting, and a blue cell indicates that this will be done outside of a meeting. Note that this planning also considers the division of work to a large degree.
 
=== Milestones ===
We now consider the milestones within the project. Here, we consider Table 1 that displays the accomplishments on a specific date. Furthermore, if there were any learning moments during each of these accomplishments, they will be written down in the `Aditional notes' column and taken into consideration for the next accomplishment. Note that this table will be regularly updated throughout the course.
 
{| class="wikitable" | style="vertical-align:middle;" | border="2" style="border-collapse:collapse" ;
|+ '''Table 1: Milestones'''
! align="center"; style="width: 10%" | '''Date'''
! align="center"; style="width: 30%" | '''Accomplishment'''
! align="center"; style="width: 30%" | '''Additional notes'''
|-
| 06/02/2019
| Finalise the decision of the subject
| N/A
|-
|
| Finalise research into State of The Art
|
|-
|
| Formulate analysis of problem space
|
|-
|
| Formulate possible solutions to identified problems
|
|-
|
| Formulate advantages and disadvantages of each solution
|
|-
|
| Formulate possible further improvements
|
|-
|
| Formulate conclusions regarding proposed solutions
|
|-
|
| Create presentation format of our research
|
|-
|
| Present complete research
|
|-
|
| Finalise the Wiki and documentation
|
|-
|}
 
=== Deliverables ===
We now cover the deliverables of this project.
The deliverables focus on the problem introduced in the problem description.
These deliverables for this project will be as follows:
In this section, we refer to the [[Present situation - Group 4 - 2018/2019, Semester B, Quartile 3|present situation]], which consider the present situation regarding the specific problem description. We discuss the current rules and regulations, current solutions, and the limitations of the current rules, regulations, and the limitations.
* A presentation regarding the problem and possible solutions.
 
This presentation will be held in the final week of the course. In this presentation, we start by introducing a problem through a summary of the problem description. Then, the finding regarding the problem will be presented. This is followed by multiple solutions to the problem with their advantages and disadvantages. Then, we zoom into the `best' solution and provide a design regarding this solution. If possible, a demonstration will also be given.
 
* A Wiki page in the form of a literature research
 
This Wiki page contains an in-depth study regarding the problem introduced in the problem description. An extensive literature study will be presented, which offers multiple solutions with both their advantages and disadvantages. Furthermore, it will be argued what solution would be the `best'. This is followed by areas that are still undiscovered and improvements that can be made to our design.


== Major USE aspects ==
The goal of this wiki page is to show a study and analysis of a robotic subject. This research is an assignment of the course Robots Everywhere (0LAUK0). For this project, students work in a group of five people choosing a subject in the core of robotics to work on, thereby making sure the USE aspects are leading. As is usual in a Wiki, multiple pages will be used rather than considering one extremely long page. Make sure to explore all subpages contained under this page.
In this section, we consider the users, society, and the enterprise around the general problem description.


=== Users ===
=== [[Notes - Group 4 - 2018/2019, Semester B, Quartile 3|Notes from meetings]] ===
There are multiple stakeholders involved in a solution to the problem introduced in the problem description. By far the largest and most diverse category of stakeholders consists of those parties that are (majorly) disadvantaged by unauthorized or unwanted UAV operations, or malicious events that could follow. We can identify several subcategories of stakeholders whose material possessions or immaterial values are at stake.


The most important users are as follows:
=== [[Initial ideas - Group 4 - 2018/2019, Semester B, Quartile 3|Initial ideas]] ===
* The Government
As the governing body, a collection of many large instances with national interests, the government of a nation aims to preserve the material and immaterial assets of its citizens. This goal might be obstructed by the unwanted presence of UAVs or events caused by them.
* Non-governmental organizations
Includes companies or other privately owned bodies that want to protect their material assets against damage from UAV incidents, or protect immaterial assets such as privacy or intellectual property that could be violated by unwanted presence of UAVs.
* Civilians or individuals in general
Civilians or individuals in general are also stakeholders in the problem space that we consider. They might have their assets violated in some way by UAVs or UAV related events, such as civilian espionage empowered by UAVs. Since drone flight is growing as a commercial pass-time, more specifically the operation of drones by civilians for fun is becoming more popular, this user group must also be considered as a stakeholder from this perspective.


=== Society ===
=== [[Project setup - Group 4 - 2018/2019, Semester B, Quartile 3|Project setup]] ===
The society as a whole is affected by the already existing and upcoming dangers of drones. First of all, drones can be a huge hindrance at for example airports (Gatwick airport), football stadiums or other public places. However, apart from simple hindrance, drones can also be  extremely dangerous for society, as they can be weaponized and used by terrorists, the military or any other person with bad intentions. Furthermore, more and more people are using drones privately, causing privacy issues for society, as these drones are equipped with a camera most of the times and can easily reach private places. This is why drone interception is so important to society. If there were to be a tool that could detect, identify and neutralize drones, this could help in a decrease of hostile drones and thereby also decrease the aforementioned dangers that drones bring to society.


=== Enterprise ===
== Literature Research ==
Enterprise is greatly affected by the illegal use of drones, for example, the airlines at Gatwick lost a lot of revenue due to delayed flights and passenger compensation. The airport itself also suffered from the forced shutdown. Other industries are also threatened by drones, espionage via drones can be done remotely, where attackers may steal a company secrets through aerial photography or by taking pictures through windows. Hence the development of anti-drone will be of enormous benefit to existing enterprises but also spark new business opportunities for security contractors and UAV oriented startups.


== Specific problem description ==
=== [[General problem - Group 4 - 2018/2019, Semester B, Quartile 3|General problem description]] ===
As described in the 'Approach' Section, we expected the societal issue of unwanted UAV presence to be divisible into multiple subcategories. Following our initial literature study, we indeed found this to be the case. There are many axes along which the problem space can be divided. For example, we might consider a division based on the nature of the cause of a drone incident, and as such whether it was caused by human failure or technical failure. Another possible distinction can be given based on the specific part of society that is impacted, whether it be the privacy of individuals when a camera-equipped UAV flies over their backyard, or the safety of a group of users when there are UAVs present around an airfield. When we consider the existing legal regulations, another commonly occuring division is that between human-controlled and autonomous UAVs.


This realization lead us to formulate a more specific problem definition with a smaller scope. In our study, we consider possible deterrents against unwanted UAV presence around airports. This includes studying the current legal regulations considering UAVs, both in general and more specifically considering airports. The term UAV is also divisible into multiple subcategories, for this study we take all sub-types of UAV into account. These specific sub-types will be further discussed in a following Section.
=== [[State of the Art - Group 4 - 2018/2019, Semester B, Quartile 3|State of the Art]] ===


== Specific USE aspects ==
=== [[Specific problem - Group 4 - 2018/2019, Semester B, Quartile 3|Specific problem description]] ===
In this section, we consider the users, society, and enterprise when considering specific problem description.


=== Users ===
=== [[Present situation - Group 4 - 2018/2019, Semester B, Quartile 3|Present situation]] ===


=== Society ===
=== [[Drones - Group 4 - 2018/2019, Semester B, Quartile 3|Drone analysis]] ===


=== Enterprise ===
=== [[Airports under a microscope - Group 4 - 2018/2019, Semester B, Quartile 3|Airport analysis]] ===
When we restrict the USE case analysis to only deterrents against unwanted UAVs or drones around airports, the enterprise aspect of the use analysis becomes more concrete. The main type of enterprise that is under risk is the airport branch. The total revenue of the aviation industry in 2018 alone is a staggering 821 billion USD<ref name="Aviation revenue">[https://www.iata.org/pressroom/facts_figures/fact_sheets/Documents/fact-sheet-industry-facts.pdf "International Aviation Transport Industry: Fact Sheet"], December 2018. Retrieved on 11-02-2019.</ref>, so there are huge amounts of money at risk here. The current protocol is to suspend all flights of the airport by 30 minutes, the average lifespan of a drone. This means that, should drones occur often enough, all flights will be suspended for an indefinite amount of time<ref name="CNN drone protocol">[https://edition.cnn.com/2018/12/20/uk/drone-gatwick-airport-explainer-gbr-intl/index.html "CNN: How can a drone bring an airport to a standstill?"], December 2018. Retrieved on 11-02-2019.</ref>. This will of course have huge costs for multiple branches of the aviation industry. For these three enterprise branches, we will analyse the consequences of such an unwanted drone near an airport.


*Airports
=== [[Solutions - Group 4 - 2018/2019, Semester B, Quartile 3|Solution analysis]] ===
Airports suffer the largest loss in the case of such a drone in the airspace, which makes sense since it is where the problem is located. The airports suffer huge financial losses mainly through three different ways. First and foremost, no profits can be made when no planes fly. For example, the drone incident at Gatwick Airport caused a loss of over 50 million English Pounds<ref name="Independent Gatwick Cost">[https://www.independent.co.uk/travel/news-and-advice/gatwick-drone-airport-cost-easyjet-runway-security-passenger-cancellation-a8739841.html "The Independent: Gatwick drone disruption cost over £50 million"], January 2019. Retrieved on 11-02-2019.</ref>. This was caused by suspending all flights, which were just over 400, over the total duration of 33 hours. . the airport suffers a huge blow to their reputation.  So the financial hourly losses are huge for airports when flights must be suspended due to drones in the area.


In terms of the aviation enterprise, we can differentiate between its different enterpirse subgroups.
== Decision Model ==


* Airlines
=== [[Types of Decision Models - Group 4 - 2018/2019, Semester B, Quartile 3|Decision Model investigation]] ===
Airlines also suffer huge losses during the event of a drone suspending or cancelling flights. The airlines are the companies actually offering the flights to travellers. What also causes more losses for airlines is that they have to compensate the travellers for the delay or cancellation of their flights. By European Law, airlines are required to provide travellers with enough food, drinks, and nightly accommodations for as long as necessary<ref name = "European Aviation Laws">[https://europa.eu/youreurope/citizens/travel/passenger-rights/air/faq/index_nl.htm "European Aviation Laws"], November 2018, Retrieved on 11-02-2019</ref>. For a large sudden suspension of flights at one place, which is the case in our problem, this also becomes an enormously difficult task for an airline. If the airline would not act accordingly, the airline could also suffer from a huge reputation loss, resulting in travellers not flying with that airline anymore. Furthermore, the travellers are also eligibile for financial compensation by European Law<ref name = "European Aviation Laws">[https://europa.eu/youreurope/citizens/travel/passenger-rights/air/faq/index_nl.htm "European Aviation Laws"], November 2018, Retrieved on 11-02-2019</ref>.
Airports.


Another aspect of this branch are the employees of the airlines. Apart from the company as a whole, the employees, such as flight attendants and pilots, suffer greatly from such an airline 'shutdown'. This is because of the way that the employees get paid. They do get a baseline salary, but the most salary they receive come from the hours that they are actually in the plane either flying or aiding passengers<ref name = "Aviation Employers" [https://www.huffpost.com/entry/why-flight-attendants-hate-delays-more-than-you-from_b_577d3f1de4b0746f5648b920 "Huffpost: Why flight attendants hate delays more than you"], July 2016, Retrieved on 11-02-2019 </ref>. If the planes do not fly, they suffer from a huge salary cut, which means that the whole branch of airline employees have financial losses.
=== [[Decision Model - Group 4 - 2018/2019, Semester B, Quartile 3|Decision Model implementation]] ===
Companies who transport goods via aviation.


*Companies who transport goods via aviation.
=== [[Decision Model validation - Group 4 - 2018/2019, Semester B, Quartile 3|Decision Model validation]] ===


== Present situation ==  
=== [[Categorizing solutions - Group 4 - 2018/2019, Semester B, Quartile 3|Categorising solutions]] ===


In this section, we refer to the [[Present situation - Group 4 - 2018/2019, Semester B, Quartile 3|present situation]], which consider the present situation regarding the specific problem description. We discuss the current rules and regulations, current solutions, and the limitations of the current rules, regulations, and the limitations.
=== [[Web Application - Group 4 - 2018/2019, Semester B, Quartile 3|Web Application]] ===


== Solutions ==
== Wrapping up ==  
In this section, we refer to the [[Solutions - Group 4 - 2018/2019, Semester B, Quartile 3|solutions]], which consider the requirements of the solutions, all possible solutions, and both the advantages and disadvantages of each solution.
As with most projects, we wrap up by looking ahead and thinking about the next steps that can be taken, providing a conclusion regarding the project as a whole, and discussing the process. Furthermore, we verify if all objectives have been meant and what the main takeaways for future projects are.  


== Conclusion ==
The [[Future - Group 4 - 2018/2019, Semester B, Quartile 3|Future]], [[Conclusion - Group 4 - 2018/2019, Semester B, Quartile 3|Conclusion]], and [[Discussion - Group 4 - 2018/2019, Semester B, Quartile 3|Discussion]] pages consider the future, conclusion, and discussion respectively about both the Literature Research and the Decision Model.


== Discussion ==
=== [[Future - Group 4 - 2018/2019, Semester B, Quartile 3|Future]] ===


= References =
=== [[Conclusion - Group 4 - 2018/2019, Semester B, Quartile 3|Conclusion]] ===
<references />


=== [[Discussion - Group 4 - 2018/2019, Semester B, Quartile 3|Discussion]] ===


= Links to our other wiki pages =
□
*[[Notes - Group 4 - 2018/2019, Semester B, Quartile 3|Notes]]
*[[Initial ideas - Group 4 - 2018/2019, Semester B, Quartile 3|Initial ideas]]
*[[State of the Art - Group 4 - 2018/2019, Semester B, Quartile 3|State of Art]]
*[[Solutions - Group 4 - 2018/2019, Semester B, Quartile 3|Solutions]]

Latest revision as of 17:54, 2 April 2019

0LAUK0 - 2018/2019 - Q3 - Group 4

On this page, we provide a hierarchical overview of the project done by Group 4 in Q3 2018/2019 for 0LAUK0 (Project Robots Everywhere). We start with the formalities where we introduce the group members, provide a small introduction to the project, and talk about the project setup, et cetera. Then, we consider a `Literature Research' and a `Decision Model' section that both provide many new and exciting insights. The hierarchical structure provided below is given in chronological order.

Single page variant

Important: For the convenience of the reader and in order to adhere to the standards used by all other groups, we also have a single page that consists of the whole project. This page then depicts the complete process in chronological order. When using this page for the final evaluation, one does not have to visit any other pages. It is up to the reader to decide which page to use. The single page can be found here.

Formalities

Group members

The group members of Group 4 are as follows:

Name Student ID Major
Jort de Bokx 1050214 Software Science
Sander de Bruin 1006147 Software Science
Stijn Derks 1008002 Software Science
Martin de Quincey 1007047 Software Science and Applied Mathematics
Nick van de Waterlaat 1009357 Software Science

Introduction

The goal of this wiki page is to show a study and analysis of a robotic subject. This research is an assignment of the course Robots Everywhere (0LAUK0). For this project, students work in a group of five people choosing a subject in the core of robotics to work on, thereby making sure the USE aspects are leading. As is usual in a Wiki, multiple pages will be used rather than considering one extremely long page. Make sure to explore all subpages contained under this page.

Notes from meetings

Initial ideas

Project setup

Literature Research

General problem description

State of the Art

Specific problem description

Present situation

Drone analysis

Airport analysis

Solution analysis

Decision Model

Decision Model investigation

Decision Model implementation

Decision Model validation

Categorising solutions

Web Application

Wrapping up

As with most projects, we wrap up by looking ahead and thinking about the next steps that can be taken, providing a conclusion regarding the project as a whole, and discussing the process. Furthermore, we verify if all objectives have been meant and what the main takeaways for future projects are.

The Future, Conclusion, and Discussion pages consider the future, conclusion, and discussion respectively about both the Literature Research and the Decision Model.

Future

Conclusion

Discussion

□

Retrieved from "https://dsdwiki.wtb.tue.nl/index.php?title=PRE2018_3_Group4&oldid=71221"