arkitekturdok_framsida.html


Date	Version	Name	Change
200302-06	0.1	Robert Johansson	The making of this document (DES, IMP, DOC).
2003-02-25	0.2	Robert Johansson	Update after scrutiny.
2003-03-01	0.3	Robert Johansson	Update after opposition.
2003-03-03	1.0	Per Andersson	Update after inspection.
2003-03-07	1.1	Robert Johansson	Added gui call diagrams.
2003-05-01	1.2	Christoffer Årstrand	Layout modified for HTML export.

DOCUMENT HISTORY

Architecture document

Editor: Robert Johansson

Version: 1.2

Date: 2003-05-01

PROJECT IDENTITY

The Shimpsons
PUM-group 6, 2002 - 2003
Linköping Institute of Technology
Department of Computer and Information Science (IDA)

Project members


Name	Responsibility	Telephone	E-mail
Per Andersson	Document responsible (DOK)	0733-742995	peran100@student.liu.se
David Akhvlediani	Implementation responsible (IMP)	013-4730999	davak342@student.liu.se
Robert Johansson	Design responsible (DES)	0705-382170	robjo442@student.liu.se
Lars Larsson	Customer responsible (KUND)	0705-973390	larla582@student.liu.se
Johan Marnetoft	Quality responsible (KVAL)	0706-008442	johma174@student.liu.se
Gustav Rosén	Project leader (PL)	0701-754456	gusro628@student.liu.se
Mikael Svärd	Test responsible (TEST)	0707-343272	miksv824@student.liu.se
Christoffer Årstrand	System responsible (SYS)	0707-733934	chrar273@student.liu.se

Mailing list for the entire group

pum6@und.ida.liu.se

Homepage

http://www.lysator.liu.se/~lunkwill/pum6

Customer

Sony Ericsson Mobile Communications AB

Customer contact

Wanqing Shi, wanqing.shi@sonyericsson.com

Sonia Sangari, sonia.sangari@sonyericsson.com

Mentor

Mustapha Skhiri, mussk@ida.liu.se

Course responsible

Uwe Assman, uweas@ida.liu.se

Abstract

This document describes the architecture of Audio Jury. It presents and motivates decisions made concerning architecture and gives a general understanding of how the system is going to work. This is accomplished by presenting which modules the system will consist of, as well as showing a prototype of the user interface.

A combination of use case diagrams and module descriptions will also show how the architecture fulfils the requirement specification.

The document is the basis on which the detailed design document will rely on.