Executional data model using SQL

Generally, the development of the database application includes the requirement analysis phase of creating ERD (Entity Relationship Diagram) and process models, coding, and testing. From the above phases, the analysis phase is most informal. It is usually hard task because (1) customers don't know the details of the desired system; (2) developers can't with ease understand the business logic of the customers; (3) the outcomes of the analysis, which are ERD and process models, are not easy to understand to the customers. This paper proposes that the executional forms, which are better to understand, of the systems should be presented to the customers instead of ERD. These forms should accept the data input so that customers can review the various aspects of the outcome models. The developers should be able to instantly implement the business logic and also should be able to visually demonstrate the logic in order to get the details of it. For this goal, the customer supplied business logic should be able to be implemented by the references between forms, actions, and constraints from the perspective of the data flow. The customers try to execute the forms implementing the business logic, review their supplied logic, and find new necessary business logic of their own. Iterating these procedures for the requirement analysis would result in the success of the analysis which is sufficiently detailed without conflicts.