| || |
How to validate/accept/test a model ?
first a quick hello, i've around anonymously for a very long time and have found lots of answers to many questions I had in the past. So thanks for that.
But today I'm in a situation I've never met so far, and cannot find any one who did it before.
The question is : "How to test a model?"
Be careful, It is NOT about model-driven testing !! In a nutshel the application we are to test is driven by a business model, this business model needs to be "created" and validated because it feeds the business process plateform which will derive the logic/screens and flows from it.
As the model is part of the solution, we need to make sure the model is correct. And the model being a deliverable, we need to "accept" it, i.e. define our acceptance process + acceptance criteria.
So back to the original question : How can we test a model? (it is a sort of executable model, there are possibilities to fill some inputs and get some output values ... )
My first guess would be to have End-to-End Business Scenarios, derieve them into various use cases, and simulate a couple of them in the model simulation tool.
My second guess was to revert back to the basics :
- What is a model, from what is composed of ?
- What could go wrong ?
and come up with idea to mitigate those risks
Has anyone ever had some situation which looked similar ?
I think it's a very interesting topic in the sense it shakes our confort zone ... dealing with coded software, line of code, etc ...
Are you talking about models in the MVC (Model/View/Controller common programming pattern for interactive applications) or MVVC programming pattern?
What exactly is a model in your question?
Tags for this Thread