软件复用在C++中的主要实现机制

本文在分析比较软件复用及其不同粒度特点的基础上,着重研究软件复用在C 语言级上的主要支持手段及其实现机制,并结合实例对相关问题进行了讨论。     

COM组件技术与软件的复用

用可复用软件构造软件是现代软件发展的趋势,本文从软件复用的角度来讨论COM组件,主要包括程序框架的复用以及组件的复用。     

软件复用与基于Java的COM组件实现

COM组件是实现软件复用的有效途径之一。本文讨论了COM技术对分布武程序开发的支持和基于COM技术的三层架构。利用Java的跨平台能力，给出了使用Java开发COM组件的方法和步骤。     

如何在C++中实现软件复用

~~如何在C 中实现软件复用$河北经贸大学@赵宝琴     

基于构件复用的软件方法与COM支持

作为研究的热点,近年来提出的构件模型层出不穷。出于相互之间互操作性的考虑,必须具备一个公共的构件底层框架。分析各种实际的因素,ＣＯＭ是一个可行的选择。文中讨论了ＣＯＭ规范对组件复用的支持及其发展前景,提出了基于ＣＯＭ的复用思想：以接口的标准化推动服务的标准化,为复用软件的开发和使用建立规范。     

软件复用与COM及.NET组件技术

介绍了软件开发技术的发展和软件复用的关系，揭示了COM组件的原理以及从COM到．NET组件技术的变化，最后给出了开发．NET组件的方法和步骤。     

基于复用的.NET组件接口模型的研究

有较高封装性的组件是软件复用研究的重点。为了满足我们设计和定义的多种组件模型,首先介绍了支持软件复用的、支持设计和实现统一的、多种类型的.NET组件接口模型定义;接着介绍了各种类型接口的实现方式,包括类设计器和控件工具箱等;详细分析了采用多种组件接口模型的意义。     

C++的动态多态和静态多态

多态是C＋＋中面向对象技术的核心机制之一,包含静态多态和动态多态,它们之间有一定的相似性,但是应用范围不同。该文论述了这种相似性,并重点论述了以模板实现的静态多态的应用范围。     

用Visual C++编写典型测控软件

给出了工业自动化领域的应用测控软件编制的一般流程,并对编程中可能遇到的几个关键问题分别做了介绍,给出了解决方案.     

基于.NET组件软件复用工程的研究

以复用技术为基础的软件开发过程被称为软件复用工程.首先介绍一种基于.NET组件技术的复用工程,描述其各个步骤的关系和产生的复用制品;介绍该复用工程满足设计与实现统一的要求;分析该复用工程具有的特点.     

软件重用技术研究

目前软件重用技术已经成为内容非常广泛的研究领域,是当今软件工程领域中的一个研究热点。文中重点论述了目前研究得较多且应用较广泛的基于构件的软件重用技术,指出目前软件重用技术中存在的带有普遍性的问题,针对一些流行的关于软件重用的模糊、错误的认识进行了分析,并提出一些观点。     

基于WebService的软件分布式重用的研究与实现

本文从时间、空间、与应用领域分析了软件重用的特征与重用粒度,针对传统软件不能跨平台、分布式用重等问题,提出了基于WebService的软件分布式重用模式,同时结合实例描述了基于WebService的软件分布式重用的实现;     

基于构件的软件复用技术研究及在MIS中的应用

阐述了基于构件的软件复用技术,并就基于构件软件开发技术在管理信息系统（MIS）中的应用作了探讨,对提高软件开发效率有着重要意义。     

VB环境下基于类的软件复用技术研究

为提高VB环境下软件开发的效率,研究了软件复用技术,提出了以代码组件为核心的软件复用工程化思想.结合具体应用,详细介绍了VB中类的创建、复用方法,以及基于类的ActiveXDLL代码组件复用技术,同时还对VB中常用的其它代码组件的复用方法进行了简单介绍.研究结果表明,合理利用相关的软件复用技术,可以缩短软件的开发周期,提高软件的开发质量.     

基于COM+构件的多层体系结构的研究与实现

该文在对COM+构件技术进行深入研究的基础上,设计了一种基于构件的多层软件体系结构该体系结构能有效提高软件开发的效率、增强软件系统对环境变化的适应能力。     

Implementing interactive applications in C++

This paper presents an object-oriented approach for the implementation of interactive systems. This approach applies the model-view-controller (MVC) paradigm, which is modified for the C++ environment. The modified paradigm is called MVC++. In this approach the design of interactive applications starts by constructing an object model that represents the key concepts of the problem domain. This object model does not contain any user interface elements. According to the MVC++ approach, the object model is called the model part of the application. Only after the model part has been created, is the user interface designed. A collection of user interface classes is called the view. The classes that connect the model and the view form the controller, which is designed to communicate with both the model and the view. The approach presented in this paper provides a number of benefits. Advantages of the original MVC approach are obtained in a standard C++ environment, the structure of applications becomes clear and stable, and reusability as well as readability of the classes increases. Reusability is achieved by employing a mechanism called ‘abstract partners’. The approach presented in this paper is being applied in the development of a large network management system with over one million lines of C++ code running in the XII environment.     

The impact of software evolution and reuse on software quality

This paper presents a case study of a software project in the maintenance phase. The case study was based on a sample of modules, representing about 1.3 million lines of code, from a very large telecommunications system. Software quality models were developed to predict the number of faults expected from the coding through operations phases. Since modules from the prior release were often reused to develop a new release, one model incorporated reuse data as additional independent variables. We compare this model's performance to a similar model without reuse data.Software quality models often have product metrics as the only input data for predicting quality. There is an implicit assumption that all the modules have had a similar development history, so that product attributes are the primary drivers of different quality levels. Reuse of software as components and software evolution do not fit this assumption very well, and consequently, traditional models for such environments may not have adequate accuracy. Focusing on the software maintenance phase, this study demonstrated that reuse data can significantly improve the predictive accuracy of software quality models.     

Measuring complexity in C++ application software

This paper concerns the use of design/source-code complexity metrics in analysing C++ software. It describes the use of one suite of object-oriented metrics published by Chidamber and Kemerer¹ to evaluate a commercial C++ application. It provides an interpretation and critique of these metrics, including the use of two traditional metrics (Cyclomatic Complexity² and Software Science³) in association with these object-oriented metrics. The evolution, over a two and a half year period, of one commercial grade C++ application comprising 114 classes with 25,000 lines of code is studied. The efforts consumed in bug fixes and enhancements are correlated with the complexity measures on a per class basis, and results are presented. These results are compared to those from other workers. The paper provides a detailed analysis of the practical strengths and weaknesses of the metrics suite in the light of experiences with its use. © 1998 John Wiley & Sons, Ltd.     

基于UCML的软件开发的研究

UCML(Universal Component Modeling Logic)通用组件建模逻辑是一个面向WEB、面向框架,基于工作流和组件重用技术的软件开发平台,它涵盖了一个应用系统业务开发的全过程。文章介绍了该平台的体系结构、面向框架技术、组件重用技术和工作流原理,分析了它们在该平台软件开发设计和实现中的运用,并描述了基于该平台进行应用程序的开发模式。     

组件对象模型(COM)在Web开发中的应用

组件对象模型 (COM)技术是Microsoft许多软件的基石 ,它提供了一种能跨越编程语言、操作系统和网络来访问对象的通用途径 ,使软件复用成为可能。本文论述其技术内涵和它在Web开发中的应用。