一种分布式软件运行时监控机制

软件在信息社会生活中起着越来越重要的作用,而如何提高软件系统的可信性也成为研究的重要课题,而运行时监控技术是提升软件可信性的重要方法之一.针对当前软件网络化、分布化的发展趋势,提出了一种全新的分布式软件运行时监控机制,通过建立监控服务使得远程监控客户端能够实现对软件系统跨网络、跨平台、实时的监控,从而进一步增强原有软件系统的可信性.这种机制在实际软件系统中获得了有效的应用,具有可行性和合理性.     

一种软件系统运行安全保护方法

通过分析软件系统自身安全的各种保护方案的优缺点,提出了一种软件系统的运行安全保护方法。描述了该方法的通信协议和具体实现技术,并给出了一个在实际系统中的应用实例和性能测试结果。     

软件系统协调技术研究

复杂软件系统常常由若干子系统或组件通过组装而成,子系统或组件之间的有效协调是系统开发的一个关键问题.特别是在开放、分布和移动的企业计算环境下,软件系统包含大量异构实体,对协调的可重用性、动态性和适应性提出了更高的要求,以应对业务环境和用户需求的持续变化.对软件系统协调技术的研究现状进行了综述,从协调体系结构、协调设计与实现方法学、协调活动的表示等视角对目前的协调技术进行了总结,探讨了复杂软件系统的协调策略,最后指出了目前协调技术存在的问题和面临的挑战.     

基于组件的虚拟仪器软件系统设计

本文介绍了组件技术和虚拟仪器软件系统,讨论了采用组件技术开发软件的优势,并结合组件技术模型设计了一种虚拟仪器软件系统基于组件的应用模型。     

信号量技术在MIS开发中的应用

本文提出一种利用信号量技术提高应用软件可靠性的方法。此方法是针对整个软件系统全局考虑的。它可根据不同应用领域的具体业务要求有效地限制各个功能模块的执行顺序和执行次数,使整个系统处在一种安全的状态下,避免了由于用户的错误操作对系统造成的损害。     

面向软件体系结构和Agent联邦的软件系统合成

提出面向软件体系结构和多Ａｇｅｎｔ联邦技术的大型软件系统设计与合成方法,可以有效地利用多Ａｇｅｎｔ联邦技术为软件体系结构的设计到软件系统的实际开发提供一种从抽象到具体的平滑过渡手段。     

GKCI:改进的基于图神经网络的关键类识别方法

研究人员将软件系统中的关键类作为理解和维护一个系统的起点,而关键类上的缺陷对系统造成极大的安全隐患.因此,识别关键类可提高软件的可靠性和稳定性.常用识别方法是将软件系统抽象为一个类依赖网络,再根据定义好的度量指标和计算规则计算每个节点的重要性得分,如此基于非训练的框架得到的关键类,并没有充分利用软件网络的结构信息.针对这一问题,本文基于图神经网络技术提出了一种有监督的关键类识别方法.首先,将软件系统抽象为类粒度的软件网络,并利用网络嵌入学习方法node2vec得到类节点的表征向量,再通过一个全连接层将节点的表征向量转换为具体分值;然后,利用改进的图神经网络模型,综合考虑类节点之间的依赖方向和权重,进行节点分值的聚合操作;最后,模型输出每个类节点的最终得分并进行降序排序,从而实现关键类的识别.在八个Java开源软件系统上通过与基准方法实验对比,验证了本文方法的有效性.实验结果表明,在前10个候选关键类中,本文所提方法比最先进的方法提升了6.4%的召回率和3.5%的精确率.     

基于软件体系结构的软件设计及构造

1 引言软件体系结构和软件设计模式是九十年代兴起的两种软件系统研究和设计新技术。这两种技术的典型特点就是将软件设计和开发的关注重点从传统软件设计开发方法的算法和数据结构转向了对整个软件系统的组织结构和系统性能表现。其中,软件体系结构研究注重的是构成软件系统的各有机组成成分及其关联作用和语义模式。通过对软件系统的组成成分及其相互之间的关联作用和语义模式进行分析和研究,软件体系结构期望通过加深对系统构造的理解来提高有关的软件工作人员的系统设计和系统分析能力,从而在系统组织、结构重     

基于图神经网络的软件系统中关键类的识别

软件系统中通常存在一些在拓扑结构上处于核心位置的关键类,这些类上的缺陷往往会给系统带来极大的安全隐患,识别关键类对工程师理解或维护一个软件系统至关重要.针对这一问题,提出一种基于图神经网络的关键类识别方法.首先利用复杂网络理论,将软件系统抽象为软件网络;其次结合无监督网络节点嵌入学习以及邻域聚合的方式,构建一个编码-解码(encoder-decoder)框架,提取软件系统中类节点的表征向量;最后利用Pairwise排序学习实现网络中节点的重要性排序,从而实现软件系统中关键类的识别.为验证所提方法的有效性,选取4个Java开源软件作为实验对象,并与常用的5种节点重要性度量方法以及2个已有工作进行对比分析.实验结果表明:与介数中心性、K-core、接近中心性、节点收缩法和PageRank等方法相比,该方法识别关键类的效果更好;另外,相比已有工作,在前15％的关键类节点中,所提方法的召回率和准确率的提高幅度均在10％以上.     

DCS组态软件实现方法研究

介绍了一种DCS组态软件实现方法,并详细阐述各部分的主要功能及实现的关键技术.最后,提出了一种不同组态软件系统进行数据交换的可行标准.     

A business maturity model of software product line engineering

In the recent past, software product line engineering has become one of the most promising practices in software industry with the potential to substantially increase the software development productivity. Software product line engineering approach spans the dimensions of business, architecture, software engineering process and organization. The increasing popularity of software product line engineering in the software industry necessitates a process maturity evaluation methodology. Accordingly, this paper presents a business maturity model of software product line, which is a methodology to evaluate the current maturity of the business dimension of a software product line in an organization. This model examines the coordination between product line engineering and the business aspects of software product line. It evaluates the maturity of the business dimension of software product line as a function of how a set of business practices are aligned with product line engineering in an organization. Using the model presented in this paper, we conducted two case studies and reported the assessment results. This research contributes towards establishing a comprehensive and unified strategy for a process maturity evaluation of software product lines.     

一种基于UML的软件产品线可变性建模方法

将UML引入到软件产品线开发中,在产品线可变性分析的基础上,提出了一种基于UML的产品线可变性建模方法。该方法不仅支持可选、多选一等可变点类型的描述,还支持软件产品线可变性的约束建模。在此基础上,还通过一个手机应用软件的产品线可变性建模实例验证了该方法的有效性。     

A novel model-based testing approach for software product lines

Model-based testing relies on a model of the system under test. FineFit is a framework for model-based testing of Java programs. In the FineFit approach, the model is expressed by a set of tables based on Parnas tables. A software product line is a family of programs (the products) with well-defined commonalities and variabilities that are developed by (re)using common artifacts. In this paper, we address the issue of using the FineFit approach to support the development of correct software product lines. We specify a software product line as a specification product line where each product is a FineFit specification of the corresponding software product. The main challenge is to concisely specify the software product line while retaining the readability of the specification of a single system. To address this, we used delta-oriented programming, a recently proposed flexible approach for implementing software product lines, and developed: (1) delta tables as a means to apply the delta-oriented programming idea to the specification of software product lines; and (2) DeltaFineFit as a novel model-based testing approach for software product lines.     

Managing requirements specifications for product lines - An approach and industry case study

Software product line development has emerged as a leading approach for software reuse. This paper describes an approach to manage natural-language requirements specifications in a software product line context. Variability in such product line specifications is modeled and managed using a feature model. The proposed approach has been introduced in the Swedish defense industry. We present a multiple-case study covering two different product lines with in total eight product instances. These were compared to experiences from previous projects in the organization employing clone-and-own reuse. We conclude that the proposed product line approach performs better than clone-and-own reuse of requirements specifications in this particular industrial context.     

Produktgetriebene Entwicklung von Softwareproduktlinien

For the realization of software product families the software-technical concept of the software product line finds an increasing spreading. Due to the high initial costs of current methods for software product line development these methods are not suitable for small and medium-size software enterprises. The contribution of this paper is a method for software product line development which reduces costs for the establishment of a software product line, supports a product-driven advancement of product lines and enables the application of the product line approach in small and medium-size software enterprises. After an introduction to the state of the art, we analyze the requirements for the development of software product lines in small and medium-size enterprises. Subsequently, a product-driven development method is introduced which considers these requirements and supports an evolutionary development of software product lines.     

Exemplar driven development of software product lines

The benefits of following a product line approach to develop similar software systems are well documented. Nevertheless, some case studies have revealed significant barriers to adopt such approach. In order to minimize the paradigm shift between conventional software engineering and software product line engineering, this paper presents a new development process where the products of a domain are made by analogy to an existing product. Furthermore, this paper discusses the capabilities and limitations of different techniques to implement the analogy relation and proposes a new language to overcome such limitations.     

An organizational maturity model of software product line engineering

Software product line engineering is an inter-disciplinary concept. It spans the dimensions of business, architecture, process, and the organization. Some of the potential benefits of this approach include cost reduction, improvements in product quality and a decrease in product development time. The increasing popularity of software product line engineering in the software industry necessitates a process maturity evaluation methodology. Accordingly, this paper presents an organizational maturity model of software product line engineering for evaluating the maturity of organizational dimension. The model assumes that organizational theories, behavior, and management play a critical role in the institutionalization of software product line engineering within an organization. Assessment questionnaires and a rating methodology comprise the framework of this model. The objective and design of the questionnaires are to collect information about the software product line engineering process from the dual perspectives of organizational behavior and management. Furthermore, we conducted two case studies and reported the assessment results using the organizational maturity model presented in this paper.     

Automating Test Case Selection in Model-Based Software Product Line Development

We address the problem of how to select test cases for products in a controlled model-based software product line development process. CVL, the common variability language, gives a framework for materialisation of product models from a given base model, variability model and resolution model. From such product models, software products can be derived. In practise, test case development for the product line often is independent from the product development. Therefore, the problem arises which test cases can be applied to which products. In particular, the question is whether a test case for one speci c product can be also used for a "similar" product. In this paper, we show how the expected outcome of a test case to a product in a model-based software product line development can be determined. That is, we give a procedure for assigning the outcome of a given test case on an arbitrary member of a software product line. We recall the relevant de nitions for software product line engineering, describe our approach, and demonstrate it with the example of a product line of super-automatic espresso machines.     

DRAMA: A framework for domain requirements analysis and modeling architectures in software product lines

One of the benefits of software product line approach is to improve time-to-market. The changes in market needs cause software requirements to be flexible in product lines. Whenever software requirements are changed, software architecture should be evolved to correspond with them. Therefore, domain architecture should be designed based on domain requirements. It is essential that there is traceability between requirements and architecture, and that the structure of architecture is derived from quality requirements. The purpose of this paper is to provide a framework for modeling domain architecture based on domain requirements within product lines. In particular, we focus on the traceable relationship between requirements and architectural structures. Our framework consists of processes, methods, and a supporting tool. It uses four basic concepts, namely, goal based domain requirements analysis, Analytical Hierarchy Process, Matrix technique, and architecture styles. Our approach is illustrated using HIS (Home Integration System) product line. Finally, industrial examples are used to validate DRAMA.