Business Analysis

Presented an overview of their work on filling in the Business Vision template

Their work helped us find immediately a miscommunication of the situation. 

Due on Nov. 1st

  1. Business Use Case
  2. Business Vision
  3. Risk List


Reported they hadn't found time to meet since last week.

Due on Nov. 1st

  1. Vision (John plans to do for next week)
  2. Use Case Models (rest of group)

Project Manager

  1. Iteration plan
  2. Software Development Plan


Business Modeling

Discussed the following modifications to the business documents

Business Vision


Vision Statement: Discussed the term “user” and its definition

Global Use Cases

Modified our previous global use case which specified the way the software interacts on a very high level.  Several alternative methods were discussed to decide how the software should function when a user who is already authenticated to use one resource attempts to use a second resource. 

Have the user re-authenticate.  Pros: Very Secure Cons: Too much overhead for the user.  Trent would offer no advantage over existing solutions

Have the user verify their identity using a string which is not their password and is only good once.  Pros: a bit more secure than above because actual secrets don't go over the network more than once.  Cons: same as above

Keep the connection between Trent and the user open the entire time and simply prompt the user to confirm whenever they try and connect to a new resource.  They can also enter their secret again to up their privileges. Pros: Simplicity is the key to security.  Little overhead for each new connection Cons: None known.


2 hours


2 hours



Groups were assigned which correspond to the tasks on the Wiki homework page.

Jeremy, since you weren't there to pick, you were put in group three which will do a review of the documents generated by the other two groups.

I have sent this to the TA, so the first part of the assignment is done. We have until the 15th to complete the remainder of the frist assignment

Our next meeting will be Tuesday Feb 13th from 7-9pm in a location to be determined. Subsequent meetings will be every Tuesday 7-9pm.

For the newcomers, please visit
Especially Jeremy who missed the meeting and let us know if you are confused about anything. You'll find all the documents under the "Documentation manager" of sourceforge.

PERL was decided to be the language of choice. Information can be found here, An informative (basic) perl tutorial can be found here: Perl Tutorial

Versions of perl are available on most all campus *nix machines including the CSIL machines and EWS for sure. I'm not sure if students has perl or not. You can find out by typing "perl". If you don't get an error, then the machine has perl. You can also download perl for almost any platform including windows ( is easiest to install). In any case, if anyone has perl questions, please forward to the list and someone will help you out. The tutorial mentioned doesn't cover object oriented Perl, because I couldn't find a good tutorial for that, so if someone else has a good resource please point us in the right direction.

We also devised a list of goals and a tentative vision statement for the semester.

Vision: Only web-based operation, Only passwords, no other forms of auth to start

Pair programming and testing will be strongly encouraged. In Iteration 1 a framework for testing will also be implemented.

If anyone has questions, comments, or nasty remarks, please let me know.


Main points:

People stated preferences on which language they'd prefer to work with, but I was a complete idiot and forgot to write them down. Please, everyone mail me your preference so I can record it.

Tomorrow I hope to lay out java framework for the rest of the modules, frank and his posse will do the same, though I can't attest to when.

Java Notes

Javadoc will be used for java code. The Java API Reference will prove invaluable.

On CSIL, the Java 1.3 executables can be found in /usr/dcs/software/supported/bin. The libraries can be found in and must be added to your CLASSPATH when compiling. I plan to write a script to do all of this for us. A good CVS reference.


frank gave a cvs demo for us. He explained how to add, commit, remove, checkout, update and diff using cvs.

briefly discussed XML interface between the SCM and the UTDT (user trent data translator)

Java Group

Perl Group

These are most likely changing to put many more people in the java end of the program, but these changes are not yet finalized.


The structure of the database was discussed.

There will be five tables so far, they will be:

this data will be kept in a mysql relational database


We talked about changes to the xml data the modules will be passing back and forth. We added an attribute to the message tag which will be the source of the message. For instance <message source=utdt> this way the scm can know where the message came from. Also, we decided on new elements to be the only child of the message element there are four: login,login_response,access,access_response.

The perl/php group is still vascilating between the two options. They are currently leaning toward php, and have written some code to parse xml.

over the next few days i will be java docing everything to aid with development. The javadocs will be kept in the source repository as a form of documentation.


utdt: develop a working basic prototype

scm: continue to extend functionality. add more xml handling, add auth, access and other classes


New assignments


Integration Testing

SCM Testing