一种支持设计时软件重用的反射式软件体系结构及其形式化研究

软件体系结构在软件重用中有着特殊的意义。缺乏显式的描述并使用支持体系结构重用过程的信息和缺乏有效的重用方法是软件体系结构难以重用最根本的原因。在软件设计阶段,将元信息、元建模、反射和软件体系结构结合起来,构造了一种支持软件体系结构重用的反射式软件体系结构。给出了基于反射式软件体系结构的软件体系结构重用过程。给出了反射式软件体系结构的具体化过程的基本原理和具体化操作的Object-Z形式化描述,即创建元组件、创建元连接器、创建元组合件操作的形式化描述。给出了基于反射式软件体系结构的软件体系结构重用的支撑工具的设计过程。     

基于Object-Z的ReflectiveArchitecture形式化研究

将元信息、元建模、反射和软件体系结构结合起来,提出了一种基于反射机制的软件体系结构重用方法,该方法是一种更通用、更便捷的重用方法;该方法定义并构造了一种在设计阶段支持软件体系结构重用的反射机制RMRSA。描绘了基于反射机制RMRSA的反射式软件体系结构ReflectiveArchitecture的元级体系结构模型。运用形式规格说明语言Object-Z对元级体系结构模型进行了完整的描述;选取链接模式Link,给出了它的初始化定理及其证明过程,以此为范例证明了被形式化的反射式软件体系结构的正确性。     

一种支持设计时软件重用的方法ArchBean

目前,在设计阶段重用软件体系结构所面临的主要问题是:虽然存在大量的具有重用价值的体系结构制品,但是这些制品却难以得到成功的重用.提出了一种支持软件体系结构设计时重用的ArchBean方法.该方法基于反射机制将支持重用的元信息和体系结构制品本身封装成自包含、自描述的大粒度可重用资.源.给出了支持这种方法的反射机制RMRSA和反射式软件体系结构.基于Object-Z形式化描述了PMB协议.详细给出了基于ArchBean方法的支撑工具ArchBean Studio的设计和实施过程.     

一种支持软件体系结构重用的反射机制RMRSA

软件实现阶段的重用技术,特别是组件重用技术已经取得了巨大的进展。然而,对于软件开发早期阶段的软件资源的重用却进展缓慢。软件体系结构在软件重用中有着特殊的意义。反射机制在代码重用方面取得了成功,但还没有用于软件体系结构及其组成元素的重用。提出了一种支持软件体系结构设计时重用的反射机制,概述了基于反射机制的软件体系结构重用方法。详细说明了反射机制RMRSA的元级体系结构模型和基级体系结构模型,描述了元级软件体系结构和基级软件体系结构之间进行交互和互操作的协议PMB,以及反射机制RMRSA支持软件体系结构重用的过程。利用所提出的基于反射机制的重用方法,设计人员在软件设计阶段,通过重用体系结构及其组成元素来高效地完成软件计任务。     

一种软件体系结构关注点多维分离模型

传统方法设计出的体系结构中始终存在着一些横切现象,使得体系结构变得复杂、难以理解、难以演化和难以重用.基于关注点分离和面向方面软件开发的相关理论,探讨了体系结构中的关注点,提出一种体系结构层关注点多维分离模型.该模型通过形象地表示关注点之间的关系,识别那些在体系结构中可能产生横切的关注点,有效解决传统软件体系结构设计中存在的关注点横切问题,为软件体系结构的演化和重用提供了重要的指导作用.     

一种支持软件体系结构重用的反射机制及其形式化

软件开发早期阶段软件资源的重用进展缓慢.反射机制在代码重用方面取得了成功,但还没有用于软件体系结构及其组成元素的重用.提出了一种支持软件体系结构设计时重用的反射机制,详细描绘了基于反射机制的反射式软件体系结构的基级元素模型和元级元素模型.还用形式规格说明语言Object-Z语言对基级元素模型进行了完整的描述;以基级元素模型的连接模式Connections为例,给出了它的初始化定理及其证明过程.     

基于反射机制的软件体系结构重用方法及工具

针对软件开发早期阶段软件资源重用进展缓慢,反射机制在代码重用方面取得成功但还没有用于软件体系结构及其组成元素的重用等问题,提出一种支持软件体系结构设计时重用的反射机制,概述基于反射机制的软件体系结构重用方法。给出基于反射机制的软件体系结构重用的支撑工具ArchBean Studio的设计和实施过程。利用该方法,设计人员通过重用软件体系结构及其组成元素能高效地完成软件设计任务。     

一种基于CCM业务构件的可重构企业信息系统结构

针对制造企业信息系统的软件体系结构和功能应用软件的可重用问题进行研究.基于软件体系结构描述语言ADL的BNF语法和OMG/CCM的构件技术,详细设计了企业信息系统的可重构软件体系结构模型、系统的可重用业务构件和系统的即插即用框架.通过扩充CCM构件的消息和通知服务,描述了企业信息系统软件体系结构和功能应用软件的重用.     

管理信息系统软件体系结构演化研究

采用软件体系结构技术,可以使软件开发具有较高的实用价值,开发的软件系统具有可重用性、共享性和可维护性,并可以提高软件生命周期.论文对综合人事信息系统软件体系结构发现、演化、复用进行了研究,分析了综合人事信息系统体系结构发展中的四种体系结构,揭示了综合人事信息系统软件体系结构从管道型到异构型的演化历程,研究成果对管理信息系统软件体系结构设计有重要参考价值.     

软件体系结构与组件技术

在理论上,软件体系结构和基于组件的开发是理想的匹配;另一方面,软件体系结构是可重用软件组件的一种自然补充.只有通过实现体系结构模型,才能体现组件互操作性模型的所有优点.首先给出了大规模复杂分布式应用程序设计和进化方法选择中的关键因素;然后讨论软件组件技术与软件体系结构方法相互之间的要求,并探论了将软件体系结构与软件组件结合起来的可能途径.     

Configuring policies in public health applications

Public health is a complex practice due to the requirements of different jurisdictions. These requirements present a challenging environment in which to develop public health applications; software must be flexible in order to adapt to the complexities of different jurisdictions. One approach is to integrate policy management. Policies that define the rules governing an application can be created, modified, or deleted based on the deployment of that application. This paper describes a software architecture and expert system implementation of a policy manager designed to address jurisdictional requirements in public health applications. We define our policy requirements and policy model, the components of the architecture, and how the architecture has been used to implement our policy manager. Finally, we present examples of how the policy manager has configured policies used in three public health applications.     

一种基于四层结构的构件库模型研究

文章提出了一种基于四层结构的构件库模型,并按照构架层、构件层、叶类层、叶函数(叶方法)层的层次结构管理可复用构件。并且对于各层实体的描述形式作了进一步的研究,说明了构架、构件、类、函数(类方法)的描述属性以及它们之间的关系,促进更有效地组织和管理可复用构件,从而支持构件使用者更好地检索、理解和选取构件。     

通用嵌入式系统软件测试平台的设计

仿真测试是嵌入式软件系统测试阶段的一种有效测试方法,探讨了通过在PC机上仿真模拟ARM嵌入式系统,对嵌入式系统软件进行仿真测试的通用测试平台的设计。该平台可以在不做大幅度修改的情况下对不同的嵌入式系统软件进行各种测试。重点介绍了仿真模拟器、测试管理器和测试平台专用工具链的设计,提出了一种测试管理器的实现模型,并进行了详细的描述。     

The difference between marketecture and tarchitecture [software systems architecture]

We can divide software systems architecturally along two broad dimensions. The first is the tarchitecture or "technical architecture" and the second is the marketecture or "marketing architecture." I refer to the traditional software architect or chief technologist as the tarchitect and the product-marketing manager, business manager, or program manager responsible for the system as the marketect. The tarchitecture is the dominant frame of reference when developers think of a system's architecture. For software systems, it encompasses subsystems, interfaces, the distribution of processing responsibilities among processing elements, threading models, and so forth. In recent years, several authors, including Martin Fowler and Mary Shaw, have documented distinct tarchitecture styles or patterns, including client-server, pipeline, embedded systems, and blackboards. Our profession has begun to document how and when these various kinds of architectures are appropriate. It remains to be seen if we'll have the discipline to routinely leverage this knowledge.     

SOCA-DOM: A Mobile System-on-Chip Array System for Analyzing Big Data on the Move

Recently, analyzing big data on the move is booming. It requires that the hardware resource should be low volume, low power, light in weight, high-performance, and highly scalable whereas the management software should be flexible and consume little hardware resource. To meet these requirements, we present a system named SOCA-DOM that encompasses a mobile system-on-chip array architecture and a two-tier “software-defined” resource manager named Chameleon. First, we design an Ethernet communication board to support an array of mobile system-on-chips. Second, we propose a two-tier software architecture for Chameleon to make it flexible. Third, we devise data, configuration, and control planes for Chameleon to make it “software-defined” and in turn consume hardware resources on demand. Fourth, we design an accurate synthetic metric that represents the computational power of a computing node. We employ 12 Apache Spark benchmarks to evaluate SOCA-DOM. Surprisingly, SOCA-DOM consumes up to 9.4x less CPU resources and 13.5x less memory than Mesos which is an existing resource manager. In addition, we show that a 16-node SOCA-DOM consumes up to 4x less energy than two standard Xeon servers. Based on the results, we conclude that an array architecture with fine-grained hardware resources and a software-defined resource manager works well for analyzing big data on the move.     

Analyzing the effectiveness of fault-management architectures in layered distributed systems

Fault management infrastructure in distributed systems includes manager processes and agents with various kinds of interactions for monitoring and surveillance of the status of the application software and hardware. The system architecture now includes these additional components and interactions, and they affect the system availability. This paper describes an architecture model called MAMA (Model for Availability Management Architecture) with an architecture definition language MAMA-dl for the combination of the application and management parts, and its analysis. The analysis extends the Fault Tolerant Layered Queueing Model to account for propagation of knowledge of the system state in the management sub-architecture. The model is demonstrated on a problem of placement of manager tasks in a system.     

基于元信息的粗糙集规则并行挖掘方法

1.引言在当前的信息化时代,为从大量积累的历史数据中获取有用的知识,使得数据挖掘已成为研究热点。Pawlak教授提出粗糙集合理论,经过众多学者的研究和完善,已成为数据挖掘的重要手段。在大数据环境下,数据挖掘方法的速度将直接影响整个数据挖掘系统的性能,如何有效地提高数据挖掘方法的速度,是迫切需要解决的问题。与此同时,计算机网络存在大量的运算资源,充分利用这些资源是提高数据挖掘方法速度的有效途径。为此,本文提出     

COTS软件系统开发的研究*

基于COTS的软件开发方法日益受到重视。分析了用COTS组件来构建软件系统的优点和缺点,提出了这种软件系统开发方法需要解决的关键问题,并对COTS软件系统的体系结构及其各个部分进行详细剖析和研究,说明如何组织COTS组件来开发COTS软件系统。     

Creating architectures with building blocks

Large systems need a sound architecture. In our method, we decompose the system into building blocks to make it “future-proof,” accommodate functional needs, and minimize system complexity. We organize the system construction along three design dimensions covered by the system architecture: structure, aspects, and behavior. The structure determines the system's decomposition into parts and the relationships between the parts. Aspects model the functional decomposition of the system. Behavior deals with processing that takes place within the system. Of the three dimensions, we consider structure to be the most important. In this dimension, reducing complexity is our main concern. We organize system functionality into four layers, or subsystems. These subsystems are composed of software modules-building blocks-which are the basic software entities in the system architecture     

Managing Software Engineering Projects: A Social Analysis

Managing software engineering projects requires an ability to comprehend and balance the technological, economic, and social bases through which large software systems are developed. It requires people who can formulate strategies for developing systems in the presence of ill-defined requirements, new computing technologies, and recurring dilemmas with existing computing arrangements. This necessarily assumes skill in acquiring adequate computing resources, controlling projects, coordinating development schedules, and employing and directing competent staff. It also requires people who can organize the process for developing and evolving software products with locally available resources. Managing software engineering projects is as much a job of social interaction as it is one of technical direction. This paper examines the social arrangements that a software manager must deal with in developing and using new computing systems, evaluating the appropriateness of software engineering tools or techniques, directing the evolution of a system through its life cycle, organizing and staffing software engineering projects, and assessing the distributed costs and benefits of local software engineering practices. Ths purpose is to underscore the role of social analysis of software engineering practices as a cornerstone in understanding what it takes to productively manage software projects.