Abstract Modern enterprise systems are likely to have a very long life. Their specifications therefore need to employ mechanisms that allow them to evolve during their lifetime; where they exploit generic components, these must be adaptable for use in novel situations. The paper looks at some of the issues that arise from this requirement, and how the exploitation of domain-specific language technologies in the tool-chain can assist in maintaining consistency of the specification as a whole. First, it reviews the final state of the family of standards supporting the ODP Enterprise Language, which is intended to handle this kind of application. In particular, it looks at the way the framework for defining policies can be used to accommodate changing requirements during the lifetime of an evolving system. It also looks at the way the idea of deontic tokens enables factoring out of the management of obligations from the basic behaviour of interacting system components. It then proposes a roadmap for building tools that can be used to unify the constraints from different areas of concern into a single specification. The approach taken is to exploit the power of domain-specific languages (DSLs) to allow designers in the various areas of concern to provide their input in terms natural to them. Finally, it looks at the way this approach promotes the establishment of a robust tool-chain capable of handling the evolution and scalability of enterprise systems. The paper uses a running example from the e-health domain to show how specific areas identified in the e-health standards can lead to language definitions, and so to tooling, that can be used to manage unified, system-wide specifications.

Several important choices need to be made during the development of domain-specific languages, including the one regarding which concrete syntax to implement.There are several alternatives, with graphical and textual syntaxes being the most common ones.Having in mind that the developers and domain experts often have different preferences, supporting both is sometimes the best option.This means that models created using textual editors might need to be opened using separately developed graphical editors.Graphical elements corresponding to model elements must then be automatically created and positioned.Doing so in an aesthetically pleasing way requires usage of graph layout algorithms.Since implementing them is not an easy task, most developers have to rely on existing solutions.There are many Java libraries which have such capabilities, but they all have certain limitations and room for improvement, some of which are addressed in a new graph drawing and analysis library presented in this paper.• offer a large number of different graph drawing algorithms, including some that haven't been implemented in Java yet• provide a very quick and easy way to lay out elements of any existing graphical editor• offer algorithms for graph analysis, which can later be used to automatically select a suitable layout algorithm• enable the users to specify aesthetic criteria and automatically choose an appropriate layout algorithm based on their wishes

This paper presents Kroki (fr. croquis - sketch), a tool for participatory development of business applications based on mockups. Kroki provides a graphical editor for visual creation of mockups and two engines (Web and desktop) for mockup execution. Kroki is developed in order to foster development agility, communication and better understanding of end-user needs. The mockup editor and engines are based on our EUIS (Enterprise User Interface Specification) DSL for specifying user interfaces of business applications.