An ontology-based knowledge framework for engineering material selection

Engineering material selection intensively depends on domain knowledge. In the face of the large number and wide variety of engineering materials, it is very necessary to research and develop an open, shared, and scalable knowledge framework for implementing domain-oriented and knowledge-based material selection. In this paper, the fundamental concepts and relationships involved in all aspects of material selection are analyzed in detail. A novel ontology-based knowledge framework is presented. The ontology-based Semantic Web technology is introduced into the semantic representation of material selection knowledge. The implicit material selection knowledge is represented as a set of labeled instances and RDF instance graphs in terms of the concept model, which provides a formal approach to organizing the captured material selection knowledge. A knowledge retrieval and reasoning approach integrating ontology concepts, instances, knowledge rules, and semantic queries encoded with Query-enhanced Web Rule Language (SQWRL) is proposed. The presented knowledge framework can provide powerful knowledge services for material selection. Finally, based on this knowledge framework, a case study on constructing a mold material selection knowledge system is provided. This work is a new attempt to build an open and shared knowledge framework for engineering material selection.     

The KlaperSuite framework for model-driven reliability analysis of component-based systems

Automatic prediction tools play a key role in enabling the application of non-functional requirements analysis, to simplify the selection and the assembly of components for component-based software systems, and in reducing the need for strong mathematical skills for software designers. By exploiting the paradigm of Model-Driven Engineering (MDE), it is possible to automatically transform design models into analytical models, thus enabling formal property verification. MDE is the core paradigm of the KlaperSuite framework presented in this paper, which exploits the KLAPER pivot language to fill the gap between design and analysis of component-based systems for reliability properties. KlaperSuite is a family of tools empowering designers with the ability to capture and analyze quality of service views of their systems, by building a one-click bridge towards a number of established verification instruments. In this article, we concentrate on the reliability-prediction capabilities of KlaperSuite and we evaluate them with respect to several case studies from literature and industry.     

The design and use of the TMiner component-based data mining framework

This paper provides some practical guidelines for the design of data mining frameworks. It describes the rationale behind some of the key design decisions that guided the design, development, and implementation of the TMiner component-based data mining framework. TMiner is a flexible framework that can be used as a stand-alone tool or integrated into larger business intelligence (BI) solutions. TMiner is a general-purpose component-based system designed to support the whole KDD process into a single framework and thus facilitate the implementation of complex data mining scenarios.     

Design of a component-based integrated environmental modeling framework

Integrated environmental modeling (IEM) includes interdependent science-based components that comprise an appropriate software modeling system and are responsible for consuming and producing information as part of the system, but moving information from one component to another (i.e., interoperability) is the responsibility of the IEM software system. We describe and discuss the Framework for Risk Analysis in Multimedia Environmental Systems (FRAMES), a component-based IEM system, from the standpoint of software design requirements which define system functionalities. Design requirements were identified in a series of workshops, attended by IEM practitioners, and reported in the development of a number of IEM software systems. The requirements cover issues associated with standards, component connectivity, linkage protocols, system architecture and functionality, and web-based access, all of which facilitate the creation of plug & play components from stand-alone models through a series of software support tools and standards.     

基于构件技术的快速样机原型的软件框架

以自主研发的HLRESP（honeycomb-like rapid embedded system platform）快速样机系统为基础,提出一种基于构件技术地快速样机原型的软件框架。该软件系统以Eclipse开放平台为基础,并采纳了角色的概念,使之能够支持一定程度上的多人协作开发任务。提出了板级IP（BLIP）的概念,使其在软件系统中的管理方式与FPGA内的IP管理方式一致,简化了软件设计工作。对于IP库的管理,使用了XML（extensible markup language）表示IP（intellectual property）,结合CVS版本控制系统,使得用户能够方便地从IP构件库中获得、配置并集成IP。     

基于ARM Cortex-M4的构件化汇编框架的研究

规范易用的汇编框架与样例是微处理器深层次应用开发的基础,但汇编编程复杂,并且目前针对32位ARM Cortex-M4的汇编程序资料和样例程序非常匮乏,学习难度大,开发工作困难重重。在深入分析ARM Cortex-M4汇编指令系统和寻址方式的基础上,以NXP半导体公司发布的Kinetis K(KK)系列MCU为蓝本,根据软件工程思想和构件设计理论,提出层次架构的工程框架建模思想,并构建基于ARM Cortex-M4内核的构件化汇编框架,据此制作GPlO驱动构件。指示灯闪烁样例工程的设计及测试结果表明了汇编框架规范、实用、易用,能降低嵌入式汇编语言的学习难度。框架能为业界基于ARM Cortex-M4的汇编开发提供参考。     

A framework for automated distributed implementation of component-based models

Although distributed systems are widely used nowadays, their implementation and deployment are still time-consuming, error-prone, and hardly predictable tasks. In this paper, we propose a method for producing automatically efficient and correct-by-construction distributed implementations from a model of the application software in Behavior, Interaction, Priority (BIP). BIP is a well-founded component-based framework encompassing high-level multi-party interactions for synchronizing components (e.g., rendezvous and broadcast) and dynamic priorities for scheduling between interactions. Our method transforms an arbitrary BIP model into a Send/Receive BIP model that is directly implementable on distributed execution platforms. The transformation consists in (1) breaking the atomicity of actions in components by replacing synchronous multiparty interactions with asynchronous Send/Receive interactions; (2) inserting distributed controllers that coordinate the execution of interactions according to a user-defined partition of interactions, and (3) adding a distributed algorithm for handling conflicts between controllers. The obtained Send/Receive BIP model is proven observationally equivalent to its corresponding initial model. Hence, all functional properties of the initial BIP model are preserved by construction in the implementation. Moreover, the obtained Send/Receive BIP model can be used to automatically derive distributed executable code. The proposed method is fully implemented. Currently, it is possible to generate C++ implementations for (1) TCP sockets for conventional distributed communication, (2) MPI for multi-processor platforms, and (3) POSIX threads for deployment on multi-core platforms. We present four case studies and report experimental results for different design choices including partition of interactions and choice of algorithm for distributed conflict resolution.     

Constructing component-based software engineering environments: issues and experiences

Developing software engineering tools is a difficult task, and the environments in which these tools are deployed continually evolve as software developers’ processes, tools and tool sets evolve. To more effectively develop such evolvable environments, we have been using component-based approaches to build and integrate a range of software development tools, including CASE and workflow tools, file servers and versioning systems, and a variety of reusable software agents. We describe the rationale for a component-based approach to developing such tools, the architecture and support tools we have used some resultant tools and tool facilities we have developed, and summarise the possible future research directions in this area.     

A framework to integrate design knowledge reuse and requirements management in engineering design

This paper presents a framework to integrate requirements management and design knowledge reuse. The research approach begins with a literature review in design reuse and requirements management to identify appropriate methods within each domain. A framework is proposed based on the identified requirements. The framework is then demonstrated using a case study example: vacuum pump design. Requirements are presented as a component of the integrated design knowledge framework. The proposed framework enables the application of requirements management as a dynamic process, including capture, analysis and recording of requirements. It takes account of the evolving requirements and the dynamic nature of the interaction between requirements and product structure through the various stages of product development.     

rCOS: a formal model-driven engineering method for component-based software

Model-driven architecture (MDA) has become a main stream technology for software-intensive system design. The main engineering principle behind it is that the inherent complexity of software development can only be mastered by building, analyzing and manipulating system models. MDA also deals with system complexity by providing component-based design techniques, allowing independent component design, implementation and deployment, and then system integration and reconfiguration based on component interfaces. The model of a system in any stage is an integration of models of different viewpoints. Therefore, for a model-driven method to be applied effectively, it must provide a body of techniques and an integrated suite of tools for model construction, validation, and transformation. This requires a number of modeling notations for the specification of different concerns and viewpoints of the system. These notations should have formally defined syntaxes and a unified theory of semantics. The underlying theory of the method is needed to underpin the development of tools and correct use of tools in software development, as well as to formally verify and reason about properties of systems in mission-critical applications. The modeling notations, techniques, and tools must be designed so that they can be used seamlessly in supporting development activities and documentation of artifacts in software design processes. This article presents such a method, called the rCOS, focusing on the models of a system at different stages in a software development process, their semantic integration, and how they are constructed, analyzed, transformed, validated, and verified.     

Reducing verification effort in component-based software engineering through built-in testing

Today component- and service-based technologies play a central role in many aspects of enterprise computing. However, although the technologies used to define, implement, and assemble components have improved significantly over recent years, techniques for verifying systems created from them have changed very little. The correctness and reliability of component-based systems are still usually checked using the traditional testing techniques that were in use before components and services became widespread, and the associated costs and overheads still remain high. This paper presents an approach that addresses this problem by making the system verification process more component-oriented. Based on the notion of built-in tests (BIT)—tests that are packaged and distributed with prefabricated, off-the-shelf components—the approach partially automates the testing process, thereby reducing the level of effort needed to establish the acceptability of the system. The approach consists of a method that defines how components should be written to support and make use of run-time tests, and a resource-aware infrastructure that arranges for tests to be executed when they have a minimal impact on the delivery of system services. After providing an introduction to the principles behind component-based verification and explaining the main features of the approach and its supporting infrastructure, we show by means of a case study how it can reduce system verification effort.     

Knowledge management of product design: A requirements-oriented knowledge management framework based on Kansei engineering and knowledge map

For the knowledge management of product design, knowledge innovation is the foundation and motivation for the independent innovation and enhancing the core competitiveness. Most of the product knowledge exists in the brain of designers. How to obtain the required knowledge accurately in massive knowledge database becomes the key to knowledge innovation. However, the design knowledge based on consumer’s requirement has not been extensively studied. There is no consensus on the reasonable and effective implementation of the knowledge management framework to select the optimum design knowledge based on the consumer’s requirements. In this study, to efficiently realize the knowledge acquisition and knowledge selection, a requirements-oriented knowledge management model is established, with the advantage of Kansei engineering in knowledge acquisition and multi-objective decision-making in knowledge selection. Finally, the outdoor leisure chairs design is used as a case study to explain the implementation of the knowledge management framework. To reveal the advantages of the framework, it was compared with other frameworks. The results show that the proposed knowledge management framework is more efficient and provided a method of designers to acquire design knowledge based on the consumer’s requirements.     

Editorial to theme issue on model-driven engineering of component-based software systems

Software and Systems Modeling - This theme issue aims at providing a forum for disseminating latest trends in the use and combination of model-driven engineering (MDE) and component-based software...     

Better knowledge management through knowledge engineering

The authors believe that current knowledge management practice significantly under-utilizes knowledge engineering technology, despite recent efforts to promote its use. They focus on two knowledge engineering processes: using knowledge acquisition processes to capture structured knowledge systematically; and using knowledge representation technology to store the knowledge, preserving important relationships that are far richer than those possible in conventional databases. To demonstrate the usefulness of these processes, we present a case study in which the drilling optimization group of a large oil and gas service company uses knowledge engineering practices to support the three facets of the knowledge management task: knowledge capture; knowledge storage; and knowledge deployment.     

Reconfigurable, component-based systems and the role of enterprise engineering concepts

General requirements of next generation enterprise systems are considered and classified. This highlights the potential importance of emerging component-based approaches that facilitate the detailed design of IT systems and their rapid implementation and ongoing development. It also highlights the need for complementary systems engineering approaches that address enterprise engineering on a broad scale, taking into account business and human aspects of large scale projects as well as technical aspects. This characterises the role that current generation enterprise engineering concepts can play in support of the conceptual design of future enterprise engineering systems and in the specification of sets of enterprise components from which large scale, change-capable enterprise systems can be constructed.     

The role of assumptions in knowledge engineering

Problem-solving methods are means of describing the inference process of knowledge-based systems. In recent years, a number of these problem-solving methods have been identified that can be reused for building new systems. However, problem-solving methods require specific types of domain knowledge and introduce specific restrictions on the tasks that can be solved by them. These requirements and restrictions are assumptions that play a key role in the reuse of problem-solving methods, in the acquisition of domain knowledge, and in the definition of the problem that can be tackled by knowledge-based systems. In this paper we discuss the different roles assumptions play in the development of knowledge-based systems and provide a survey of assumptions used in diagnostic problem solving. We show how such assumptions introduce targets and bias for goal-driven machine learning and knowledge discovery techniques. © 1998 John Wiley & Sons, Inc.