There are several usage patterns for domain-specific languages: ? processing with standalone tools, invoked via direct user operation, often on the command line or from a Makefile (e.g., the GraphViz tool set) ? domain-specific languages which are implemented using programming language macro systems, and which are converted or expanded into a host general purpose language at compile-time or read-time ? embedded (or internal) domain-specific languages, implemented as libraries which exploit the syntax of their host general purpose language or a subset thereof, while adding domain-specific language elements (data types, routines, methods, macros etc.).
The transformation is determined by the business needs, and the business needs vary wherever you are. Your industry determines the kind of data you deal with, and how it will need to be used. A medical database will need to find details of a patient’s medical records. A retailer may need to track all individual POS sales, both to watch the financial side, and to observe the impact on inventory. A voter registration database may need to give reports of people using various filters for marketing or polling. And each of these systems has different details of what kinds of source data it needs as input and how the output data needs to be queried, all of which need to be checked for data
I have 2.5 Years of experiance in Automation testing using Selenium and appium. I have hands on experiance in Web application, mobile Application and WAP.
Recent comments