Language Requirements

This section presents the defined requirements, directly related to design decisions (DDs).

---

• RQ1. The DSL must be made available under an open-source license (DD1).

As the focus of the proposal is on the teaching process, the language must be open-source. The advantage that this requirement provides is the further evolution and collaborative maintenance with the involvement of other developers.

---

• RQ2. The DSL must allow the textual representation of conceptual DB models (DD1).

As it is an objective that the solution is another option concerning graphical approaches, this requirement is justified. This allows focusing on understanding the domain and developing the DSL.

---

• RQ3. The conceptual models must support the definition of entities, attributes, relationships, and cardinalities (DD2).

The tool used to develop the language needs to allow implementation of the domain concepts that govern the traditional ER diagram structure.

---

• RQ4. The conceptual models must support the definition of identifying attributes, generalization/specialization, self-relationships, and ternary relationships (DD2).

The language should allow more sophisticated domain concepts to be defined.

---

• RQ5. The implementation of DSL must perform the transformation from the conceptual to the logical model (DD3).

The solution must perform the transformation from conceptual to logical, displaying the generated result to the user.

---

• RQ6. The implementation of DSL must generate equivalent SQL statements based on the conceptual or logical model (DD4).

The solution needs to generate SQL statements for different DBMSs.

---

• RQ7. The implementation of DSL should generate some form of graphical representation (DD5).

The solution needs to perform diagram generation based on the conceptual model.