\documentclass[12pt,fleqn,a4paper]{report}
\usepackage[english]{babel}
\usepackage{german}
\usepackage{amsfonts}
\usepackage{latexsym}
\usepackage{xspace}
\usepackage{epsfig}
\usepackage{psfrag}
\usepackage{graphicx}

\textheight	680pt
\textwidth	460pt
\topmargin	-40pt
\oddsidemargin	  5pt
\evensidemargin	  5pt
\parindent	  0pt

\begin{document}
\begin{titlepage}
\centerline{\large  PS Software Engineering I}
\vspace{0.5cm}
\hspace {2.3cm}
SE-001-2001
\hspace{5.2cm}
\today

\vspace{2cm}
\centerline{\Large\bf InfoWarrior}
\vspace{0.2cm}
\centerline{\Large\bf Example1}

\vspace{1cm}
\centerline{\bf Report}
\centerline{\bf }

\vspace {1cm}
\centerline{\large Dr. Schwaiger Roland}
\vspace{0.2cm}
\centerline{rschwaig@cosy.sbg.ac.at}
\vspace {1cm}
\centerline{Academic Supervisor Dr. Mag. Dipl.-Ing. Schwaiger Roland}

\vspace{1cm}
\centerline{\large Department of Computer Science}
\vspace{0.2cm}
\centerline{\large University of Salzburg}

\vspace{8cm}
Correspondence to: \\
\centerline{Universit\"{a}t Salzburg} \\
\centerline{Institut f\"{u}r Computerwissenschaften und Systemanalyse} \\
\centerline{Jakob--Haringer--Stra\ss e 2} \\
\centerline{A--5020 Salzburg} \\
\centerline{Austria}

\clearpage
\end{titlepage}

\title{\Large\bf InfoWarrior - Example1}

\author{{\large Dr. Schwaiger Roland}\\
{\small Department of Computer Science} \\
{\small University of Salzburg} \\
{\small A--5020 Salzburg, Austria} \\
{\small rschwaig@cosy.sbg.ac.at}}

\date{}

\maketitle

\begin{abstract}
Our goal is to step through the whole software engineering process in order to transform the requirements of a specific problem at hand into a model which may be implemented in a subsequent step. The specific problem description is below. Through the various steps of the process, s.a. requirements modeling, analysis, design we will utilize the unified modeling language (UML).
Our goal is to step through the whole software engineering process in order to transform the requirements of a specific problem at hand into a model which may be implemented in a subsequent step. The specific problem description is given below. Through the various steps of the process, s.a. requirements modeling, analysis, design we will utilize the unified modeling language (UML).
\end{abstract}

\tableofcontent


\chapter{Problem Statement}
We were contacted by a news agency, called ``e-News''. They asked us develop a system for information gathering and presentation (project name ``InfoWarrior'').

Potential users of the system are human data collectors and human data consumers. Other systems may, as well, play the part of data collectors and comsumers.

Thus there are at least two resulting scenarios:
\begin{itemize}
\item The collected information is handed over to other systems either actively or passively (XML has to be used).
\item The collected information is requested by human users. Thus the information has to be presented in an adequate way.
\end{itemize}

e-News noted as a prime requirement the ease of maintainance of InfoWarrior, e.g. no local installation of collection and presentation interfaces for the system. 
Further they want to easily change the presentation layout for human users of InfoWarrior.

In the first phase of the project we are asked and required to concentrate the project to the essentials. Nevertheless InfoWarrior should easily be expandable to further requirements.

\chapter{CRC Session}
\section{Goals}
For a detailed discussion see \cite{Ambler98}. Class responsibility collaborator (CRC) is a low-tech method for communication between developers and business domain experts (BDE). As the prime result business requirements are understood and identified. 

Originally CRC cards were introduced by Beck and Cunningham (\cite{BeckCunningham89}) as a method for teaching object-oriented (OO) thinking. A CRC card is divided into three sections. One section holds the name, the next holds the responsibilities (data and functionality), and the third holds collaborators.

Our goal in this context is to develop a CRC model\footnote{A CRC model is a collection of CRC cards that represents whole or part of a problem domain.} for the problem given in the beginning.

\section{CRC Session Planning}
Some aspects have to be thought of planning a CRC session:
\begin{itemize}
\item Put together a CRC modeling team: The roles are: {\em BDE} about four in order to get a broad view and experience of the problem domain at hand, {\em Facilitator} to coordinate the session, {\em Scribe} to write down the detailed business logic, {\em Observer} a passive role.
\item Organize the modeling room: Room with flip chart, whiteboard. Some index cards. A modeling table where the cards may be put and moved around. Chairs for the participants.
\item Do some brainstorming: Quite important before starting the session (see \cite{Ambler98} for relevant questions)
\item Explain the CRC technique.
\item Iteratively perform the steps of CRC modeling: Find classes, find responsibilities, define collaborators, define use-cases, arrange cards on table.
\item Perform use-case scenario testing.
\end{itemize}

\section{Interrelationship of CRC Modeling with other Modeling Techniques}
In figure~\ref{fCRCModel} the interconnection of the CRC Model with other models is shown.
\begin{figure}[hbt]
\centerline{\epsfxsize=12cm
\epsfbox{crcmodel.xfig.eps}}
\caption{Interconnection of the CRC model with other models.}
\label{fCRCModel}
\end{figure}
As seen from the figure a iterative and sequential process is defined where the various steps influence each other. So where to start? Some authors argue that the process shoud be started from use-cases and interface prototyping the detailing the process by means of the CRC model and further concretizing with the help of class modeling. In our context we start with the CRC model and will come back automatically to the use-case and intercase modeling.

Naturally one interation of the process will not be sufficient. Thus we have to iterate and therefore generate more and more detailed versions of the various models.

\chapter{Next Section} 
... here goes your text...

\appendix
\chapter{Protocols}
\section{31.10.2001}
\begin{enumerate}
\item Person responsible for protocol: Schwaiger
\item Participating persons: Schwaiger
\item Topics talked about: CRC model
\item New assignments:
\item Open questions:
\item etc.
\end{enumerate}


\bibliographystyle{ieeetr}
\addcontentsline{toc}{chapter}{Bibliography}
\bibliography{Paper}
\end{document}
