% .tex-tiedosto projektin dokumenttien latomiseksi.

% Kirjoitelmaluokka, tässä käytetään projektien projdoc-luokkaa.
\documentclass[twoside]{projdoc}

% Projektin nimi
\project{Muksis project}

% Luottamuksellisuus: käytä termiä 'Luottamuksellinen' tai 'Julkinen'
\publicity{Public}

% Versionumero: numerointikäytäntö on projektikohtainen
\version{0.3}

% Dokumentin nimi
\title{Project plan}

% Tekijät: huomaa aakkosjärjestys sukunimen mukaan
\author{Richard Domander}{Tuomas Mäenpää}{Teemu Nisu}{Tommi Teistelä}
% Puhelinnumerot: tekijöitä vastaava järjestys!
\authorphones{050-3482668}{040-7600465}{040-8349310}{045-6528709}
% Sähköpostiosoitteet: tekijöitä vastaava järestys!
\authoremails{dimadoma@jyu.fi}{tutamaen@jyu.fi}{tejonisu@jyu.fi}{totateis@jyu.fi}
% Etu- ja sukunimen alkukirjaimet: tekijöitä vastaava järjestys!
\authorinitials{RD}{TM}{TN}{TT}

% Tiivistelmä dokumentista: tämä ei siis ole tiivistelmä projektista,
% vaan tämän ko. dokumentin tarkoituksesta. 
\docabstract{This is the project plan document of application project Muksis. The document introduces readers to the area of this project explaning terms and giving background information and describing goals, available resources and management methods. In the later part of the plan the document hadles information about tasks, schedule and risks.} 

% Tiivistelmä projektista
\projectabstract{Project Muksis designs and implements new features, like black frame detection, support for DVB subtitles and search in MPEG TS to an open source media player application MPlayer and/or improves similar existing features for Matthieu Weber.}

% Avainsanat: dokumentin sisältöön liittyviä olennaisia asiasanoja: aakkosjärjestys, ensimmäinen sana isolla alkukirjaimella ja piste loppuun.
\keywords{Application project, black frame detecting, DVB, MPEG, search in MPEG TS, Muksis, MPlayer.}

% Varsinainen tulosteessa näkyvä ladonta alkaa
\begin{document}

% Tämä latoo versiohistorialle ympäristön, sen alapuolelle ladotaan
% versiohistoriataulukko. Esimerkin vuoksi tehty. 
\versionhistory

\begin{tabular}{|c|r|p{7cm}|p{3.5cm}|}
\hline
Version & Date & Changes & Authors \\
\hline \hline
0.1    &  19.9.2008  & First version. Introduction and contact information started. & TM\\
\hline
0.2    &  28.9.2008  & Introduction written. Terms, background, project goals and resources started. & TM\\
\hline
0.3    &  29.9.2008  & Recources written. & RD\\
\hline
\end{tabular}


% \projectinfo latoo ympäristön projektin tiivistelmälle, joka on 
% projektikohtainen.
% Projektin tiivistelmä ja tekijöiden tiedot ladotaan automaattisesti sivun
% alkuun. Eli lisättävä projektiorganisaation tiedot muiden kuin tekijäiden
% osalta sekä tarvittavat yhteystiedot. Alla tämä on tehty esimerkin vuoksi.
\projectinfo

\textbf{Customer:}

\begin{tabular}{p{6cm}p{5cm}p{3cm}}
~~~$\bullet$~~Matthieu Weber & \texttt{mweber@mit.jyu.fi} & 014-2603065 \\
\end{tabular}

\vspace{1truecm}
\textbf{Supervisors:}

\begin{tabular}{p{6cm}p{5cm}p{3cm}}
~~~$\bullet$~~Ville Isomöttönen & \texttt{vilisom@cc.jyu.fi} & 014-2604976 \\
\end{tabular}

\vspace{1truecm}
\textbf{Contact information:}

\begin{tabular}{p{6cm}p{9cm}}
~~~$\bullet$~~Mailing lists: & \texttt{muksis@korppi.jyu.fi} \\  
		                 
~~~$\bullet$~~Archives: & \texttt{https://korppi.jyu.fi/kotka/servlet/} \\
																	& \texttt{list-archive/muksis/} \\ 
                                     
~~~$\bullet$~~Room: & AgC 225.3 / 014-2604971
\end{tabular}
%----------------------------------------------------------------------------
% \mainmatter latoo automaattisesti sisällysluettelon ym. alkusivut, ja 
%% sen jälkeen alkaa dokumentin sisällysluettelossa näkyvät luvut.
\mainmatter

\chapter{Introduction} \label{chap:introduction}

Muksis is a student application project in the Department of Mathematical Information Technology at the University of Jyväskylä. During fall 2008 and the beginning of year 2009 the project designs and implements new features, like black frame detection, support for DVB subtitles and search in MPEG TS to an open source media player application MPlayer and/or improves similar existing features possibly found in original MPlayer code if found meaningful. The application is made for Matthieu Weber who is a senior assistant in the Department of Mathematical Information Technology at the University of Jyväskylä.

MPlayer is a free open source media player distributed under the GNU General Public License. It is a command line application with different optional graphical user interfaces. The program supports all major operating systems, including Linux and other Unix-like systems, Microsoft Windows and Mac OS X. MPlayer has support for very wide variety of media formats. In addition to its generous range of supported formats MPlayer can also save all streamed content to a file. 

The project will be performed in a group of four students: Richard Domander, Tuomas Mäenpää, Teemu Nisu and Tommi Teistelä. All members except Tuomas Mäenpää have a good knowledge of programming language C. Tommi Teistelä is also familiar with the MPlayer source code. Tuomas Mäenpää has mostly done web based developing before the project.

This document is an introduction to the work flow of the project Muksis. In Chapter \ref{chap:terms} the main terms used in this document are explained. Chapter \ref{chap:background} expounds background information and chapter \ref{chap:goals} construes and reasons the main goals. Chapter \ref{chap:resources} analyzes available resources, chapter \ref{chap:management} describes project management methods and chapter \ref{chap:tasks} explains about tasks, workload and division of labour. Project schedule is introduced in chapter \ref{chap:schedule} and finally chapter \ref{chap:risks} describes possible risks involved in this application project.

\chapter{Terms} \label{chap:terms}
Following terms appear on this document:

\begin{Ventry}{Agile software development}
\item[Agile software development] a software development process. Agile methods emphasize realtime communication and working software as the primary measure of progress using iterative development.
\item[Application project] course on The Department of Mathematical Information Technology.
\item[C] a general-purpose, high-level programming language. 
\item[DVB]
    Digital Video Broadcasting, a set of open standards for digital television. Defines various details about the physical and data link layer-level transmission of data, refers to existing MPEG standards for the actual format specifications where possible. The datastream itself is an MPEG-2 Transport Stream with some DVB-specific constraints and may contain multiple channels. 
\item[Iterative development] technique of developing and delivering incremental components of business functionality. A single iteration results in one or more bite-sized but complete packages of project work that can perform some tangible business function. Multiple iterations recurse to create a fully integrated product. 
\item[MPEG]
    The Motion Picture Experts Group, a working group of ISO/IEC. Also a common name for certain standards created by them. 
\item[MPEG-2]
    The MPEG standard specifying video, audio and related format specifications, primarily used for DVDs and digital television broadcasting. 
\item[User story] a software system requirement formulated as one or two sentences in the everyday language of the user.
\end{Ventry}

\chapter{Background} \label{chap:background}

\section{Documents}
The following documents will be realized during the project:
\begin{itemize}
\item \textbf{Architecture report} explains meaningful information about MPlayer stucture.
\item \textbf{Application report} describes how new features work.
\item \textbf{Project plan} describes about the meaning of the project. The document introduces readers to the area of this project and describing goals, resources and management methods used in the project. It also contains information about tasks, workload, division of labour, schedule and risks.
\item \textbf{Requirement analysis(?)} 
\item \textbf{Project report}
\item \textbf{Source code}
\item \textbf{Installing introduction(?)}
\item \textbf{Resource management report}
\item \textbf{Showcase reports (esittelyraportit)}
\item \textbf{Test report}
\item \textbf{E-mail archive}
\end{itemize}

All documents are written in english, except showcase reports that are in finnish.

\chapter{Project goals} \label{chap:goals}
- Tommi
\section{Patch for MPlayer community}
\section{Patch for Matthieu Weber}

\section{Software}

\section{Other results}

\chapter{Resources} \label{chap:resources}

This chapter describes the available resources for project Muksis.

\section{Recource constraints}
One ECTS credit (op, opintopiste) equals about 27 hours of work [1], so a student can expect to work between 270 and 400 hours for the project (10-15 op for the course). The team members don't have many other courses simultaneously, so it won't be challenge for anyone to allocate the required time. If the allocated time is not enough the features will be at least partially implemented, because of the iterative process used in this project. 

\section{The team}
The team consists of four mathematical information technology majors. The supervisors tried to form as heterogenous team as possible from the course applicants. Still, all members meet the requirements set for the course, and this fall all selected were quite advanced in their studies.  

\section{Physical resources}
The project team has been given the room AgC225.3 inside the project space AgC223.1. In the room there are four computers (1/member) and office supplies. The team can also use the project space, but a reservation has to be made beforehand. The printer in project space and MIT department's copier can be used for project documents. Also a small "library" of technical books is available, but most of the technical documents needed is provided by the client, Matthieu Weber. 

The team can request further software installations and resources (for example, Trac) from MIT's PC support. Team members are not allowed to install programs. The team chose Linux and CodeBlocks IDE, but kept one Windows machine just in case. The team can also get a projector and a digital audio recorder for the meetings. 

\section{Supervisors}

The supervisor in charge is Ville Isomöttönen from MIT. He supervises all aspects of the project and especially its planning, process, management, and general state. He also acts as a sort of mediator between the client and the team. There currently is no technical supervisor for the project, but everyone in the team has some experience with C. Linux OS and CodeBlocks IDE are familiar too for most of the members, so they can instruct those less versed. Weber has specific technical knowledge about the 
subject, so the team will cope even if no technical supervisor is found, altough lack of one presents unique risks.

\chapter{Management methods} \label{chap:management}
\section{Meeting}
-official meetings
-Other meetings
-methods: m


\chapter{Tasks, workload and division of labour} \label{chap:tasks}

\chapter{Schedule} \label{chap:schedule}

\chapter{Risks} \label{chap:risks}
- Teemu
-What could make project to fail
--MPlayer's source code changes much during project

\chapter{Summary} \label{chap:summary}

%LÄHTEET
\begin{thebibliography}{1}
%Katso kirjoitusohjeen luku 2.3 ja 2.4.
%\bibitem[1]{Jok05} Jokinen, R., ''Ohjelmistoprosessit'', Helsinki: Otava, 2005.
\bibitem[1]{credit}
University of Jyväskylä; KIEPO termipankki, refrenced 29.9.2008 \\
\texttt{http://www.jyu.fi/hum/laitokset/solki/tutkimus/projektit/kiepo/termipankki/opintopiste/?searchterm=opintopiste}
\end{thebibliography}

%LIITTEET
\begin{appendix}

\chapter{First appendix}

\end{appendix}

% Dokumentin  lopetus
\end{document}
