By the same authors

From the same journal

Using formal metamodels to check consistency of functional views in information systems specification

Research output: Contribution to journal › Article

Standard

Using formal metamodels to check consistency of functional views in information systems specification. / Laleau, Regine; Polack, Fiona.

In: Information and Software Technology, Vol. 50, No. 7-8, 06.2008, p. 797-814.

Research output: Contribution to journal › Article

Harvard

Laleau, R & Polack, F 2008, 'Using formal metamodels to check consistency of functional views in information systems specification', Information and Software Technology, vol. 50, no. 7-8, pp. 797-814. https://doi.org/10.1016/j.infsof.2007.10.007

APA

Laleau, R., & Polack, F. (2008). Using formal metamodels to check consistency of functional views in information systems specification. Information and Software Technology, 50(7-8), 797-814. https://doi.org/10.1016/j.infsof.2007.10.007

Vancouver

Laleau R, Polack F. Using formal metamodels to check consistency of functional views in information systems specification. Information and Software Technology. 2008 Jun;50(7-8):797-814. https://doi.org/10.1016/j.infsof.2007.10.007

Author

Laleau, Regine ; Polack, Fiona. / Using formal metamodels to check consistency of functional views in information systems specification. In: Information and Software Technology. 2008 ; Vol. 50, No. 7-8. pp. 797-814.

Bibtex - Download

@article{b63dec93af8d4af3affbc21bbd18c127,
title = "Using formal metamodels to check consistency of functional views in information systems specification",
abstract = "UML notations require adaptation for applications such as Information Systems (IS). Thus we have defined IS-UML. The purpose of this article is twofold. First, we propose an extension to this language to deal with functional aspects of IS. We use two views to specify IS transactions: the first one is defined as a combination of behavioural UML diagrams (collaboration and state diagrams), and the second one is based on the definition of specific classes of an extended class diagram. The final objective of the article is to consider consistency issues between the various diagrams of an IS-UML specification. In common with other UML languages, we use a metamodel to define IS-UML. We use class diagrams to summarize the metamodel structure and a formal language, B, for the full metamodel. This allows us to formally express consistency checks and mapping rules between specific metamodel concepts. (C) 2007 Elsevier B.V. All rights reserved.",
keywords = "information system design, unified modelling language notation, metamodel, formal notation, UML",
author = "Regine Laleau and Fiona Polack",
note = "{\textcopyright} 2007 Elsevier B.V. This is an author produced version of a paper published in Information and Software Technology. Uploaded in accordance with the publisher's self-archiving policy.",
year = "2008",
month = jun,
doi = "10.1016/j.infsof.2007.10.007",
language = "English",
volume = "50",
pages = "797--814",
journal = "Information and Software Technology",
issn = "0950-5849",
publisher = "Elsevier",
number = "7-8",

}

RIS (suitable for import to EndNote) - Download

TY - JOUR

T1 - Using formal metamodels to check consistency of functional views in information systems specification

AU - Laleau, Regine

AU - Polack, Fiona

N1 - © 2007 Elsevier B.V. This is an author produced version of a paper published in Information and Software Technology. Uploaded in accordance with the publisher's self-archiving policy.

PY - 2008/6

Y1 - 2008/6

N2 - UML notations require adaptation for applications such as Information Systems (IS). Thus we have defined IS-UML. The purpose of this article is twofold. First, we propose an extension to this language to deal with functional aspects of IS. We use two views to specify IS transactions: the first one is defined as a combination of behavioural UML diagrams (collaboration and state diagrams), and the second one is based on the definition of specific classes of an extended class diagram. The final objective of the article is to consider consistency issues between the various diagrams of an IS-UML specification. In common with other UML languages, we use a metamodel to define IS-UML. We use class diagrams to summarize the metamodel structure and a formal language, B, for the full metamodel. This allows us to formally express consistency checks and mapping rules between specific metamodel concepts. (C) 2007 Elsevier B.V. All rights reserved.

AB - UML notations require adaptation for applications such as Information Systems (IS). Thus we have defined IS-UML. The purpose of this article is twofold. First, we propose an extension to this language to deal with functional aspects of IS. We use two views to specify IS transactions: the first one is defined as a combination of behavioural UML diagrams (collaboration and state diagrams), and the second one is based on the definition of specific classes of an extended class diagram. The final objective of the article is to consider consistency issues between the various diagrams of an IS-UML specification. In common with other UML languages, we use a metamodel to define IS-UML. We use class diagrams to summarize the metamodel structure and a formal language, B, for the full metamodel. This allows us to formally express consistency checks and mapping rules between specific metamodel concepts. (C) 2007 Elsevier B.V. All rights reserved.

KW - information system design

KW - unified modelling language notation

KW - metamodel

KW - formal notation

KW - UML

UR - http://www.scopus.com/inward/record.url?scp=42649122312&partnerID=8YFLogxK

U2 - 10.1016/j.infsof.2007.10.007

DO - 10.1016/j.infsof.2007.10.007

M3 - Article

VL - 50

SP - 797

EP - 814

JO - Information and Software Technology

JF - Information and Software Technology

SN - 0950-5849

IS - 7-8

ER -

York staff: edit these data