Re: Thinking about re-introducing UML in our workflow

On Sunday, 15 November 2015 5:37 AM, Dan Haywood wrote: > Thanks for this James. > My observation re: using the (relational) data model as the initial input > though is that this is likely to lead to rather coupled code, ultimately > not maintainable.

Does ISIS make following "rich domain model" pattern easier?

Hi All, I am looking for reasons why Apache ISIS framework promotes and enables a "rich domain model" [1] [2] and therefore promotes OO design. And of course any reasons to the contrary (i.e. things that ISIS does that gets in the way of OO design). Or is it simply neutral? i.e. developer

Re: Thinking about re-introducing UML in our workflow

All very interesting! Over the years I tried numerous modelling tools and only the low-tech ones stayed: drawing on a whiteboard, using coloured index cards [1] (learned from Dan) or using a simple online tool like yUML [2]. And I only use them to communicate the broad picture or for explorative

Re: Does ISIS make following "rich domain model" pattern easier?

Hi David, I would ask a slightly different question: does Isis assist with DDD as explained by Evans as a means of "tackling complexity" (the root of what makes big projects fail I believe)?. In fact its slightly disturbing to me to hear this talk of UML "design-time" tools and of

Re: Does ISIS make following "rich domain model" pattern easier?

On 15 November 2015 at 20:30, David Tildesley wrote: > Hi All, > > I am looking for reasons why Apache ISIS framework promotes and enables a > "rich domain model" [1] [2] and therefore promotes OO design. > > It certainly _enables_ a rich domain model, whereas many other