Mind Map and Business Process Model: Specification support by model transformation

One of the main reasons for the software project setback is the poor level of requirements specification. Communication between customer and developer is often a problematic part of the requirements specification phase. This also arises from the fact developers use modeling techniques specific for the software engineering domain to record requirements. However, customers often have difficulty understanding what the models are representing because they do not know the notations used in the domain of software engineering. The solution could be in using simpler, natural and comprehensible modeling techniques to most people. Some models, because of their simplicity, may be less expressive than the more complex models. But they could be able to help customers to understand what the software engineering models represent. The paper deals with the transformation between these two types of models.