|
| From: | Alex Forrest |
| Subject: | Re: [Adonthell-general] Merry Xmas!!! |
| Date: | Thu, 26 Dec 2002 22:09:52 +0000 |
Hey James, heres the minutes (phew!) for the first meetin. I didnt know the agenda, you had it you southern fairy. :P
Loadsa Love
Alex
Agenda: Sorry James?
<BR>
Format for documentation We discussed possible formats for the documentation for the project; the group agree upon the use of HTML as the format, as it is obviously accessible through event-horizon, is easy to implement, accessible and we can provide links for possible references.
<BR>
Basic Aims over the next few weeks The group agreed the neccessity for the whole group to be up to date on the UML covered in the lectures so far, by the end of the holiday period. The group discussed the possibility of assignments of speciality research we can be divided into three groups to each have th goal of learning and achieving guru status in obviously UML(advanced and beyond the scope of the course), HTML for documentation and other, Java(API/Swing) for the graphical user interface of the timetabling system and Java OOP advanced and algorithms, for the core programming of the project. A complete familiarity with the specification is a bare essential for everyone going away this christmas. <BR>
Rough ideas for the program <BR>
<BR>
The views There was discussion over the actual ueser interface, whether a login prompt may be a good idea, or even the possibility of a password prompt for certain areas of the program. The actual passenger view may be always displayed, no matter which level of access login. This is clearly seen in many other already professionally implemented ideas, such as the national rail and coach service websites, where no login gives normal restricted access to the basic website, and a higher level login or login here gives access to other administrative parts of the website. A real-time view will not always be needed a simple query is needed for most purposes. There may be a common config file with get and set methods.
<BR>
The passenger view Many ideas were discussed; the inclusion of pull down lists, the options. Whether each separate view would be its own java program, all referring to a central database and config file. The passenger view should be viewable to all three views by default.
<BR>
The network operator view There was discussion over the view which the net-op should have; a graphic interface with visual representations of the nodes, tracks and trains is necessary. We will assume constant speed for visual representation of the train journeys. There could be reference to the system clock for use with the graph.
<BR>
The group agreed much of the ideas should not be properly implemented until the UML is completed, and then assignments of the specialities can be done. There arose the possibility of splitting the group for the design, implementation and coding of the project, but one must first be completed before the next can be started successfully.
<BR>
Next meeting is to take place in Cholo on Tuesday 2-3pm.
| [Prev in Thread] | Current Thread | [Next in Thread] |