Abstract: Model driven engineering (MDE) approaches necessitate verification and validation (V&V) of the models used. Balancing usability of modeling languages with verifiability of the specification presents several challenges. Conventional modeling languages have automated solvers but are hard to interpret and use. Implementations 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 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.

Abstract: Model driven engineering (MDE) approaches necessitate verification and validation (V&V) of the models used. Balancing usability of modeling languages with verifiability of the specification presents several challenges. Conventional modeling languages have automated solvers but are hard to interpret and use. Implementations 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 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.

Abstract: A model framework for generating batch programs has an abstraction representing a batch program, an abstraction representing a batch function of the program, an abstraction representing operation of the function, an abstraction representing a data provider to the function, and an abstraction representing a context class of the function. The framework is characterized in that instantiation of the model with the appropriate input data parameters input to each abstraction generates appropriate instances of batch functions including function operations wherein the generated instances are executable as part of a run sequence of the batch program.

Abstract: A model framework for generating batch programs has an abstraction representing a batch program, an abstraction representing a batch function of the program, an abstraction representing operation of the function, an abstraction representing a data provider to the function, and an abstraction representing a context class of the function. The framework is characterized in that instantiation of the model with the appropriate input data parameters input to each abstraction generates appropriate instances of batch functions including function operations wherein the generated instances are executable as part of a run sequence of the batch program.

Abstract: System architecture is taught for adapting at least one legacy system for functional interface with at least one component system. The architecture includes a data reconciliation bus for enabling reconciliation of redundant data between legacy systems, at least one component wrapper within the architecture for describing a legacy system, at least one component object within the architecture for describing a component system, and a connectivity bus within the architecture between at least one component object and at least one component wrapper, the bus for extending legacy function to the at least one component system. In a preferred embodiment, a user operating a GUI has access to legacy services in an automated client/server exchange wherein heterogeneous data formats and platform differences of the separate systems are resolved in an object-oriented way that is transparent to the user.

Abstract: A hardware/software system for developing a software application by component modeling and instantiation is disclosed. The system has at minimum a computerized workstation with a GUI for enabling user control of system entities, a data repository for storing data particulars necessary for application development, a server application for providing data particulars and functionality required for component development, a processor for hosting the server application, and a modeling program accessible to the workstation and to the server application for design, construction, and testing application components. In a preferred embodiment, the application components are separately defined, built and tested using the modeling program and server functions wherein the coding required to generate and enable each application component from model information is automatically generated by the modeling program.