面向构件化软件的合约检查测试框架

基于构件软件开发的主要思想是使用现存的构件来建构软件系统。而这样的系统由于构件本身的特点导致了许多测试困难。B. Meyer将构件与其客户代码之间的关系形式化地定义为一种合约，它严格限定了构件对象之间的交互规则。通过对合约的监视和检查，可以容易地发现构件之间的交互错误，从而达到集成测试构件化软件的目的。该文提出了一种基于合约检查的构件集成测试框架 (contract-checking test framework，CCTF)。讨论了该框架合约检查的思想、5大功能模块以及其测试流程，并介绍了将CCTF应用到构件化软件测试平台实现的一些关键技术。     

用于测试的SA动态模型生成方法

SA(软件体系结构)的动态性描述在基于软件体系结构的一致性测试中是非常关键的一步。许多软件体系结构描述语言是利用带标号的转换系统(LTS)来模拟软件体系结构动态性的,利用LTS作为软件体系结构动态性模型并从中选取测试序列。通过实例研究了两种体系结构描述语言及其分别向动态模型LTS转变的过程。     

基于LTS的Statecharts操作语义研究

Statecharts是一种用于复杂反应式系统行为的可视化规格语言。该文提出了一种基于标签变迁系统(LTS)的Statecharts操作语义描述方法，介绍了Statecharts及其项语法和一步语义，并基于进程代数描述Statecharts的并发行为，使用结构化的操作语义SOS规则描述Statecharts的组合语义，从而得到相应的LTS。     

面向测试的构件系统模型及测试用例生成方法

随着面向构件的软件开发方法的广泛应用,构件系统的描述和测试成为保证软件质量的关键所在。由于构件系统的复杂性和开发方法的特殊性,用传统方法对构件系统进行集成测试往往面对很多困难。提出了一种改进的面向测试的构件描述模型,称为TCSM,它着重对构件系统中的构件间的交互和约束进行了动态描述,为构件系统集成测试阶段的功能测试和边界测试等提供了大量可用信息。在此基础上,进一步提出一种把TCSM转换成测试模型的方法,以UML协作图模型为原型,实现了构件系统从描述模型到测试模型的自动转换。最后,实现了一种在所产生的测试模型上自动生成测试用例的算法。TCSM更好地描述了构件的交互行为信息,进一步实现了系统的自动化测试,减少了通常需要在构件系统搭建完成后,针对测试对系统手工建立测试模型的工作,提高了构件系统开发的效率和可靠性。     

基于行为协议的构件软件静态测试研究

系统的静态分析能在设计开发阶段发现错误,从而避免了在运行时错误检测技术在系统执行期间带来的负面影响。基于尽可能避免静态错误这一构件测试策略的基本思想提出了一种对构件化软件系统进行静态测试的方法。采用通信模型对数据库服务构件系统进行抽象建模,并结合用于描述构件系统中构件之间交互的形式化方法行为协议,通过对构件系统构件行为协议的一致性验证,从而测试构件交互的正确性。     

基于行为协议的构件软件静态测试研究

系统的静态分析能在设计开发阶段发现错误,从而避免了在运行时错误检测技术在系统执行期间带来的负面影响.基于尽可能避免静态错误这一构件测试策略的基本思想提出了一种对构件化软件系统进行静态测试的方法.采用通信模型对数据库服务构件系统进行抽象建模,并结合用于描述构件系统中构件之间交互的形式化方法行为协议,通过对构件系统构件行为协议的一致性验证,从而测试构件交互的正确性.     

基于MVC模式的嵌入式软件测试开发环境设计

嵌入式软件仿真测试开发环境(ESTDE,Embedded Software Testing Development Environment)是嵌入式软件仿真测试平台(ESSTP,Embedded Software Simulation Testing Platform)的重要组成部分,是有效实现嵌入式软件实时、闭环测试的基础。MVC(Model-View-Controller)是一种开发交互式软件系统的典型体系结构模式,在分析和研究ESTDE功能、组成和工作原理的基础上,将MVC应用于ESTDE的设计当中,不仅保证了ESSTP的成功开发,而且提高了系统的可复用性和可适应性。     

基于构件的软件开发方法及实现

基于构件(Component-Based Software Development,CBSD)的软件系统中的构件可以是COTS(Commercial-Off-the-Shelf)构件,也可以是通过其它途径获得的构件(如自行开发)。CBSD体现了“购买而不是重新构造“的哲学,将软件开发的重点从程序编写转移到了基于已有构件的组装,以便更快地构造系统,减轻用来支持和升级大型系统所需要的维护负担,从而降低软件开发的费用     

基于XML的构件化软件集成测试方法研究

分析了当前构件化软件集成测试方法的局限性,利用XML技术特性,使用XML描述构件、构件的交互、构件间交互服从的规约、测试用例及测试序列等,并结合基于规约的测试方法,从而提出一种基于XML的规约驱动的构件化软件集成测试方法。     

用于测试的SA动态模型生成方法

SA（软件体系结构）的动态性描述在基于软件体系结构的一致性测试中是非常关键的一步。许多软件体系结构描述语言是利用带标号的转换系统（LTS）来模拟软件体系结构动态性的，利用LTS作为软件体系结构动态性模型并从中选取测试序列。通过实例研究了两种体系结构描述语言及其分别向动态模型LTS转变的过程。     

一种舰载指控系统构件集成测试方法

基于构件的软件开发方法强调基于构件的组合装配以快速搭建应用系统,因此针对此类系统的多个构件组合后的集成测试技术尤为重要。文章针对舰载指控系统构件的特点,给出了构件依赖关系矩阵的定义和生成方法,提出了一种基于依赖关系矩阵的舰载指控系统构件集成测试方法。     

Object‐oriented integration testing

Object‐oriented software development is an evolutionary process, and hence the opportunities for integration are abundant. Conceptually, classes are encapsulation of data attributes and their associated functions. Software components are amalgamation of logically and/or physically related classes. A complete software system is also an aggregation of software components. All of these various integration levels warrant contemporary integration techniques. Traditional integration techniques towards the end of software development process do not suffice any more. Integration strategies are needed at class level, component level, sub‐system level, and system levels. Classes require integration of methods. Various types of class interaction mechanisms demand different testing strategies. Integration of classes into components presses its own integration requirements. Finally, the system integration demands different types of integration testing strategies. This paper discusses the various integration levels prevalent in object‐oriented software development. The integration requirements of each level are met by suggesting a solution for the same. An integration framework for integrating classes into a system is also proposed. This revised version was published online in June 2006 with corrections to the Cover Date.     

An industrial study on the importance of software component documentation: A system integrator?s perspective

Component integration is widely recognized as a process which plays a central role in overall Component Based System (CBS) development. A system integrator focuses on assembling existing components, developed by different parties, to build a software system. The integration process usually involves adapting existing component interfaces and writing new functions to handle the mismatches between stakeholder needs and available component features. The lack of detailed component documentation has been a key area of concern in CBS development due to its profound impact on the integration phase of a CBS development life cycle. In this paper, we report results of an industrial survey conducted among system integrators to understand role of component documentation in the CBS integration phase. The survey investigates whether the presence of component documentation helps a system integrator and its correlations with typical CBS integration success factors. The result reinforces current perceptions of the significance of component documentation in CBS integration. However, the lack of comprehensive component documentation presents a potential risk for a system integrator during integration effort estimation and testing processes.     

一种基于内置合约检查和可配置接口的软构件测试技术*

从构件使用者和开发者的角度分析构件及构件化软件的测试,利用B. Meyer的合约化软件设计思想作为构件测试的理论基础,并在其上面进行了扩展与改进,提出了一种基于内置合约检查和可配置接口的构件测试技术。该方法的优点是：当构件被部署到新的系统环境中时,能够自动测试其服务端是否遵守彼此之间合约,并验证自身在运行阶段履行其所声明的义务的能力;利用可配置接口,可以根据所部署环境和特定系统的需求,动态地选择测试强度;当构件集成出现问题时,能够从抛出的异常信息定位到出错的位置。     

Analysis and testing of black‐box component‐based systems by inferring partial models

From experience in component‐based software engineering, it is known that the integration of high‐quality components may not yield high‐quality software systems. It is difficult to evaluate all possible interactions between the components in the system to uncover inter‐component misfunctions. The problem is even harder when the components are used without source code, specifications or formal models. Such components are called black boxes in literature. This paper presents an iterative approach of combining model learning and testing techniques for the formal analysis of a system of black‐box components. In the approach, individual components in the system are learned as finite state machines that (partially) model the behavioural structure of the components. The learned models are then used to derive tests for refining the partial models and/or finding integration faults in the system. The approach has been applied on case studies that have produced encouraging results. Copyright © 2013 John Wiley & Sons, Ltd.     

Research issues in testing business components

The advantages of migrating from traditional monolithic business applications to reusable object-based business components (self-contained software that carries out a certain business task) are well documented. A business system assembled from reusable components is argued to be highly reliable since these components have been tested and used in many other business applications. However, all possible uses of components are not known at design and construction stage. Additionally, integration testing is needed as components are assembled to make business application systems. Component-based software development requires that testing issues be addressed adequately. In this paper, we explore testing related issues in business components and in particular, business application systems that are made by integrating these components. An integration test strategy for business component application systems is proposed.     

一种面向对象程序系统的有效测试方法

针对面向对象的程序系统提出了一种集成测试的有效方法。描述了如何从面向对象的系统设计中生成一个测试模型，对模型图正规化并做进一步分解，根据优化后的结果运用并行测试的思想指导系统的集成测试，以期在尽量少的测试开销基础上加快软件测试的进程。     

Developing applications using model-driven design environments

Historically, software development methodologies have focused more on improving tools for system development than on developing tools that assist with system composition and integration. Component-based middleware like Enterprise Java-Beans (EJB), Microsoft .NET, and the CORBA Component Model (CCM) have helped improve software reusability through component abstraction. However, as developers have adopted these commercial off-the-shelf technologies, a wide gap has emerged between the availability and sophistication of standard software development tools like compilers and debuggers, and the tools that developers use to compose, analyze, and test a complete system or system of systems. As a result, developers continue to accomplish system integration using ad hoc methods without the support of automated tools. Model-driven development is an emerging paradigm that solves numerous problems associated with the composition and integration of large-scale systems while leveraging advances in software development technologies such as component-based middleware. MDD elevates software development to a higher level of abstraction than is possible with third-generation programming languages.     

航天地面应用系统联调测试平台设计

由于航天地面应用系统是分工协作开发的大型系统,接口复杂多样,在系统集成与联试时往往花费较多的人力物力。因此提出了一种辅助航天地面应用系统进行系统集成联试的工具一联调测试平台。首先针对联调测试平台设计中需要解决的问题给出了解决方法。然后阐述了联调测试平台的功能特点和体系构架及其所使用的关键技术,并给出了软件的设计实现。     

基于构件的软件开发的方法与实践

随着软件工业的成熟以及对软件生产要求的不断提高,基于构件的软件开发作为一种新的软件开发方法被提了出来.该方法的开展通过集成已存在的构件进行,可以分为构件的评选、构件适配、构件组装、系统演化四个阶段.使用基于构件的软件开发能减少软件开发费用、提高软件开发速度等,但同时也可能带来一定的风险,因此,开发者在开发时应该遵循一定的原则,这些原则是在用该方法开发软件时总结出来的.