From OOA to GUI — The Janus System

Balzert, Helmut

doi:10.1007/978-1-5041-2896-4_53

Cited by 16 publications

(12 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In Rose's implementation of the UML [35], a use case is elaborated either by attaching a subordinate use case diagram (task decomposition) or several sequence diagrams. For work specifically addressing the relationship between task analysis and object-oriented methods, refer to [3,41].…”

Section: Use Case Diagram (Usecased)mentioning

confidence: 99%

See 1 more Smart Citation

Automated Prototyping of User Interfaces Based on UML Scenarios

Elkoutbi¹,

Khriss

Keller³

2006

Autom Software Eng

View full text Add to dashboard Cite

Abstract. User interface (UI) prototyping and scenario engineering have become popular techniques. Yet, the transition from scenario to formal specifications and the generation of UI code is still ill-defined and essentially a manual task, and the two techniques lack integration in the overall requirements engineering process. In this paper, we suggest an approach for requirements engineering that generates a user interface prototype from scenarios and yields a formal specification of the application. Scenarios are acquired in the form of collaboration diagrams as defined by the Unified Modeling Language (UML), and are enriched with user interface (UI) information. These diagrams are automatically transformed into UML Statechart specifications of the UI objects involved. From the set of obtained specifications, a UI prototype is generated that is embedded in a UI builder environment for further refinement. Based on end user feedback, the collaboration diagrams and the UI prototype may be iteratively refined, and the result of the overall process is a specification consisting of the Statechart diagrams of all the objects involved, together with the generated and refined prototype of the UI. The algorithms underlying this process have been implemented and exercised on a number of examples.

show abstract

Section: Use Case Diagram (Usecased)mentioning

confidence: 99%

“…Janus [3] derives the different windows of a UI from object models as introduced by Coad and Yourdon [6]. Non-abstract classes are transformed into windows; in case attributes or methods are marked as irrelevant for the UI, they are ignored in the transformation process.…”

Section: Related Workmentioning

confidence: 99%

Automated Prototyping of User Interfaces Based on UML Scenarios

Elkoutbi¹,

Khriss

Keller³

2006

Autom Software Eng

View full text Add to dashboard Cite

show abstract

“…To express these models, different notations have been used, but undoubtedly, the most commonly used are entity-relationship notation and UML class diagrams. Some of the MB-UIDEs using class diagrams are OVID [29], Janus [2], AME [17], Teallach [4], OO-H [7] and IdealXML [21]. Two of the Mb-UIDEs that use entity-relationship notation for domain modeling are Trident [5] and Genius [14].…”

Section: Related Workmentioning

confidence: 99%

Metamodels Infrastructure and Heuristics for Metamodel-Driven Multi-touch Interaction

López-Jaquero¹,

Navarro²,

Montero³

et al. 2013

Human-Computer Interaction – INTERACT 2013

View full text Add to dashboard Cite

Abstract. Novice users usually find it hard to manipulate models by using traditional Model-Driven Development techniques, because of the gap between the modeling tools and these users' mental models. In this context, multi-touch interfaces emerge as an alternative to make it easier for novice users to interact with the models by using natural gestures and taking advantage from the popularity that touch-based devices have achieved. In this paper, a metamodel infrastructure and a set of heuristics are presented to automatically generate multi-touch visual editors for manipulating models. The editor generated is driven by a metamodel that also prevents the user from creating not valid models. These heuristics have been validated while developing an environment for novice users, such as psychologists or physiotherapists, for the treatment of people with Acquired Brain Injury.

show abstract

“…GENIUS [5], JANUS [6], TRIDENT [7], GUIPS [8] are some examples of studies related to the automatic creation of a user interface. Table 1 sums up the characteristics of recent studies into the automatic creation of a user interface.…”

Section: Related Workmentioning

confidence: 99%

Usage-Centered Interface Design for Quality Improvement

Lee

Chang

Lee

2007

Computational Science – ICCS 2007

View full text Add to dashboard Cite

Abstract. As application development environment changes rapidly, importance of user interface design is increasing. Usually, most of designers are clustering by subjective method of individual to define objects that have relativity in design interface. But, interface which is designed without particular rules just adds inefficiency and complexity of business to user who use this system. We propose an object oriented design model that allows for flexible development by formalizing the user interface prototype in any GUI environment. The visual cohesion of the user interface is a new set of criteria which has been studied in relation to the user interface contents, and is founded on the basis of the cohesion of the interface as defined using basic software engineering concepts. The visual cohesion includes the issue of how each unit is arranged and grouped, as well as the cohesion of the business events which appear in the programming unit.

show abstract

From OOA to GUI — The Janus System

Cited by 16 publications

References 2 publications

Automated Prototyping of User Interfaces Based on UML Scenarios

Automated Prototyping of User Interfaces Based on UML Scenarios

Metamodels Infrastructure and Heuristics for Metamodel-Driven Multi-touch Interaction

Usage-Centered Interface Design for Quality Improvement

Contact Info

Product

Resources

About