Abstract
In the paper a form-driven approach to the application development is presented. Our development environment IIS*Studio suports presented form-driven approach. It is aimed to provide the information system design and generating executable application prototypes. A form type is central IIS*Studio concept, used to model the structure and constraints of various business documents. On the one hand, a set of specified form types represents a platform independent model (PIM) of a real system. On the other hand, it is a PIM of the future software application. Starting from such a platform independent specification, through the chain of transformations, IIS*Studio generates a set of relational database subschemas in the 3 rd normal form and also a global relational database schema by integration of the subschemas. It enables a full implementation of database schemas under different target database management systems. IIS*Studio comprises a tool for the formal specification of business applications, and a generator of the executable application prototypes. The case study presented in the paper illustrates main features of IIS*Studio application generator tool and the methodological aspects of its usage. We consider the chain of transformations from a PIM, through the series of platform specific models with different degree of platform specificity, towards executable program code, as a crucial in our approach.
Highlights
A form is a way of organizing and presenting data
Specifying the form types must precede the design of a business application, because the specification of a business application in IIS*Studio comprises a structure of the selected form types
A form type is the central concept of our IIS*Studio tool aimed at automated information system (IS) design and application generation
Summary
A form is a way of organizing and presenting data. In the context of organization and its information system one can distinguish between business forms and computerized forms. Business forms (documents) are broadly used in organizations to conduct daily operations and to communicate with their affiliated entities (e.g. staff, superior managers, customers, suppliers, etc.) They may provide an important input source for database (db) schema design, since the most widely used data are gathered or reported in them ([1], [2], [3], [4]). This methodology uses the information extracted from both form structure and instances as a database reverse engineering input using an interaction with a user This approach inspired later research on extracting personalized ontology from data-intensive web application [12]. Bensliman based their approach on the idea that semantics can be extracted by applying a reverse engineering technique on the structures and the instances of HTMLforms which are the most convenient interface to communicate with relational databases on the current data-intensive web application This semantics is exploited to produce a personalized ontology.
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
