Concepts for automating systems integration

Barkmeyer, Edward J.; Feeney, Allison Barnard; Denno, Peter; Flater, David W.; Libes, Don; Steves, Michelle P.; Wallace, Evan

doi:10.6028/nist.ir.6928

Cited by 25 publications

(15 citation statements)

References 32 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The former articulate concepts of interest for a locus of usage, in such a way that the concepts can be reused in contexts different from that in which they originally appear, but it is difficult to reason with them because they do not contain axioms or constraints. Ontologies of the latter group include all elements that enable inferences about the knowledge they contain [16][17].…”

Section: Mechatronics System Ontology (Mso)mentioning

confidence: 99%

Ontology-based information integration framework for mechatronics system multi-disciplinary design

Zhang

Fan

2008

2008 6th IEEE International Conference on Industrial Informatics

View full text Add to dashboard Cite

In order to meet the information integration requirement of mechatronics system multi-disciplinary design tools, an ontology-based information integration framework is proposed. This developed integration framework adopts component-based architecture which facilitates the design and simulation applications plug-and-play in the framework. Mechatronics System Ontology (MSO) is defined and the standard application component interfaces are specified. MSO includes all the major objects as well as the relationships of the objects in the process of mechatronics systems design and standard component interfaces provide applications a standard way to exchange information based on MSO.

show abstract

Section: Mechatronics System Ontology (Mso)mentioning

confidence: 99%

Ontology-based information integration framework for mechatronics system multi-disciplinary design

Zhang

Fan

2008

2008 6th IEEE International Conference on Industrial Informatics

View full text Add to dashboard Cite

show abstract

“…The Automated Methods for Integrating Systems (AMIS) project [2] at the National Institute of Standards and Technology (NIST) identifies several technologies available to develop automated methods for integration of software systems. It identifies semantic conflicts as an important issue in solving an integration problem.…”

Section: Introductionmentioning

confidence: 99%

Ontology formalization of product semantics for product lifecycle management

Patil¹,

Dutta²,

Sriram³

2005

View full text Add to dashboard Cite

Abstract-Product Lifecycle Management (PLM) is a concept that takes into account that the development of a product is influenced by knowledge from various stakeholders throughout its lifecycle. Computing environments in the PLM framework are expected to have several independent information resources. This requires a meaningful formal representation of product data semantics throughout the product's lifecycle. This paper presents an ontological approach to formalize product semantics into a Product Semantic Representation Language (PSRL). Building blocks to develop the explicit, extensible and comprehensive PSRL are described. The PSRL is open and based on standard W3C OWL constructs. The extensibility is demonstrated by considering an example product. The representation and the method of its development is expected to support several applications in the context of PLM. The use of OWL will enable the provision of the application software and information resources as Web services in the context of the Semantic Web.

show abstract

“…A viewpoint is an abstraction that yields the specification of the whole system restricted to a particular set of concerns, and it is created with a specific purpose in mind. In any given viewpoint it is possible to produce a model of the system that contains only the objects that are visible from that viewpoint [11]. Such a model is known as a viewpoint model, or view of the system from that viewpoint.…”

Section: Quadaimentioning

confidence: 99%

Validating a model-driven software architecture evaluation and improvement method: A family of experiments

González-Huerta

Insfrán

Abrahão

et al. 2015

Information and Software Technology

View full text Add to dashboard Cite

ElsevierGonzález Huerta, J.; Insfrán Pelozo, CE.; Abrahao Gonzales, SM.; Scanniello, G. (2015 Context: Software architectures should be evaluated during the early stages of software development in order to verify whether the Non-Functional Requirements (NFRs) of the product can be fulfilled. This activity is even more crucial in Software Product Line (SPL) development, since it is also necessary to identify whether the NFRs of a particular product can be achieved by exercising the variation mechanisms provided by the product line architecture or whether additional transformations are required. These issues have motivated us to propose QuaDAI, a method for the derivation, evaluation and improvement of software architectures in model-driven SPL development.Objective: We present in this paper the results of a family of four experiments carried out to empirically validate the evaluation and improvement strategy of QuaDAI. Method:The family of experiments was carried out by 92 participants: Computer Science Master's and undergraduate students from Spain and Italy. The goal was to compare the effectiveness, efficiency, perceived ease of use, perceived usefulness and intention to use with regard to participants using the evaluation and improvement strategy of QuaDAI as opposed to the Architecture Tradeoff Analysis Method (ATAM). Results:The main result was that the participants produced their best results when applying QuaDAI, signifying that the participants obtained architectures with better values for the NFRs faster, and that they found the method easier to use, more useful and more likely to be used. The results of the meta-analysis carried out to aggregate the results obtained in the individual experiments also confirmed these results. Conclusions:The results support the hypothesis that QuaDAI would achieve better results than ATAM in the experiments and that QuaDAI can be considered as a promising approach with which to perform architectural evaluations that occur after the product architecture derivation in model-driven SPL development processes when carried out by novice software evaluators.

show abstract

Concepts for automating systems integration

Cited by 25 publications

References 32 publications

Ontology-based information integration framework for mechatronics system multi-disciplinary design

Ontology-based information integration framework for mechatronics system multi-disciplinary design

Ontology formalization of product semantics for product lifecycle management

Validating a model-driven software architecture evaluation and improvement method: A family of experiments

Contact Info

Product

Resources

About