\documentclass[12pt,fleqn,a4paper]{report}
\usepackage[english]{babel}
\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}
\vspace{0.5cm}
\hspace {2.3cm}
SE-001-2000
\hspace{5.2cm}
\today

\vspace{2cm}
\centerline{\Large\bf Aufgabe 1}
\vspace{0.2cm}
\centerline{\Large\bf }

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

\vspace {1cm}
\centerline{\large  \hfill }
\centerline{@cosy.sbg.ac.at \hfill @cosy.sbg.ac.at}
\vspace{0.2cm}
\centerline{\large \hfill }
\centerline{@cosy.sbg.ac.at \hfill @cosy.sbg.ac.at}
\vspace{-0.3cm}
\begin{flushleft}
\large{}\\
\normalsize{@cosy.sbg.ac.at}
\end{flushleft}
\vspace {1cm}
\centerline{Academic Supervisor Mag. Dipl.-Ing. Schwaiger Roland}

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

\vspace{5.5cm}
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 Aufgabe 1}

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

\date{}

\maketitle

\begin{abstract}
{\sl This document deals with the development of a software-system with the
working title ''Archaeological Data System - ADS'' for entering, administering
and presenting archaeological data via the internet.}
\end{abstract}

\tableofcontents


\chapter{Productanalysis}
The productanalysis aims at clarifying topics such as our customer's wishes
and requirements concerning the software, it shall give restrictions what the
software is not to do as well as point out questions which are to be discussed
with our customer.
\\ \\
As R. Yeh and P. Zave describe \cite{requirements1}, a great deal of time and
money is invested in maintenance of a software-product. To reduce this in order
to be more productive as you can concentrate on other projects, a very
important part of software-developement is to specify exactly the system's
requirements.\\
Yeh and Zave also mention 3 major steps which should be persued during this
phase of the software-project:

\begin{enumerate}
\item \textit{Problem identification:} One shall identify and describe the
needs of a system for certain purposes;
\item \textit{Problem understanding:} Collect and analyze information about the
system and its environment, as well as their interaction;
\item \textit{Problem specification:} Describe the behavior of the system.
\end{enumerate}

The following sections of course will provide the software's requirements -
this will therefore satisfy step 1. In order to do this completey, we need more
detailed information about our customer's wishes; questioning our customer will
therefore be the next main activity - this equals step 2. The 3rd step will be
covered as soon as enough information is available.
\\ \\
This chapter will be the product of these 3 steps.

\section{Introduction}
Our company was engaged to develop a software-system with the working title
''Archaeological Data System - ADS'' which first of all shall:

\begin{itemize}
\item Provide an interface via the world-wide-web enabling our customer to
enter archaeological data such as tombs, settlements or artefacts into a
central database.
\item Enable third parties to query the database for information via the
world-wide-web.
\item Present the data also via a virtual museum.
\end{itemize}

We are responsible for the design and implementation of this system including
the following points:

\begin{itemize}
\item Web-front-end to manipulate and display data.
\item The design and implentation of the database itself.
\item Maintain these services.
\item Host the database on a server or at least administer this work.
\end{itemize}

\section{General (I)}
As the database shall be accessible via a standard web-browser, we will not
develope an independant programme which could connect to the database for
example via TCP/IP. Just the web-front-end for web-browsers will be designed
and implemented.

\begin{itemize}
\item Has the customer already gained experience with a similar software or do
they already use one?
\item Is there currently a homepage or a special corporate design our
software-system has to be adopted to?
\item How much financial capital has been allocated for this project?
\item Are there any time-frames for parts of or the whole software-system?
\end{itemize}

\section{Database}
Concerning the database as well as the data itself there are several
questions:

\begin{itemize}
\item Approximately how many data-records will there be and what will they
contain? Will there just be ASCII-based data or also non-text formats such as
pictures, audio- or video-files?
\item Approximately of how many entries will a record consist?
\item As the database shall be searchable, which criteria will there be to be
searched for? (This can be necessary to know concerning the possible different
data-formats.)
\item Can the visitors who query the database via the web-front-end search
the whole database? Or will they just be able to access certain selections of
it such as the objects of the museum's current exhibition (see below for
details concerning the museum).
\item The data collectors can specify a record's entries the visitor can or can
not see when querying the database. Will these selections be global ones or
apply to archaeological objects differently. \\
E.g.: Imagine you have 50 tombs, each with the attributes place, who was
burried there and when it was found. A data collector's possible selection
could be ''place'' and ''who was burried''. Shall this apply on all 50 tombs,
or shall there be some among them with other selections to present to the
visitor?
\end{itemize}

\section{Entering Data}
There are two main groups who can enter data into the database:
\begin{enumerate}
\item Data collectors
\item Scientific data collectors
\end{enumerate}
Members of the first group will enter general data concerning the
archaeological object such as the place where it was found, while members of
the second group will add additional information such as interpretations and
publications concerning this object.

Questions are:
\begin{itemize}
\item Have the data collectors the right to manipulate all currently available
data?
\item What rights do the scientific data collectors have?
\item How many (scientific) data collectors will be working with the software?
\item How about the administrators mentioned below?
\item Who can create new rooms or showcases?
\item Who can edit already collected data?
\item How shall data be entered, especially if there are pictures or other
non-text formats?
\end{itemize}

So far besides our maintaining-team probabely the following four groups will
have contact with the software:
\begin{description}
\item[Data collectors:] They will enter general data concerning the
archaeological objects. They also can define relationships between different
types of data or specific records. Data collectors also can edit the virtual
museum where the objects are to be presented.
\item[Scientific data collectors:] They will enter more specific data such as
publications concerning the archaeological objects. Again they have the option
of defining relationships as mentioned before as well as editing the virtual
museum.
\item[Visitors:] They will just have the option to query the database for
information as well as to walk through the virtual museum.
\item[Administrators:] The administrators will be able to maintain and repair
small but urgent concerns, perhaps via the internet.
\end{description}

\section{Virtual Museum}
The software-system shall include a virtual museum where the visitors can walk
through and zoom into descriptions of archaeological objects and artefacts. The
museum shall not host all the data collected as the customer wants to perform
special exhibitions on current topics.
\begin{itemize}
\item What shall the museum look like?
\end{itemize}

We can exclude the option of (advanced) 3d-graphics as this definitely
conflicts with the required compatability to standard-webbrowsers.
Nevertheless, there are several options:


\begin{itemize}
\item Show photography-like pictures of the rooms, move within the museum by
clicking on arrows or signs.
\item Present the museum animated (via tools such as Quicktime, Flash,
Shockwave, etc.)
\item Just show a clickable room-map.
\item Others.
\end{itemize}

Nevertheless we need to know:

\begin{itemize}
\item What extent will the museum be of? How many rooms will it consist of?
\item Will there be several exhibitions at once?
\item As the data collectors shall be able to design the final showcases, one
option could be to offer them a given set of different showcases, frames and
boards for their data they can choose from. Another option would be to just
give them a list, which entries of the data-record will be shown. To what
extent shall the data collectors be able to edit the final look?
\end{itemize}

At this point we want to remind the customer of the fact that also this
virtual museum will be accessed via the internet. Unfortunately, still the
majority of visitors will have low-speed connections and therefore can not
enjoy the museum if there is too much (graphical) data to be transferred.

\section{General (II)}
Having a good idea now of either what the software-system shall offer or what
remains to be answered by the customer, there are some additional topics left
to be dealt with:\\
\\
The customer wants to produce represantative CD's as well as catalogues with
the virtual museum and its exhibitions.

\begin{itemize}
\item Shall these CD's also contain the whole database and therefore
offer full searchability or just the objects relevant to the exhibitions?
\item Who will be responsible for producing the CD's and the catalogues? How
will this process be dealt with?
\end{itemize}

Our management demands the use of XML in order to be as platform-independant
as possible. Besides the web-front-end, are there any other parts of the
software which will be implemented in XML?\\
\\
Perhaps the customer wishes to extract a set of, a single data-record or just
some entries of such. This functionality would require an export-option. Is
this necessary? If so, what shall be the data-format exported to (txt, xml,
etc.)?



\appendix
\chapter{Protocolls}
\section{11. October 2000}
In this first meeting our academic supervisor Mag. Dipl.-Ing. Schwaiger Roland
introduced us to the project. Several groups will work on the project and each
develope their own solutions. At the end of the semester, there will
presentations in order to let the others know, how each group solved their
problems.

\begin{description}
\item[Person responsible for protocoll:] .
\item[Participating persons:] The whole PS-group.
\item[Topics talked about:] Introduction to the project. General Information.
\item[New assignments:] Start with the productanalysis and prepare questions
for the upcoming meeting with our customer's represantative.
\item[Open questions:] None yet.
\end{description}



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