[Equanda-svn-commit] SF.net SVN: equanda: [45] trunk/src/site/wiki

[<tri...@us...>]

Revision: 45
          http://equanda.svn.sourceforge.net/equanda/?rev=45&view=rev
Author:   triathlon98
Date:     2007-08-22 08:19:13 -0700 (Wed, 22 Aug 2007)

Log Message:
-----------
doc improvements

Modified Paths:
--------------
    trunk/src/site/wiki/index.wiki
    trunk/src/site/wiki/vision.wiki

Modified: trunk/src/site/wiki/index.wiki
===================================================================
--- trunk/src/site/wiki/index.wiki	2007-08-22 07:11:44 UTC (rev 44)
+++ trunk/src/site/wiki/index.wiki	2007-08-22 15:19:13 UTC (rev 45)
@@ -7,11 +7,11 @@
 
 equanda is a tool which should help you to build enterprise grade (J2EE based) application with minimal effort, focussing not only on the initial version, but considering that most of the cost will be in maintaining and evolving the application.
 
-This is done by generating as much as possible directly from an XML description of the the data and interactions (the _object model_ "om").
+This is done by generating as much as possible directly from an XML description of the the data and interactions (the _[object model|om.html]_ "om"). Some more thoughts about the concept (generation) can be found [here|http://blog.progs.be/?p=29].
 
 There are many ways to enhance/improve the generated application, but this is always done in such a way that most changes in the object model don't cause any problems. You just recompile (which re-generates al lthe files which needs modifying) and all the manual changes are preserved.
 
-The idea is that application development should be focussed on doing the important stuff (the unique features of the application), and that common aspects should only be done once (even more so because this improves consistency). The goal is to work towards a [vision|vision.html] of how application development should be (original thoughts in this [blog|http://blog.progs.be/?p=21]). Some more thoughts about the concept (generation) can be found [here|http://blog.progs.be/?p=29]. 
+The idea is that application development should be focussed on doing the important stuff (the unique features of the application), and that common aspects should only be done once (even more so because this improves consistency). The goal is to work towards a [vision|vision.html] of how application development should be (original thoughts in this [blog|http://blog.progs.be/?p=21]).
 
 h2. Features
 

Modified: trunk/src/site/wiki/vision.wiki
===================================================================
--- trunk/src/site/wiki/vision.wiki	2007-08-22 07:11:44 UTC (rev 44)
+++ trunk/src/site/wiki/vision.wiki	2007-08-22 15:19:13 UTC (rev 45)
@@ -1 +1,5 @@
-h1. Vision for equanda
\ No newline at end of file
+h1. Vision
+
+Application development is a non-trivial task which usually happens in iterative fases. Even if this was not the original plan, the requirements often change while the application is being used (or even during development).
+To remedy the requirement creep during development, it is best to keep the development cycles as short as possible.
+To allow requirement changes while the application is being used, tools should be used which consider that software will evolve and which allow these changes to be applied with as little works as possible.
\ No newline at end of file


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.