Mercurial > docs > Development-Case
annotate development-case.tex @ 12:b1d215fc244c default tip
Added tag Abgabeversion for changeset fb6ee4e487da3edb2ad4f5634b3c5de8f60bc1fd
author | meillo@marmaro.de |
---|---|
date | Wed, 06 Feb 2008 11:06:53 +0100 |
parents | fb6ee4e487da |
children |
rev | line source |
---|---|
0 | 1 % V. 1.0 |
2 \documentclass[a4paper,12pt,titlepage,DIV12,parskip]{scrreprt} | |
3 \setlength{\parskip}{3mm} %abstand abs\"{a}tze und listen | |
4 \usepackage{setspace} | |
5 \usepackage[utf8]{inputenc} | |
6 \usepackage{ngerman} | |
7 \usepackage[pdftex]{graphicx} | |
8 \usepackage[table]{xcolor} | |
9 %\usepackage{SIunits} | |
10 \usepackage{ragged2e,array} | |
11 \usepackage{wrapfig} | |
12 \usepackage[footnotesize]{caption2} | |
13 \usepackage{supertabular} | |
14 \usepackage{chngcntr} | |
15 \usepackage{longtable} | |
16 %\usepackage{lastpage} | |
17 \usepackage{caption2} | |
18 \usepackage[right]{eurosym} | |
19 %\usepackage{float} | |
20 \usepackage[ngerman]{varioref} | |
21 %\usepackage{enumitem} | |
22 \usepackage[colorlinks,linkcolor=black,urlcolor=blue,bookmarks,bookmarksopen,bookmarksnumbered]{hyperref} | |
23 | |
24 %PDF Infos | |
25 \pdfinfo{ | |
26 /Title (development-case.tex) | |
27 /Subject (Development Case) | |
28 %/Creator (TeX / pdfTeX) | |
29 %/Producer (Christoph Galler) | |
30 /Author (markus schnalke) | |
31 /CreationDate (D:20080113090000) | |
32 /ModDate (D:20080113090000) | |
33 } | |
34 | |
35 %neues Kommando fuer Breitenangabe in der Tabelle mit vorgegebener Breite: | |
36 \newcommand{\preserveBackslash}[1]{\let\temp=\\#1\let\\=\temp} | |
37 \newcolumntype{R}[1]{>{\preserveBackslash\RaggedLeft}p{#1}} | |
38 % Font Familie | |
39 \renewcommand{\familydefault}{\sfdefault} | |
40 %\nofiles | |
41 % Fuer tabellenkopf | |
42 \newcommand{\hoehe}{\parbox[1pt][2em][c]{0cm}{}} | |
43 | |
44 \definecolor{gray09}{gray}{0.9} | |
45 \definecolor{gray07}{gray}{0.7} | |
46 | |
47 %Counternummerierung \"{a}ndern -> 1.1 2.1 3.1 etc. | |
48 \counterwithin{section}{chapter} | |
49 | |
50 % Name f\"{u}r autoref bei figure Umgebungen: Abbildung x.z | |
51 \renewcommand{\figureautorefname}{Abbildung} | |
52 \renewcommand{\chapterautorefname}{Kapitel} | |
53 \renewcommand{\sectionautorefname}{Unterkapitel} | |
54 \renewcommand{\tableautorefname}{Tabelle} | |
55 | |
56 | |
57 % Textkoerperhoehe | |
58 \setlength{\headsep}{0.6cm} | |
59 \addtolength{\textheight}{0.9cm} | |
60 \setlength{\footskip}{0.9cm} | |
61 | |
62 % Kopf- und Fu{\ss}zeile | |
63 \setlength{\headheight}{2cm} | |
64 \usepackage[automark]{scrpage2} | |
65 \automark[section]{section} | |
66 \setheadwidth{15.8cm} | |
67 \ihead{\headmark} | |
8 | 68 \ihead{Development Case} |
0 | 69 \chead{{\color{blue}\color{black}\rule[-10pt]{18.4cm}{0.1pt}\color{black}}} |
70 \ohead{\headmark} | |
71 \setfootwidth[-74pt]{18.3cm} | |
72 \setfootsepline[foot]{.1pt} | |
8 | 73 \ifoot{\hspace{2.6cm}\footnotesize Gruppe 2: Seminarverwaltungssystem (Topcased)} |
0 | 74 \cfoot{} |
75 \ofoot{\footnotesize Seite \thepage} % ~von \pageref{LastPage}} | |
76 \renewcommand*{\chapterpagestyle}{scrheadings} | |
77 \renewcommand*{\indexpagestyle}{scrheadings} | |
78 \pagestyle{scrheadings} | |
79 | |
80 % Kapitel nicht zu tief beginnen | |
81 \renewcommand*\chapterheadstartvskip{\vspace*{0cm}} | |
82 | |
83 | |
84 \begin{document} | |
85 | |
86 % | |
87 % Titelei | |
88 % | |
89 \begin{titlepage} | |
90 \vspace*{-0cm} | |
91 {\hspace*{11cm}\includegraphics*[scale=0.5]{pictures/png/logo_hsu_klein}} | |
92 \begin{center} | |
93 \vspace*{1.9cm} | |
8 | 94 {\normalsize\textsc{Gruppe 2: Rui Gu, Wei Zhu, Veysel Imamoglu, |
95 Dimitar Dimitrov, \\Karl Oppermann, Nathalie Hrycej, Markus Schnalke, | |
96 Christoph Galler}} \par | |
0 | 97 \vspace*{0.6cm} |
8 | 98 \large \textbf{Modellgetriebene Softwareentwicklung auf Basis von |
99 TOPCASED am Beispiel eines Seminarverwaltungssystems} \par | |
0 | 100 \Huge \textbf{Development Case} \par |
101 \vspace*{0.8cm} | |
8 | 102 {\Large{} \par |
0 | 103 \vspace*{0.7cm} |
104 {\textsc{Ulm, \today}}} \par | |
8 | 105 \vspace*{4.5cm} |
0 | 106 {\normalsize\textsc{Betreut durch: \\ |
107 Prof. Dr. Klaus Baer \\ | |
108 Hochschule Ulm \\ | |
8 | 109 Prittwitzstraße 10\\ |
0 | 110 89075 Ulm\\}} |
8 | 111 \end{center} |
0 | 112 \vfill |
113 \end{titlepage} | |
114 | |
8 | 115 |
116 | |
0 | 117 \addsec{Version dieses Dokuments} |
118 \begin{tabular}{|p{1.5cm}|p{3.cm}|p{1.6cm}|p{2cm}|p{1.4cm}|p{4cm}|} | |
119 \hline | |
7
1f955918cf53
lots of minor things; changed to english names
meillo@marmaro.de
parents:
6
diff
changeset
|
120 \multicolumn{5}{|l}{\parbox[0pt][3.4em][l]{12cm}{\vspace{0.2cm}\large Dokument: \textbf{Development Case} \newline \emph{ Online-Seminarbuchungssystem}}} & \multicolumn{1}{r|}{\parbox[0pt][3.4em][r]{1.9cm}{\includegraphics*[scale=0.25]{pictures/png/logo_hsu}}} \\ |
0 | 121 \hline\hline |
122 \hoehe{\textbf{Version}} & \textbf{Person} & \textbf{Aktion} & \textbf{Datum} & \textbf{Status} & \textbf{Kommentar} \\ | |
123 \hline\hline | |
8 | 124 0.1 & Markus Schnalke & E & 2007-11-27 & O & Erste Version \\ \hline |
125 0.2 & Markus Schnalke & AE & 2008-01-13 & O & Neue Struktur des Dokuments \\ \hline | |
126 0.4 & Markus Schnalke & AE & 2008-01-16 & A & Struktur überarbeitet \\ \hline | |
7
1f955918cf53
lots of minor things; changed to english names
meillo@marmaro.de
parents:
6
diff
changeset
|
127 0.4.1 & Karl Oppermann & QS & 2008-01-17 & A & Allgemeines Review \\ \hline |
11 | 128 0.5 & Markus Schnalke & AE & 2008-01-18 & A & Überarbeitung \\ \hline |
8 | 129 0.5.1 & Veysel Imamoglu & QS & 2008-01-18 & A & Rechtschreibkorrektur \\ \hline |
10 | 130 1.0 & Markus Schnalke & AB & 2008-01-22 & A & Finale Version für R3 \\ \hline |
0 | 131 \end{tabular} |
132 {\footnotesize\vspace*{-0.1cm}Aktion: E – Erstellung; AE – \"{A}nderung; QS – Review; AB – Abnahme} \par | |
133 {\footnotesize\vspace*{-0.4cm} Status: O – Offen; D – Diskussion; A – Akzeptiert} | |
134 \clearpage | |
135 | |
136 % Inhaltsverzeichnis | |
137 \setcounter{tocdepth}{3} | |
138 %\renewcommand\contentsname{"Uberblick} | |
139 \tableofcontents | |
140 | |
141 \clearpage | |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
142 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
143 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
144 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
145 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
146 % Content |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
147 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
148 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
149 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
150 \chapter{Einleitung} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
151 |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
152 \section{Zweck des Dokuments} |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
153 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
154 Dieses Dokument beschreibt den Entwicklungsprozess nach dem wir in unserem Projekt vorgehen. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
155 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
156 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
157 \section{Definitionen und Abkürzungen} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
158 |
10 | 159 Die verwendeten Begriffe sind im Glossary erklärt. Bei Bedarf kann dort nachgeschlagen werden. |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
160 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
161 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
162 |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
163 \section{Verweise auf andere Artefakte} |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
164 |
10 | 165 Der \textbf{Software Development Plan} ist an vielen Stellen mit diesem Dokument verknüpft. |
166 | |
11 | 167 %Zur Klärung der verwendeten Fachbegriffe kann im \textbf{Glossary} nachgeschlagen werden. |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
168 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
169 |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
170 |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
171 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
172 |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
173 %%%%%%%%%%%%%% |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
174 \chapter{Entwicklungsprozess} |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
175 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
176 \section{Überblick} |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
177 |
9 | 178 Wir werden unser Projekt nach dem \emph{Rational Unified Process}$^{\ddagger}$ (kurz RUP) entwickeln. |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
179 |
7
1f955918cf53
lots of minor things; changed to english names
meillo@marmaro.de
parents:
6
diff
changeset
|
180 Der RUP ist ein dynamischer und iterativer Entwicklungsprozess, der das Projekt in zwei Dimensionen (zeitlich und inhaltlich) betrachtet. |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
181 |
9 | 182 An sich ist der RUP für große Projekte, mit vielen Mannjahren, ausgelegt. Für unser kleines Projekt (90 Manntage) ist er eher weniger gut geeignet. Wir haben uns trotzdem für den RUP entschieden, da wir ihn in der Vorlesung ``Softwaretechnik 1'' ausführlich behandelt hatten und wir dieses Theoriewissen nun in der Praxis anwenden wollen. |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
183 |
9 | 184 Wir haben diesen mächtigen und umfangreichen Prozess für unser kleines Projekt abgespeckt und angepasst. Wie unsere Adaptation des RUP genau aussieht, das beschreibt dieses Dokument. |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
185 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
186 |
11 | 187 \section{Der Rational Unified Process auf einen Blick} |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
188 |
11 | 189 Natürlich kann man diesen umfassenden Entwicklungsprozess nicht in einem Bild komplett abbilden, jedoch zeigt die nachfolgende Grafik sehr schön, wie die Entwicklung im Bezug auf die zwei Dimensionen aussieht. Dieser Übersichtplan soll den Aufbau des Prozesses nochmal ins Gedächtnis rufen. |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
190 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
191 \begin{figure}[htb] |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
192 \centering |
9 | 193 \includegraphics[width=9cm]{pictures/png/RationalUnifiedProcess.png} |
194 \caption{Übersicht über einen Zyklus im RUP$^{\ddagger}$ } | |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
195 \label{fig:rationalunifiedprocess} |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
196 \end{figure} |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
197 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
198 |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
199 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
200 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
201 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
202 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
203 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
204 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
205 %%%%%%%%%%%%%% |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
206 \chapter{Zeitliche Dimension} |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
207 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
208 \section{Anpassungen} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
209 |
11 | 210 Wir führen in unserem Projekt drei Zyklen durch. Jeder der drei Zyklen wird circa fünf Wochen (30 Manntage) umfassen. An deren Ende wird jeweils ein Release stehen. (siehe \emph{Software Development Plan}) |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
211 |
11 | 212 Die einzelnen Phasen in den Zyklen versuchen wir, so gut es geht, zu berücksichtigen. Es muss bedacht werden, dass bei uns pro Phase ganz grob nur etwa 4 Manntage (d.h. circa 4 Stunden pro Person) zur Verfügung stehen. |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
213 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
214 Iterationen innerhalb der Zyklen werden wir, auf Grund der kurzen Zyklen, komplett außen vor lassen. |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
215 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
216 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
217 |
11 | 218 Ein Beispiel um ein Gefühl für die Größenverhältnisse zu bekommen: Unsere 90 Manntage, entsprechen realistischerweise eher einer einzelnen Iteration, als den drei Zyklen, die wir für uns geplant haben. |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
219 |
9 | 220 %Wir werden deshalb ein paar Ungenauigkeiten bei unserem Verhalten im Kauf nehmen; versuchen aber natürlich, uns möglichst nahe an die Leitlinie RUP zu halten. |
7
1f955918cf53
lots of minor things; changed to english names
meillo@marmaro.de
parents:
6
diff
changeset
|
221 |
9 | 222 %Wir finden es trotzdem wichtig, diesen Prozess zu wählen, weil die theoretischen Inhalte der Vorlesung ``Softwaretechnik 1'' sich erst durch ihre tatsächliche Anwendung im realen Projekt richtig verfestigen können. |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
223 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
224 |
9 | 225 |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
226 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
227 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
228 \section{Konkrete Projektplanung} |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
229 |
9 | 230 Die konkrete Planung der einzelnen Zyklen und ihrer Meilensteine finden sich im \emph{Software Development Plan}. |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
231 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
232 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
233 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
234 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
235 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
236 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
237 |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
238 %%%%%%%%%%%%%%%%%%%% |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
239 \chapter{Inhaltliche Dimension} |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
240 |
11 | 241 In der zweiten Dimension wird festgelegt, \emph{wer} (Rolle), \emph{wie} (Aktivität), \emph{was} (Artefakt), \emph{wann} (Zeitpunkt) macht. Diese Elemente werden in Workflows vereint. |
10 | 242 |
243 Hier beschreiben wir, wie wir die vorgegebenen Workflows des RUP anpassen. | |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
244 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
245 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
246 |
9 | 247 \section{Business Modeling} |
248 | |
10 | 249 \subsection*{Zweck} |
11 | 250 Gemeinsames Verständnis zwischen Entwicklern und Anwendern schaffen. |
9 | 251 |
10 | 252 \subsection*{Anpassungen} |
11 | 253 Wir erstellen keinen Business Use Case, weil das Seminarsystem ein gestelltes, abgeschlossenes Szenario ist und nicht in bestehende Geschäftsabläufe eingebunden werden muss. |
9 | 254 |
10 | 255 \subsection*{Artefakte} |
256 \begin{tabular}{p{4cm}p{10cm}} | |
11 | 257 \rowcolor{gray09} Artefakt & \textbf{Glossary} \\ |
10 | 258 \rowcolor{white} Rolle & Fachliches Team, Kunde \\ |
259 \rowcolor{gray09} Aktivität & erstellen gemeinsam \\ | |
11 | 260 \rowcolor{white} Zeitpunkt & Inception, Ergänzungen jeder Zeit \\ |
10 | 261 \rowcolor{gray09} Review & Fachliches Team und Kunde durch gemeinsames Erstellen \\ |
262 \end{tabular} | |
9 | 263 |
264 | |
265 | |
266 \section{Requirements} | |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
267 |
10 | 268 \subsection*{Zweck} |
269 Ermitteln, was das System leisten soll. Die funktionalen Anforderungen erfassen. | |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
270 |
10 | 271 \subsection*{Anpassungen} |
8 | 272 Keine besonderen. |
273 | |
10 | 274 \subsection*{Artefakte} |
275 \begin{tabular}{p{4cm}p{10cm}} | |
11 | 276 \rowcolor{gray09} Artefakt & \textbf{Vision} \\ |
10 | 277 \rowcolor{white} Rolle & Fachliches Team, Kunde \\ |
278 \rowcolor{gray09} Aktivität & erarbeiten im Gespräch \\ | |
11 | 279 \rowcolor{white} Zeitpunkt & Inception \\ |
10 | 280 \rowcolor{gray09} Review & Fachliches Team und Kunde durch gemeinsames Erarbeiten \\ |
281 & \\ | |
11 | 282 \rowcolor{gray09} Artefakt & \textbf{Use Cases} \\ |
10 | 283 \rowcolor{white} Rolle & Fachliches Team, Kunde \\ |
284 \rowcolor{gray09} Aktivität & erarbeiten im Gespräch \\ | |
11 | 285 \rowcolor{white} Zeitpunkt & Inception und Elaboration \\ |
10 | 286 \rowcolor{gray09} Review & Fachliches Team und Kunde durch gemeinsames Erarbeiten \\ |
287 \end{tabular} | |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
288 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
289 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
290 |
9 | 291 \section{Analysis \& Design} |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
292 |
10 | 293 \subsection*{Zweck} |
11 | 294 Aufbau und Technologie des Systems festlegen. Festlegung, wie das System realisiert wird. |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
295 |
10 | 296 \subsection*{Anpassungen} |
11 | 297 Die Technologie und die Rahmenbedingungen der Umsetzung sind durch das Projekt vorgegeben und somit fix. |
8 | 298 |
11 | 299 Zum jetzigen Zeitpunkt arbeiten wir uns vor allem in die neue Technologie ein. Unsere Softwarearchitektur ist bisher vor allem eine Vorarbeit für später. |
8 | 300 |
10 | 301 \subsection*{Artefakte} |
302 \begin{tabular}{p{4cm}p{10cm}} | |
11 | 303 \rowcolor{gray09} Artefakt & \textbf{Software Architecture Document} \\ |
304 \rowcolor{white} Rolle & Team ``Technische Architektur'' \\ | |
10 | 305 \rowcolor{gray09} Aktivität & erstellt \\ |
11 | 306 \rowcolor{white} Zeitpunkt & Elaboration \\ |
10 | 307 \rowcolor{gray09} Review & Entwickler nach Änderungen \\ |
308 \end{tabular} | |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
309 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
310 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
311 |
8 | 312 |
9 | 313 \section{Implementation} |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
314 |
10 | 315 \subsection*{Zweck} |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
316 Systemteile entwickeln und zusammenfügen. Komponententests. |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
317 |
10 | 318 \subsection*{Anpassungen} |
319 Momentan besteht dieser Workflow in erster Line aus der Entwicklung von Prototypen jeder Art (Modelle, Templates, etc) um die Technologie zu erforschen. | |
320 | |
11 | 321 Konkrete Artefakte werden bisher nicht erstellt, weil es zum jetzigen Stand nicht sinnvoll ist nach festen Plänen vorzugehen. Unser Kenntnisstand ändert sich sehr schnell und wir wollen flexibel reagieren können. |
8 | 322 |
10 | 323 \subsection*{Artefakte} |
324 Keine definiert. | |
325 % \begin{tabular}{p{4cm}p{10cm}} | |
11 | 326 % \rowcolor{gray09} Artefakt & \textbf{Glossary} \\ |
10 | 327 % \rowcolor{white} Rolle & Fachliches Team, Kunde \\ |
328 % \rowcolor{gray09} Aktivität & erstellen gemeinsam \\ | |
11 | 329 % \rowcolor{white} Zeitpunkt & Inception (ergänzend jeder Zeit) \\ |
10 | 330 % \rowcolor{gray09} Review & \\ |
331 % \end{tabular} | |
8 | 332 |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
333 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
334 |
9 | 335 \section{Testing} |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
336 |
10 | 337 \subsection*{Zweck} |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
338 Test des Zusammenspiels der Komponenten. Funktionsweise des Systems gegen die Anforderungen prüfen. |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
339 |
10 | 340 \subsection*{Anpassungen} |
11 | 341 Wir erkunden eine neue Technologie. Unser Ziel ist es, in kurzer Zeit möglichst viele Bereiche und Möglichkeiten zu erkunden. Tests bremsen die Entwicklungsgeschwindigkeit zugunsten von Qualität. Unser Hauptaugenmerk ist es voran zu kommen, nicht komplett fehlerfreie Ergebnisse zu liefern. Deshalb verzichten wir komplett auf Software-Tests. So können wir die dadurch verfügbaren Ressourcen an anderer Stelle effektiv nutzen. Sobald wir nicht mehr nur Prototypen erzeugen, werden wir natürlich Software-Tests einführen. |
10 | 342 |
343 Alle Dokumente müssen von mindestens einer weiteren Person begutachtet werden. Die genauen Vorgaben stehen bei den Artefaktbeschreibungen in diesem Kapitel. | |
8 | 344 |
10 | 345 \subsection*{Artefakte} |
346 Keine definiert. | |
347 % \begin{tabular}{p{4cm}p{10cm}} | |
11 | 348 % \rowcolor{gray09} Artefakt & \textbf{Dokument Reviews} \\ |
10 | 349 % \rowcolor{white} Rolle & Beliebiger Mitarbeiter \\ |
350 % \rowcolor{gray09} Aktivität & prüfen gemeinsam das Dokument \\ | |
11 | 351 % \rowcolor{white} Zeitpunkt & nachdem Dokument erstellt/geändert wurde \\ |
10 | 352 % \rowcolor{gray09} Review & \\ |
353 % \end{tabular} | |
8 | 354 |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
355 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
356 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
357 |
9 | 358 \section{Deployment} |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
359 |
10 | 360 \subsection*{Zweck} |
361 Auslieferung des Systems an den Kunden und Inbetriebnahme. | |
362 | |
363 \subsection*{Anpassungen} | |
11 | 364 Solange wir keine lauffähigen Ergebnisse haben, vernachlässigen wir diesen Workflow. Wenn dies nicht mehr der Fall sein wird, muss eine Anleitung zur Inbetriebnahme des Programms erstellt werden. Ebenso muss dann der genaue Funktionsumfang des Systems beschrieben sein. |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
365 |
10 | 366 \subsection*{Artefakte} |
367 \begin{tabular}{p{4cm}p{10cm}} | |
11 | 368 \rowcolor{gray09} Artefakt & \textbf{Release Notes} \\ |
10 | 369 \rowcolor{white} Rolle & Projektleiter, Entwickler \\ |
370 \rowcolor{gray09} Aktivität & sollen erstellen \\ | |
11 | 371 \rowcolor{white} Zeitpunkt & Transition \\ |
372 \rowcolor{gray09} Review & anderer Entwickler vor der Auslieferung \\ | |
10 | 373 \end{tabular} |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
374 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
375 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
376 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
377 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
378 |
9 | 379 \section{Configuration \& Changemanagement} |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
380 |
10 | 381 \subsection*{Zweck} |
382 Verwaltung der zum Projekt gehörenden Daten. Versionierung der Daten. Change-Request-Management. | |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
383 |
10 | 384 \subsection*{Anpassungen} |
385 Alle Daten müssen im zentralen Project Repository abgelegt werden. | |
8 | 386 |
387 Jeder Mitarbeiter darf an jeder Stelle des Projekts Änderungen durchführen. | |
388 | |
10 | 389 Change-Requests werden nach dem vertraglich festgelegten Verfahren bearbeitet. |
9 | 390 |
10 | 391 \subsection*{Artefakte} |
392 Keine definiert. | |
393 | |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
394 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
395 |
8 | 396 |
9 | 397 \section{Projectmanagement} |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
398 |
10 | 399 \subsection*{Zweck} |
400 Planung des Projekts. Zwischen konkurrierenden Zielen vermitteln. Auf Risiken reagieren. | |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
401 |
10 | 402 \subsection*{Anpassungen} |
8 | 403 Keine besonderen. |
404 | |
10 | 405 \subsection*{Artefakte} |
406 \begin{tabular}{p{4cm}p{10cm}} | |
11 | 407 \rowcolor{gray09} Artefakt & \textbf{Software Development Plan} \\ |
10 | 408 \rowcolor{white} Rolle & Projektleiter \\ |
409 \rowcolor{gray09} Aktivität & erstellt \\ | |
11 | 410 \rowcolor{white} Zeitpunkt & Inception \\ |
10 | 411 \rowcolor{gray09} Review & Entwickler und Risikomanager nach Änderungen \\ |
412 & \\ | |
11 | 413 \rowcolor{gray09} Artefakt & \textbf{Risk Management Plan} \\ |
10 | 414 \rowcolor{white} Rolle & Riskmanager \\ |
415 \rowcolor{gray09} Aktivität & erstellt \\ | |
11 | 416 \rowcolor{white} Zeitpunkt & Alle Phasen \\ |
10 | 417 \rowcolor{gray09} Review & Komplettes Team in Inception Phase \\ |
418 \end{tabular} | |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
419 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
420 |
8 | 421 |
9 | 422 \section{Environment} |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
423 |
10 | 424 \subsection*{Zweck} |
425 Rahmenbedingungen schaffen. Bereitstellung von Hardware, Software und Know-How. | |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
426 |
10 | 427 \subsection*{Anpassungen} |
428 Die Hochschule Ulm stellt uns ein Project Repository zur Verfügung. | |
429 | |
430 Die offiziellen Kommunikationwege im Team sind das wöchentliche Teammeeting und die Projekt-Mailingliste. | |
8 | 431 |
10 | 432 \subsection*{Artefakte} |
433 \begin{tabular}{p{4cm}p{10cm}} | |
11 | 434 \rowcolor{gray09} Artefakt & \textbf{Development Case} \\ |
10 | 435 \rowcolor{white} Rolle & Projektleiter \\ |
436 \rowcolor{gray09} Aktivität & erstellt \\ | |
11 | 437 \rowcolor{white} Zeitpunkt & Inception \\ |
10 | 438 \rowcolor{gray09} Review & Komplettes Team in Inception Phase \\ |
439 & \\ | |
11 | 440 \rowcolor{gray09} Artefakt & \textbf{Tutorials} \\ |
10 | 441 \rowcolor{white} Rolle & Toolspezialist \\ |
442 \rowcolor{gray09} Aktivität & kann erstellen \\ | |
11 | 443 \rowcolor{white} Zeitpunkt & Alle Phasen \\ |
10 | 444 \rowcolor{gray09} Review & eine Person für die das Tutorial geschrieben wurde \\ |
445 \end{tabular} | |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
446 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
447 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
448 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
449 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
450 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
451 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
452 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
453 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
454 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
455 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
456 |
0 | 457 |
458 \appendix | |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
459 %\chapter{Glossar} |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
460 \chapter{Quellen} |
2
64246b8cbb50
added content for glossary; added info sources and links
meillo@marmaro.de
parents:
0
diff
changeset
|
461 \begin{itemize} |
9 | 462 \item Dokumentation zum \emph{Rational Unified Process} \\ (\texttt{http://www-306.ibm.com/software/awdtools/rup/}) |
11 | 463 \item Skript von Herrn Prof. Dr. Baer zur Vorlesung \emph{Softwaretechnik 1} an der Hochschule Ulm |
2
64246b8cbb50
added content for glossary; added info sources and links
meillo@marmaro.de
parents:
0
diff
changeset
|
464 \item http://wikipedia.org |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
465 \item \emph{Rational Unified Process - Best Practices for Software Development Teams} |
2
64246b8cbb50
added content for glossary; added info sources and links
meillo@marmaro.de
parents:
0
diff
changeset
|
466 \end{itemize} |
64246b8cbb50
added content for glossary; added info sources and links
meillo@marmaro.de
parents:
0
diff
changeset
|
467 |
9 | 468 $\ddagger{}$ The image \ref{fig:rationalunifiedprocess} is from the Rational Unified Process (software product) version 2003.06.12.01. This image and the names ``Rational Unified Process'' and ``RUP'' are copyright by Rational Software Corporation, now a division of IBM. |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
469 |
0 | 470 |
471 | |
472 \end{document} | |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
473 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
474 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
475 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
476 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
477 %%%%%%%% HowTo %%%%%%%%%% |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
478 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
479 % picture block |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
480 \begin{figure}[h] |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
481 \includegraphics[scale=0.65]{pictures/png/logistiksicht_v6} |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
482 \caption{Logistiksicht für SAP} |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
483 \label{fig:logistiksicht} |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
484 \end{figure} |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
485 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
486 % picture inline |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
487 \begin{wrapfigure}[11]{r}[0pt]{6.4cm} |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
488 \centering %OPTIONAL |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
489 \includegraphics[scale=0.7]{pictures/png/werkdresden} |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
490 \caption{OptiBoard Werk Dresden} |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
491 \end{wrapfigure} |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
492 |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
493 % tabellen |
10 | 494 \begin{table}[htb] |
6
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
495 \centering |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
496 \begin{tabular}{p{4cm}|p{3cm}|p{3.3cm}} |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
497 \rowcolor{gray07} \textbf{Teil} & \textbf{Menge} & \textbf{Einheit}\\ |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
498 \hline |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
499 \rowcolor{white} LED-Block & 105 & Stück\\ |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
500 \rowcolor{gray09} Feder & 105 & Stück\\ |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
501 \rowcolor{white} Platine & 1 & Stück\\ |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
502 \rowcolor{gray09} Chip & 1 & Stück\\ |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
503 \rowcolor{white} Kabel & 1 & Stück\\ |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
504 \rowcolor{gray09} Kunststoffgranulat & 350 & Gramm\\ |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
505 \end{tabular} |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
506 \caption{Mengenübersichtstückliste OptiBoard Pro} |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
507 \label{tbl:mengenPro} |
b9b93523dc05
a lot of content and restructuring and even more :-)
meillo@marmaro.de
parents:
4
diff
changeset
|
508 \end{table} |