支持软件重用的面向模式的软件开发方法

软件模式作为一种有效的重用手段正日益得到开发组织和学术界的广泛关注．目前对软件模式的研究侧重于利用非结构化的方法构建和描述模式，开发者很难对模式进行维护和重用．本文提出了一个支持软件重用的面向模式的软件开发过程，它将基于体系结构的建模方法与软件过程有机地结合在一起．面向模式的软件开发过程包括四个阶段：业务分析、需求分析、构件设计和构件实施．模式用于描述各个阶段的丁作产品，同时也是开发经验的表示．不同模式之间的可跟踪性是随着开发过程自动产生的，软件构件具有可跟踪性，其可重用性得到提高．     

J2EE构件化软件支撑平台研究与应用开发

为了提高软件复用程度,适应需求变化,提高业务应用系统开发效率和可维护性,研究了构件化、平台化的软件开发方法。基于Java2企业版（J2EE）的软件支撑平台,应用结构化、层次化和面向对象的方法,重点研究了软件支撑平台组成结构、软件构件定义、属性、表现和模型、构件分类与管理技术。同时,结合J2EE构件化软件支撑平台及其构件,研究了基于构件的业务应用软件的开发方法和过程模型。给出了基于J2EE的软件支撑平台的业务应用具体开发步骤,在多个实际项目中得到了应用。应用结果表明,提高了业务系统开发效率20％左右,软件复用显著提高,适应需求变化,可维护性增强。     

Using policies in highly configurable component-based NGOSS

The mission of operational support systems (OSS) is to run and manage the daily operations of a company. It is very important that the OSS exhibits great flexibility in adjusting its behaviour to ad hoc circumstances and in evolving as dictated by emerging changes. Contemporary advances in the area of software engineering, involving component-based frameworks, service-oriented architectures and Web Services, considerably facilitate the development of flexible component-based OSS. However, unless business rules, constraints and processes are disentangled from the OSS and become separately managed entities, every single change on them would require direct modifications within the system’s software, a fact that still limits the flexibility. It is the primary aim of this paper to examine the role that policies can play in delivering highly adaptable, configurable and flexible component-based new generation OSS (NGOSS). In order to ensure the highest degree of flexibility for NGOSS, the paper makes a threefold contribution. Firstly, a generic high-level model is introduced encompassing constructs that include policies capable of specifying NGOSS components in a technology-neutral way. The model complies with most of the TeleManagement Forum’s NGOSS principles. Secondly, we show how policies can be specified and used to flexibly configure component behaviour. Thirdly, the design of a component container is presented, which provides all necessary tools to facilitate the use of policies and aids the software materialisation of a policy-enabled interface to OSS components. An implementation of the container and an example scenario of its use is then shown.     

Managerial Decision-Making in Establishing R&M Design Goals

The concepts of operational capability and life-cycle cost are used to develop a managerial decision model for establishing design goals for system reliability and maintainability (R&M), and the apportionment of these goals to subsystem design levels, during the conceptual phase of system development. The model uses experience, engineering judgment, etc. to provide input data on attainable R&M levels and the programs required for achieving them. Solving the model allocates effort where the results are best according to a life-cycle cost objective function which reflects managerial aversion to cost and risk. Specifically, the model (with the solution technique) provides program managers a systematic approach for establishing R&M design goals when: 1) attainable R&M levels are not known with certainty; 2) costs are not known with certainty; 3) limited funds are available for system development; 4) constraints exist on at least some of the following factors: system availability, weight, and R&M; 5) some R&M alternatives are interdependent; and 6) the suitability of establishing R&M design goals depends on both cost and risk considerations. Utility of the model for R&M program decision making is demonstrated by applying it to the analysis of a system with 20 subsystems, each of which has a maximum of 9 possible R&M combinations.     

基于微内核结构的统一网管平台设计研究

微内核结构的软件系统是软件设计发展的方向之一。提出并设计了一套基于微内核结构的统一网管平台。平台采用客户/服务器群模式,服务器端各功能服务器仅负责各业务组件的初始化以及作为调度者充当业务组件与客户端、其他功能服务器之间数据传输的桥梁;具体业务皆由各网管业务组件负责完成。客户端以单一框架为容器,各业务显示、设置部件统一加载、分布其中。同时阐述了网管平台各业务的关键技术实现思想。最后给出了平台运营实例。     

基于PLM的可视化构件组装环境的设计与实现

本文在基于构件的软件开发方法基础上介绍了一种面向中小企业的可视化构件组装开发环境的设计和实现,并对构件技术的发展方向进行展望。     

Data Warehousing Process Maturity: An Exploratory Study of Factors Influencing User Perceptions

This paper explores the factors influencing perceptions of data warehousing process maturity. Data warehousing, like software development, is a process, which can be expressed in terms of components such as artifacts and workflows. In software engineering, the Capability Maturity Model (CMM) was developed to define different levels of software process maturity. We draw upon the concepts underlying CMM to define different maturity levels for a data warehousing process (DWP). Based on the literature in software development and maturity, we identify a set of features for characterizing the levels of data warehousing process maturity and conduct an exploratory field study to empirically examine if those indeed are factors influencing perceptions of maturity. Our focus in this paper is on managerial perceptions of DWP. The results of this exploratory study indicate that several factors—data quality, alignment of architecture, change management, organizational readiness, and data warehouse size—have an impact on DWP maturity, as perceived by IT professionals. From a practical standpoint, the results provide useful pointers, both managerial and technological, to organizations aspiring to elevate their data warehousing processes to more mature levels. This paper also opens up several areas for future research, including instrument development for assessing DWP maturity.     

基于领域工程的特种作战指挥系统建模研究

在领域工程理论的指导下,通过分析研究特种作战自动化指挥领域各业务领域的特点,采用面向特征的领域分析方法,结合面向对象的软件设计思想,得出了该领域的可继承和研究的共用和业务通用构件及系统集成模型框架。阐述了特种作战自动化指挥领域分析模型、领域设计模型和领域实现模型的建模过程及各阶段建模目标,介绍了选用的建模工具及模型的表示方法。     

构件化业务流程重组应用服务器可信属性建模方法研究

针对面向业务流程重组的应用服务器在可信属性建模方面的不足,基于组成应用服务器的构件属性和构件组合行为特征,利用进程代数等相关方法进行抽象,从构件之间的运算角度,定义BPRAS构件运算算子,从而建立BPRAS代数模型,并基于该代数模型,进一步对其支撑的业务流程应用软件可信属性建模,提出多种可信范式,为可信BPRAs软件设计提供理论模型支撑。最后介绍了一个应用实例。     

Design and Implementation of an Inclusive Ubiquitous Access

The development towards ubiquitous network access requires innovative solutions to get remote areas included, especially rural areas of developing regions. The challenges include robustness of network components, poor or non-existent power supply and sustainable business models. We argue that large scale user-driven community networks are becoming technically viable to deploy in areas that are short of supply of telecommunication services due to little or no commercial interest. To support this claim, we discuss the design of key network elements and careful power management based on alternative energy sources and storage. We also provide a status report from ongoing field-tests regarding provisioning of broadband network services in Serengeti, Tanzania, and outline briefly our strategy to achieve sustainability. On the technical side, we first discuss an affordable, high-performance, low-effect router based on open source software and standard off-the-shelf hardware offering both copper and fibre links. Our design is capable of forwarding more than 700?kpps at 22.3?W. The power consumption is considerably less than all alternatives in our comparison. Then we discuss power management and the use of batteries and super-capacitors as backup and storage solutions.     

Cellular network management goals and data-centric solutions

We elaborate on the management goals of next-generation cellular networks and describe how data-centric solutions can meet these goals. In a data-centric solution, operator applications act on a database representation of the cellular network. Network operations are invoked as a consequence to database changes, and the network, in turn, feeds the database with data such as network event notifications. The data-centric approach allows a focus on data as it is specified by the business needs of network management. This approach is augmented with data independence to assure consistent and flexible access of the data environment through the use of a common data interface. The data-centric design is contrasted with an application-centric design, and we conclude by providing suggestions on how application interface components can augment a data-centric network management solution     

基于GEF的业务模式图形编辑器的设计与实现

业务模式是根据客户需求而制定的一些规则和方法。改变传统手工编织代码来实现这些规则和方法,通过设计业务模式图形编辑器将这些规则和方法图形化使得项目开发效率更高。GEF提供了标准程序结构和组件框架,缩短了开发时间并提供了一致性的外观模型,GEF也提供了标准的开发框架,为图形编辑器的设计提供了基础组件,并进一步研究运用了框架中的命令设计模式,可以很容易地实现撤消/重做等功能。在此基于Eclipse平台和GEF架构设计和实现业务模式图形编辑器,提高开发效率和软件的可维护性。     

Using a software reliability model to design a telecommunicationssoftware architecture

The author proposes a software reliability model for a large real-time telecommunications software architecture. Some simple examples of the critical components of the software architecture and their dependencies are described. The component dependencies permit the propagation of faults from the component in which the fault originates to the other components. This propagation can cause failures in the chain (or in the tree) of components. Detection and failures depends on the tests executed or on the number and type of customer requests. An error can occur in any component. This error can be caused by a fault that propagated from another component or it can be a fault that originates in that component. The error can be traced through the component-dependency chain (or tree) to repair all the faults that are associated with that error. The software reliability model guides the design of the software architecture     

System-on-a-chip design for modern communications

In this article, the trends and opportunities in SoC IC design for the networking communication industry is presented. These trends will significantly affect innovation and practice of the microelectronics business in the future. Microchip development and deployment will not be treated as pure components business. In fact, it will become a solution-oriented business that requires knowledge of electronics, software, systems, and soft skills such as business, marketing, psychology for human factors, etc     

Three keys to developing and integrating telecommunications servicemanagement systems

With the deregulation of the telecommunication industry in Europe and the United States, communication and information services (e.g., multimedia entertainment services, educational services) are being increasingly delivered across value chains of network, service, and value-added service providers. The benefit of such interoperable services is the provision of “one-stop shopping” in which “tailored” services are delivered without their customers dealing with the multiplicity of underlying telecommunication services and network providers. The difficulty with such delivery chains is the complexity of managing these services across the different provider organizations (i.e., across both administrative and technological domains). These difficulties include achieving an understanding of business process across the organizations and the heterogeneity of the components to be (re)used to support these business processes in the organizations. This article examines three crucial elements in ensuring successful and flexible development of such service management systems-namely, a development process which is customized to support management system component development and component reuse; the development of business models capable of representing the underlying business processes for these systems; and an integration strategy designed to assist the flexible and timely cooperation of these management components both within a single organization (single administrative domain) as well as across organizations (multidomain)     

A scenario-based reliability analysis approach for component-based software

This paper introduces a reliability model, and a reliability analysis technique for component-based software. The technique is named Scenario-Based Reliability Analysis (SBRA). Using scenarios of component interactions, we construct a probabilistic model named Component-Dependency Graph (CDG). Based on CDG, a reliability analysis algorithm is developed to analyze the reliability of the system as a function of reliabilities of its architectural constituents. An extension of the proposed model and algorithm is also developed for distributed software systems. The proposed approach has the following benefits: 1) It is used to analyze the impact of variations and uncertainties in the reliability of individual components, subsystems, and links between components on the overall reliability estimate of the software system. This is particularly useful when the system is built partially or fully from existing off-the-shelf components; 2) It is suitable for analyzing the reliability of distributed software systems because it incorporates link and delivery channel reliabilities; 3) The technique is used to identify critical components, interfaces, and subsystems; and to investigate the sensitivity of the application reliability to these elements; 4) The approach is applicable early in the development lifecycle, at the architecture level. Early detection of critical architecture elements, those that affect the overall reliability of the system the most, is useful in delegating resources in later development phases.     

Multiprocessor SoC software design flows

Typical design flows supporting the software development for multiprocessor systems are based on a board support package and high-level programming interfaces. These software design flows fail to support critical design activities, such as design space exploration or software synthesis. One can observe, however, that design flows based on a formal model of computation can overcome these limitations. In this article, we analyze the major challenges in multiprocessor software development and present a taxonomy of software design flows based on this analysis. Afterwards, we focus on design flows based on the Kahn process network (KPN) model of computation and elaborate on corresponding design automation techniques. We argue that the productivity of software developers and the quality of designs could be considerably increased by making use of these techniques.     

A Method and Tool for Identifying Domain Components Using Object Usage Information

To enhance the productivity of software development and accelerate time to market, software developers have recently paid more attention to a component‐based development (CBD) approach due to the benefits of component reuse. Among CBD processes, the identification of reusable components is a key but difficult process. Currently, component identification depends mainly on the intuition and experience of domain experts. In addition, there are few systematic methods or tools for component identification that enable domain experts to identify reusable components. This paper presents a systematic method and its tool called a component identifier that identifies software components by using object‐oriented domain information, namely, use case models, domain object models, and sequence diagrams. To illustrate our method, we use the component identifier to identify candidates of reusable components from the object‐oriented domain models of a banking system. The component identifier enables domain experts to easily identify reusable components by assisting and automating identification processes in an earlier development phase.