Overview
This time I joined a team DueDates-polu, and 4 developers in my group tried our best to enhance DueDates. So far DueDates was a command base application, but now we used web application framework called Wicket.
Process
We used Google code hosting to manage our project. It has functionality for Issues, svn, wiki, and many things we need. Everybody in my team worked well for the project. We split our project into small tasks and tried to set own due time for each tasks.
Communication
The best procedure of software development would be pair programming, however since everybody has different schedule we mostly met only before and after class to discuss our issues, for a few hours. So we often discussed online using Google chat. One thing I found out this time is, Google chat automatically saves what we typed, and we can see it under "Inbox" of G-mail. Since we discuss about our issues, it's very useful that we can take a look at the record anytime.
Development
I think we finished all the requirements. We also tried to enhance it for Extra Credit 2 and 3, which is back-end database and background processing, but we were not able to complete it and we are running out of time. I will try to experiment during winter break.
Software ICU
We also used a tool called Hackystat, and it automatically sends data to server while we work on Eclipse and it shows many aspects of how we are doing for our project. The only issue with that is, sometimes it takes a while that Hackystat sends our data to server. For example, if I worked on (S), it will not show there until (W), I think.
Conclusion
This was one of the most interesting project I did in my ICS courses. I think the reason is that group members help each other and each of them have their own strength. Rather than working alone, this time we could ask. If there is a next opportunity, I want to do more pair programming.
Our project
http://code.google.com/p/duedates-polu/
12/08/2008
11/21/2008
Stack Wicket
Overview
Last week I worked to use Wicket to enhance stack-johnson, so that everybody can use it on the web browser. With this, people do not need to use command prompt which is hard for some people, and also they even do not need to download the program.
What is Wicket?
Wicket is a web application framework for Java developers. Wicket focuses on programming with components and tries to use object oriented programming in web application. It is now part of Apache project.
Setup
Before I start development, I did setup for Jetty, Wicket, and SLF4J. Jetty is Java base web server, and SLF4J is library for logging.
Development
My professor provided us great examples of how Wicket works at the following.
http://code.google.com/p/ics-wicket-examples/
I was wondering how Jetty finds right html to display, but after looking at his Example01, I found out why. The program was executed in following order.
build.xml > Jetty > ExampleApplication > HelloWorldPage
ExampleApplication uses getHomePage to set HelloWorldPage as home page, then it works with HelloWorldPage.html to display. It was interesting to know its program flow.
Then I looked through examples and API for [ Jetty ] and [ Wicket ] to develop the application.
Conclusion
Implementing first Wicket application was very fun. Now I can access the program from anywhere. I'm looking forward to develop next applications. By the way, another wonderful resource I recommend is [ Wicket in Action ], which is available in both book and eBook.
The Wicket application can be downloaded from here.
Last week I worked to use Wicket to enhance stack-johnson, so that everybody can use it on the web browser. With this, people do not need to use command prompt which is hard for some people, and also they even do not need to download the program.
What is Wicket?
Wicket is a web application framework for Java developers. Wicket focuses on programming with components and tries to use object oriented programming in web application. It is now part of Apache project.
Setup
Before I start development, I did setup for Jetty, Wicket, and SLF4J. Jetty is Java base web server, and SLF4J is library for logging.
Development
My professor provided us great examples of how Wicket works at the following.
http://code.google.com/p/ics-wicket-examples/
I was wondering how Jetty finds right html to display, but after looking at his Example01, I found out why. The program was executed in following order.
build.xml > Jetty > ExampleApplication > HelloWorldPage
ExampleApplication uses getHomePage to set HelloWorldPage as home page, then it works with HelloWorldPage.html to display. It was interesting to know its program flow.
Then I looked through examples and API for [ Jetty ] and [ Wicket ] to develop the application.
Conclusion
Implementing first Wicket application was very fun. Now I can access the program from anywhere. I'm looking forward to develop next applications. By the way, another wonderful resource I recommend is [ Wicket in Action ], which is available in both book and eBook.
The Wicket application can be downloaded from here.
ICS Industry Day
Overview
This Thursday UH Manoa had ICS Industry Day, which many tech compnaies from Hawaii do presentation about their business. Below are companies that I took a look.
1. Datahouse
They often develop software with Ruby on Rails, C#, and PHP. Their clients include government, educational organization, financial services, and etc.
2. Camber Corporation
Since Ikayzo was late for the presentation, Camber Corporation did presentation after datahouse. Camber Corporation has its office nationwide and they make various applications. On their slide, there were many keywords that sound interesting. Here is a list of that and I will search more and experiment if I need it.
rubyonrails.org
Active Scaffold
REST
Flex
ExtJS
Google Earth / KML
BackgrounDRb
3. Ikayzo
Ikayzo developed TechHui. Some of their software also works for several languages including Japanese and Taiwanese. Many famous companies including Oracle purchased commercial licenses of their software.
4. Concentris Systems
They talked about their router which utilize mesh network. It allows traffic to split and provides us more reliable connection.
Conclusion
I learned many things from these presentations such as programming trend, what they develop, and ideal candidate as employees. In terms of programming trend, I have an impression that most of them talked about Ruby on Rails. In ICS department at UH, it is good to learn assembly language in order to understand computer architecture, but I also wanted to learn practical things such as Ruby and PHP.
With these presentations I really thought there are many great tech companies in Hawaii. In general I think we don't have strong image that Hawaii is a place for technology, but if these tech companies continue to develop great products as they do now, Hawaii can be like Sillicon Valley. It was really good experience to join ICS Industry Day. Whenever there is next opportunity, I want to join again.
This Thursday UH Manoa had ICS Industry Day, which many tech compnaies from Hawaii do presentation about their business. Below are companies that I took a look.
1. Datahouse
They often develop software with Ruby on Rails, C#, and PHP. Their clients include government, educational organization, financial services, and etc.
2. Camber Corporation
Since Ikayzo was late for the presentation, Camber Corporation did presentation after datahouse. Camber Corporation has its office nationwide and they make various applications. On their slide, there were many keywords that sound interesting. Here is a list of that and I will search more and experiment if I need it.
rubyonrails.org
Active Scaffold
REST
Flex
ExtJS
Google Earth / KML
BackgrounDRb
3. Ikayzo
Ikayzo developed TechHui. Some of their software also works for several languages including Japanese and Taiwanese. Many famous companies including Oracle purchased commercial licenses of their software.
4. Concentris Systems
They talked about their router which utilize mesh network. It allows traffic to split and provides us more reliable connection.
Conclusion
I learned many things from these presentations such as programming trend, what they develop, and ideal candidate as employees. In terms of programming trend, I have an impression that most of them talked about Ruby on Rails. In ICS department at UH, it is good to learn assembly language in order to understand computer architecture, but I also wanted to learn practical things such as Ruby and PHP.
With these presentations I really thought there are many great tech companies in Hawaii. In general I think we don't have strong image that Hawaii is a place for technology, but if these tech companies continue to develop great products as they do now, Hawaii can be like Sillicon Valley. It was really good experience to join ICS Industry Day. Whenever there is next opportunity, I want to join again.
11/17/2008
DueDates 1.2
Overview
We want to make DueDates even more useful to users and decided to add 3 more options as follow.
1. -console
Report will be sent to the console.
usage: -console
2. -email
E-mail will be sent to the address using the supplied SMTP server.
usage: -email < emailaccount > < smtpserver >
3. -wakeup
Program will run and check for due items with given interval.
usage: -wakeup < interval >
Process
I and my partner Jeho Jung worked on this development last week. We have been working as a partner for a while toward development of DueDates and now we really understand the most efficient way to proceed is pair programming. Our houses are close, so we met a few times and shared our knowledge.
Conclusion
With this update, now this program is able to do useful task. For example, following execution will run the program once a day and checks if there are books due within next 24 hours. If there is, the program will send E-mail and if not it does nothing.
-email name@hawaii.edu mail.hawaii.edu -wakeup 1 -within 1
I think this is a very useful option since people these days are busy and tend to forget many things. For now it only notifies us about books in the library, but if it had functions to tell us anything due it would be more useful. If I had enough time, I want to add such functions in the future.
We want to make DueDates even more useful to users and decided to add 3 more options as follow.
1. -console
Report will be sent to the console.
usage: -console
2. -email
E-mail will be sent to the address using the supplied SMTP server.
usage: -email < emailaccount > < smtpserver >
3. -wakeup
Program will run and check for due items with given interval.
usage: -wakeup < interval >
Process
I and my partner Jeho Jung worked on this development last week. We have been working as a partner for a while toward development of DueDates and now we really understand the most efficient way to proceed is pair programming. Our houses are close, so we met a few times and shared our knowledge.
Conclusion
With this update, now this program is able to do useful task. For example, following execution will run the program once a day and checks if there are books due within next 24 hours. If there is, the program will send E-mail and if not it does nothing.
-email name@hawaii.edu mail.hawaii.edu -wakeup 1 -within 1
I think this is a very useful option since people these days are busy and tend to forget many things. For now it only notifies us about books in the library, but if it had functions to tell us anything due it would be more useful. If I had enough time, I want to add such functions in the future.
11/07/2008
Software ICU
Software ICU tells us the condition of the software, indeed its health. For this time I took advantage of an open source software called Hackystat. Its role is to show various information such as coverage, complexity, coupling, and etc. I installed JavaNCSS and DependencyFinder here so that it will work on complexity and coupling respectively.
Result
Here is brief summary of vital signs.
For now coverage of duedates-green is low, so the source code should be modified to improve its reliability. Except that, Hackystat is showing we are not in danger.
Conclusion
Although it takes a while to download and setup various tools for Eclipse, Hackystat allows us to easily understand the condition and health of our software project. It is also possible to manually run each tools, but we are programmers and we should let computers to do it automatically. Hackystat is very useful which accomplishes that task.
Result
Here is brief summary of vital signs.
| Vital Signs | What to measure |
| Coverage | Percentage of code executed by tests. |
| Complexity | Density of branches and loops. |
| Coupling | Number of dependencies between classes. |
| Churn | Lines of code added, deleted, and modified in a commit. |
| CodeIssue | Number of warnings generated by QA tools. |
| Commit | Number of commits to the repository. |
| Build | Number of builds. |
| UnitTest | Number of unit tests. |
| Size | Amount of code. |
| DevTime | Time spent. |
For now coverage of duedates-green is low, so the source code should be modified to improve its reliability. Except that, Hackystat is showing we are not in danger.
Conclusion
Although it takes a while to download and setup various tools for Eclipse, Hackystat allows us to easily understand the condition and health of our software project. It is also possible to manually run each tools, but we are programmers and we should let computers to do it automatically. Hackystat is very useful which accomplishes that task.
10/24/2008
Project Review: DueDates
Overview:
It's always good to review each other. It allows us to take a look at source code of others so that we get new insight. At the same time we also get comments from other developers about what was good or what should be improved. Therefore we did review on our project, DueDates.
Process:
First of all, members of each project made a copy of their source code to "svn/tags/Review-2008-10-20". We did it because this way we can save frozen snapshot of the system. If developers want to update their source code in "trunk", they don't need to wait for reviewers to finish and can always make changes.
Next we started to review source code of other projects. From the project page I went to "Source > Browser" and took a look at "svn/tags/Review-2008-10-20". I will see the code, so if there is something I noticed and I want to make comments, I do it by double-clicking the code so that small section to post will pop up. Then I went to "Changes" which is located right next to "Browse" and clicked the version I reviewed, then left comments there.
Review:
It's really good to know how other developers tried their best for the development. Since we worked on the same problem, we can easily understand the flow of program and what the issue is. Here is something I learned from other projects. One project was showing "Processing..." while they connect to database and get a result. I was thinking the connecting process takes a little long but didn't show any words like this. I think this is very user friendly. Other project was showing menu. It's also nice since as we enhance this project later it will have a lot more capability, and instead of using option we can choose from menu. For my project, I got some comments that I should clean up a bit more, and also some comments that our output of the library information is easily understandable to read.
Conclusion:
Reviewing is a really good way to improve each other. The only con is it takes some time to give out useful comments. I thought Google Code is a very useful tool for this purpose. When I make a review next time, I will take notes of what others were doing and I will try to remember them for future use.
It's always good to review each other. It allows us to take a look at source code of others so that we get new insight. At the same time we also get comments from other developers about what was good or what should be improved. Therefore we did review on our project, DueDates.
Process:
First of all, members of each project made a copy of their source code to "svn/tags/Review-2008-10-20". We did it because this way we can save frozen snapshot of the system. If developers want to update their source code in "trunk", they don't need to wait for reviewers to finish and can always make changes.
Next we started to review source code of other projects. From the project page I went to "Source > Browser" and took a look at "svn/tags/Review-2008-10-20". I will see the code, so if there is something I noticed and I want to make comments, I do it by double-clicking the code so that small section to post will pop up. Then I went to "Changes" which is located right next to "Browse" and clicked the version I reviewed, then left comments there.
Review:
It's really good to know how other developers tried their best for the development. Since we worked on the same problem, we can easily understand the flow of program and what the issue is. Here is something I learned from other projects. One project was showing "Processing..." while they connect to database and get a result. I was thinking the connecting process takes a little long but didn't show any words like this. I think this is very user friendly. Other project was showing menu. It's also nice since as we enhance this project later it will have a lot more capability, and instead of using option we can choose from menu. For my project, I got some comments that I should clean up a bit more, and also some comments that our output of the library information is easily understandable to read.
Conclusion:
Reviewing is a really good way to improve each other. The only con is it takes some time to give out useful comments. I thought Google Code is a very useful tool for this purpose. When I make a review next time, I will take notes of what others were doing and I will try to remember them for future use.
10/20/2008
Creating a project DueDates
Overview:
DueDates is a command base program that allows us to access library database and get information about our own account. I worked with Jeho Jung to enhance this project.
Procedures as a team:
It was challenging to do project with partners since our schedule are different, but we discussed about the project somehow and worked on it step by step. Since there were many things to do, we split work into subproblems and set deadline for each. That way we don't feel too much pressure and we can see if we are on the right track in terms of schedule.
Enhance:
First of all, we worked on formatting output. Since the original project didn't show due date, we added a feature to access it and format using String.format(). It was interesting to know we can use format such as "%1$-15s %2$-70s", which is similar to C language. Then we worked on error handling to check if it shows user friendly message. Lastly we worked on test case to make sure everything works well.
We also worked on writing Wiki page for UserGuide and DeveloperGuide while we enhance DueDates. Those Wiki pages are guide to others and at the same time they are notes for ourselves to remember later.
Conclustion:
Dealing with DueDates was a good review of what we learned so far in software engineering class. Now I'm confident with working on any projects in the world with other developers.
Our project, duedates-green
http://code.google.com/p/duedates-green/
executable jar file
http://duedates-green.googlecode.com/files/DueDates.jar
DueDates is a command base program that allows us to access library database and get information about our own account. I worked with Jeho Jung to enhance this project.
Procedures as a team:
It was challenging to do project with partners since our schedule are different, but we discussed about the project somehow and worked on it step by step. Since there were many things to do, we split work into subproblems and set deadline for each. That way we don't feel too much pressure and we can see if we are on the right track in terms of schedule.
Enhance:
First of all, we worked on formatting output. Since the original project didn't show due date, we added a feature to access it and format using String.format(). It was interesting to know we can use format such as "%1$-15s %2$-70s", which is similar to C language. Then we worked on error handling to check if it shows user friendly message. Lastly we worked on test case to make sure everything works well.
We also worked on writing Wiki page for UserGuide and DeveloperGuide while we enhance DueDates. Those Wiki pages are guide to others and at the same time they are notes for ourselves to remember later.
Conclustion:
Dealing with DueDates was a good review of what we learned so far in software engineering class. Now I'm confident with working on any projects in the world with other developers.
Our project, duedates-green
http://code.google.com/p/duedates-green/
executable jar file
http://duedates-green.googlecode.com/files/DueDates.jar
Subscribe to:
Posts (Atom)