Automated Code Generation for Industrial-Strength Systems

Model-driven engineering proposes to develop software systems by first creating an executable model of the system design and then transforming this model into an implementation. This paper discusses the design of an automatic code generation system that transforms such models into product implementations for highly reliable, industrial-strength systems. It provides insights, practical considerations, and lessons learned when developing code generators for applications that must conform to the constraints imposed by real-world, high-performance systems. Automatic code generation has played a large part in dramatically increasing both the quality and the reliability of software for these systems

Message sequence chart specifications with cross verification

Current software specification verification methods are usually performed within the context of the specification method. There is little cross verification, pitting one type of specification against another, taking place. The most common techniques involve syntax checks across specifications or doing specification transformations and running verification within the new context. Since viewpoints of a system are different even within programming teams we concentrate on producing an efficient way to run cross verification on specifications, particularly specifications written with Message Sequence Charts and State Transition Diagrams.;In this work an algorithm is proposed in which all conditional MSCs are transformed into an algebraic representations, Message Flow Graphs and by stepwise refinement, a Global State Transition Graph is created. This GSTG has all the properties of a State Transition Diagram and therefore can be analyzed in conjunction with the original STD

Comparative Evaluation of the State-of-art Requirements-based Test Case Generation Approaches

The overall aim of software testing is to deliver the error-free and high-quality software products to the end users. The testing process ensures that a software is aligned with the user specification and requirements.  In software testing process, there are many challenging tasks however test case generation process is considered as the most challenging one. The quality of the generated test cases has a significant impact on efficiency and effectiveness of the testing process.  In order to improve the quality of a developed software, the test cases should be able to achieve maximum adequacy in the testing and requirements' coverage. This paper presents a comparative evaluation of the prominent requirement-based test case generation approaches. Five evaluation criteria namely, inputs for test case generation, transformation techniques, coverage criteria, time and tool's support are defined to systematically compare the approaches. The results of the evaluation are used to identify the gap in the current approaches and research opportunities in requirement-based test case's generation.

Modular Feature Specification

CRESS (CHISEL Representation Employing Systematic Specification) is a notation and set of tools for graphical specification and analysis of features. It is applicable wherever a system consists of base functionality to which are added optionally selected features. The CRESS notation is introduced for basic diagrams, feature diagrams, and rules governing their behaviour. Although telephony is used to illustrate the approach, CRESS is not limited to this domain. The structure and use of the portable CRESS toolset is explained. CRESS can generate code for a variety of target languages. The strategy for translation to LOTOS is presented, along with some techniques for analysing the generated specifications

Modelling SIP Services using CRESS

CRESS (CHISEL Representation Employing Systematic Specification) is a notation and set of tools for graphical specification and analysis of services. It is applicable wherever a system consists of base functionality to which may be added selected services. The CRESS notation is introduced for root diagrams, service diagrams, and rules governing their behaviour. It is shown how CRESS can represent services in SIP (Session Initiation Protocol). For analysis, service diagrams can be automatically translated into LOTOS (Language Of Temporal Ordering Specification) or SDL (Specification and Description Language). For scripting, translation is into CPL (Call Processing Language) or CGI (Common Gateway Interface). The structure of the portable CRESS toolset is explained