Support for modular parsing in software reengineering

Peake, Ian; Salzman, Eric

doi:10.1109/step.1997.615464

Cited by 4 publications

(2 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Semantics are a more complex issue. The feature interaction problem [Zave 1999] has been described as the primary problem in extensible language development [Berners-Lee and Connolly 1998;Peake and Salzman 1997]. In our approach, ensuring semantic compatibility among language features is the responsibility of the ADL developer.…”

Section: Introductionmentioning

confidence: 99%

A comprehensive approach for the development of modular software architecture description languages

Dashofy

Hoek

Taylor

2005

ACM Trans. Softw. Eng. Methodol.

138

View full text Add to dashboard Cite

Research over the past decade has revealed that modeling software architecture at the level of components and connectors is useful in a growing variety of contexts. This has led to the development of a plethora of notations for representing software architectures, each focusing on different aspects of the systems being modeled. In general, these notations have been developed without regard to reuse or extension. This makes the effort in adapting an existing notation to a new purpose commensurate with developing a new notation from scratch. To address this problem, we have developed an approach that allows for the rapid construction of new architecture description languages (ADLs). Our approach is unique because it encapsulates ADL features in modules that are composed to form ADLs. We achieve this by leveraging the extension mechanisms provided by XML and XML schemas. We have defined a set of generic, reusable ADL modules called xADL 2.0, useful as an ADL by itself, but also extensible to support new applications and domains. To support this extensibility, we have developed a set of reflective syntax-based tools that adapt to language changes automatically, as well as several semantically-aware tools that provide support for advanced features of xADL 2.0. We demonstrate the effectiveness, scalability, and flexibility of our approach through a diverse set of experiences. First, our approach has been applied in industrial contexts, modeling software architectures for aircraft software and spacecraft systems. Second, we show how xADL 2.0 can be extended to support the modeling features found in two different representations for modeling product-line architectures. Finally, we show how our infrastructure has been used to support its own development. The technical contribution of our infrastructure is augmented by several research contributions: the first decomposition of an architecture description language into modules, insights about how to develop new language modules and a process for integrating them, and insights about the roles of different kinds of tools in a modular ADL-based infrastructure.

show abstract

Section: Introductionmentioning

confidence: 99%

A comprehensive approach for the development of modular software architecture description languages

Dashofy

Hoek

Taylor

2005

ACM Trans. Softw. Eng. Methodol.

138

View full text Add to dashboard Cite

show abstract

“…Concrete and abstract syntax must be located separately. We have accordingly developed a variant to Software Refinery's Dialect component -the "Language eXtension WorkBench" [9,10]. Dialect/LXWB remedies the above infelicities respectively as follows: syntax may be redefined at the level of granularity of a single production, and concrete and abstract syntax may be defined together in a single "language model" construct.…”

Section: Adaptabilitymentioning

confidence: 99%

Design derivation of an open, Java-based reengineering platform

Bailes¹,

Peake²

Seventh European Conference onSoftware Maintenance and Reengineering, 2003. Proceedings.

Self Cite

View full text Add to dashboard Cite

Essential reengineering platform functionality can be made more accessible, and even extended, using Java as a basis for platform development, as follows. The process of software reengineering tool development should be able to enjoy the benefits conferred by "open" enabling technologies. Reengineering tool development and use involves distinctive processes and thus has distinctive requirements of enabling technologies. The earlier dominant "Software Refinery" proprietary reengineering tool development platform is both lacking with respect to required reengineering characteristics and moreover has limited accessibility. However, using Java as basis, the functionality of the proprietary platform can be substantially recreated to achieve open technology goals of adaptability, portability, accessibility and eventually heterogeneity also.

show abstract