Open Source in the world of software is amazing. Developers share and distribute source codes with each other. SourceForge is one of the well-known platforms. I have registered my first Open Source project in SourceForge. The project is called Mark Six Analyst at https://sourceforge.net/projects/marksixanalyst/ . It is a simple tool to forecast the result of Hong Kong lottery or so-called Mark Six by various statistics methods. For the success of the project, I would like to thank Java, JavaDB (Apache Derby), Java Swing, Java Persistence API, TopLink, Hibernate Entity Manager, NetBeans and CsvReader. Because of them, developing a software application becomes rapidly quicker and the developed application becomes more stable and much easily maintained. Especially for Java Persistence API or called JPA, developers are less annoyed to handle entity EJBs and Object-Relational Mapping. It is helpful for developing an application with a database of complicated entity relationships. On the ot
Comments
Implementing then specificating?
Testing before coding? xD
I'm serious, what's the problem with this method?
The main problem is that we cannot practically complete a task in a phase. Software Development needs iterative and incremental process instead of sequential process as Waterfall.
I know that a modified Waterfall Model is added with iteration but it does not solve its sequential process problem.
See detail at http://en.wikipedia.org/wiki/Rational_Unified_Process
See the wikipedia article for more information.
Also, building the architecture as the needs grow is a central agile practice. And most user-centric design approaches emphasize the importance of iterative design with frequent user feedback, which means that you need to implement something in order to refine your specifications.
Thanks for your opinion. You raised a very good point - Iterative Refinement.