Machine Problem on Java Web Development

As I've mentioned in a previous post, I've written some code to illustrate how to properly build a basic Java web application. I've decided to leave this code unfinished so that it can be used as a machine problem for a one-semester or two-semester course on Software Engineering or Enterprise Development. You can find the code here.

I recommend to professors to not just grade students on the whether the system works or not. In fact, with my own trainees, I don't even bother to check whether the code works. My focus is on code quality and process. Here are some of the things I personally look out for:

• Coding practices and Object-Oriented Design.

• See "Clean Code" by Robert Martin or the Java Practices website.

• Test-Driven Development

• Suggested References:
• Test-Driven by Lasse Koskela
• JUnit
• Mockito
• DbUnit

• Fine-grained, frequent commits and expressive commit messages, using Git & Github.