"Integrare", a Collaborative Environment for Behavior-Oriented Design

in this paper, we introduce a new cooperative design and visualization environment, called "integrare", which supports designers and developers in building dependable, component-based systems using a new behavior-oriented design method. This method has advantages in terms of its abilities to manage complexity, find defects and make checks of dependability. The environment integrates and unifies several tools that support multiple phases of the design process, allowing them to interact and exchange information, as well as providing efficient editing capabilities. it can help formalize individual natural language functional requirements as Behavior Trees. These trees can be composed to create an integrated tree-like view of all the formalized requirements. The environment manages complexity by allowing multiple users to work independently on requirements translation and tree editing in a collaborative mode. Once a design is constructed from the requirements, it can be visually simulated with respect to an underlying operational semantics, and formally verified by way of a model checker.

[1]  César Muñoz,et al.  An Overview of SAL , 2000 .

[2]  Gilles Motet,et al.  A UML model consistency verification approach based on meta-modeling formalization , 2006, SAC.

[3]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[4]  Yanchun Zhang,et al.  Achieving convergence, causality preservation, and intention preservation in real-time cooperative editing systems , 1998, TCHI.

[5]  R. Geoff Dromey,et al.  From requirements to design: formalizing the key steps , 2003, First International Conference onSoftware Engineering and Formal Methods, 2003.Proceedings..

[6]  Barry W. Boehm,et al.  Verifying and Validating Software Requirements and Design Specifications , 1989, IEEE Software.

[7]  Guillermo Som Visual Studio 2005 , 2005 .

[8]  Gilles Motet,et al.  UML 2.0 Consistency Rules Identification , 2005, Software Engineering Research and Practice.

[9]  Robert L. Glass Is this a revolutionary idea, or not? , 2004, CACM.

[10]  Gul A. Agha,et al.  Concurrent object-oriented programming , 1993, CACM.

[11]  Tilmann F. W. Bruckhaus The impact of inserting a tool into a software process , 1993, CASCON.

[12]  Brian Henderson-Sellers,et al.  A metamodel for the behavior trees modelling technique , 2005, Third International Conference on Information Technology and Applications (ICITA'05).

[13]  Rolf Ernst,et al.  An Event-Driven Multi-Threading Architecture for Embedded Systems , 1997, CODES.

[14]  Saad Zafar,et al.  Integrating safety and security requirements into design of an embedded system , 2005, 12th Asia-Pacific Software Engineering Conference (APSEC'05).

[15]  Kai Lin,et al.  Maintaining multi-way dataflow constraints in collaborative systems , 2005, 2005 International Conference on Collaborative Computing: Networking, Applications and Worksharing.

[16]  Jürgen Börstler,et al.  The PLUSS toolkit?: extending telelogic DOORS and IBM-rational rose to support product line use case modeling , 2005, ASE '05.

[17]  Fabrice Bouquet,et al.  Mastering Test Generation from Smart Card Software Formal Models , 2004, CASSIS.

[18]  Kai Lin,et al.  Maintaining Constraints in Collaborative Graphic Systems: the CoGSE Approach , 2005, ECSCW.

[19]  Shaoying Liu Formal Engineering for Industrial Software Development: Using the SOFL Method , 2004 .

[20]  Edmund M. Clarke,et al.  Formal Methods: State of the Art and Future Directions Working Group Members , 1996 .

[21]  Jocelyn Simmonds,et al.  A tool for automatic UML model consistency checking , 2005, ASE '05.

[22]  Geoff Dromey,et al.  Scaleable Formalization of Imperfect Knowledge , 2006 .

[23]  Peter A. Lindsay,et al.  An Automated Failure Mode and Effect Analysis Based on High-Level Design Specification with Behavior Trees , 2005, IFM.

[24]  Lian Wen,et al.  From requirements change to design change: a formal path , 2004, Proceedings of the Second International Conference on Software Engineering and Formal Methods, 2004. SEFM 2004..

[25]  Robert Colvin,et al.  Early Validation and Verification of a Distributed Role-Based Access Control Model , 2007, 14th Asia-Pacific Software Engineering Conference (APSEC'07).

[26]  Harold Ossher,et al.  Software engineering tools and environments: a roadmap , 2000, ICSE '00.

[27]  Chengzheng Sun,et al.  Consistency maintenance in real-time collaborative graphics editing systems , 2002, TCHI.

[28]  Stephen Travis Pope,et al.  A cookbook for using the model-view controller user interface paradigm in Smalltalk-80 , 1988 .

[29]  Shaoying Liu,et al.  Formal Engineering for Industrial Software Development , 2004, Springer Berlin Heidelberg.

[30]  Lawrence Chung,et al.  Managing change in an OTS-aware requirements engineering approach , 2005, ACM SIGSOFT Softw. Eng. Notes.

[31]  Geoff Dromey,et al.  Early Requirements Defect Detection(INVITED PUBLICATION) , 2005 .

[32]  Elvinia Riccobene,et al.  A framework to simulate UML models: moving from a semi-formal to a formal environment , 2004, SAC '04.

[33]  Betty H. C. Cheng,et al.  A general framework for formalizing UML with formal languages , 2001, Proceedings of the 23rd International Conference on Software Engineering. ICSE 2001.

[34]  Kirsten Winter,et al.  Formalising Behaviour Trees with CSP , 2004, IFM.

[35]  Peter A. Lindsay,et al.  An environment for building a system out of its requirements , 2004, Proceedings. 19th International Conference on Automated Software Engineering, 2004..

[36]  Robert Colvin,et al.  Verification of an Integrated Role-Based Access Control Model , 2006 .

[37]  Alan Bundy,et al.  Constructing Induction Rules for Deductive Synthesis Proofs , 2006, CLASE.

[38]  Lian Wen,et al.  Architecture Normalization for Component-based Systems , 2006, FACS.

[39]  Stephen Gilmore,et al.  Mobile Resource Guarantees for Smart Devices , 2004, CASSIS.