Re: [Cobold-developer] ideas and discussion issues

[joern t. <joe...@we...>]

hello *,

oliver charlet wrote:

> hello cobolds,
> 
> this is a short protocol about the dicussion we had yesterday:
> 
> please feel free to correct and change!
> 
> - separation of entities and behaviour
> a basic pattern must be, to separate value objects and business logic. in
> that way the datamodel can be modeled and implemented regardless of any
> semantic functions that use a lot of different entities. if the behaviour
> would be inside the data objects, there would exist a very ugly network of
> close coupled objects.
i would prefer to speak of logic or behaviour instead of just business 
logic cause this is only a small subset of the code to be created for a 
full application. additionally this may be misleading cause the business 
logic normally is the part with the smallest potential of automization 
in generative development.

> 
> - back end design
> given the fact, that Chiba is a fix component of the cobold architecture,
> the other major issue to think about is the creation of a back end that fits
> into the Chiba architecture. It needs tests and prototyping to develop an
> efficient work flow to achieve 1) a well defined application framework and
> 2) a pragmatic software development process.
> 
> - GUI / navigation
> since the GUI part of chiba as today is suboptimal in terms of easy
> deployment of individual design, it seems to be a good idea to embed chiba
> inside another front end component like a cms or portal framework (e.g. jet
> speed etc.).
> it is an unsolved issue to integrate a modular and flexible front end design
> into xForms.
i'd like to paraphrase this as: its not the goal of XForms to provide a 
presentation/layout facility - this is always the responsibility of the 
embedding language may it be XHTML, SVG or whatever. site- or 
application navigation shouldn't be handled with xforms; established 
technologies like portals or jsp are more suitable for this level.

> 
> - Chiba integration
> being the first and only applicable software component of cobold, chiba is
> to be beta tested to develop a prototype for a complete system. first steps
> will be to port the form4 jforce framework and adapt it to the chiba
> controller.
> 
> - Use Case XML / documentation
> with the goal of a generative system in mind, there could be first versions
> of descriptive XML for UseCases, data model and business logic. Since form4
> already has some experience in usecase implementations, a basic XML to
> describe the requirements to generate UseCase source code should be
> developed in the next time.
yes. very interesting. we could then take this as a testcase and build 
XForms for it to get a feeling how this might fit together.


> 
> - MDA / UML 2.0
> since the generative view of software development is becoming more common
> and is in the press constantly, it must be validated, how MDA specifications
> and UML 2.0 can be deployed to be a part of the cobold project.

interesting to look at:
- EMF (Eclipse project)
- http://www.architectureware.de/ Open Source MDA tool / Generative Umgebung

Joern
> 
> 
> so far for now...
> :olliC
> 
> -----------------------
> oliver charlet
> form4 gmbh & co. kg
> rungestr. 19
> 10179 berlin
> fon +49 (30) 27 87 84 -0
> fax +49 (30) 27 87 84 -10
> oli...@fo...
> http://www.form4.de
> -----------------------
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Cobold-developer mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobold-developer
>