Attempto - From Specifications in Controlled Natural Language towards Executable Specifications

Deriving formal specifications from informal requirements is difficult since one has to take into account the disparate conceptual worlds of the application domain and of software development. To bridge the conceptual gap we propose controlled natural language as a textual view on formal specifications in logic. The specification language Attempto Controlled English (ACE) is a subset of natural language that can be accurately and efficiently processed by a computer, but is expressive enough to allow natural usage. The Attempto system translates specifications in ACE into discourse representation structures and into Prolog. The resulting knowledge base can be queried in ACE for verification, and it can be executed for simulation, prototyping and validation of the specification.Comment: 15 pages, compressed, uuencoded Postscript, to be presented at EMISA Workshop 'Naturlichsprachlicher Entwurf von Informationssystemen - Grundlagen, Methoden, Werkzeuge, Anwendungen', May 28-30, 1996, Ev. Akademie Tutzin

Correlating Business Process and Organizational Models to Manage Change

Business Process Management (BPM) provides the methods, tools and modelling notations to support a processcentric organizational view and management capability. As organizations grow in size and complexity, process improvement initiatives may involve change that has direct / significant impact across an organization. Thus, we provide methods and extensions to existing process modelling notations to analyse change against high- level models of the organization. Our approach permits improved analysis against higher-level organizational structures, motivations, inter-dependencies and capabilities that should be ideally considered as primary requirements during process design. Additionally, the organizational model becomes the ‘scaffolding’ with which to construct effective process architectures and management portfolios. This paper discusses our approach in the context of two modelling notations – the i* framework as an organizational modelling notation, and the BPMN notation for business process modelling

A model-driven method for the systematic literature review of qualitative empirical research

This paper explores a model-driven method for systematic literature reviews (SLRs), for use where the empirical studies found in the literature search are based on qualitative research. SLRs are an important component of the evidence-based practice (EBP) paradigm, which is receiving increasing attention in information systems (IS) but has not yet been widely-adopted. We illustrate the model-driven approach to SLRs via an example focused on the use of BPMN (Business Process Modelling Notation) in organizations. We discuss in detail the process followed in using the model-driven SLR method, and show how it is based on a hermeneutic cycle of reading and interpreting, in order to develop and refine a model which synthesizes the research findings of previous qualitative studies. This study can serve as an exemplar for other researchers wishing to carry out model-driven SLRs. We conclude with our reflections on the method and some suggestions for further researc

A Model-Driven Method for the Systematic Literature Review of Qualitative Empirical Research

This paper explores a new model-driven method for systematic literature reviews (SLRs), for use where the empirical studies found in the literature search are based on qualitative research. SLRs are an important component of the evidence-based practice (EBP) paradigm, which is receiving increasing attention in information systems (IS) but has not yet been widely-adopted. We illustrate the model-driven approach to SLRs via an example focused on the use of BPMN (Business Process Modelling Notation) in organizations. We discuss in detail the process followed in using the model-driven SLR method, and show how it is based on a hermeneutic cycle of reading and interpreting, in order to develop and refine a model which synthesizes the research findings of qualitative studies. This study can serve as an exemplar for other researchers wishing to carry out model-driven SLRs. We conclude with our reflections on the method and some suggestions for further research

A maturity model of evaluating requirements specification techniques

It is important to evaluate and understand the state-of-art technologies to position our research and invest our energy and resources in more effective ways. Unfortunately, no systematic approach has been introduced to evaluate the maturity of technologies except a few models such as Redwine/Riddle's model (Redwine and Riddle, 1985), which does not contain a significant concept, "goals" of technologies. A new goal-oriented, technology maturity evaluation model has been proposed in this present study. The model aids to measure how a technology meets the goal of the technology along with a well-defined procedure. The model has applied to evaluate the maturity of the requirements specification technology as a case study. The results showed that this approach promoted effectiveness of measuring the technology maturity and understanding the state-of-art technology

Requirements specification using concrete scenarios

The precision of formal specifications allows us to prove program correctness. Even if formal methods are not used throughout the software project, formalisation improves our understanding of the problem. Formal specifications are amenable to automated analysis and consistency checking. However using them is challenging. Customers do not understand formal notations. Specifiers have difficulty tackling large problems. Once systems are built, formal specifications quickly become outdated during software maintenance. A method of developing formal specifications using concrete scenarios is proposed to tackle the disadvantages just mentioned. A concrete scenario describes system behaviour with successive steps. The pre- and post-states of scenario steps are expressed with actual data rather than variables. Concrete scenarios are expressed in a natural language or formal notation. They increase customer involvement in the creation of formal specifications. Scenarios may be ranked by priorities allowing specifiers to focus on a small part of the system. Formal specifications are constructed incrementally. New requirements are also captured in concrete scenarios which guide the modification of formal specifications. On one hand, concrete scenarios assist the creation and maintenance of formal specifications. On the other hand, they facilitate program correctness proofs without using conventional formal specifications. This is achieved by adding implementation details to customer scenarios. The resulting developer scenarios, encapsulating decisions of data structures and algorithms, are generalised to operation schemas. With the implementation details, the schemas written in formal notations are programs rather than specifications.EThOS - Electronic Theses Online ServiceGBUnited Kingdo