Java web based development
- Published March 29th, 2006 in Software Eng.
I’ll be developing a Java web based CRM for the next few months and we’re still at the requirements analysis and planning phase (including architectural analysis)[1].
The system will be complex enough to demand a MVC design pattern but we’re not going to reinvent the wheel. And here’s where the problems begin. Apache Struts is too complex for the task. Java Server Faces is an option, like is Dinamica or Spring. We still don’t know if we’ll need Hibernate.
I found out a framework that follows the logic behind Ruby on Rails. It’s called Trails but it’s only at a beta stage and has lots of dependencies. And we need to be agile and fast — so wasting time with the inners is an absolute showstopper.
So we’re accepting kind suggestions on what to use. We hope it to be agile enough. We’ll probably be using Jetty instead of Tomcat at the development phase (we’ll leave Tomcat for the deployment stage) and the idea is to have the necessary dependencies available as JARs. This means that Eclipse along with a fresh svn checkout would be enough to do the job.
Ideas? :-) Don’t be shy, we won’t be receiving any kind of revenue so “we won’t use your ideas to gain money”!
[1] - We’re following an agile development methodology called FDD - Feature Driven Development.
I wont be giving any kind of sugestions here, I will just remind you and your group that LGP is a complete package. So don’t forget the other aspects of your product such as marketing.
No matter how good your product is, you will need to sell it not only to your client, which most likely be your best ally at those mid-term and final presentations, but also to other teams clients.
Thrust me we I say that those other team clients will ask you the most absurde questions regarding your product, but not in tech terms, but in vision and utility.
Best of luck!
We realized that some time ago and we’re really betting on it. Nevertheless, we must build something :-)