实时构件合成的语义研究

实时构件合成是实时应用系统中软件合成的基础，是实现软件复用思想的软件生产活动，其语义研究从实时构件的反射式语义模型、实时构件合成的适配性验证和合成构件的语义规约机制三个方面展开，规约为实时构件合成中的分析理论。     

软件构件管理与重用方法探究

软构件技术是影响整个软件产业的关键技术之一，软件重用在提高软件生产率与质量、减少软件开发时间和成本等方面起到了关键的作用。从软构件的基本属性出发，讨论了软构件的分类原则、描述方法等软构件的管理技术，以及构件重用中的研究热点——构件检索方法，并对软件构件对软件产业造成的影响做了分析。     

软件构件管理与重用方法探究

软构件技术是影响整个软件产业的关键技术之一,软件重用在提高软件生产率与质量、减少软件开发时间和成本等方面起到了关键的作用。从软构件的基本属性出发,讨论了软构件的分类原则、描述方法等软构件的管理技术,以及构件重用中的研究热点——构件检索方法,并对软件构件对软件产业造成的影响做了分析。     

一种基于嵌入式软件构件管理方法

构件化软件开发的最终目的是希望软件像传统产品一样能在生产线上生产出来。软件最终由软件框架来实现,一个良好的软件框架应该能够将设计结果尽量保存下来,同时可以灵活更换和重用软件部件。研究构件化的软件框架对构件化的开发技术在嵌入式实时软件开发中迅速普及具有最直接的推动作用。对嵌入式控制系统嵌入软件构件框架进行了深入研究,完成了框架中的数据管理和构件调度机制等内容,验证了该源码构件模型在嵌入式控制软件领域中的可用性。     

一种软件构件仓库及实现方法

为了有效提高软件质量和开发效率,基于软件复用思想将软件模块和业务模块抽象为软件构件,提供以特定规则存储、查询、使用和进化构件的软件构件仓库.软件构件仓库的使用过程主要包括创建构件、查询构件、引用构件以及自动构建与持续集成等步骤.软件构件的逻辑模型采用了结合刻面分类法和键值对表示法的集成方法,定义了一种以URL方式表示构件信息的构件管理协议用于在系统内部存储、传递和解析软件构件信息,构件逻辑模型存储在关系型数据库中,用于描述构件包含的所有信息的模型,构件物理模型用来表达软件构件所对应的实体-文件的存储形式,保证构件仓库能够无障碍地升级和迁移.     

软件构件表示与检索形式化的研究与进展

1 引言软件复用被认为是提高软件生产效率和软件质量较为现实的途径。尽管软件复用的思想已经提出了30多年,但软件复用的现状离人们最初的设想仍然相距甚远。阻碍大规模软件复用的技术与非技术因素很多,主要的技术因素有构件分类、构件表示、构件检索、构件更改及构件库的管理与维护等。其中,软件构件表示与检索是软件复用获得成功的重要前提。     

面向功能构件的软件构件识别方法研究

为了从功能构件中识别出低耦合、高聚合的软件构件,分析了软件构件识别问题,提出了基于业务行为关系的软件构件识别方法,详细介绍了该方法的原理与过程。最后给出一个应用示例,说明方法的合理性和有效性。     

面向领域的软件构件技术研究

广州市软件协会与广州市各大高校合作,于2005年初开始了广州市软件构件库的建设.该项目的目标是研发面向领域的软件构件库、构建软件构件库管理系统、形成面向领域的构件化应用系统.软件构件库建设的一期任务是医院管理领域应用.一期工程目前已经顺利完成,各项指标均达到预定目标.广州市软件构件库的建设,对面向领域的构件库的研究具有一定的参考价值.     

基于刻面分类的软件构件的表示

软件复用作为提高软件生产率和质量的一种重要技术,被广大的软件开发人员所应用,而在软件复用的同时,对构件进行有效的分类是关键技术之一.本文主要针对刻面分类的方法,使用XML语言对构件进行描述,提出了软件构件的表示方法.使用该方法,在构件组装平台下给出了对构件的刻面定义,以提高软件的复用性.     

软件构件化生产集成支撑平台研发

对大型软件构件化生产过程中的构件识别与映射、构件建模、构件测试和构件评估进行了研究,报告了软件构件化研究和实践现状和存在的问题,提出了一套基于业务构件组装开发支撑平台实现框架,详细阐述了构件功能之间的关联关系,给出了构件化组装技术原理和实现过程,阐述了业务构件框架与原子业务构件组装过程,为基于业务构件组装的软件构件化生产提供了一种新的解决方案。     

An active-architecture approach to COTS integration

COTS software products are increasingly becoming standard components for building integrated information systems. At the same time, the growth of electronic trading, turbulent market conditions, and a project-style approach to business have created a demand for information systems that can be rapidly adapted to changing business process demands. However, the ongoing development of COTS products is unpredictable as their developers and source code are rarely available. Flexible information systems use COTS components because they cost-effectively supply required component functionality. A software architecture can capture a system design as a set of interacting components and capture the role of COTS software in "implementing" certain components.     

Assessing COTS software in a certifiable safety-critical domain

Abstract.  Commercial off-the-shelf (COTS) software solutions have become commonplace in many domains, including the military, because they can provide standardized functionality with more responsiveness, a shorter time-to-market and at lower costs than custom-made solutions. In one domain, however, that of certifiable safety-critical applications, COTS software has not been adopted. One particular type of certifiable safety-critical domain, the civil air transport industry, is under pressure to reduce cost and time-to-market while simultaneously increasing safety. Therefore, the use of COTS software, rather than exclusive reliance on custom-made software, would appear to be a solution worthy of investigation. This study examines the certifiability of COTS software, its technical feasibility in this environment, and the ability to achieve the expected responsiveness, time-to-market and cost benefits. A detailed evaluation of COTS software and domain-specific certification requirements is used to demonstrate that the certification of COTS-based systems is possible. A prototype COTS-based system (built upon a number of COTS components) is created to illustrate the technical feasibility of such a system in the civil air transport domain. Expected benefits from COTS solutions are evaluated both by examining process artefacts from the development of the COTS-based system and by comparing this development process with the domain's traditional custom-development process.     

Guest Editors' Introduction: Integrating COTS into the Development Process

Building and evolving software systems is an arduous, costly, lengthy, and complex task. The resulting systems are similarly complex. We're thus constantly searching for ways to reduce such costs, time, and complexity while increasing system functionality and quality. One strategy that originally seemed promising was the notion of "buy not build." Using COTS products is one way to implement this strategy, because software development then becomes the process of "simply" integrating COTS components. However, it turns out that dealing with COTS is a high-risk activity for a variety of reasons.     

Integrating COTS Software into Systems through Instrumentation and Reasoning

Commercial-off-the-shelf (COTS) software tends to be cheap, reliable, and functionally powerful due to its large user base. It has thus become highly desirable to incorporate COTS software into software products (systems) as it can significantly reduce development cost and effort, while maintaining overall software product quality and increasing product acceptance. However, incorporating COTS software into software products introduces new complexities that developers are currently ill equipped to handle. Most significantly, while COTS software frequently contains programmatic interfaces that allow other software components to obtain services from them on a direct call basis, they usually lack the ability to initiate interactions with other components. This often leads to problems of state and/or data inconsistency. This paper presents a framework for integrating COTS software as proactive components within a software system that maintain the consistency of the state and data they share with other components. The framework utilizes a combination of low-level instrumentation and high-level reasoning to expose the relevant internal activities within a COTS component required to initiate the communication needed to maintain consistency with the other components with which it shares state and data. We will illustrate these capabilities through the integration of IBM's Rational Rose into a design suite and demonstrate how our framework solves the complex data synchronization problems that arise from this integration.     

COTS software: the economical choice?

A new trend in software commerce is emerging: generic software components, also called commercial off the shelf components, that contain fixed functionality. COTS components can be incorporated into other systems still under development so that the developing system and the generic components form a single functional entity. The role of COTS components is to help new software systems reach consumers more quickly and cheaply. Because arriving last to market spells sudden death in the software industry, any approach that carves days or weeks from a development schedule is worth considering. The article gives advice on taking the COTS option and the management decisions that have to be made     

Encapsulating windows-based software applications into reusable components with design patterns

Reusing software by integrating Commercial Off-The-Shelf (COTS) applications into a software system is maturing in practice. Our previous work [1] presented a component wrapping approach to convert Windows-based COTS applications into CORBA objects. A formal and generalized representation of the conversion process for a Windows-based COTS application into a reusable software component would be useful and desirable for applying such software reuse to COTS-based system development. This study addresses a pattern-based representation of our experience. The patterns in this study offer clear documentation and sufficient information for a software developer to develop a COTS-based software system rapidly. An example system, Graphic Mechanical Part Management System (GMPMS) assembling two COTS applications under MS-DOS and MS-Windows 2000/XP, respectively, is also developed in this study to reveal how the patterns are utilized.     

商业构件评价与选择方法研究

在基于商业构件（COTS）的软件开发中，构件的评价与选择是贯穿整个开发过程的关键步骤。有两类典型的基于COTS的系统，即COTS方案系统和COTS密集型系统。本文首先描述了针对COTS方案系统的单构件评价问题的特点，并对各种评价方法进行了分析、对比。然后将COTS密集型系统的多构件选择问题定义为一个在给定的约束条件下求解最佳构件组合的数学优化问题。最后给出了该优化问题的形式描述及其相应的求解方法。     

COTS-based systems top 10 list

Presents a COTS-based system (CBS) software defect-reduction list as hypotheses, rather than results, that also serve as software challenges for enhancing our empirical understanding of CBSs. The hypotheses are: (1) more than 99% of all executing computer instructions come from COTS products (each instruction passed a market test for value); (2) more than half the features in large COTS software products go unused; (3) the average COTS software product undergoes a new release every 8-9 months, with active vendor support for only its latest three releases; (4) CBS development and post-deployment efforts can scale as high as the square of the number of independently developed COTS products targeted for integration; (5) CBS post-deployment costs exceed CBS development costs; (6) although glue-code development usually accounts for less than half the total CBS software development effort, the effort per line of glue code averages about three times the effort per line of developed applications code; (7) non-development costs, such as licensing fees, are significant, and projects must plan for and optimize them; (8) CBS assessment and tailoring efforts vary significantly by COTS product class (operating system, database management system, user interface, device driver, etc.); (9) personnel capability and experience remain the dominant factors influencing CBS development productivity; and (10) CBS is currently a high-risk activity, with effort and schedule overruns exceeding non-CBS software overruns, yet many systems have used COTS successfully for cost reduction and early delivery     

Requirements for a COTS software component: A case study

The goal of the GUARDS project is to design and develop a generic fault-tolerant computer architecture that can be built from predefined standardised components. The architecture favours the use of commercial off-the-shelf (COTS) hardware and software components. However, the assessment and selection of COTS components is a non-trivial task as it requires balancing a myriad of requirements from end-users and the preliminary architecture design. In this paper, we present the requirements and assessment criteria for a specific COTS software component, the operating system kernel. As an interface specification constitutes a major compatibility criterion for the selection of COTS components in GUARDS, a particular emphasis is placed on operating system conformance to the POSIX 1003.1 standard. We discuss the general lessons learned from the assessment process and raise a number of questions relevant to the assessment of any COTS software component.     

Identifying and classifying processes (traditional and soft factors) that support COTS component selection: a case study

COTS-Based Systems (CBS) development focuses on building large software systems by integrating previously existing software components. CBS success depends on successful evaluation and selection of Commercial-Off-The-Shelf (COTS) software components to fit customer requirements. Literature shows that successful selecction of off-the-shelf systems to fit customer requirements remains problematic. This paper presents the outcome of a study aimed at using a social-technical approach to identify and classify processes (including traditional and soft factors) that support COTS software selection. The identified factors and lessons learnt from the case study assisted in elaborating and further development of Social-Technical Approach to COTS Evaluation framework (STACE).