Here are the project assignments: Administrative Tools: Shannon Academic Management Tools: Pati Instructor Management System: Matt Student Management System: George Registration Management System: Jansen and Jordan Backend/Server side Support & Database Management System: Jansen and Jordan Five of us talked for a bit after our DBMS class and I wanted to share the ideas/thoughts that we bounced around: - it would probably be good if each of us had a package for our code. It doesn't matter what each of us call our package, but we need to share that with Jansen and Jordan. - also, we need a common repository for the code so everyone has access to it, especially Jansen and Jordan. Jordan mentioned that he has some room that we use for this project. - each of us should come up with a draft list of classes and methods that we will be creating for our pieces. it just needs to be a draft at this point for Jansen and Jordan. - (I just thought of this one) since most of us use DrJava, which includes JUnit for testing, should we all create the test cases for our piece in it? or is there a better tool for this? Like FindBugs... - Java has an SQL API, so SQL may be used instead of Oracle. And a couple questions: - are we supposed to be accessing the .txt files for the data or should we be accessing the SQL tables? If it's the second option, then we could use the java.sql API for methods, etc. - what's the schedule for this project? how should we break it down? Thanks, PatiReceived on Tue Mar 24 2009 - 21:14:37 EDT
This archive was generated by hypermail 2.2.0 : Tue Mar 24 2009 - 21:14:49 EDT