Abstract
In the enterprise information system, as the adoption of the distributed ledger technology and the Web service API increases for the mutual cooperation of the systems, it is important to visualize the entities to be managed in the business as resources, to agree on and exchange among the organizations. The need is getting stronger. Specifically, it is important for developers to properly design and maintain the conceptual model of the business domain, to build a database based on it, and to provide an API for accessing the DB that has been constructed It is a responsibility. Conceptual models have been conventionally written using ER diagrams, UML class diagrams, and the like. Though these figures are easy to read for human beings, the figures themselves are not machine readable, and even if modeling tools are used, those that can be generated from diagrams are RDB's Create Table statements, class definitions of program languages such as Java In addition to being limited to the skeleton code level. And the drawing itself is a laborious task. Also, a human must manually define the entity's primary key and foreign key. Originally, as with the object id, the primary key must be one that can identify the instance, never changed due to the circumstances of the business, the foreign key is automatically guided by the type of association to the reference destination . It is nonsense that humans define such things one by one and lower the readability and persistence of the model. Therefore, in this paper, we propose domain specific language (DSL) which is easy to describe, specialized in describing the conceptual model of existence dependent analysis result which is human and machine readable. Proposed DSL can be obtained by database implementation of domain model and API specification for accessing them by processing with trial implemented compiler. Also, in the proposed DSL, history management can be specified as an attribute of an entity, and a document-oriented database is used together for history management. In this paper, we explain the syntax and elements and semantics of the proposed DSL, and seven examples are discussed and its descriptiveness was confirmed.
