Relate the lines of code as well as the lines of comments to each of the versions of your server. Take the time to figure
[continue reading...]

Decided to look at the commenting style of the files (throughout code, tops of files only, etc) as input to how any change over the
[continue reading...]

We went over ideas for the metrics to measure various aspects of the applications’ evolution.
Size growth:

Lines of code
Byte size of files — core/common ones
[continue reading...]

Over spring break i did not accomplish anything for this project. I was busy the entirety of the week working.

Continued work on finding similarities and differences between all of the servers code and its containing patterns

Started working on finding our similarities between my servers code and the rest of the group’s server code

Homework #4

Work on operational Schemas

Project:

UML Diagrams for:

Tornado
Jetty

What to work on:

Come up with operational schemas for Zed over the weekend. On Monday we will work on Homework #4.
Finish UML generation. Use Netbeans
[continue reading...]

Finished reverse engineering code using Netbeans. I have gotten the UML diagrams from it. Now I need to make sure that it is an accurate representation of the code. Next week the group will meet together to compare all other server’s UML to get a better understanding of what we should research in our server

I have gotten all of the necessary source code for Tornado.  I had to decompile version 3 from its jar file into java files. Started working on reverse engineering my code to get its UML.