Mercurial > docs > Development-Case
annotate development-case.tex @ 5:303fa01dce67
added Makefile
author | meillo@marmaro.de |
---|---|
date | Wed, 16 Jan 2008 11:46:50 +0100 |
parents | a967aa02ee99 |
children | b9b93523dc05 |
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} | |
68 \ihead{Online Seminarbuchungssystem} | |
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} | |
73 \ifoot{} %~~~~~~~~~~~~~~~~~~~\footnotesize Christoph Galler} | |
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} | |
94 {\normalsize\textsc{Gruppe 2: Rui Gu, Wei Zhu, Veysel Imamoglu, Dimitar Dimitrov, \\Karl Oppermann, Nathalie Hrycej, Markus Schnalke, Christoph Galler}} \par | |
95 \vspace*{0.6cm} | |
96 \Large \textbf{Online-Seminarbuchungssystem} \par | |
97 \Huge \textbf{Development Case} \par | |
98 \vspace*{0.8cm} | |
99 \Large \textbf{Verfasser: Markus Schnalke} \par | |
100 {\large{} \par | |
101 \vspace*{0.7cm} | |
102 {\textsc{Ulm, \today}}} \par | |
103 \vspace*{5cm} | |
104 {\normalsize\textsc{Betreut durch: \\ | |
105 Prof. Dr. Klaus Baer \\ | |
106 Hochschule Ulm \\ | |
107 Prittwitzstra{\ss}e 10\\ | |
108 89075 Ulm\\}} | |
109 \end{center} | |
110 \vfill | |
111 \end{titlepage} | |
112 | |
113 % \addsec{Bitte beachten} | |
114 Version vom \today: Das Dokument befindet sich noch im Aufbau, \"{A}nderungen sind dadurch jederzeit M\"{o}glich. | |
115 \addsec{Version dieses Dokuments} | |
116 \begin{tabular}{|p{1.5cm}|p{3.cm}|p{1.6cm}|p{2cm}|p{1.4cm}|p{4cm}|} | |
117 \hline | |
118 \multicolumn{5}{|l}{\parbox[0pt][3.4em][l]{12cm}{\vspace{0.2cm}\large Dokument: \textbf{Name des Dokumentes} \newline \emph{ Online-Seminarbuchungssystem}}} & \multicolumn{1}{r|}{\parbox[0pt][3.4em][r]{1.9cm}{\includegraphics*[scale=0.25]{pictures/png/logo_hsu}}} \\ | |
119 \hline\hline | |
120 \hoehe{\textbf{Version}} & \textbf{Person} & \textbf{Aktion} & \textbf{Datum} & \textbf{Status} & \textbf{Kommentar} \\ | |
121 \hline\hline | |
3
5084c6cb99f2
added short explanations to all workflows; german names for workflows, etc; minor stuff
meillo@marmaro.de
parents:
2
diff
changeset
|
122 0.1 & Markus Schnalke & E & 2007-11-27 & O & Erste Version \\ |
0 | 123 \hline |
3
5084c6cb99f2
added short explanations to all workflows; german names for workflows, etc; minor stuff
meillo@marmaro.de
parents:
2
diff
changeset
|
124 0.2 & Markus Schnalke & AE & 2008-01-13 & O & Neue Struktur des Dokuments \\ |
5084c6cb99f2
added short explanations to all workflows; german names for workflows, etc; minor stuff
meillo@marmaro.de
parents:
2
diff
changeset
|
125 \hline |
5084c6cb99f2
added short explanations to all workflows; german names for workflows, etc; minor stuff
meillo@marmaro.de
parents:
2
diff
changeset
|
126 0.3 & Markus Schnalke & AE & 2008-01-14 & O & Glossar erstellt \\ |
0 | 127 \hline |
128 \end{tabular} | |
129 {\footnotesize\vspace*{-0.1cm}Aktion: E – Erstellung; AE – \"{A}nderung; QS – Review; AB – Abnahme} \par | |
130 {\footnotesize\vspace*{-0.4cm} Status: O – Offen; D – Diskussion; A – Akzeptiert} | |
131 \clearpage | |
132 | |
133 % Inhaltsverzeichnis | |
134 \setcounter{tocdepth}{3} | |
135 %\renewcommand\contentsname{"Uberblick} | |
136 \tableofcontents | |
137 | |
138 \clearpage | |
139 %\setcounter{tocdepth}{3} | |
140 %\renewcommand\contentsname{Detailliertes Inhaltsverzeichnis} | |
141 %\tableofcontents | |
142 %\clearpage | |
143 % | |
144 % Inhalt | |
4
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
145 % \input{development-case-content} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
146 |
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 \chapter{Einleitung} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
150 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
151 \section{Zweck} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
152 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
153 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
|
154 |
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 \section{Definitionen und Abkürzungen} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
157 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
158 Die verwendeten Begriffe sind im Projekt-Glossar erklärt. Bei Bedarf kann dort nachgeschlagen werden. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
159 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
160 \textbf{Workflow} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
161 Aufeinander folgende Aktivitäten die ein messbares Ergebnis erzeugen. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
162 %The sequence of activities performed in a business that produces a result of observable value to an individual actor of the business. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
163 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
164 \textbf{Entwicklungsprozess} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
165 Definiertes Vorgehensmodell zur Erstellung einer Software. Ein Entwicklungsprozess soll die Softwareentwicklung übersichtlicher gestalten und die Komplexität beherrscbar machen. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
166 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
167 \textbf{Zyklus} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
168 Ein kompletter Durchlauf der vier Phasen: Konzeption (Inception), Entwurf (Elaboration), Konstruktion (Construction) und Übergabe (Transition). |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
169 %One complete pass through the four phases: inception, elaboration, construction and transition. The span of time between the beginning of the inception phase and the end of the transition phase. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
170 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
171 \textbf{Iteration} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
172 Eine geplante Abfolge von Aktivitäten mit einem messbaren Ergebnis, die in einem Release enden (intern oder extern). |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
173 %A distinct sequence of activities with a base-lined plan and valuation criteria resulting in a release (internal or external). |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
174 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
175 \textbf{Phase} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
176 Die Zeit zwischen zwei bedeutenden Projekt-Meilensteinen. Während einer Phase werden, eine festgelegte Menge an Aufgaben bearbeitet, Artefakte erstellt und die Entscheidung gefällt, ob man in die nächste Phase einsteigt, oder nicht. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
177 %The time between two major project milestones, during which a well-defined set of objectives is met, artifacts are completed, and decisions are made to move or not move into the next phase. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
178 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
179 \textbf{RUP} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
180 Der Rational Unified Process (RUP) ist ein objektorientiertes Vorgehensmodell zur Softwareentwicklung und ein kommerzielles Produkt der Firma Rational Software. Der RUP ist ein iterativer Entwicklungsprozess. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
181 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
182 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
183 \textbf{Iterativer Entwicklungsprozess} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
184 Ein Entwicklungsprozess, der in Iterationen unterteilt ist. Dies ermöglicht Flexibilität, Risiken werden frühzeitig erkannt und es wird berücksichtigt, dass sich Anforderungen während eines Projektes oftmals ändern. |
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 \textbf{Manntag} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
187 Ein Manntag ist die Menge an Arbeit, die eine Person durchschnittlich an einem Arbeitstag (8 Stunden) schafft. Man verwendet diesen Begriff, um Schätzungen für die Gesamtmenge an Arbeit für die Erledigung einer Aufgabe zu errechnen. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
188 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
189 \textbf{Release} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
190 %Die fertige und veröffentlichte Version einer Software wird als Release bezeichnet. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
191 %A subset of the end-product that is the object of evaluation at a major milestone. A release is a stable, executable version of product, together with any artifacts necessary to use this release, such as release notes or installation instructions. A release can be internal or external. An internal release is used only by the development organization, as part of a milestone, or for a demonstration to users or customers. An external release (or delivery) is delivered to end users. A release is not necessarily a complete product, but can just be one step along the way, with its usefulness measured only from an engineering perspective. Releases act as a forcing function that drives the development team to get closure at regular intervals, avoiding the "90\% done, 90\% remaining" syndrome. See also prototype, baseline. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
192 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
193 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
194 \section{Verweise} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
195 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
196 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
197 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
198 |
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 \chapter{Entwicklungsprozess} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
203 \section{Überblick} |
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 Wir werden unser Projekt nach dem Rational Unified Process (kurz RUP) entwickeln. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
206 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
207 Der RUP ist ein dynamischer und iterativer Entwicklungsprozess, der das Projekt in zwei Dimensionen betrachtet. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
208 Er ist ausführlich spezifiziert und umfangreich dokumentiert. (http://www-306.ibm.com/software/awdtools/rup/). |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
209 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
210 An sich ist der RUP für große Projekte, mit vielen Mannjahren, ausgelegt. Wir haben uns trotzdem für den RUP entscheiden, da wir ihn in der Vorlesung Softwaretechnik 1 ausführlich behandelt hatten und wir dieses Theoriewissen nun in der Praxis anwenden wollen. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
211 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
212 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
213 \section{Anpassungen} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
214 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
215 Es gilt also diesen mächtigen und umfangreichen Entwicklungsprozess für unser klares Projekt abzuspecken und anzupassen. Dies ist natürlich nicht ganz einfach, da unsere 85 Manntage realistischerweise eher einer einzelnen Iteration entsprechen, als den drei Zyklen, die wir für uns geplant haben. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
216 Wir werden deshalb ein paar Ungenauigkeiten bei unserem Verhalten im Kauf nehmen; versuchen aber natürlich, uns möglichst nah an die Leitlinie RUP zu halten. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
217 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
218 Wir werden drei Zyklen des Projekts durchführen. Insgesamt soll das Projekt sechs Zyklen umfassen, von denen die letzten drei Zyklen aber nur grob geplant werden. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
219 Jeder Zyklus wird circa vier Wochen umfassen (18 Manntage). An dessen Ende ein Release steht. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
220 Iterationen innerhalb der Zyklen werden wir, aufgrund der kurzen Zyklen, außen vor lassen. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
221 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
222 Die einzelnen Phasen (zweite Dimension) in den Zyklen versuchen wir, so gut es geht, zu berücksichtigen. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
223 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
224 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
225 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
226 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
227 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
228 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
229 \chapter{Projektplanung} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
230 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
231 siehe \emph{Projektplan} diesbezüglich |
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 \chapter{Kern-Workflows} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
238 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
239 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
240 \subsection{Geschäftsprozessmodellierung} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
241 (Business Modeling) |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
242 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
243 Dokumentation der relevanten Geschäftsprozesse in Use Cases, mit dem Ziel eines gemeinsamen Verständnisses zwischen Entwicklern und Anwendern. |
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 \paragraph{Artefakte} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
246 \begin{itemize} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
247 \item Glossary |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
248 \item Use-Case |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
249 \item Use-Case Model |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
250 \item Vision |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
251 \end{itemize} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
252 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
253 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
254 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
255 \subsection{Anforderungen} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
256 (Requirements) |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
257 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
258 Ermitteln, was das System leisten soll. Die funktionalen Anforderungen sollen erfasst werden. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
259 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
260 \paragraph{Artefakte} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
261 \begin{itemize} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
262 \item Use-Case |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
263 \item Use-Case Model |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
264 \item Vision |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
265 \end{itemize} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
266 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
267 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
268 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
269 \subsection{Analyse \& Design} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
270 (Analysis \& Design) |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
271 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
272 Aufbau und Technologie des Systems festlegen. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
273 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
274 \paragraph{Artefakte} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
275 \begin{itemize} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
276 \item Software Architecture Document |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
277 \end{itemize} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
278 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
279 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
280 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
281 \subsection{Implementierung} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
282 (Implementation) |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
283 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
284 Systemteile entwickeln und zusammenfügen. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
285 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
286 \paragraph{Artefakte} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
287 |
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 \subsection{Test} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
290 (Testing) |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
291 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
292 Funktionsweise des Systems gegen die Anforderungen prüfen. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
293 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
294 Da wir eine neue Technologie erkunden, macht Test keinen wirklichen Sinn. Unser Ziel ist es, in kurzer Zeit möglichst viele Bereiche und Möglichkeiten zu erkunden. Dabei würde Testing nur bremsen. Unser Hauptaugenmerk ist es vorran zu kommen, nicht komplett fehlerfreie Ergebnisse zu liefern, deshalb verzichten wir komplett auf diesen Workflow. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
295 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
296 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
297 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
298 \subsection{Verteilung} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
299 (Deployment) |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
300 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
301 Auslieferung des Systems an den Kunden und Inbetriebnahme. Schulung der Benutzer. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
302 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
303 \paragraph{Artefakte} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
304 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
305 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
306 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
307 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
308 \section{Unterstützungs-Workflows} |
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 \subsection{Konfigurations- \& Änderungsmanagement} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
311 (Configuration \& Changemanagement) |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
312 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
313 Verwaltung der zum Projekt gehörenden Daten. Versionierung und Konsistenz. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
314 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
315 \paragraph{Artefakte} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
316 \begin{itemize} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
317 \item Project Repository |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
318 \end{itemize} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
319 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
320 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
321 \subsection{Projektmanagement} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
322 (Projectmanagement) |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
323 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
324 Zwischen konkurrierenden Zielen vermitteln. Auf Risiken reagieren. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
325 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
326 \paragraph{Artefakte} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
327 \begin{itemize} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
328 \item Software Development Plan |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
329 \item Iteration Plan % FIXME |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
330 \end{itemize} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
331 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
332 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
333 \subsection{Entwicklungsumgebung} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
334 (Environment) |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
335 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
336 Bereitstellung von Hardware, Software und Know-How. |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
337 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
338 \paragraph{Artefakte} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
339 \begin{itemize} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
340 \item Development Case |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
341 \item Tools |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
342 \item User Interface Guidlines % FIXME |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
343 \end{itemize} |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
344 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
345 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
346 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
347 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
348 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
349 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
350 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
351 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
352 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
353 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
354 |
a967aa02ee99
development case: everything in one file now
meillo@marmaro.de
parents:
3
diff
changeset
|
355 |
0 | 356 |
357 \appendix | |
358 \chapter{Glossar} | |
359 \chapter{Quellen und Links} | |
2
64246b8cbb50
added content for glossary; added info sources and links
meillo@marmaro.de
parents:
0
diff
changeset
|
360 \begin{itemize} |
64246b8cbb50
added content for glossary; added info sources and links
meillo@marmaro.de
parents:
0
diff
changeset
|
361 \item Dokumentation zum \emph{Rational Unified Process} |
64246b8cbb50
added content for glossary; added info sources and links
meillo@marmaro.de
parents:
0
diff
changeset
|
362 \item Skript von Herrn Baer zur Vorlesung \emph{Softwaretechnik 1} an der Hochschule Ulm |
64246b8cbb50
added content for glossary; added info sources and links
meillo@marmaro.de
parents:
0
diff
changeset
|
363 \item http://wikipedia.org |
64246b8cbb50
added content for glossary; added info sources and links
meillo@marmaro.de
parents:
0
diff
changeset
|
364 \end{itemize} |
64246b8cbb50
added content for glossary; added info sources and links
meillo@marmaro.de
parents:
0
diff
changeset
|
365 |
0 | 366 |
367 | |
368 \end{document} |