Pārlūkot izejas kodu

Some improvements

master
Wouter Horlings pirms 4 gadiem
vecāks
revīzija
ea66efb401
3 mainītis faili ar 30 papildinājumiem un 24 dzēšanām
  1. +9
    -7
      content/conclusion.tex
  2. +16
    -12
      content/evaluation.tex
  3. +5
    -5
      content/introduction.tex

+ 9
- 7
content/conclusion.tex Parādīt failu

@@ -42,17 +42,18 @@
\begin{itemize}
\item Preparation phase
\begin{itemize}
\item Have complete life cycle: from problem description to system functionality
\item The design method must cover the complete life cycle: from problem to final product
\item describe how to split the functionality into features.
\item Incorporate software and hardware in decissions
\item Incorporate software and hardware in the design process
\end{itemize}
\item Development tooling
\begin{itemize}
\item Version Control to manage model versions
\item Central design database, where models inherit from
\item Modelling software should support version control
\item Central design database, where models inherit their parameters from
\item Automated testing, for all models
\end{itemize}
\item Use hardware prototyping to its advantage
\item Always use a design team, with more than one developer
\end{itemize}
\end{block}
}
@@ -180,13 +181,14 @@
%notes
\begin{block}{Future Iterations}
\begin{itemize}
\item Involve experienced team
\item It must involve an experienced design team
\item Include adaptations from this thesis
\item Two strategies:
\begin{itemize}
\item Expand to full design model\\
include full life cycle
\item Integrate in existing design models
\item Integrate the development cycle and variable-detail approach
\item in existing design models
\end{itemize}
\end{itemize}
\end{block}
@@ -200,7 +202,7 @@
\item Two strategies:
\begin{itemize}
\item Expand to full design model
\item Integrate in existing design models
\item Integrate technique in existing design models
\end{itemize}
\end{itemize}
\end{block}


+ 16
- 12
content/evaluation.tex Parādīt failu

@@ -6,13 +6,13 @@
\item Preparation Phase: the steps prior to the development Cycle
\begin{itemize}
\item What elements are required to describe a feature
\item How should these features and their elements be defined
\item How these features and their elements should be defined
\end{itemize}
\item Development Cycle: That is performed for each feature
\begin{itemize}
\item The role of design and model in the process
\item Select which feature to implement
\item Tooling required for Development
\item Tooling required for the design method
\end{itemize}
\item Design in General
\begin{itemize}
@@ -94,20 +94,22 @@



\begin{block}{Feature Definition}
\begin{itemize}
\item The preparation phase determines
\item functionality of the system
\begin{itemize}
\item thus also the features
\item thus also how the features are defined
\item which are developed into the final product
\end{itemize}
\item The simple set of steps: problem definition; requirements; initial design
\item difficult to design this simple system with
\item approach must also be able to determine features
\item of complex problems.
\item Eventhough the tweet on a whiteboard
\item is a fairly simple system.
\item It was still difficult to design the system
\item using the simple set of steps: problem definition; requirements; initial design
\item The rapid iterative design method needs an
\item approach for the development of the functionality
\item and thus the definition of features
\item and must be able to deal with complex problems as well.
\end{itemize}
\end{block}
}
{
%overlay
@@ -203,9 +205,9 @@
\item difficult to organize the levels of detail
\item Model software must be compatible with version control
\begin{itemize}
\item Allow atomic commits
\item Make merging easy
\item Possible to revert changes
\item Allow atomic commits
\item Make merging easy
\item Possible to revert changes: not only the last one
\item Link and reuse other submodels
\end{itemize}
\end{itemize}
@@ -350,6 +352,7 @@
\customslide
{
%notes
the design process lacked a:
\begin{block}{Development Team}
\begin{itemize}
\item Missed design and software experience
@@ -363,6 +366,7 @@
\item Requires multi-disciplinary design team
\end{itemize}
\end{block}
Attempting to design a complex system on your own, makes it even more difficult than it already is.
}
{
%overlay


+ 5
- 5
content/introduction.tex Parādīt failu

@@ -117,11 +117,11 @@
my presentation starts with a:
\begin{itemize}
\item Brief introduction of design method
\item How I used the case study to test this method
\item What is the result of the case study
\item What did I learn from the case study
\item In the conclusion I adress the influence and adaptations
\item And the last this are the recommendations for future research
\item Then I explain how this is design method is applied using a case study
\item Followed by the result of the case study
\item In the evaluation I explain what I learned from the case study
\item As conclusion I will discuss the research objectives
\item And finaly some recommendations for future research
\end{itemize}
}
{


Notiek ielāde…
Atcelt
Saglabāt