Software changes faster than data. Every few years applications get replaced, extended, upgraded or rewritten on a different technical platform. A 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 modelling done in UML starts of at the level of classes. Verbalising the user requirements is the basis of this modelling process. Yet UML captures none of these in a methodological manner. Architect experience is required to try and minimise the mistakes and translate users requirements as exact as possible.

CaseTalk offers a methodological way of capturing user requirements and validating the information model derived from these. While maintaining all verbalisations, examples and constraints a UML class diagram can be generated from this to start UML modelling for process modelling.

Starting UML modelling with a sound conceptual model as closely to user requirements as you can get, will prove a solid investment for your business.