Citation Context

...ell(...) bookId : BookId title : String nbLoans : int Member register(...) unregister(...) memberId : MId name : String Loan lend(...) renew(...) return(...) loanDate : Date dueDate : Date (a) entity type book (bId : BookId) ∆= acquire(bId, , , ) · ( (loan(bId, )∗ || rId : RId : reservations(rId, bId) ) · sell(bId) attribute nbLoans(s : Trace, bId : BookId)) ∆= case last(s) = acquire(bId, , , ) : return 0; last(s) ∈ {lend(ca, , ), renew(ca, )} : return 1 + nbLoans(front(s), bId); otherwise : return nbLoans(front(s), bId) endCase (b) (c) Figure 1: An example of an eb3 specification formats. In [7, 12], the authors show how sequence diagrams can be translated into a statechart diagram. The first approach [7] uses a framework, called the minimally adequate teacher, to synthesize a state machine by interacting with the designer, in order to obtain additional details not available in the sequence diagrams. The second approach is automatic (no user intervention). Conflicts between sequence diagrams are detected and resolved. In both approaches, the resulting statecharts must be refined by designers in order to completely specify a system. Actions are defined using the Object Constraint Langage ...

Citation Context

... models, data models, objects models, graphical user interface layout, and perform basic translation of these models into executable code. But the bulk of the design, programming and testing is manually done by humans. These three activities consume up to 70 % of the development effort. They are usually not hard to realize, but they are time consuming and error-prone. The key in reducing development cost and increasing quality clearly resides in suppressing/mechanizing these three tasks. 2.2 Model-Based Interface Development Environments Model-based interface development environments (MB-IDE) [8] address the issue of generating a GUI from abstract models. These models describe various aspects like the application functions, data, window contents, dialogue (interactions between the users and the systems), user tasks, platform, etc. The presentation model describes which association and filtering conditions to use for an entity, and the graphical representation of entities. The dialogue model describes the system reaction to a user action. The user model defines the access privilege and preferences of a user (e.g., limited access to some entity types, attributes, or entities, special-pu...

Citation Context

...ue model describes the system reaction to a user action. The user model defines the access privilege and preferences of a user (e.g., limited access to some entity types, attributes, or entities, special-purpose representations of some data). A knowledge-base, algorithms and mapping rules, sometimes supplemented with human guidance, can generate a concrete GUI from the abstract models. Early approaches (e.g., [4]) were able to generate a standard (single style) interface from a data model. Recent approaches have focused on providing more flexibility for specifying a wider ranger of GUI styles [9, 11] to satisfy various user requirements. The main challenges facing MB-IDE are i) the composition of the various models in order to obtain a coherent GUI, and ii) management of model complexity in order to achieve greater flexibility in GUI style. Model complexity significantly increases when more flexibility is provided. MB-IDE are still at the research prototype level; there is no commercial product available. The industrial tool PollenLight, from e-Companion, shares similarities with MB-IDE. It generates a GUI from UML models, which are not as complete and sophisticated as the models used in ...

Citation Context

...ems), user tasks, platform, etc. The presentation model describes which association and filtering conditions to use for an entity, and the graphical representation of entities. The dialogue model describes the system reaction to a user action. The user model defines the access privilege and preferences of a user (e.g., limited access to some entity types, attributes, or entities, special-purpose representations of some data). A knowledge-base, algorithms and mapping rules, sometimes supplemented with human guidance, can generate a concrete GUI from the abstract models. Early approaches (e.g., [4]) were able to generate a standard (single style) interface from a data model. Recent approaches have focused on providing more flexibility for specifying a wider ranger of GUI styles [9, 11] to satisfy various user requirements. The main challenges facing MB-IDE are i) the composition of the various models in order to obtain a coherent GUI, and ii) management of model complexity in order to achieve greater flexibility in GUI style. Model complexity significantly increases when more flexibility is provided. MB-IDE are still at the research prototype level; there is no commercial product availa...

Citation Context

...ue model describes the system reaction to a user action. The user model defines the access privilege and preferences of a user (e.g., limited access to some entity types, attributes, or entities, special-purpose representations of some data). A knowledge-base, algorithms and mapping rules, sometimes supplemented with human guidance, can generate a concrete GUI from the abstract models. Early approaches (e.g., [4]) were able to generate a standard (single style) interface from a data model. Recent approaches have focused on providing more flexibility for specifying a wider ranger of GUI styles [9, 11] to satisfy various user requirements. The main challenges facing MB-IDE are i) the composition of the various models in order to obtain a coherent GUI, and ii) management of model complexity in order to achieve greater flexibility in GUI style. Model complexity significantly increases when more flexibility is provided. MB-IDE are still at the research prototype level; there is no commercial product available. The industrial tool PollenLight, from e-Companion, shares similarities with MB-IDE. It generates a GUI from UML models, which are not as complete and sophisticated as the models used in ...

Citation Context

...ell(...) bookId : BookId title : String nbLoans : int Member register(...) unregister(...) memberId : MId name : String Loan lend(...) renew(...) return(...) loanDate : Date dueDate : Date (a) entity type book (bId : BookId) ∆= acquire(bId, , , ) · ( (loan(bId, )∗ || rId : RId : reservations(rId, bId) ) · sell(bId) attribute nbLoans(s : Trace, bId : BookId)) ∆= case last(s) = acquire(bId, , , ) : return 0; last(s) ∈ {lend(ca, , ), renew(ca, )} : return 1 + nbLoans(front(s), bId); otherwise : return nbLoans(front(s), bId) endCase (b) (c) Figure 1: An example of an eb3 specification formats. In [7, 12], the authors show how sequence diagrams can be translated into a statechart diagram. The first approach [7] uses a framework, called the minimally adequate teacher, to synthesize a state machine by interacting with the designer, in order to obtain additional details not available in the sequence diagrams. The second approach is automatic (no user intervention). Conflicts between sequence diagrams are detected and resolved. In both approaches, the resulting statecharts must be refined by designers in order to completely specify a system. Actions are defined using the Object Constraint Langage ...

Citation Context

...of generating an executable system from the specification. The foundations of the case tool are abstract models of IS (formal functional specifications) and algorithms that generates an executable system from these models (modelbased interface development environment – MB-IDE), and specification interpretation. The apis project has to a) define a comprehensive set of integrated models for information systems, b) develop new algorithms for specification interpretation and code generation, and c) implement them in a case tool. The eb3 specification language will be the foundation for the models [5]. It is a formal, object-oriented, executable language which is very well adapted for the functional specification of IS. eb3 will be supplemented with a language to specify graphical user interfaces (GUI) in order to have a comprehensive model of an IS. The apis project will be the first to study the automation of information systems production from formal specifications. The success of the apis project would represent a significant breakthrough in terms of productivity and quality in IS development. apis could cut up to 50 % of the cost of IS development, because it would relieve software de...

Citation Context

...more abstract than traditional state-machine oriented specification languages like B, Z or VDM. Entity process expressions provide a more explicit representation of the system behavior; they can be graphically represented using their entity structure diagrams (JSD-like). Attribute definitions are encapsulated in a single expression, which facilitates their understanding and maintenance. To ease the integration of eb3 in an industrial environment, we have also defined a UML-like syntax for eb3 which looks more familiar to practitioners; it allows them to specify using traditional UML construct [10]. 2.4 UML The de facto standards in industry for modeling information systems are UML and structured analysis techniques. UML contains several diagrams; some of them contain the same information, but it is represented in different 2 Book acquire(...) sell(...) bookId : BookId title : String nbLoans : int Member register(...) unregister(...) memberId : MId name : String Loan lend(...) renew(...) return(...) loanDate : Date dueDate : Date (a) entity type book (bId : BookId) ∆= acquire(bId, , , ) · ( (loan(bId, )∗ || rId : RId : reservations(rId, bId) ) · sell(bId) attribute nbLoans(s : Trace, bI...