Some folks are working on a standard curriculum for software engineering and a standard process to follow that incorporates both waterfall and agile methodologi

Some folks are working on a standard curriculum for software engineering and a standard process to follow that incorporates both waterfall and agile methodologies. In fact it also includes having an engineering team think about what they are doing and evaluating the quality of their process using a number of standard dimensions and metrics. Read more about SEMAT here http://semat.org/ http://semat.org/ Stuff like this is a prerequisite to creating software that is done, and can be used for 200 years without any substantial change. Could Java ever get to that stage? What about some of the JVM ecosystem such as Tomcat or Camel?