Luigi Logrippo

Followers

Following

Co-author

Public Views

Interests

Uploads

Papers by Luigi Logrippo

Symboleo: Towards a Specification Language for Legal Contracts

2020 IEEE 28th International Requirements Engineering Conference (RE)

Feature Execution Trees and Interactions

Pdpta, 2002

Deriving use cases for distributed systems from knowledge requirements

Adt, 2000

Knowledge requirements for distributed systems express desired states of affairs concerning initi... more Knowledge requirements for distributed systems express desired states of affairs concerning initial and final knowledge of the components of a system. It is shown how use cases (i.e. sets of scenarios) can be obtained from knowledge requirements. The technique involves the use of event structures that specify use cases capable of achieving the requirements, and logical postconditions for events. The technique allows design refinement, both in the form of architectural refinement and in the form of event refinement. The correctness of refinements can be checked by checking logical implications. As an example, use cases and scenarios for a simple mobile telephony protocol, based on GPRS (the data extension of GSM) are derived, on the basis of the corresponding knowledge requirements. Scenarios are given in the form of Message Sequence Charts.

Download

Formal Methods after 15 Years: Status and Trends (Paper based on contributions of the panelists at the FORmal TEchnique '95, Conference, Montreal, October 1995)

Cn, 1996

File Structures, Program Structures, and Attributed Grammars

Ieee Transactions on Software Engineering, May 1, 1983

A language for defining sequential file structures, characterized as nested sequences of records ... more A language for defining sequential file structures, characterized as nested sequences of records having in common certain keys and types, is presented. "Input schemata" are defined as program skeletons that contain all the necessary control structure to process a specified file. A method for obtaining an input schema from the corresponding file structure definition is given. The method is based on attributed grammars, and has been implemented in the programming language PROLOG. This constitutes a formalization of some aspects of the data-directed program design method of Jackson and Warnier. Examples of applications of this method to business data processing problems such as file updating and report generation are given. Index Terms-Attributed grammars, data-directed program design, data processing, logical construction of programs, logic programming, program generation, program structure, PROLOG, sequential file structures, software engineering.

Download

Detecting feature interaction in CPL

ABSTRACT Abstract An approach,for detecting feature interactions in IETF’s Call Processing Langua... more ABSTRACT Abstract An approach,for detecting feature interactions in IETF’s Call Processing Language,(CPL) scripts is presented. The approach,is logic based in the sense that it uses a logic representation,of CPL scripts, of requirements and of detection rules and, in several cases, specific detection rules are shown to be derived from,requirements,by logical deduction. The Simple Formal Specification Language (SFSL) is introduced,to express,the intentions of CPL scripts in logic format. A method,for translating CPL into SFSL is presented. The rules address both interactions within a single script, and interactions between,two scripts. An automatic,feature interaction detection tool applying,these rules was implemented,in SWI-Prolog. The general method,is not specific to CPL and could be used in other feature interaction research. r,2005 Elsevier Ltd. All rights reserved. Keywords: Internet telephony; VoIP; Features; Services; Feature interaction; CPL; Call Processing Language

The ISO Reference Model for Open Distributed Processing-An Introduction

Abstract: The ISO Reference Model of Open Distributed Processing (RM-ODP) consists of four parts ... more Abstract: The ISO Reference Model of Open Distributed Processing (RM-ODP) consists of four parts - an Overview of the reference model, the Descriptive Model, the Prescriptive Model, and the Architectural Semantics. The four parts provide the concepts and rules of distributed processing to ensure openness between,interacting distributed application components. Openness is a combination of characteristics, i.e. scalability, accessibility, heterogeneity, autonomy

Feature Interactions in Telecommunications and Software Systems VII, June 11-13, 2003, Ottawa, Canada

Fiw, 2003

... for sharing their wisdom and experience, and the three invited speakers for providing enlight... more

An experience modelling telecommunications systems using ODP-DLcomp

IFIP Advances in Information and Communication Technology, 1997

The ODP-DLcomp language is intended to describe systems in the ODP computational model. It is obj... more The ODP-DLcomp language is intended to describe systems in the ODP computational model. It is object-oriented, implementation-independent and its formal semantics are based on LOTOS, thus it is a Formal Description Technique. It supports specification of interface and object templates, with appropriate creation and binding operations. An application of the language is demonstrated using the Plain Old Telephone System example.

Download

Personalization of internet telephony services for presence with SIP and extended CPL

Computer Communications, Nov 1, 2006

Abstract, This paper discusses issues of personalization of presence services in the context of I... more Abstract, This paper discusses issues of personalization of presence services in the context of Internet Telephony. Such services take into consideration the willingness and ability of a user to communicate in a network, as well as possibly other factors such as time, address, etc. Via a three-layer service ar-chitecture for communications in the Session Initiation Protocol (SIP) standard, presence system

Cluster analysis for the computer-assisted statistical analysis of melodies

Comput Hum, 1986

Download

Input-directed program design

Proceedings of the Acm 81 Conference, 1981

In spite of their importance in the world of computing, business data processing programming tech... more In spite of their importance in the world of computing, business data processing programming techniques have scarcely been studied in the recent literature on program verification and program synthesis (see among others (D, Jo)). Some authors seem to tacitly assume that business data processing programs are straightforward and can be constructed according to the same principles that apply to well-studied programs such as factorial, greatest common divisor, or sorting. Within a completely different research framework, Warnier (W) and Jackson (J) have shown that these programs indeed are structurally interesting and have their own rules of construction (see (CY) for a tutorial on these ideas). This paper attempts to bridge the gap existing between these two schools of thought.

Validation of Consistency and Completeness of Access Control Policy Sets

Architecture for Open Distributed Software Systems

Two Approaches for Advanced Presence Services in SIP Communications

2005 13th IEEE International Conference on Networks Jointly held with the 2005 IEEE 7th Malaysia International Conf on Communic, 2005

... Authors are Dongmei Jiang, Tet Hin Yeap, Ramiro Liscano and Luigi Logrippo D. Jiang is with t... more

Reusability at the Early Development Stages of Mobile Wireless Communication Systems

Development productivity and quality improvements, as well as cost reduction, are the main factor... more

Formal support for design techniques: a Timethreads-LOTOS approach

IFIP Advances in Information and Communication Technology, 1996

A design methodology which allies the graphical expressiveness of the timethread notation with th... more A design methodology which allies the graphical expressiveness of the timethread notation with the analytical power of the LOTOS language and its associated tools is presented. The concept of timethread is at the basis of a design methodology based on scenarios. A simple telephone system is used as an example. It is shown how the main scenarios of such a system can be expressed by the timethread notation, leading to an abstract system design. Further, it is shown how the notation can be translated into LOTOS. LOTOS tools are used to validate the high-level design. Tools used include LOLA for analysis and design testing, LMC for checking temporal logic properties, and GOAL for checking reachability of actions. Keywords FDT-based software engineering, tools and tool support, design and design validation, timethreads, LOTOS 1 INTRODUCTION 1.1 Context and motivation A software design methodology should meet two criteria: expressiveness and flexibility of the design language, and power of analysis and validation methods. For this reason, one seeks design methods that are based on expressive visual design notations, and formal analysis methods that are based on sound theoretical foundations. Design methods are intended to be used by system designers (architects or engineers) to describe systems (or system properties, such as scenarios, architecture and data transformation), while formal methods are used to verify that the system has the desired properties. Timethreads (Buhr and Casselman, 1992 and 1995) are a high-level design notation for distributed systems that expresses scenario paths. In this paper, we show how the formal language LOTOS and its associated analysis methods and tools can be used to analyze and validate timethreads visual design descriptions. Scenario-based approaches are now widely used in industry for the design of distributed systems. One of the main reasons is that scenarios describe top-level critical requirements that need to be fulfilled by any detailed design, and thereafter by implementations. Also, scenarios can usually be obtained easily from requirements. They express sequences of activities that need to be executed within the system in order to produce correct outputs from triggering events. The concept of timethreads has been defined to be used in early stages of design (highlevel design) to capture the different scenario paths that should drive the design process. They are used as a thinking tool in the requirement analysis phase where system designers try to understand the set of requirements as a whole before stepping into the detailed-design phase. Timethreads are defined as scenario paths because they illustrate paths along which scenarios flow in the system. One of the particularities of the timethread methodology is that individual timethreads can be composed into a diagram called timethread map. Also, unlike other models for scenario description, timethreads make abstraction of specific mechanisms of component interaction. They provide for a notion of refinement of activities from a level of abstraction to the next. Timethreads exist independently of any system structure, or decomposition. However, they are usually superimposed on structures, in which case they illustrate the sequences of activities through the set of system components. In this case, timethread activities, also called responsibilities in the timethread literature, are assigned to system components that become responsible to execute them in the detailed-design. Space does not allow us to mention all aspects of the timethread methodology. Suffice is to say that it covers different stages of high-level design development. The ISO standard FDT (Formal Description Technique) LOTOS (ISO, 1988) is used in this project for formal analysis and validation purpose. The reasons for choosing LOTOS are multiple. LOTOS allows to express both individual timethreads, as LOTOS processes, and interactions between timethreads in timethread maps, as LOTOS process interactions. It is executable with a formal operational semantics. Also, LOTOS possesses a hide operator that allows the designer to explicitly hide some gates in the specification, without having to modify the rest of the specification. This allows designers to focus on certain sets of activities when executing a specification. Finally, since LOTOS is an ISO standard, the number of tools that support it and the analysis and validation power of these tools are constantly increasing. Research on integrating LOTOS in a design discipline which was a forerunner of timethreads was described in (Vigder and Buhr, 1992). Timethreads were then called slices. In the context of object-oriented systems (Buhr and Casselman, 1995), the authors renamed timethreads as use case paths. Requirements Scenarios (timethreads) High-Level Design (timethread map) Analysis & Req. Capture Composition Validation Timethread map 1: Successful connection.

Download

Group Interrogation: A Group Programming Primitive

IFIP Advances in Information and Communication Technology, 1997

Renamings in parallel program schemas /

ABSTRACT

Telephone Service Specification: An Exercise in LOTOS Style

Luigi Logrippo

Uploads

Papers by Luigi Logrippo

Log In