Ver código fonte

Add feedback from Tim

tags/0.2.2-analysis^2
Wouter Horlings 5 anos atrás
pai
commit
2ae3c07457
2 arquivos alterados com 9 adições e 7 exclusões
  1. +1
    -1
      content/background.tex
  2. +8
    -6
      content/introduction.tex

+ 1
- 1
content/background.tex Ver arquivo

@@ -36,7 +36,7 @@ Each iteration of the rapid development incorporates the following steps:
\item Implement and test that feature.
\end{enumerate}
The first step is to create an initial design and tests that are used to verify the requirements of the current feature.
During the second step, the initial design will developed into a detailed design of the feature.
During the second step, the initial design is developed into a detailed design of the feature.
This detailed design of the feature is develop with the variable detail approach, in which the level of detail is stepwise incremented.
When the second step is completed, the implemented feature contains all the required details and passes all the tests as defined in the first step.
From this point the rapid development cycle is repeated for the next feature, or, when no features are left, finish the development.


+ 8
- 6
content/introduction.tex Ver arquivo

@@ -2,14 +2,15 @@
\chapter{Introduction}
\label{introduction}
\section{Context of this Thesis}
\ac{cps} integrate computation and physical components as an engineered system.
\ac{cps} are computer systems which control and monitor a physical system.
This physical system is often a system of mechanical components which are deeply intertwined with the software components.
Automobiles, robots, medical devices and even the smart grid are examples of \ac{cps}.
The complexity of \ac{cps} has gone from an embedded system that improved the fuel consumption of a car engine to a fully self-driving vehicle.
Although the complexity opens up more design possibilities, improved efficiency and safety, it has downsides.
Although the complexity opens up more design possibilities, improved efficiency, and beter safety, it has downsides.
The problem with the increasing complexity is the resulting increased developing cost and the decreasing reliability.
Within the research topics that focus on \ac{cps}, lies the development of new design methods that deal with this complexity problem.
The \emph{design method} by \textcite{broenink_rapid_2019} is one of these new design methods and focusses on the rapid development of embedded control software.
The rapid development is a design technique that splits the development into small individual steps, which can be implemented and tested separately.
The rapid development is a design technique that splits the development into small individual steps, which are implemented and tested separately.
Testing each individual step creates feedback on a short interval, with the goal to detect errors made during the development as early as possible.
As part of the research, Broenink and Broenink performed a small case study.
In this case study, they have designed a controller, and implemented the controller in software for a physical off-the-shelf system.
@@ -31,7 +32,7 @@

\section{Approach}
Within this thesis, the design method by \textcite{broenink_rapid_2019} is evaluated in a case study.
The case study performs a development process according to the design method and will evaluate the result.
The case study performs a development process according to the design method and evaluates the result.
However, there are a couple of steps required prior to the start of the case study (see \autoref{fig:approach}).
The first step is to produce a concrete \emph{design plan} based on the design method.
The concrete design plan improves the evaluation of the design techniques.
@@ -56,7 +57,8 @@
Normally, the design process focusses on delivering the end product in the most effective manner.
However, the goal of this research is to use the design process to evaluate the design method, not to develop a product.
A possible pitfall is that during the design process a simple solution is found, such that the design techniques to deal with the increased complexity are left untouched.
Choosing to develop a very complex subject would ensure that all the design techniques are used, except that the limited time budget of a master's thesis does not allow that.
Choosing to develop a very complex subject ensures that the case study covers all the design techniques.
Unfortunately, the limited time budget of a master's thesis makes it impossible to perform a case study for a complex subject.
One of the requirements for the possible subjects is therefore a minimum level of complexity, forcing the developer to not go with the simplest solution.
Some other requirements, based on practical decisions like budget, tools, and time were defined as well.
Based on these requirements, the subject of choice is "Writing a tweet on a whiteboard".
@@ -69,7 +71,7 @@
Design method is a commonly-used notion throughout the different papers and research used in this thesis.
\textcite{broenink_rapid_2019} refer to their design method as 'the methodology', which is to generic for this thesis.
To ensure distinct terminology throughout this thesis, their methodology is named \acl{ridm} and is abbreviated as \acs{ridm}.
The more concrete version of the design method that is tested in the case study, will be referred to as the 'design plan'.
The more concrete version of the design method that is tested in the case study, is referred to as the 'design plan'.
The object or system that is going to be designed during the case study is referred as 'subject of design'.

\section{Structure}


Carregando…
Cancelar
Salvar