My Sharing about JavaFX Attending JManc , an unconference organised by Manchester Java Community and hosted at Auto Trader 's offices, was an exciting experience. This unique event demonstrating the essence of participant-driven learning and collaboration, set the stage for a series of engaging and enlightening sessions. Propose and vote for topics In the morning, we proposed topics using sticky notes. Afterward, we voted on these topics with dots, shaping the day's agenda based on collective interest. This process itself was a testament to the community's diverse interests and expertise. Breakfast Keynote by Helen Scott Keynote by Helen Scott The unconference kicked off with a keynote by Helen Scott from JetBrains . Helen's talk centered on AI, a topic so crucial and timely that, as she humorously noted, audience would have thrown her out of the window if she did not speak of AI. Her insights into AI's impact on development and the future of programming set a tho...
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.