205,209 research outputs found
Specification and implementation of the Larch shared language
This project aims to prototype formal specification in Larch. The motivation for looking at formal specifications stems from an appreciation of the problem outlined above, frustration with current methods, and a desire to practise what is preached. The aim is to implement a formal specification language, to write a non-trivial specification and to employ formal methods of specification during software development. As a result, one should have a thorough understanding of a formal specification language, and the practical implications of using it as a basis for formal methods
Formal Specification Language for Vehicular Ad-Hoc Networks
Vehicular Ad-Hoc Network (VANET) is a form of Mobile Ad-Hoc Network (wireless
Network), originally used to provide safety & comfort for passengers, & currently being
used to establish Dedicated Short Range Communications (DSRC) among near by
Vehicles (V2V Communications) and between vehicles and nearby fixed infrastructure
equipments; Roadside equipments (V2I Communications). VANET was used also to
warn drivers of collision possibilities, road sign alarms, auto-payment at road tolls and
parks. Usually VANET can be found in Intelligent Transportation Systems (ITS).
VANET is the current and near future hot topic for research, that has been
targeted by many researchers to develop some applications and protocols specifically for
the VANET. But a problem facing all VANET researchers is the unavailability of a
formal specification language to specify the VANET systems, protocols, applications and
scenarios proposed by those researchers.
A specification language is a formal language that is used during the systems
design, analysis, and requirements analysis. Using a formal specification language, a
researcher can show “What his system does”, Not How.
As a contribution of our research we have created a formal specification language
for VANET. We made the use of some Romans characters & some basic symbols to
represent VANET Systems & Applications. In addition, we have created some combined
symbols to represent actions and operations of the VANET system and its participating
devices. Our formal specification language covers many of the VANET aspects, and
offers Validity Test and Consistency Test for the systems.
Using our specification language, we have presented three different case studies
based on a VANET system model we have created and put them into the system validity
and consistency tests and showed how to describe a VANET system and its applications
using our formal specification language
Recommended from our members
Generating natural language descriptions of Z test cases
Critical software most often requires an independent validation and verification (IVV). IVV is usually performed by domain experts, who are not familiar with specific, many times formal, development technologies. In addition, model-based testing (MBT) is a promising testing technique for the verification of critical software. Test cases generated by MBT tools are logical descriptions. The problem is, then, to provide natural language (NL) descriptions of these test cases, making them accessible to domain experts. In this paper, we present ongoing research aimed at finding a suitable method for generating NL descriptions from test cases in a formal specification language. A first prototype has been developed and applied to a real-world project in the aerospace sector
A Survey of Languages for Specifying Dynamics: A Knowledge Engineering Perspective
A number of formal specification languages for knowledge-based systems has been developed. Characteristics for knowledge-based systems are a complex knowledge base and an inference engine which uses this knowledge to solve a given problem. Specification languages for knowledge-based systems have to cover both aspects. They have to provide the means to specify a complex and large amount of knowledge and they have to provide the means to specify the dynamic reasoning behavior of a knowledge-based system. We focus on the second aspect. For this purpose, we survey existing approaches for specifying dynamic behavior in related areas of research. In fact, we have taken approaches for the specification of information systems (Language for Conceptual Modeling and TROLL), approaches for the specification of database updates and logic programming (Transaction Logic and Dynamic Database Logic) and the generic specification framework of abstract state machine
Modelling the pacemaker in event-B: towards methodology for reuse
The cardiac pacemaker is one of the system modelling problems posed to the Formal Methods community by the {\it Grand Challenge for Dependable Systems Evolution} \cite{JOW:06}. The pacemaker is an intricate safety-critical system that supports and moderates the dysfunctional heart's intrinsic electrical control system. This paper focusses on (i) the problem (requirements) domain specification and its mapping to solution (implementation) domain models, (ii) the significant commonality of behaviour between its many operating modes, emphasising the potential for reuse, and (iii) development and verification of models.We introduce the problem and model three of the operating modes in the problem domain using a state machine notation. We then map each of these models into a solution domain state machine notation, designed as shorthand for a refinement-based solution domain development in the Event-B formal language and its RODIN toolki
Formalization and classification of product requirements using axiomatic theory of design modeling
The objective of the present thesis is to transform the customer requirement described in a natural language into a formal specification. The effective specification of product requirements is critical for designers to deliver a quality design solution in a reasonable range of cost and time. No significant research results have been reported in the literature regarding the generation of formal design specification, regardless of its important roles in product development. A good specification depends on a well-defined classification and categorization of product requirements, on flexible means of representation that can capture the various structures behind the requirements, and also on the formalization of natural language based description of the design problem. The present thesis proposes two criteria to classify the product requirements based on the structure of the product-environment. A graphical language, named ROM, is developed to represent the formal specification of the design problem. Since majority of design problems are described in a natural language, the relationship between the formal specification and the structure of natural language is investigated in the present thesis by the formal linguistic analysi
- …