SE2006:group bar:minutes

From Earlham Cluster Department

(Difference between revisions)
Jump to: navigation, search
(Apr 10)
 
(16 intermediate revisions not shown)
Line 217: Line 217:
==Apr 10==
==Apr 10==
-
 
-
Aybars, where are our notes?
 
* Geocoder ideas (Colin & Toby):
* Geocoder ideas (Colin & Toby):
Line 231: Line 229:
* Data formatter (Alex):
* Data formatter (Alex):
** for tomorrow: create XML schema for markers & polylines (to be fed to UI)
** for tomorrow: create XML schema for markers & polylines (to be fed to UI)
 +
 +
* Estimation of an average time left per person to be submitted on Tuesday.  According to our statistical extrapolations we have a gigantic amount of more work to do.
 +
 +
==Apr 11==
 +
 +
* Created a brain-storm-like-map where we created the user interface on board.  We discussed a range of problems and solutions.  Topics included:
 +
**The user interface design
 +
** XML
 +
** Tomcat
 +
** ScrAPI to Tomcat connection
 +
** Tomcat to user interface connection
 +
 +
==Apr 12==
 +
 +
* We split into groups and:
 +
** Developed the user interface design.  We are trying create:
 +
*** Website intra-communication where different parts of the website can change the other parts on event calls
 +
*** Create the basis for connection with Tomcat server
 +
*** Nice design
 +
** Streaming database insertion
 +
** Worked on the Tomcat server
 +
 +
==Apr 17==
 +
 +
* Tomorrow is the due date for the beta version, everyone is pretty much stressed out.  We worked on everything, which was mostly the user interface and debugging.
 +
 +
* We worked on database and database-user interface relation.
 +
 +
* Debugging on scrAPI and some efforts for better standardization.
 +
 +
==Apr 19==
 +
 +
* We have created a list of tasks, and decided on their priorities and how much more we need to learn to accomplish those tasks.
 +
 +
* We created a bunch of design ideas for the user interface.
 +
** How will the data be displayed?
 +
** Where will it be displayed?
 +
** How will a bunch of data be displayed?
 +
** What will be the displaying options?
 +
 +
==Apr 24==
 +
 +
* At this time, most of our work focuses on debugging.  Most of our ideas of the big picture are implemented, but a lot of things work incorrectly or insufficiently.  Today we concentrated on:
 +
** Testing
 +
** JavaScript related problems (these problems are bugging the group deeply) and understanding JavaScript abnormalities
 +
** General debugging
 +
 +
==Apr 25==
 +
 +
* We worked again mostly on debugging (we are trying to get this mostly done until our next deadline, thursday morning).
 +
 +
* Debugging list includes:
 +
** Bug #2: "Save source metadata in database"
 +
** Some test files
 +
** Objects within JavaScript
 +
 +
==Apr 26==
 +
 +
* Tomorrow is the last deadline before the actual submission date and the presentation.
 +
 +
* We are overstressed and working on getting things done.  Our list includes:
 +
** User Interface, especially the "Regional Stats."  Being the middle box in the right, this gives summarized average information about the points in the screen.
 +
** Some JavaScript debugging
 +
** Some general debugging to get it generally ready
 +
** Metadata/database stuff
 +
 +
==Apr 30==
 +
 +
* Tomorrow is the actual submission and presentation day.  Today is the last group meeting for software engineering.
 +
 +
* We are doing some last minute polishing stuff and getting ready for presentation.  Our software seems mostly ready for presenting and is open to further development.

Latest revision as of 02:12, 1 May 2006

Contents

Feb 15

Possible meeting time: Working M/W/F in the evening for 1 or 2 hours starting the 27th. Toby, Kevin, and I are going to be working this weekend on clustcomp projects and then going to a conference on Feb 22-26.


Feb 28


Mar 1

Mar 6

We compared three of our Kerasotes lab scripts. We apparently all wrote them in PHP. The best innovations we found were Toby's data point definition abstraction and test suite. In essence, the data point definition abstraction allows one to describe a data source and data points that one would like to harvest in a general manner. The test suite is a basis for more general testing of the software that we will write. Also of note, were some of our findings as far as regular expressions. For instance, as a group we learned how to make a regular expression not greedy and how to not save a group (?).
Attached you will find an image of our general model thus far. We have already incorporated some of the ideas discussed in this session, including a more general data point abstraction and streamlined data flow between the programmer API, database, and WUI. As part of our plan, we intend to use Java as the base language, XML for temporary data storage and transfer, PostgreSQL or MySQL for data storage, and XHTML Transitional and JavaScript for the WUI.

Mar 7

Mar 8

Mar 13

Mar 14

Mar 15


Mar 27

Mar 28

Mar 28

Mar 31

April 3

(Toby standing in for Aybars)

Questions for class tomorrow:

Apr 4


Apr 5

Apr 10

Apr 11

Apr 12

Apr 17

Apr 19

Apr 24

Apr 25

Apr 26

Apr 30

Personal tools
Namespaces
Variants
Actions
websites
wiki
this semester
Toolbox