一种面向复用的增量软件开发过程框架

以复用思想指导软件开发是软件产业发展的趋势,而当前主要面向复用的软件开发方法没有考虑到我国软件企业以中小型为主的现状,缺乏针对性,使得复用在我国软件开发中应用不够广泛。在基于构件开发的基础上提出了一种面向复用的增量软件开发过程框架。该过程框架适于我国中小型软件企业,采用了以体系结构为指导的增量开发模式,涵盖了可复用资产的生产过程和利用可复用资产的软件开发过程。     

中国计算机软件产业发展的基本对策

本文分析了软件行业在我国的发展现状,针对现状分析其存在的一些问题,并且就这些存在的问题提出改进意见,并结合行业发展状况软件企业的市场发展方向提出建议。     

Software development methods and usability: Perspectives from a survey in the software industry in Norway

This paper investigates the relationship between software development methodologies and usability. The point of departure is the assumption that two important disciplines in software development, one of software development methods (SDMs) and one of usability work, are not integrated in industrial software projects.

Building on previous research we investigate two questions; (1) Will software companies generally acknowledge the importance of usability, but not prioritise it in industrial projects? and (2) To what degree are software development methods and usability perceived by practitioners as being integrated? To this end a survey in the Norwegian IT industry was conducted. From a sample of 259 companies we received responses from 78 companies.

In response to our first research question, our findings show that although there is a positive bias towards usability, the importance of usability testing is perceived to be much less than that of usability requirements. Given the strong time and cost pressures associated with the software industry, we believe that these results highlight that there is a gap between intention and reality. Regarding our second research question our survey revealed that companies perceive usability and software development methods to be integrated. This is in contrast to earlier research, which, somewhat pessimistically, has argued for the existence of two different cultures, one of software development and one of usability. The findings give hope for the future, in particular because the general use of system development methods are pragmatic and adaptable.     

Software Process Improvement Problems in Twelve Software Companies: An Empirical Analysis

In this paper we discuss our study of the problems 12 software companies experienced in software development. In total we present qualitative data collected from 45 focus groups that involved over 200 software staff. We look at how different practitioner groups respond to software process improvement problems. We show our classification and analysis of this data using correspondence analysis. Correspondence analysis is a graphical data representation method new to software development research. The aim of the work we present is to develop a more holistic understanding of the problems practitioners are experiencing in their attempts to improve their software processes. Our main finding is that there is an association between a company's capability maturity and patterns of reported problems. Organizational problems are more associated with high maturity companies than with low maturity companies. Low maturity companies are closely linked to problems relating directly to projects such as documentation, timescales, tools and technology. Our findings also confirm differences in practitioner group problems. Senior managers cite problems with goals, culture and politics. Project managers are concerned with timescales, change management, budgets and estimates. Developers are experiencing problems with requirements, testing, documentation, communication, tools and technology. These associations are displayed graphically through correspondence analysis maps.     

软件开发外包项目管理案例分析及探索

软件外包是一个非常大的市场,目前在国内有很多软件公司从事软件项目外包行业,或把自己的部分业务发包给外包方,软件项目外包管理随着近年软件项目外包的发展越来越受到重视,它与公司项目的内容管理既关联又存在差异,文章通过对企业实际外包项目的具体案例的风险进行分析,提出了相应的解决方案,并总结了项目实施过程中存在的问题及改进意见,为软件企业的外包项目管理提供了借鉴。     

基础软件技术的发展趋势

从分析基础软件的基本概念和特性出发,对基础软件的内容、需求、技术、产品等方面进行了系统论述。探讨了现有的主流开发技术及未来的发展趋势。通过分析现有部分国产软件系统在一些典型领域的应用,揭示我国基础软件发展的现状和难题,为现有国产基础软件产业的发展提供决策参考。     

软件测试文档工程论述

文档在软件开发生命周期中至关重要,文档也是质量管理的需要,软件测试文档更是直接反应软件产品的质量。阐述了诸多公司在软件测试文档工程中存在的问题,并将发现的问题进行归类分析,提出了切实可行的软件测试文档管理方案。     

浅论软件开发项目的管理

随着信息技术的飞速发展,软件产品的规模也越来越庞大,个人单打独斗的作坊式开发方式已经越来越不适应发展的需要。各软件企业都在积极将软件项目管理引入开发活动中,对开发实行有效的管理。     

Key activities for product derivation in software product lines

More and more organizations adopt software product lines to leverage extensive reuse and deliver a multitude of benefits such as increased quality and productivity and a decrease in cost and time-to-market of their software development. When compared to the vast amount of research on developing product lines, relatively little work has been dedicated to the actual use of product lines to derive individual products, i.e., the process of product derivation. Existing approaches to product derivation have been developed independently for different aims and purposes. While the definition of a general approach applicable to every domain may not be possible, it would be interesting for researchers and practitioners to know which activities are common in existing approaches, i.e., what are the key activities in product derivation. In this paper we report on how we compared two product derivation approaches developed by the authors in two different, independent research projects. Both approaches independently sought to identify product derivation activities, one through a process reference model and the other through a tool-supported derivation approach. Both approaches have been developed and validated in research industry collaborations with different companies. Through the comparison of the approaches we identify key product derivation activities. We illustrate the activities’ importance with examples from industry collaborations. To further validate the activities, we analyze three existing product derivation approaches for their support for these activities. The validation provides evidence that the identified activities are relevant to product derivation and we thus conclude that they should be considered (e.g., as a checklist) when developing or evaluating a product derivation approach.     

A survey on search-based software design

This survey investigates search-based approaches to software design. The basics of the most popular meta-heuristic algorithms are presented as background to the search-based viewpoint. Software design is considered from a wide viewpoint, including topics that can also be categorized as software maintenance or re-engineering. Search-based approaches have been used in research from the high architecture design level to software clustering and finally software refactoring. Enhancing and predicting software quality with search-based methods is also taken into account as a part of the design process. The background for the underlying software engineering problems is discussed, after which search-based approaches are presented. Summarizing remarks and tables collecting the fundamental issues of approaches for each type of problem are given. The choices regarding critical decisions, such as representation and fitness function, when used in meta-heuristic search algorithms, are emphasized and discussed in detail. Ideas for future research directions are also given.     

Knowledge-based approaches in software documentation: A systematic literature review

ContextSoftware documents are core artifacts produced and consumed in documentation activity in the software lifecycle. Meanwhile, knowledge-based approaches have been extensively used in software development for decades, however, the software engineering community lacks a comprehensive understanding on how knowledge-based approaches are used in software documentation, especially documentation of software architecture design.ObjectiveThe objective of this work is to explore how knowledge-based approaches are employed in software documentation, their influences to the quality of software documentation, and the costs and benefits of using these approaches.MethodWe use a systematic literature review method to identify the primary studies on knowledge-based approaches in software documentation, following a pre-defined review protocol.ResultsSixty studies are finally selected, in which twelve quality attributes of software documents, four cost categories, and nine benefit categories of using knowledge-based approaches in software documentation are identified. Architecture understanding is the top benefit of using knowledge-based approaches in software documentation. The cost of retrieving information from documents is the major concern when using knowledge-based approaches in software documentation.ConclusionsThe findings of this review suggest several future research directions that are critical and promising but underexplored in current research and practice: (1) there is a need to use knowledge-based approaches to improve the quality attributes of software documents that receive less attention, especially credibility, conciseness, and unambiguity; (2) using knowledge-based approaches with the knowledge content in software documents which gets less attention in current applications of knowledge-based approaches in software documentation, to further improve the practice of software documentation activity; (3) putting more focus on the application of software documents using the knowledge-based approaches (knowledge reuse, retrieval, reasoning, and sharing) in order to make the most use of software documents; and (4) evaluating the costs and benefits of using knowledge-based approaches in software documentation qualitatively and quantitatively.     

构建基于CSCW的TSP实施系统的研究

软件开发是一个群体协作的过程，要求团队成员在开发活动中相互分工、紧密协作。小组软件过程(TSP)的产生为规范软件开发和改进过程能力提供了有效而实际的帮助，TSP的实施遇到阻碍，主要是由于小组成员对TSP过程不够理解、交流和协同工作困难、软件过程数据处理繁琐等原因。该文提出了计算机支持的协同工作(SCW)-TSP系统解决这些问题，该系统根据CSCW的特性，将TSP的管理方法以计算机应用软件的形式加以实现，使开发团队能够更有效地应用TSP进行开发，全面提高软件开发的效率和质量。     

Process fusion: An industrial case study on agile software product line engineering

This paper presents a case study of a software product company that has successfully integrated practices from software product line engineering and agile software development. We show how practices from the two fields support the company’s strategic and tactical ambitions, respectively. We also discuss how the company integrates strategic, tactical and operational processes to optimize collaboration and consequently improve its ability to meet market needs, opportunities and challenges. The findings from this study are relevant to software product companies seeking ways to balance agility and product management. The findings also contribute to research on industrializing software engineering.     

神经网络在软件失效预测中的性能比较和研究

在软件开发的早期预测有失效倾向的软件模块,能够极大地提高软件的质量.软件失效预测中的一个普遍问题是数据中噪声的存在.神经网络具有鲁棒性而且对噪声有很强的抑制能力.不同结构的神经网络在训练算法和应用领域都有差异.该文主要就软件失效预测这个应用领域叙述几种适用的网络,并比较这几种网络在训练结果和性能上的差异.上述方法在SDH通信软件的失效预测中得到了成功的应用.试验结果显示虽然MLP、PNN、LVQ网络都能解决这类模式分类问题,但是只有MLP网络训练结果比较稳定,在不同的数据集上训练出的网络都有很好的预测效果.     

Software development in startup companies: A systematic mapping study

ContextSoftware startups are newly created companies with no operating history and fast in producing cutting-edge technologies. These companies develop software under highly uncertain conditions, tackling fast-growing markets under severe lack of resources. Therefore, software startups present a unique combination of characteristics which pose several challenges to software development activities.ObjectiveThis study aims to structure and analyze the literature on software development in startup companies, determining thereby the potential for technology transfer and identifying software development work practices reported by practitioners and researchers.MethodWe conducted a systematic mapping study, developing a classification schema, ranking the selected primary studies according their rigor and relevance, and analyzing reported software development work practices in startups.ResultsA total of 43 primary studies were identified and mapped, synthesizing the available evidence on software development in startups. Only 16 studies are entirely dedicated to software development in startups, of which 10 result in a weak contribution (advice and implications (6); lesson learned (3); tool (1)). Nineteen studies focus on managerial and organizational factors. Moreover, only 9 studies exhibit high scientific rigor and relevance. From the reviewed primary studies, 213 software engineering work practices were extracted, categorized and analyzed.ConclusionThis mapping study provides the first systematic exploration of the state-of-art on software startup research. The existing body of knowledge is limited to a few high quality studies. Furthermore, the results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.     

CMM在中国软件企业中的应用研究

CMM的应用已经从知识导入期进入研究和实施期,该文分析了我国软件组织的软件过程现状,和它们在实施CMM过程中存在的问题。同时根据SEI制订的IDEAL方法,结合笔者亲身经历的一个实施案例,探讨了我国软件企业实施CMM具体操作模型。     

一种开发和测试国际化软件的新方法

1 引言软件的国际化是目前软件设计的一个趋势。一个软件要想在国际市场上取得成功,就必须使用当地的语言和一些约定俗成的数据格式。用户们希望一个软件能按照他们所习惯的方式来运行。例如,中国用户希望使用中文界面,日期表示为yyyy年mm月dd日,货币表示为圆;美国用户则希望使用英语,日期表示为mm/dd/yy的格式,货币表示为美圆(＄);而德国用户则希望看到用德语表示的信息,日期表示为dd.mm.yyyy的格式,货币表示为德国马克(DM)。不能“入乡随俗”的软件是很难让用户满意的。对软件公司来说,在开始投资开发出第一种语言版本后,只要能将转换到其他语言的费用控制得很低,那么在别的国家销售同样的软件所带来的利润是巨大的。     

Investigating Architectural Technical Debt accumulation and refactoring over time: A multiple-case study

ContextA known problem in large software companies is to balance the prioritization of short-term with long-term feature delivery speed. Specifically, Architecture Technical Debt is regarded as sub-optimal architectural solutions taken to deliver fast that might hinder future feature development, which, in turn, would hinder agility.ObjectiveThis paper aims at improving software management by shedding light on the current factors responsible for the accumulation of Architectural Technical Debt and to understand how it evolves over time.MethodWe conducted an exploratory multiple-case embedded case study in 7 sites at 5 large companies. We evaluated the results with additional cross-company interviews and an in-depth, company-specific case study in which we initially evaluate factors and models.ResultsWe compiled a taxonomy of the factors and their influence in the accumulation of Architectural Technical Debt, and we provide two qualitative models of how the debt is accumulated and refactored over time in the studied companies. We also list a set of exploratory propositions on possible refactoring strategies that can be useful as insights for practitioners and as hypotheses for further research.ConclusionSeveral factors cause constant and unavoidable accumulation of Architecture Technical Debt, which leads to development crises. Refactorings are often overlooked in prioritization and they are often triggered by development crises, in a reactive fashion. Some of the factors are manageable, while others are external to the companies. ATD needs to be made visible, in order to postpone the crises according to the strategic goals of the companies. There is a need for practices and automated tools to proactively manage ATD.     

构件技术与软件Agent技术研究

构件技术的提出对软件重用和软件开发效率的提高具有非常重要的意义。而软件Agent技术的提出为复杂问题的求解找到了很好的办法。首先分析了组件技术和软件Agent技术的主要内容,然后提出将构件技术与软件Agent技术相融合可以有效地提高软件的重用性、灵活性及适应性等,最后分析了组件技术和软件agent技术在软件开发中的应用。     

基于CMM、PSP、TSP的软件开发模型

在软件开发中软件工程师个人及软件组织不可避免地会遇到各种困难,尤其是软件组织在实施CMM中面对的各种挑战。CMM用于提高整个软件组织的能力成熟度,PSP和TSP分别用于改进软件工程师个人的工作风格和提高小组的软件开发质量和效率。三者的有效结合将进一步提高软件产品的质量和生产率以及软件组织的能力成熟度。该文提出一种将三者及软件体系结构等其他技术结合起来的软件开发模型。