Writing and verifying interoperability requirements: Application to collaborative processes
•The paper presents an interoperability requirements engineering process for interoperability requirements verification.•The verification is applied on collaborative processes.•A repository for interoperability requirements is proposed to manage interoperability requirements.•A Domain Specific Langu...
Gespeichert in:
| Veröffentlicht in: | Computers in industry 2016-10, Vol.82, p.1-18 |
|---|---|
| Hauptverfasser: | , , , |
| Format: | Artikel |
| Sprache: | eng |
| Schlagworte: | |
| Online-Zugang: | Volltext |
| Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
| container_end_page | 18 |
|---|---|
| container_issue | |
| container_start_page | 1 |
| container_title | Computers in industry |
| container_volume | 82 |
| creator | Daclin, N. Daclin, S. Mallek Chapurlat, V. Vallespir, B. |
| description | •The paper presents an interoperability requirements engineering process for interoperability requirements verification.•The verification is applied on collaborative processes.•A repository for interoperability requirements is proposed to manage interoperability requirements.•A Domain Specific Language is developed to allow stakeholders to write their own interoperability requirements.•The verification is performed thanks to formal technique such as model checking.
Interoperability analysis is highly correlated with interoperability requirements, the ability to grasp, structure, author and verify such requirements has become fundamental to the analytical process. To this end, requirements must be: (1) properly submitted in a suitable and usable repository; (2) written correctly by stakeholders with relevance to the studied domain; and (3) as easily verifiable as possible on various models of the system for which interoperability capabilities are being requested. The purpose of this article is to present both a structured repository for interoperability requirements and a Domain Specific Language to write and verify interoperability requirements – within a collaborative process model – using formal verification techniques. The interoperability requirements repository, which serves to structure interoperability requirements and make them available, is itself structured through abstraction levels, views and interoperability life cycle dimensions. Additional parameters detailing the requested information and the known impacts of requirements on behavior of the studied system have also been included. The Domain Specific Language provides the means for writing interoperability requirements. Afterwards, these requirements − more specifically the temporal requirements − are re-written into properties by transforming the temporal logic TCTL to allow for their effective verification by using the model checker UPPAAL. The overall approach is illustrated in a case study based on a collaborative drug circulation process. The article also draws conclusions and offers an outlook for future research and application efforts |
| doi_str_mv | 10.1016/j.compind.2016.04.001 |
| format | Article |
| fullrecord | <record><control><sourceid>proquest_hal_p</sourceid><recordid>TN_cdi_hal_primary_oai_HAL_hal_01930301v1</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><els_id>S0166361516300616</els_id><sourcerecordid>1835618892</sourcerecordid><originalsourceid>FETCH-LOGICAL-c451t-8f91a376308aaff231a3d93afeb17d01bb87b3bcd93d92d4831f8ff330c4ff6e3</originalsourceid><addsrcrecordid>eNqFkUGLFDEQhYMoOO76E4QGL3roNtXpSae9yLCoKwzsxWUPHkI6XdEMPUlvkhmYf781zOLBi7mEevmqeKnH2DvgDXCQn3aNjfvFh6lpqWx413AOL9gKVN_WEobuJVvRg6yFhPVr9ibnHafT93LFfj0kX3z4XZkwVUdM3p3OlQ8FU1wwmdHPvpyqhI8Hn3CPoeTP1WZZZm9N8TFUJVY2zrMZYyLhiNWSosWcMV-zV87MGd8-31fs_tvXnze39fbu-4-bzba23RpKrdwARvRScGWMc62gahqEcThCP3EYR9WPYrSkTUM7dUqAU84JwW3nnERxxT5e5v4xs16S35t00tF4fbvZ6rPGYRBccDgCsR8uLLl8PGAueu-zRfIfMB6yBiXWEpQaWkLf_4Pu4iEF-glRMAzQAkii1hfKpphzQvfXAXB9jkfv9HM8-hyP5p2meKjvy6UPaTNHj0ln6zFYnGjNtugp-v9MeALKupyb</addsrcrecordid><sourcetype>Open Access Repository</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>1819912116</pqid></control><display><type>article</type><title>Writing and verifying interoperability requirements: Application to collaborative processes</title><source>Elsevier ScienceDirect Journals Complete</source><creator>Daclin, N. ; Daclin, S. Mallek ; Chapurlat, V. ; Vallespir, B.</creator><creatorcontrib>Daclin, N. ; Daclin, S. Mallek ; Chapurlat, V. ; Vallespir, B.</creatorcontrib><description>•The paper presents an interoperability requirements engineering process for interoperability requirements verification.•The verification is applied on collaborative processes.•A repository for interoperability requirements is proposed to manage interoperability requirements.•A Domain Specific Language is developed to allow stakeholders to write their own interoperability requirements.•The verification is performed thanks to formal technique such as model checking.
Interoperability analysis is highly correlated with interoperability requirements, the ability to grasp, structure, author and verify such requirements has become fundamental to the analytical process. To this end, requirements must be: (1) properly submitted in a suitable and usable repository; (2) written correctly by stakeholders with relevance to the studied domain; and (3) as easily verifiable as possible on various models of the system for which interoperability capabilities are being requested. The purpose of this article is to present both a structured repository for interoperability requirements and a Domain Specific Language to write and verify interoperability requirements – within a collaborative process model – using formal verification techniques. The interoperability requirements repository, which serves to structure interoperability requirements and make them available, is itself structured through abstraction levels, views and interoperability life cycle dimensions. Additional parameters detailing the requested information and the known impacts of requirements on behavior of the studied system have also been included. The Domain Specific Language provides the means for writing interoperability requirements. Afterwards, these requirements − more specifically the temporal requirements − are re-written into properties by transforming the temporal logic TCTL to allow for their effective verification by using the model checker UPPAAL. The overall approach is illustrated in a case study based on a collaborative drug circulation process. The article also draws conclusions and offers an outlook for future research and application efforts</description><identifier>ISSN: 0166-3615</identifier><identifier>EISSN: 1872-6194</identifier><identifier>DOI: 10.1016/j.compind.2016.04.001</identifier><identifier>CODEN: CINUD4</identifier><language>eng</language><publisher>Amsterdam: Elsevier B.V</publisher><subject>Checkers ; Circulation ; Collaboration ; Computational Complexity ; Computer Aided Engineering ; Computer Science ; Correlation analysis ; Domain Specific Language ; Interoperability ; Interoperability requirements ; Mathematical analysis ; Mathematical models ; Modeling and Simulation ; Programming languages ; Repositories ; Repository for interoperability requirements ; Requirements analysis ; Requirements verification ; Studies ; Systems and Control ; Temporal logic</subject><ispartof>Computers in industry, 2016-10, Vol.82, p.1-18</ispartof><rights>2016</rights><rights>Copyright Elsevier Sequoia S.A. Oct 2016</rights><rights>Distributed under a Creative Commons Attribution 4.0 International License</rights><lds50>peer_reviewed</lds50><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c451t-8f91a376308aaff231a3d93afeb17d01bb87b3bcd93d92d4831f8ff330c4ff6e3</citedby><cites>FETCH-LOGICAL-c451t-8f91a376308aaff231a3d93afeb17d01bb87b3bcd93d92d4831f8ff330c4ff6e3</cites><orcidid>0000-0002-8610-1886 ; 0000-0001-8513-9471</orcidid></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://dx.doi.org/10.1016/j.compind.2016.04.001$$EHTML$$P50$$Gelsevier$$H</linktohtml><link.rule.ids>230,314,780,784,885,3550,27924,27925,45995</link.rule.ids><backlink>$$Uhttps://hal.science/hal-01930301$$DView record in HAL$$Hfree_for_read</backlink></links><search><creatorcontrib>Daclin, N.</creatorcontrib><creatorcontrib>Daclin, S. Mallek</creatorcontrib><creatorcontrib>Chapurlat, V.</creatorcontrib><creatorcontrib>Vallespir, B.</creatorcontrib><title>Writing and verifying interoperability requirements: Application to collaborative processes</title><title>Computers in industry</title><description>•The paper presents an interoperability requirements engineering process for interoperability requirements verification.•The verification is applied on collaborative processes.•A repository for interoperability requirements is proposed to manage interoperability requirements.•A Domain Specific Language is developed to allow stakeholders to write their own interoperability requirements.•The verification is performed thanks to formal technique such as model checking.
Interoperability analysis is highly correlated with interoperability requirements, the ability to grasp, structure, author and verify such requirements has become fundamental to the analytical process. To this end, requirements must be: (1) properly submitted in a suitable and usable repository; (2) written correctly by stakeholders with relevance to the studied domain; and (3) as easily verifiable as possible on various models of the system for which interoperability capabilities are being requested. The purpose of this article is to present both a structured repository for interoperability requirements and a Domain Specific Language to write and verify interoperability requirements – within a collaborative process model – using formal verification techniques. The interoperability requirements repository, which serves to structure interoperability requirements and make them available, is itself structured through abstraction levels, views and interoperability life cycle dimensions. Additional parameters detailing the requested information and the known impacts of requirements on behavior of the studied system have also been included. The Domain Specific Language provides the means for writing interoperability requirements. Afterwards, these requirements − more specifically the temporal requirements − are re-written into properties by transforming the temporal logic TCTL to allow for their effective verification by using the model checker UPPAAL. The overall approach is illustrated in a case study based on a collaborative drug circulation process. The article also draws conclusions and offers an outlook for future research and application efforts</description><subject>Checkers</subject><subject>Circulation</subject><subject>Collaboration</subject><subject>Computational Complexity</subject><subject>Computer Aided Engineering</subject><subject>Computer Science</subject><subject>Correlation analysis</subject><subject>Domain Specific Language</subject><subject>Interoperability</subject><subject>Interoperability requirements</subject><subject>Mathematical analysis</subject><subject>Mathematical models</subject><subject>Modeling and Simulation</subject><subject>Programming languages</subject><subject>Repositories</subject><subject>Repository for interoperability requirements</subject><subject>Requirements analysis</subject><subject>Requirements verification</subject><subject>Studies</subject><subject>Systems and Control</subject><subject>Temporal logic</subject><issn>0166-3615</issn><issn>1872-6194</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2016</creationdate><recordtype>article</recordtype><recordid>eNqFkUGLFDEQhYMoOO76E4QGL3roNtXpSae9yLCoKwzsxWUPHkI6XdEMPUlvkhmYf781zOLBi7mEevmqeKnH2DvgDXCQn3aNjfvFh6lpqWx413AOL9gKVN_WEobuJVvRg6yFhPVr9ibnHafT93LFfj0kX3z4XZkwVUdM3p3OlQ8FU1wwmdHPvpyqhI8Hn3CPoeTP1WZZZm9N8TFUJVY2zrMZYyLhiNWSosWcMV-zV87MGd8-31fs_tvXnze39fbu-4-bzba23RpKrdwARvRScGWMc62gahqEcThCP3EYR9WPYrSkTUM7dUqAU84JwW3nnERxxT5e5v4xs16S35t00tF4fbvZ6rPGYRBccDgCsR8uLLl8PGAueu-zRfIfMB6yBiXWEpQaWkLf_4Pu4iEF-glRMAzQAkii1hfKpphzQvfXAXB9jkfv9HM8-hyP5p2meKjvy6UPaTNHj0ln6zFYnGjNtugp-v9MeALKupyb</recordid><startdate>20161001</startdate><enddate>20161001</enddate><creator>Daclin, N.</creator><creator>Daclin, S. Mallek</creator><creator>Chapurlat, V.</creator><creator>Vallespir, B.</creator><general>Elsevier B.V</general><general>Elsevier Sequoia S.A</general><general>Elsevier</general><scope>AAYXX</scope><scope>CITATION</scope><scope>7SC</scope><scope>8FD</scope><scope>JQ2</scope><scope>L7M</scope><scope>L~C</scope><scope>L~D</scope><scope>1XC</scope><scope>VOOES</scope><orcidid>https://orcid.org/0000-0002-8610-1886</orcidid><orcidid>https://orcid.org/0000-0001-8513-9471</orcidid></search><sort><creationdate>20161001</creationdate><title>Writing and verifying interoperability requirements: Application to collaborative processes</title><author>Daclin, N. ; Daclin, S. Mallek ; Chapurlat, V. ; Vallespir, B.</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c451t-8f91a376308aaff231a3d93afeb17d01bb87b3bcd93d92d4831f8ff330c4ff6e3</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2016</creationdate><topic>Checkers</topic><topic>Circulation</topic><topic>Collaboration</topic><topic>Computational Complexity</topic><topic>Computer Aided Engineering</topic><topic>Computer Science</topic><topic>Correlation analysis</topic><topic>Domain Specific Language</topic><topic>Interoperability</topic><topic>Interoperability requirements</topic><topic>Mathematical analysis</topic><topic>Mathematical models</topic><topic>Modeling and Simulation</topic><topic>Programming languages</topic><topic>Repositories</topic><topic>Repository for interoperability requirements</topic><topic>Requirements analysis</topic><topic>Requirements verification</topic><topic>Studies</topic><topic>Systems and Control</topic><topic>Temporal logic</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Daclin, N.</creatorcontrib><creatorcontrib>Daclin, S. Mallek</creatorcontrib><creatorcontrib>Chapurlat, V.</creatorcontrib><creatorcontrib>Vallespir, B.</creatorcontrib><collection>CrossRef</collection><collection>Computer and Information Systems Abstracts</collection><collection>Technology Research Database</collection><collection>ProQuest Computer Science Collection</collection><collection>Advanced Technologies Database with Aerospace</collection><collection>Computer and Information Systems Abstracts Academic</collection><collection>Computer and Information Systems Abstracts Professional</collection><collection>Hyper Article en Ligne (HAL)</collection><collection>Hyper Article en Ligne (HAL) (Open Access)</collection><jtitle>Computers in industry</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Daclin, N.</au><au>Daclin, S. Mallek</au><au>Chapurlat, V.</au><au>Vallespir, B.</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Writing and verifying interoperability requirements: Application to collaborative processes</atitle><jtitle>Computers in industry</jtitle><date>2016-10-01</date><risdate>2016</risdate><volume>82</volume><spage>1</spage><epage>18</epage><pages>1-18</pages><issn>0166-3615</issn><eissn>1872-6194</eissn><coden>CINUD4</coden><abstract>•The paper presents an interoperability requirements engineering process for interoperability requirements verification.•The verification is applied on collaborative processes.•A repository for interoperability requirements is proposed to manage interoperability requirements.•A Domain Specific Language is developed to allow stakeholders to write their own interoperability requirements.•The verification is performed thanks to formal technique such as model checking.
Interoperability analysis is highly correlated with interoperability requirements, the ability to grasp, structure, author and verify such requirements has become fundamental to the analytical process. To this end, requirements must be: (1) properly submitted in a suitable and usable repository; (2) written correctly by stakeholders with relevance to the studied domain; and (3) as easily verifiable as possible on various models of the system for which interoperability capabilities are being requested. The purpose of this article is to present both a structured repository for interoperability requirements and a Domain Specific Language to write and verify interoperability requirements – within a collaborative process model – using formal verification techniques. The interoperability requirements repository, which serves to structure interoperability requirements and make them available, is itself structured through abstraction levels, views and interoperability life cycle dimensions. Additional parameters detailing the requested information and the known impacts of requirements on behavior of the studied system have also been included. The Domain Specific Language provides the means for writing interoperability requirements. Afterwards, these requirements − more specifically the temporal requirements − are re-written into properties by transforming the temporal logic TCTL to allow for their effective verification by using the model checker UPPAAL. The overall approach is illustrated in a case study based on a collaborative drug circulation process. The article also draws conclusions and offers an outlook for future research and application efforts</abstract><cop>Amsterdam</cop><pub>Elsevier B.V</pub><doi>10.1016/j.compind.2016.04.001</doi><tpages>18</tpages><orcidid>https://orcid.org/0000-0002-8610-1886</orcidid><orcidid>https://orcid.org/0000-0001-8513-9471</orcidid><oa>free_for_read</oa></addata></record> |
| fulltext | fulltext |
| identifier | ISSN: 0166-3615 |
| ispartof | Computers in industry, 2016-10, Vol.82, p.1-18 |
| issn | 0166-3615 1872-6194 |
| language | eng |
| recordid | cdi_hal_primary_oai_HAL_hal_01930301v1 |
| source | Elsevier ScienceDirect Journals Complete |
| subjects | Checkers Circulation Collaboration Computational Complexity Computer Aided Engineering Computer Science Correlation analysis Domain Specific Language Interoperability Interoperability requirements Mathematical analysis Mathematical models Modeling and Simulation Programming languages Repositories Repository for interoperability requirements Requirements analysis Requirements verification Studies Systems and Control Temporal logic |
| title | Writing and verifying interoperability requirements: Application to collaborative processes |
| url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2024-12-29T07%3A56%3A31IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_hal_p&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Writing%20and%20verifying%20interoperability%20requirements:%20Application%20to%20collaborative%20processes&rft.jtitle=Computers%20in%20industry&rft.au=Daclin,%20N.&rft.date=2016-10-01&rft.volume=82&rft.spage=1&rft.epage=18&rft.pages=1-18&rft.issn=0166-3615&rft.eissn=1872-6194&rft.coden=CINUD4&rft_id=info:doi/10.1016/j.compind.2016.04.001&rft_dat=%3Cproquest_hal_p%3E1835618892%3C/proquest_hal_p%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=1819912116&rft_id=info:pmid/&rft_els_id=S0166361516300616&rfr_iscdi=true |