Towards a Semantic-based Approach for Modeling Regulatory Documents in Building Industry

Regulations in the Building Industry are becoming increasingly complex and involve more than one technical area. They cover products, components and project implementation. They also play an important role to ensure the quality of a building, and to minimize its environmental impact. In this paper, we are particularly interested in the modeling of the regulatory constraints derived from the Technical Guides issued by CSTB and used to validate Technical Assessments. We first describe our approach for modeling regulatory constraints in the SBVR language, and formalizing them in the SPARQL language. Second, we describe how we model the processes of compliance checking described in the CSTB Technical Guides. Third, we show how we implement these processes to assist industrials in drafting Technical Documents in order to acquire a Technical Assessment; a compliance report is automatically generated to explain the compliance or noncompliance of this Technical Documents

A FORMALIZED TRANSFORMATION PROCESS FOR GENERATING DESIGN MODELS FROM BUSINESS RULES

Business rules play a critical role in building and maintaining effective and flexible information systems. In light of that critical role, the publication of the Semantic Business Vocabulary and Business Rules standard (SBVR), has been regarded a highly significant advance. Following that release, a number of research efforts have been made to convert SBVR to design models, most of which are structural models represented in UML. However, so far the proposed methodologies tend to be of an exploratory nature in the sense that they are not built on a rigorous foundation. Our aim is to identify a core subset of the SBVR features and show how those core SBVR features can be translated into an equivalent UML structural model. To do that on a sound foundation, we first provide formal models of the core SBVR and the target UML class diagram. We then transform the core SBVR model to the UML class model, completed with proofs of correctness, and describe how the mapping rules can be applied in a transformation process. Finally, to show the usefulness of our formal approach, we discuss how it is used as a crucial component in a larger project, which embraces a number of practical objectives

BPMN: A Meta Model for the Happy Path

Recently, the OMG has been working on developing a new standard for a business process management notation (BPMN). This standard development results in documents that contain the newest approved version of a standard or a standard proposal that can be ammended. It is our vision that such a standard document, that also serves as a specification for BPMN modeling tool developers could benefit from a fact-oriented model in which the same domain knowledge is represented conceptually as a list of concept definitions (including naming conventions), a set of information structure diagrams and the constraints or business rules that govern the instances of the information structure diagrams. In this paper we will show precisely, how such a fact-oriented conceptual view on a standard document can be created, and we will show how a fact-oriented approach can improve the completeness of a specification.management information;

Specification of business rules for the development of hospital alarm system: application to the pharmaceutical validation.

6 pagesInternational audienceAlthough clinical alarm systems are part of the knowledge management setting within healthcare organisations, modelling of business processes related to decision support and knowledge representation of decision rules are seldom described. We propose a customization of the Unified Process that takes into account user requirements for clinical alarm systems by introducing the Semantics of Business Vocabulary and Business Rules (SBVR). This methodology was applied to the design and implementation of a clinical alarm system for pharmaceutical validation at the European Hospital Georges Pompidou (HEGP). Rules were implemented using the IlogJRules Business Rule Management System. We produced 3 business rules patterns and 427 instances of rules. As SBVR is close to natural language, pharmacists were able to understand rules and participate to their design

Towards a Rule Interchange Language for the Web

This articles discusses rule languages that are needed for a a full deployment of the SemanticWeb. First, it motivates the need for such languages. Then, it presents ten theses addressing (1) the rule and/or logic languages needed on the Web, (2) data and data processing, (3) semantics, and (4) engineering and rendering issues. Finally, it discusses two options that might be chosen in designing a Rule Interchange Format for the Web