dmarakaki.blogspot.com
Daniel's ICS 413/414 Engineering Blog: Code review: The Good, The Bad, The Ugly
http://dmarakaki.blogspot.com/2008/10/code-review-good-bad-ugly.html
Daniel's ICS 413/414 Engineering Blog. Wednesday, October 22, 2008. Code review: The Good, The Bad, The Ugly. First off I needed to come up with clever title for the blog and I thought The Good, the Bad, and the Ugly was appropriate for reviewing code. I would like to mention that in no way is the title a reflection of my fellow classmates' programs. I will however, point out what I thought was specifically good, what was generally bad, and make a general statement about what was ugly. For (int i = 1; i.
mari-leeflestado.blogspot.com
Lee's Engineering Blog: December 2008
http://mari-leeflestado.blogspot.com/2008_12_01_archive.html
Monday, December 8, 2008. Final Project: DueDates-ulaula 2.0. Over period of time we meet and interact with different people in our lives and more times than not we learn new things from these folks that we associated with. Team consist of Tyler Wolff. And some test cases also. And I did of the test cases like TestResultPage and TestAlertPage, ResultPage and UserGuide. Fig 1 Member Build Count. Fig 2 Member Commit. Fig 3 Member Dev Time. Subscribe to: Posts (Atom). Final Project: DueDates-ulaula 2.0.
atshum.blogspot.com
atshum Engineering Log: October 2008
http://atshum.blogspot.com/2008_10_01_archive.html
Thursday, October 23, 2008. I reviewed the projects of Team Purple. At first, I was a bit hesitant to comment on their programs- after all, I don't know anything more than they do, so who am I to be making suggestions? Method to suppress the stack dump and only print out the error messages. I also got some ideas on how to better test our system by looking at their test cases. Daniel Arakaki, Yasu Kaneshige, Vincent Leung, John Ly, Robin Raqueno and Tyler Wolff reviewed our (Erin and my) project. That log...
danielftian.blogspot.com
Engineering Blog (temporary title): One small step for man, one giant leap for DueDates
http://danielftian.blogspot.com/2008/11/one-small-step-for-man-one-giant-leap.html
Engineering Blog (temporary title). Monday, November 3, 2008. One small step for man, one giant leap for DueDates. Finally, version 1.1. As I've posted previously. We are now adding shiny new features to our DueDates project! In addition to displaying borrowed books from either the Hawaii State Public Library System. Or the University of Hawaii at Manoa Library System. It's as easy as quantum physics! A way to access private methods and fields by 'unlocking' them. It got to the point where I didn't even ...
danielftian.blogspot.com
Engineering Blog (temporary title): November 2008
http://danielftian.blogspot.com/2008_11_01_archive.html
Engineering Blog (temporary title). Monday, November 24, 2008. Implementing a stack in Wicket - a simple example that leads to frustration. Now that we've been working on the DueDates project for the past few weeks, the next step is to design a web interface for it. Unfortunately, many of us don't know the difference between a CSS tag and a kangaroo, so our professor gave us a very simple assignment to help us 'jump start' our way into using Wicket. So what is Wicket? My Wicket stack project. DueDates en...
robineraqueno.blogspot.com
Robin's Software Engineering Blog: February 2009
http://robineraqueno.blogspot.com/2009_02_01_archive.html
Robin's Software Engineering Blog. Saturday, February 28, 2009. Starter Events: The Ride of a Lifetime. This week we, the class, were entrusted with an extension to finish implementing the events of the starting events for the Devcathlon. . There are ten different starter events; I was chose to create the “Everyone Builds” event. . Give points for everyone building. Award 10 bonus points for 7 straight days with everyone building every day. It covered things I never read about. . Even though with som...
danmarakaki.blogspot.com
ICS 413/414 Software Engineering blog: February 2009
http://danmarakaki.blogspot.com/2009_02_01_archive.html
ICS 413/414 Software Engineering blog. Friday, February 27, 2009. Engineering the Event pt II. The class got a reprieve and got an extension on Event development. After a disastrous start, the team struggled with the Hackystat framework. Which led to more review and an extra nudge to get everyone to work extra hard. Working with the Framework. Over the course of the 4 days I hacked away trying to figure out. How to extract members and dev time using DevTimeDailyProjectData. For the event No MIAs. I had t...
danmarakaki.blogspot.com
ICS 413/414 Software Engineering blog: October 2008
http://danmarakaki.blogspot.com/2008_10_01_archive.html
ICS 413/414 Software Engineering blog. Thursday, October 30, 2008. Code review: Learning from others. DueDates version 1.1. Gets reviewed by the other development teams in class. Team Purple was assigned to review Team Blue's DueDates. And assess their version 1.1 code and documentation. The class, also was assigned to evaluate Google Project Hosting's code review tool because of issues from the previous Code Review. Due dates. The comparator is defined as an anonymous nested class. Were not too critical...
atshum.blogspot.com
atshum Engineering Log: September 2008
http://atshum.blogspot.com/2008_09_01_archive.html
Tuesday, September 30, 2008. Limitations of Code Coverage. I modified the Stack Project to correct errors identified by Checkstyle, PMD, FindBugs and JUnit. Then. I added some unit tests to achieve 100% code coverage as reported by Emma. This time, I was challenged to introduce an error to the program while maintaining complete code coverage. My programming partner for this week, Ronn Reeves. Came up with the idea of adding a. My Stack Project with 100% coverage and an introduced bug is available here.
danielftian.blogspot.com
Engineering Blog (temporary title): DueDates project, a first taste in multi-developer coding
http://danielftian.blogspot.com/2008/10/duedates-project-first-taste-in-multi.html
Engineering Blog (temporary title). Monday, October 20, 2008. DueDates project, a first taste in multi-developer coding. Coders don't play nice with each another. Every beginning.already has another beginning. I'd like to order Subversion for two, please. Previously we played around with Subversion by ourselves, but this is the first assignment where more than one person had to actively work on a single project. I worked with Aric West. Don't call me, I'll call you. Subscribe to: Post Comments (Atom).
