Just one more thought about this. When someone design a custom software system, the information model is not only based on use cases. We all know about "general software quality characteristics" that we have to think about, like Usability, Maintainability (modifiability, adaptability, etc), Completeness, Conciseness etc, etc (http://en.wikipedia.org/wiki/Software_quality#Maintainability) (this are the basics of software engineering, nothing new to us). So, we have to think of something that:reach something that meets the use cases (complete, adds complexity),but it is also cocise (only needed things, must be simple),and maintainable (generic, good organization, simple extend and change (adapt to other realities that may be not covered by the use cases))etc ... So, the use cases are a part of the puzzle, of course are the base of the design, but not the olny piece of the final puzzle (if we want quality).
Kind regards,Pablo. > > shorter Tom Beale: Only by ignoring use cases can one design usable data > > types? > > I think is more like "you don't have to look only the use cases to > design usable data types" I agree with this vision. Because we can't think of all use cases, so we can never create datatypes that consider all posible cases. So, we need to think more general solutions, seeing not only the use cases. - Pablo. > > > heh. XML forever, it will solve every problem in the world. Just if > > everyone else does it 'my' way, we'll be right. > > there is a quote that says "XML is like violence. If it doesn't solve > your problem, you're not using enough of it." ;) > > anyway, I prefer ISO dates whenever possible > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101119/195afbc0/attachment.html>
