Coma(finally as good as finished...)

WS0405

Abstract: This is the developer's main page of the ``Conference Manager'' (Coma)-project of the winter term 2004/05. It collects most of the top-level information during the development process.

Version: Id: main.tex 5210 2005-02-08 06:29:03Z ms

Disclaimer: The material here -the webpages, the documentation, in particular the code ...- is maintained by the participants of the course, i.e., the students + the organizers. It is collected and made available for teaching purposes, in particular for non-profit purposes. Neither the university nor the organizers of the course offer any guarantee whatsoever concerning correctness, absence of errors, fitness for the purpose announced or a purpose assumed etc. In a word: have fun, learn, download if you wish, play around, but don't complain.

Requirement specification + data model

Review

Slides of the presentation

Where, what, when, who ...

8.2.05, 8o'clock -- 12 o'clock, in Ü2, our normal meeting room.

---

start	who	core	test	questions
8:15	tests	30		10
8:55	PHP 1	30	10	10
9:45	break
9:55	PHP2	30	10	10
10:45	Java	30	10	10
11:35	org	rest

Table 1: Schedule

---

Demo:

the machine, on which the server runs, is good old snert. Your demo should contain 2 parts

1. installation-demo: for the installation, this should be performed by an outsider, on a fresh account on snert. So provide some ``installation description'' (preferably fool proof, and not too complex), that you hand out to the ``fool'' who installs your tool on the new account. You may assume that the person can read ...
2. tool-in-action: ideally, your tool of course continues working after installation. However, to avoid delays (failure of installation and especially because after installation the data base is empty) you may switch to a running and already filled server, where you can demonstrate features of your tool. This part can be done by yourself (but the audience may require thing like ``What happens if you now klick down there'')
3. tool-under-stress: depending on how you plan to integrate the test-part of your part, also running tests could be part of the demo.

presentation:

you are required to present core ideas about your tool, your design, your group etc. Points you can address in that part are

• (short!) intro (no extensive blabla, no ``commercials'' ..., we do a moderately technical show.)
• structure of the tool: architecture, responsibilities, features, highlights, what's missing,
• about the development process:
  • locally in your group: how did you cooperate/coordinate? How much of your original plan was done? If something is missing, what went wrong? Which decisions have turned our good, which bad.
• globally: similar things about the global set-up of the course. What (if we would do it again) would you prefer to be done differently? And why?

Technical support:

Client machines:

there will be two laptops, with Linux running. One will have net access. This you can use to logon snert or to surf at snert. The machines have acroread running, so if wanted, one can be used for pdf slides. In case you want us to store slides on that machine, we need the file till Monday evening before the demo.

fresh accounts:

we will provide you with an fresh account on snert

own laptops:

you can of course use your own laptop. Probably, you won't be able to hook-on via ethernet-cable/DHPC, however. Whether WLAN works there, we don't know.

beamers:

there will be 2 beamers. Our laptops do synchronize with the beamer (we tested it).

Sources of information

BB

bulletin board: not obligatory, but perhaps useful.

Bugzilla

bugzilla: login via email-address + your chosen password (not the generated one, not the ssh-passphrase) For some hints, see also handout 3.

Repository:

The repository resides on the snert-machine. Write-access is password-protected, for browsing the current status, you can click here current repository status. Write access is granular in the following sense: each group can write only within its own domain of responsibilities. See also repository for fancier access.

examples:

some examples you can use for inspiration

• a ``call-for-papers'' to have a look how a conference advertisement for authors could look like.
• an empty ascii review form for some conference

Weekly meetings

---

0.		19. October		kick-off
1.		26. October		general jamboree
2.		2. November		Tools discussion
3.		9. November		Spec. presentations
4.		announcement (15.11), 16. November		group forming/next steps
5.		23. November		Various topics, in particular: status
5.		30. November		SQL shootout, communicaton problems, (blackboard for reference)
6.		7. December		status, various topics, progress?
7.		14. December		status/progress, SQL, testing, svn
8.		21. December		status/progress, nothing particular
9.		11. January		[status/progress], testing, DB problems
10.		18. January		status/progress report, plan for the rest
11.		25. January		nothing specific, date for end-demo
12.		1. February		last orders, handout 7
12.		8. February		``E-O-S'', short words about review, detailed info in the resp. slides

Table 2: Meeting minutes

---

Spec + tools groups

Other stuff

Tools potpourri & matrix

---

name	version	description	installed at		needed by
					developers					customers
			snert	lab	p1	p2	j	test	org	server	client
common development
ant	1.6.2	build tool	+	+	o	o	+	[+]	o	+	-
gnu make	3.80	build tool	+	+	o	o	-	o	+	+	-
subversion	1.0.9	CM	+	[+]	+	+	+	+	+	o	-
common basis
apache	2.0.51	web server	+	[-]	+	+	+	+	-	+	-
mysql	3.23.58	data base	+	[-]	+	+	+	+	-	+	-
``java''
jakarta tomcat	5.0.30	web server	+	-	-	-	+	+	-	+	-
java	1.5.0	language	+	+	-	-	+	+	-	+	-
java lib's	various	further libs	[+]	[+]	-	-	+	+	-	+	-
``php''
php	4.3.8	scripting lang.	+	-	+	+	-	+	-	+	-
php doc		doc generation	+	-	o	o	-	o	-	-	-
common testing
junit		unit testing	+	+	-	-	+	+	-	-	-
php unit		unit testing	+	+	[+]	[+]	-	+	-	-	-
puretester		web app. test	-	+	-	[-]	-	+	-	-	+
common spec + doc
jude		design	+	+	+	+	+	+	+	-	-
LATEX	tetex 2.0.2	doc	+	+	o	o	o	o	+	o	-
hevea	1.07	doc/html	-	+	o	o	o	o	+	-	-

Table 3: Tools, software, etc

---

External links

• J2SE
• J2EE
• EJB
• JSP
• Servelets
• JDBC
• JBoss App. Server
• Subversion
• PhP DOC
• Push2Test

Alternatives

start:

widely used

CyberChair:

some well-known conference manager, in a free and a (more modern, more stable etc) licensed version. It's based on python

openconf:

Paperdyne:

another commercial thing nice demo

Groups

---

Figure 1: Groups

---

PHP 1

PHP 2

Java

Test & quality assurance

Special assignment groups

Phase 1

Debriefing

1

With certain justified exceptions, for instance ``Klausur''. Ask for this exceptions, as they must be granted by us. Just not showing up and the rest of the groups tells us at showtime, is not enough.

2

Note that for the various java lib's there's a little confusions concerning the numbers (and file names) as some of the jar files which are offered for download at the download space of the java group are just duplicates (with the same version number, sometimes different names??) of the jars, which are installed anyway on snert as part of tomcat. One should base the tool on the official ones, as part of the chosen tomcat installation. Everything else invites trouble.

This document was translated from L^AT_EX by H^EV^EA.