Model Transformation in Analysis

The analyst’s job can be seen as mapping the real world to a model. At this an analyst has two main ways of making use of Model-to-Model Transformation in requirements analysis:

State Machine 11. Applying rules to models
Looks like the state machine in figure 1 has some, say, medium level of complexity. But when broken down to model + rules it becomes much simpler. Where the model is the one in figure 2 and the rule says “every state transition between these processing state needs to be 4-eyes-checked”.
State MachineThus one gains the understanding that 1, 3, 5, 7 are processing states (where sth is being processed) and 2, 4, 6 are checking states (where some verification is done). Even if one has exceptions to the rule like the edge 5-3, where no check is performed, the triple model + rule + exception still provides a much better understanding than the model alone.

Data + Functions2. Keeping views consistent
Like the data model and the function model in figure 3, where, say, the data flow among the functions refers to the data entities.

So, all uses of Model-to-Model Transformation in Analysis should belong to one of the above categories – do they?

About modelpractice

Modeling Theory and Abstraction Awareness in strive for scientific rigour and relevance to information systems engineering.
This entry was posted in Software_Engineering and tagged , , , , , , , , , , , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s