|
|
|
@@ -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 |
|
|
|
|