Testing scientific software: A systematic literature review

ContextScientific software plays an important role in critical decision making, for example making weather predictions based on climate models, and computation of evidence for research publications. Recently, scientists have had to retract publications due to errors caused by software faults. Systematic testing can identify such faults in code.ObjectiveThis study aims to identify specific challenges, proposed solutions, and unsolved problems faced when testing scientific software.MethodWe conducted a systematic literature survey to identify and analyze relevant literature. We identified 62 studies that provided relevant information about testing scientific software.ResultsWe found that challenges faced when testing scientific software fall into two main categories: (1) testing challenges that occur due to characteristics of scientific software such as oracle problems and (2) testing challenges that occur due to cultural differences between scientists and the software engineering community such as viewing the code and the model that it implements as inseparable entities. In addition, we identified methods to potentially overcome these challenges and their limitations. Finally we describe unsolved challenges and how software engineering researchers and practitioners can help to overcome them.ConclusionsScientific software presents special challenges for testing. Specifically, cultural differences between scientist developers and software engineers, along with the characteristics of the scientific software make testing more difficult. Existing techniques such as code clone detection can help to improve the testing process. Software engineers should consider special challenges posed by scientific software such as oracle problems when developing testing techniques.     

Global software testing under deadline pressure: Vendor-side experiences

ContextIn the era of globally-distributed software engineering, the practice of global software testing (GST) has witnessed increasing adoption. Although there have been ethnographic studies of the development aspects of global software engineering, there have been fewer studies of GST, which, to succeed, can require dealing with unique challenges.ObjectiveTo address this limitation of existing studies, we conducted, and in this paper, report the findings of, a study of a vendor organization involved in one kind of GST practice: outsourced, offshored software testing.MethodWe conducted an ethnographically-informed study of three vendor-side testing teams over a period of 2 months. We used methods, such as interviews and participant observations, to collect the data and the thematic-analysis approach to analyze the data.FindingsOur findings describe how the participant test engineers perceive software testing and deadline pressures, the challenges that they encounter, and the strategies that they use for coping with the challenges. The findings reveal several interesting insights. First, motivation and appreciation play an important role for our participants in ensuring that high-quality testing is performed. Second, intermediate onshore teams increase the degree of pressure experienced by the participant test engineers. Third, vendor team participants perceive productivity differently from their client teams, which results in unproductive-productivity experiences. Lastly, participants encounter quality-dilemma situations for various reasons.ConclusionThe study findings suggest the need for (1) appreciating test engineers’ efforts, (2) investigating the team structure’s influence on pressure and the GST practice, (3) understanding culture’s influence on other aspects of GST, and (4) identifying and addressing quality-dilemma situations.     

Performance on agile teams: Relating iteration objectives and critical decisions to project management success factors

ContextWhile project management success factors have long been established via the golden triangle, little is known about how project iteration objectives and critical decisions relate to these success factors. It seems logical that teams’ iteration objectives would reflect project management success factors, but this may not always be the case. If not, how are teams’ objectives for iterations differing from the golden triangle of project management success factors?ObjectiveThis study identifies iteration objectives and the critical decisions that relate to the golden triangle of project management success factors in agile software development teams working in two-week iterations.MethodThe author conducted semi-structured interviews with members across three different agile software development teams using a hybrid of XP and Scrum agile methodologies. Iteration Planning and Retrospective meetings were also observed. Interview data was transcribed, coded and reviewed by the researcher and two independently trained research assistants. Data analysis involved organizing the data to identify iteration objectives and critical decisions to identify whether they relate to project management success factors.ResultsAgile teams discussed four categories of iteration objectives: Functionality, Schedule, Quality and Team Satisfaction. Two of these objectives map directly to two aspects of the golden triangle: schedule and quality. The agile teams’ critical decisions were also examined to understand the types of decisions the teams would have made differently to ensure success, which resulted in four categories of such decisions: Quality, Dividing Work, Iteration Amendments and Team Satisfaction.ConclusionThis research has contributed to the software development and project management literature by examining iteration objectives on agile teams and how they relate to the golden triangle of project management success factors to see whether these teams incorporate the golden triangle factors in their objectives and whether they include additional objectives in their iterations. What’s more, this research identified four critical decisions related to the golden triangle. These findings provide important insight to the continuing effort to better assess project management success, particularly for agile teams.     

交流接触器温度场仿真及试验验证

将ANSYS有限元热分析应用到交流接触器热特性分析中,模仿其实际工作环境,构建交流接触器三维稳态热分析模型,确定热源、导热系数和表面散热系数,对接触器的稳态温度场进行分析;进一步改变施加的边界条件,研究不同散热方式下接触器的温度分布。最后对CJX2-0910型交流接触器进行温升试验,将温度场的仿真结果与试验结果比较,误差较小,表明所建立热分析模型的可行性。研究结果对接触器材料的选择、结构的设计及其性能的优化有重要意义。     

Managing knowledge on communication and information flow in global software projects

Communication is a key success factor of distributed software projects. Poor communication has been identified as a main obstacle to successful collaboration. Global projects are especially endangered by information gaps between collaborating sites. Different communication styles, technical equipment, and missing awareness of each other can cause severe problems. Knowledge about actual and desired channels, paths, and modes of communication is required for improving communication in a globally distributed project. However, many project participants know little about communication and information flow in their projects. In this contribution, we focus on knowledge about communication and information flow. It is acquired by modelling on‐going and desired flows of information, including documented and non‐documented channels of information flow. We analyzed a distributed software project from the information flow perspective. Based on the findings, we developed specific techniques to improve information flow in distributed software development according to the FLOW Method. In a second distributed project, we evaluated one of the techniques. We found the FLOW mapping technique to be suitable for effectively spreading knowledge about communication and information flow in global software projects.     

Integration by communication: knowledge exchange in global outsourcing of product software development

Global outsourcing is a growing trend among independent software vendors. In these projects like other distributed work, distances have negative effects on communication and coordination, directly impacting performance. We present a normative model designed to address this issue by improving communication and knowledge exchange. The model consists of six distinct practices and a tool blueprint, each coming with practical guidelines. It is based in part on two case studies of Dutch software vendors who have successfully outsourced part of their activities to an Eastern European outsourcing vendor, and validated by a panel of six experts from industry and the scientific community. It is concluded that knowledge exchange in global software outsourcing is a by‐product of efforts to enhance communication and coordination, rather than specific technical solutions. By committing to sharing knowledge, emphasizing transparency and integrating the outsourcing team into their organizations, customers from the product software business can realize the benefits of global outsourcing.     

基于CaO引导的甲烷蒸汽重整化学链燃烧制氢系统

为在重整气中得到高纯H_2和降低尾气CO_2分离成本,建立了基于CaO引导的甲烷蒸汽重整化学链燃烧制氢系统,该系统在重整反应器中加入CaO吸收剂,用以吸收重整器内的CO_2,提高重整气中H_2浓度,形成的CaCO_3固体在煅烧器中受热分解重新生成CaO。利用Aspen Plus进行了过程模拟及热力学分析,并研究主要参数对系统性能的影响,得到优化的操作条件为:CaO循环量/CH_4比为0.5,CH_4(燃料)/CH_4比为0.35,NiO循环量/CH_4比为1.4。CaO循环量/CH_4比从0变化到0.5时,重整气中H_2浓度从0.60增长到0.99;CH_4(燃料)/CH_4比在0.25~0.45区间变化时,重整气中H_2浓度从0.86提高到0.99,产气量增加;NiO循环量/CH_4比在1~1.6区间变化时,重整气中H_2浓度从0.88增长到0.99,系统有效能效率变化较小。     

基于“二叉决策树”模型的嵌入式软件调试

在嵌入式软件开发过程中,软件不可避免地会出现各种错误,因此调试是软件生命周期中一个非常重要的环节。针对嵌入式软件开发的流程和特点,对其调试部分进行较为深入具体的研究和探索,提出基于调试器的"二叉决策树"调试模型。该模型描述了嵌入式软件调试的一般过程、调试对象和常用方法。实践表明"二叉决策树"调试模型具有较好的实用性和扩展性。     

基于Profibus-DP总线技术的烟支重量控制系统设计

对烟支重量控制系统的控制原理做了较为详尽的描述,介绍了系统硬件组成和软件设计。系统可实时在线对高速烟支重量进行计算,及时准确剔除不合格烟支。通过Profibus-DP总线,烟支重量控制系统实现了与人机界面系统实时、可靠、高速通信,操作人员通过人机界面可以方便的调整控制参数,对设备进行维护。     

基于IndasIBMS组态软件的智能楼宇监控系统

以达实智能大厦的冷冻机房及整栋大楼的空调控制系统的建设为背景,简要介绍了IndasIBMS组态软件,最后以达实智能大厦为工程实例说明使用IndasIBMS组态软件设计智能楼宇自动化监控系统的方法,可为同行提供借鉴和参考。