Academia.eduAcademia.edu

Outline

Title
Abstract
Discussion and Experience
Discussion
References
All Topics
Computer Science
Software Engineering

From SysML/KAOS Domain Models to B System Specifications

Profile image of Amel MammarAmel Mammar

2018, arXiv (Cornell University)

Abstract

In this paper, we use a combination of the SysML/KAOS requirements engineering method, an extension of SysML, with concepts of the KAOS goal model, and of the B System formal method. Translation rules from a SysML/KAOS goal model to a B System specification have been defined. They allow to obtain a skeleton of the B System specification. To complete it, we have defined a language to express the domain model associated to the goal model. The translation of this domain model gives the structural part of the B System specification. The contribution of this paper is the description of translation rules from SysML/KAOS domain models to B System specifications. We also present the formal verification of these rules and we describe an open source tool that implements the languages and the rules. Finally, we provide a review of the application of the SysML/KAOS method on case studies such as for the formal specification of the hybrid ERTMS/ETCS level 3 standard.

Related papers

Bridging the gap between KAOS requirements models and B specifications
Abderrahman Matoussi, D. Petit

2009

Employing formal methods for complex systems specification is steadily growing from year to year. Whereas the formal specification process from abstraction to implementation via refinement is well understood, the traceability between initial user requirements (requirements analysis) and the corresponding formal specification is still unsatisfying and ambiguous. In fact, there is little research on reconciling the requirements phase with the formal specification phase. Consequently, the gap between the requirements phase and the formal specification phase continues to grow larger and the reconciliation seems more and more difficult and complicated. Our objective is to combine these two phases by using KAOS and the B method. KAOS is a goal-oriented methodology for requirements engineering enabling analysis to build requirements models and to derive requirements documents. B is a model-based formal method supported by tools and that allows the design of systems, from specification to implementation. For that purpose, we propose to derive the architecture of the B specification from the KAOS goal model. This makes traceability between KAOS requirements and B models more explicit.

View PDFchevron_right
Modeling the Hybrid ERTMS / ETCS Level 3 Implementation through Goal Diagrams and Ontologies Using the FORMOSE Approach
Amel Mammar

2018

This paper presents a specification of the hybrid ERTMS/ETCS level 3 implementation in the framework of the case study proposed for the 6th edition of the ABZ conference. The specification is based on the methodology and tools, raised from the ANR FORMOSE project, for the modeling and formal validation of critical and complex system requirements. The requirements are captured as SysML/KAOS goal diagrams and are automatically translated into B System specifications, in order to obtain the backbone of the formal specification. Domain properties are captured as ontologies through the SysML/ KAOS domain modeling language, based on OWL and PLIB. From these ontologies is automatically extracted the structural part of the system formal specification that completes the result of the translation of goal diagrams. The system construction is thus incremental, based on refinement mechanisms existing within the involved methods and leads to a formally correct system, while eliminating any unnece...

View PDFchevron_right
The SysML/KAOS Domain Modeling Approach
Amel Mammar

2017

A means of building safe critical systems consists of formally modeling the requirements formulated by stakeholders and ensuring their consistency with respect to application domain properties. This paper proposes a metamodel for an ontology modeling formalism based on OWL and PLIB. This modeling formalism is part of a method for modeling the domain of systems whose requirements are captured through SysML/KAOS. The formal semantics of SysML/KAOS goals are represented using Event-B specifications. Goals provide the set of events, while domain models will provide the structure of the system state of the Event-B specification. Our proposal is illustrated through a case study dealing with a Cycab localization component specification. The case study deals with the specification of a localization software component that uses GPS,Wi-Fi and sensor technologies for the realtime localization of the Cycab vehicle, an autonomous ground transportation system designed to be robust and completely ...

View PDFchevron_right
Requirements specification and modeling through SysML
Jos Vrancken

2007 IEEE International Conference on Systems, Man and Cybernetics, 2007

Use Case diagrams are well-known for their use to specify and describe system requirements. From initial system requirements documents, use cases can be derived representing several scenarios. These scenarios can later be detailed in different ways, as for example, through informal descriptions. In this paper, system requirements are first specified using the SysML requirements diagram and later by use cases. The main goal is to fill the gap between documents written in natural language and use cases by modeling requirements in a graphical and tabular way, which can improve the requirements representation. Also, the relationship between requirements is enhanced. An example of a real time distributed system is given to illustrate the approach.

View PDFchevron_right
A formal approach using SysML for capturing functional requirements in avionics domain
Raphael Faudou

Chinese Journal of Aeronautics, 2019

In this work, a Model-Based Systems Engineering approach based on SysML is proposed. This approach is used for the capture and the definition of functional requirements in avionics domain. The motivation of this work is triple: guide the capture of functional requirements, validate these functional requirements through functional simulation, and verify efficiently the consistency of these functional requirements. The proposed approach is decomposed into several steps that are detailed to go from conceptual model of avionics domain to a formal functional model that can be simulated in its operating context. To achieve this work, a subset of SysML has been used as an intermediate modelling language to ensure progressive transformation that can be understood and agreed by system stakeholders. Formal concepts are introduced to ensure theoretical consistency of the approach. In addition, transformation rules are defined and the mappings between concepts of ARP4754A civil aircraft guidelines and SysML are formalized through meta-model. The resulting formalization enables engineers to perform functional simulation of the top-level functional architecture extracted from operational scenarios. Finally, the approach has been tested on an industrial avionics system called the Onboard Maintenance System.

View PDFchevron_right
3.5.2 Tesperanto - A Model-Based System Specification Methodology and Language
Alex Blekhman

INCOSE International Symposium, 2013

Technical requirements, specifications, and standards are fundamental documents that serve all the stages of the systems engineering management process. This paper presents Tesperanto-"Technical Esperanto"a model-based methodology and language for authoring, analysis, design, and testing of system specifications, and its integrated development environment. Tesperanto is an English text that is generated automatically from the evolving graphical model of the system being specified, creating corresponding textmodel representation of technical information. Tesperanto was evaluated in a case study over a period of more than two years by a multinational group of systems engineering and enterprise management experts as a means to enhance text in ISO international standards. The evaluation showed that Tesperanto improves the consistency and quality of standards and can potentially be of similar value for other kinds of technical documents.

View PDFchevron_right
Model-Driven User Requirements Specification using SysML
Michel Soares

Journal of Software, 2008

Requirements engineering is an important phase in a system's life cycle. When poorly performed, various problems may occur, such as failures, cost overrun and delays. The increasing complexity of systems makes requirements engineering activities both more important and more difficult. Model-driven engineering, in which models are the main artifact during system development, is an emergent approach that tries to address system complexity by the intense use of models. This article proposes a model-driven approach to requirements engineering based on SysML Requirements and Use Case Diagrams. The main advantages are that user requirements are graphically modeled, their relationships are explicitly mapped, and system decomposition is considered in the early system development activities. In addition, requirements traceability is enhanced by using the SysML Requirements tables. The approach is illustrated by a list of user requirements for a road traffic management system.

View PDFchevron_right
Formalizing a subset of ERTMS/ETCS specifications for verification purposes
Mohamed Ghazel

Transportation Research Part C: Emerging Technologies, 2014

View PDFchevron_right
REMO2V'06 845 From Requirements Models to Formal Specifications in B
Christophe Ponsard

2009

Abstract. The development of critical systems requires a high assurance process from requirements to the running code. Formal methods, such as B, now provide industry-strength tools to develop abstract models, refine them in more concrete models and finally turn them into code. A major remaining weakness in the development chain is the gap between textual or semi-formal requirements and formal models. In this paper, we explore how to cope with this problem using a goal-oriented approach to elaborate a pertinent model, including regulation modelling, and turn it into a high quality abstract formal specification. 1

View PDFchevron_right
Model-Based System Design Using SysML
Mara Nikolaidou

2016

Model-based system design is served by a single, multi-layered model supporting all design activities, in different levels of detail. SysML is a modeling language, endorsed by OMG, for system engineering, which aims at defining such models for system design. It provides discrete diagrams to describe system structure and components, to explore allocation policies crucial for system design, and to identify design requirements. In this chapter, SysML is used for the model-based design of enterprise information system architecture, supporting a systemic view of such systems, where software and hardware entities are treated as system components composed to create the system architecture. SysML extensions to facilitate the effective description of non-functional requirements, especially quantitative ones, and their verification are presented. The integration of evaluation parameters and results into a discrete SysML diagram enhances the requirement verification process,

View PDFchevron_right

References (35)

  1. A. van Lamsweerde, Requirements Engineering -From System Goals to UML Models to Software Specifications. Wiley, 2009.
  2. C. Gnaho and F. Semmak, "Une extension SysML pour l'ingénierie des exigences dirigée par les buts," in 28e Congrès INFORSID, France, 2010, pp. 277-292.
  3. A. Mammar and R. Laleau, "On the use of domain and system knowledge modeling in goal-based Event-B specifications," in ISoLA 2016, Lecture Notes in Computer Science. Springer, pp. 325-339.
  4. F. Boniol and V. Wiels, "The landing gear system case study," ser. ABZ. Springer, 2014.
  5. J. Abrial, Modeling in Event-B -System and Software Engineering. Cambridge University Press, 2010.
  6. ANR-14-CE28-0009, "Formose ANR project," 2017. [Online]. Available: http://formose.lacl.fr/
  7. ClearSy, "Atelier B: B System," 2014. [Online]. Available: http://clearsy.com/
  8. S. Tueno, R. Laleau, A. Mammar, and M. Frappier, "Formal Representation of SysML/KAOS Domain Models ," ArXiv e-prints, cs.SE, 1712.07406, Dec. 2017. [Online]. Available: https://arxiv.org/pdf/1712.07406.pdf
  9. A. Matoussi, F. Gervais, and R. Laleau, "A goal-based approach to guide the design of an abstract Event-B specification," in ICECCS 2011. IEEE Computer Society, pp. 139-148.
  10. S. Tueno, R. Laleau, A. Mammar, and M. Frappier, "The SysML/KAOS Domain Modeling Approach," ArXiv e-prints, cs.SE, 1710.00903, Sep. 2017. [Online]. Available: https://arxiv.org/pdf/1710.00903.pdf
  11. --, "Towards using ontologies for domain modeling within the sysml/kaos approach," in IEEE 25th International Requirements Engineering Conference Workshops, RE 2017 Workshops, Lisbon, Portugal, September 4-8, 2017. IEEE Computer Society, 2017, pp. 1-5. [Online]. Available: https://doi.org/10.1109/REW.2017.22
  12. K. Sengupta and P. Hitzler, "Web ontology language (OWL)," in Encyclopedia of Social Network Analysis and Mining, 2014, pp. 2374-2378.
  13. G. Pierra, "The PLIB ontology-based approach to data integration," in IFIP 18th World Computer Congress, ser. IFIP, vol. 156. Kluwer/Springer, 2004, pp. 13-18.
  14. I. UL, "Owlgred home," 2017. [Online]. Available: http://owlgred.lumii.lv/
  15. H. H. Wang, D. Damljanovic, and J. Sun, "Enhanced semantic access to formal software models," in Formal Methods and Software Engineering -ICFEM, Lecture Notes in Computer Science, vol. 6447. Springer, 2010, pp. 237-252.
  16. E. Doberkat, "The Object-Z specification language," Softwaretechnik-Trends, vol. 21, no. 1, 2001.
  17. J. S. Dong, J. Sun, and H. H. Wang, "Z approach to semantic web," in Formal Methods and Software Engineering - ICFEM, Lecture Notes in Computer Science, vol. 2495. Springer, 2002, pp. 156-167.
  18. F. van Harmelen, P. F. Patel-Schneider, and I. Horrocks, "Reference description of the DAML+ OIL ontology markup language," 2001.
  19. I. Poernomo and T. Umarov, "A mapping from normative requirements to Event-B to facilitate verified data-centric business process management," ser. CEE-SET Lecture Notes in Computer Science, vol. 7054. Springer, 2009, pp. 136-149.
  20. E. Alkhammash, M. J. Butler, A. S. Fathabadi, and C. Cîrstea, "Building traceable Event-B models from requirements," Sci. Comput. Program., vol. 111, pp. 318-338, 2015.
  21. Alkhammash, Eman H., "Derivation of Event-B Models from OWL Ontologies," MATEC Web Conf., vol. 76, p. 04008, 2016.
  22. C. Snook and M. Butler, "UML-B: Formal Modeling and Design Aided by UML," ACM Trans. Softw. Eng. Methodol., vol. 15, no. 1, pp. 92-122, Jan. 2006.
  23. R. Laleau and A. Mammar, "An overview of a method and its support tool for generating B specifications from UML notations." The Fifteenth IEEE International Conference on Automated Software Engineering, ASE 2000, 2000, pp. 269-272.
  24. S. Tueno, R. Laleau, A. Mammar, and M. Frappier, "Event-B Specification of Translation Rules," 2017. [Online]. Available: https://github.com/stuenofotso/SysML_KAOS_Domain_Model_Parser/tree/master/ SysMLKAOSDomainModelRules
  25. --, "SysML/KAOS Domain Modeling Tool," 2017. [Online]. Available: https://github.com/stuenofotso/SysML_ KAOS_Domain_Model_Parser
  26. Jetbrains, "Jetbrains mps," 2017. [Online]. Available: https://www.jetbrains.com/mps/
  27. S. Tueno, M. Frappier, R. Laleau, and A. Mammar, "Modeling the Hybrid ERTMS/ETCS Level 3 Standard Using a Formal Requirements Engineering Approach," Springer proceedings of 6th International ABZ Conference, 2018.
  28. S. Tueno, R. Laleau, A. Mammar, and M. Frappier, "The SysML/KAOS Domain Modeling Language (Tool and Case Studies)," 2018. [Online]. Available: https://github.com/stuenofotso/SysML_KAOS_Domain_Model_ Parser/tree/master
  29. Y. A. Ameur, M. Baron, L. Bellatreche, S. Jean, and E. Sardet, "Ontologies in engineering: the OntoDB/OntoQL platform," Soft Comput., vol. 21, no. 2, pp. 369-389, 2017.
  30. T. S. Hoang, M. Butler, and K. Reichl, "The Hybrid ERTMS/ETCS Level 3 Case Study," ABZ, pp. 1-3, 2018. [Online]. Available: https://github.com/stuenofotso/SysML_KAOS_Domain_Model_Parser/blob/master/ ABZ18_ERTMS/ERTMS_L3_Hybrid.pdf
  31. EEIG ERTMS Users Group, "Hybrid ERTMS/ETCS Level 3: Principles," Ref. 16E042 Version 1A, Jul. 2017.
  32. F. Nicola, v. H. Henri, A. Laura, and B. Maarten, "ERTMS Level 3: the Game-Changer," IRSE News View, p. 232, Apr. 2017.
  33. M. J. Butler, C. B. Jones, A. Romanovsky, and E. Troubitsyna, Eds., Rigorous Development of Complex Fault- Tolerant Systems, ser. Lecture Notes in Computer Science, vol. 4157. Springer, 2006.
  34. S. Tueno, R. Laleau, A. Mammar, and M. Frappier, "SysML/KAOS Approach on the Hybrid ERTMS/ETCS Level 3 case study," 2018. [Online]. Available: https://github.com/stuenofotso/SysML_KAOS_Domain_Model_ Parser/tree/master/ABZ18_ERTMS
  35. A. Mammar, M. Frappier, S. Tueno, and R. Laleau, "An Event-B Model of the Hybrid ERTMS/ETCS Level 3 Standard," Springer proceedings of 6th International ABZ Conference ASM, Alloy, B, TLA, VDM, Z, 2018.

Related papers

SysML/KAOS Domain Models and B System Specifications
Amel Mammar

2018

In this paper, we use a combination of the SysML/KAOS requirements engineering method, an extension of SysML, with concepts of the KAOS goal model, and of the B System formal method. Translation rules from a SysML/KAOS goal model to a B System specification have been defined. They allow to obtain a skeleton of the B System specification. To complete it, we have defined a language to express the domain model associated to the goal model. The translation of this domain model gives the structural part of the B System specification. The contribution of this paper is the description of translation rules from SysML/KAOS domain models to B System specifications. We also present the formal verification of these rules and we describe an open source tool that implements the languages and the rules. Finally, we provide a review of the application of the SysML/KAOS method on case studies such as for the formal specification of the hybrid ERTMS/ETCS level 3 standard.

View PDFchevron_right
Event-B Expression and Verification of Translation Rules Between SysML/KAOS Domain Models and B System Specifications
Amel Mammar

Lecture Notes in Computer Science

In this paper, we use a combination of the SysML/KAOS requirements engineering method, an extension of SysML, with concepts of the KAOS goal model, and of the B System formal method. Translation rules from a SysML/KAOS goal model to a B System specification have been defined. They allow to obtain a skeleton of the B System specification. To complete it, we have defined a language to express the domain model associated to the goal model. The translation of this domain model gives the structural part of the B System specification. The contribution of this paper is the description of translation rules from SysML/KAOS domain models to B System specifications. We also present the formal verification of these rules and we describe an open source tool that implements the languages and the rules. Finally, we provide a review of the application of the SysML/KAOS method on case studies such as for the formal specification of the hybrid ERTMS/ETCS level 3 standard.

View PDFchevron_right
A first attempt to combine SysML requirements diagrams and B
Ahmed Hammad

Innovations in Systems and Software Engineering, 2010

This article describes a work-in-progress in the framework of a research project aiming at combining requirements engineering methods with formal methods. The main idea is to extend the SysML language with concepts of existing requirements engineering methods. In this article we present extensions to SysML with concepts from the goal model of the KAOS method and we give rules to derive a formal B specification from this goal model. The approach is then illustrated on a case study.

View PDFchevron_right
Modeling the Hybrid ERTMS/ETCS Level 3 Standard Using a Formal Requirements Engineering Approach
Amel Mammar

Lecture Notes in Computer Science

This paper presents a specification of the hybrid ERTM-S/ETCS level 3 standard in the framework of the case study proposed for the 6th edition of the ABZ conference. The specification is based on the method and tools, developed in the ANR FORMOSE project, for the modeling and formal verification of critical and complex system requirements. The requirements are specified with SysML/KAOS goal diagrams and are automatically translated into B System specifications, in order to obtain the architecture of the formal specification. Domain properties are specified by ontologies with the SysML/KAOS domain modeling language, based on OWL and PLIB. Their automatic translation completes the structural part of the formal specification. The only part of the specification, which must be manually completed, is the body of events. The construction is incremental, based on the refinement mechanisms existing within the involved methods. The formal specification of the case study is composed of seven refinement levels and all the proofs have been discharged with the Rodin prover.

View PDFchevron_right
Formal Representation of SysML/KAOS Domain Model (Complete Version)
Amel Mammar

ArXiv, 2017

Nowadays, the usefulness of a formal language for ensuring the consistency of requirements is well established. The work presented here is part of the definition of a formally-grounded, model-based requirements engineering method for critical and complex systems. Requirements are captured through the SysML/KAOS method and the targeted formal specification is written using the Event-B method. Firstly, an Event-B skeleton is produced from the goal hierarchy provided by the SysML/KAOS goal model. This skeleton is then completed in a second step by the Event-B specification obtained from system application domain properties that gives rise to the system structure. Considering that the domain is represented using ontologies through the SysML/KAOS Domain Model method, is it possible to automatically produce the structural part of system Event-B models ? This paper proposes a set of generic rules that translate SysML/KAOS domain ontologies into an Event-B specification. The rules have been...

View PDFchevron_right

Related topics

  • Computer Science
  • Goal Modeling
  • Systems Modeling Language
    • 580 California St., Suite 400
    San Francisco, CA, 94104
    © 2025 Academia. All rights reserved