SYSTEMS AND METHODS FOR VALIDATING DOMAIN SPECIFIC MODELS

Model driven engineering (MDE) approaches necessitate verification and validation (V&V) of the models used. Balancing usability of modeling languages with 5 verifiability of the specification presents several challenges. Conventional modeling languages have automated solvers but are hard to interpret and use. Embodiments of present disclosure provide systems and methods for validating domain specific models wherein rules and vocabularies in domain specific model are translated to machine interpretable rules (MIR) and machine interpretable vocabularies (MIV) which are 10 processed (via logic programming technique) to generate a logic programming representation (LPR) of the MIR and MIV based on which solution scenarios are generated for validating the domain specific model. Validation of the model involves verifying LPR using a set of ground facts. During validation of solution scenarios of model, system also checks for inconsistences in rules, if any. These rules are corrected 15 and solution scenarios are re-generated to obtain anomaly free solution scenarios. Sheet No: 3/3 Receiving, via one or more hardware processors, a domain specific model comprising one or more rules and one or more vocabularies, wherein the one or more vocabularies 302 comprise a plurality of entities and associated relationship thereof Translating, via the one or more hardware processors, the one or more rules and the one or more vocabularies into one 304 or more machine interpretable rules and one or more machine interpretable vocabularies Processing, via the one or more hardware processors, the machine interpretable rules and the machine interpretable vocabularies to generate a logic programming 306 representation comprising the machine interpretable rules and the machine interpretable vocabularies Generating, via the one or more hardware processors, one or more solution scenarios of the logic programming 308 representation Validating, via the one or more hardware processors, the domain specific model using the one or more solution 310 scenarios