Software changes faster than data does. Every few years, applications are replaced, extended, upgraded, or are rewritten on a different technical platform. Proper software design can make a major difference in the application life cycle, but even the seemingly complete and popular UML design practice suffers from inexact workings.

All process modeling in UML begins with an abstract type level, or classes. Verbalizing the user requirements is the basis of the Fact Oriented Modeling method. However, UML captures none of these methodically. Architect experience is required to try to minimize the mistakes and translate users’ requirements as exactly as possible.

CaseTalk offers a methodological way of capturing user requirements and validating the information model derived from these. The CaseTalk Viewer can derive a UML Class diagram from that. All while maintaining the verbalizations, examples, and constraints.

Starting UML modeling with a sound conceptual model that closely follows user requirements will prove a solid investment for your business.

Add comment