The Source for Java Technology Collaboration
User: Password:
Register | Login help    

Search

Online Books:
java.net on MarkMail:


View by: Most Recent | Topic | Community | Webloggers | James Gosling   
Monthly Archives:    

Blogs by topic J2EE and user mayworm

• Accessibility • Ajax • Blogging • Business • Community 
• Databases • Deployment • Distributed • Eclipse • Education 
• EJB • Extreme Programming • Games • Grid • GUI 
• IDE • Instant Messaging • J2EE • J2ME • J2SE 
• JavaOne • Jini • JSP • JSR • JXTA 
• LDAP • Linux • Mobility • NetBeans • Open Source 
• OpenSolaris • P2P • Patterns • Performance • Porting 
• Programming • Research • Security • Servlets • Struts 
• Swing • Testing • Tools • Virtual Machine • Web Applications 
• Web Design • Web Development Tools • Web Services and XML 


J2EE

Some time ago, a project I participated as a team manager, called my attention. The development team was constantly complaining about the complexity they had to grapple with for implementing every single use case. When asked whether their difficulty lay in the technological aspects, or even if the core business involved was too complex, they reported that their problem was elsewhere. Namely the challenge actually had to do with the steps they had to follow in order to attain, for instance, a simple CRUD respecting the architecture designed by the software architect. A CRUD with just two attributes required the development of 10 different classes to allow the insertion of a simple record in the database.
on Dec 21, 2005 | Permalink | Discuss