航空机轮加载测控系统软件的设计与实现

鉴于航空机轮加载试验过程中,要求上位机测控软件能够即时向下位机下达控制命令并且能够实时采集下位机上传的大量现场数据,给出了一种基于DataSocket技术和OPC协议的实时网络通信方法;针对程序执行过程中常出现的响应阻塞问题,结合LabWin-dows/CVI的多线程机制论述了一种多任务并发执行的方法;经过反复测试试验,由此所构建的上位机软件响应性能良好,其网络通信传输速率快、实时性高。     

多平台1553B总线模拟器设计

MIL-STD-1553B总线标准为目前航空航天领域中广泛应用的一种数据通信标准,在卫星中的应用也十分广泛,为此,1553B总线模拟器也已逐渐成为星载软件开发、测试的必备辅助工具,但由于商用总线仿真卡存在着灵活性不够、不具备网络通信功能等缺点,不能完全满足星载软件研制的需要,而基于总线仿真卡进行再开发能够很好地解决这个问题;文中主要阐述了在Windows和VxWorks两种环境下基于总线仿真卡进行1553B总线模拟器再开发的设计方法和实践体会。     

开源自动化控制软件Sedona在物联网中的应用

通过讨论物联网的现状、关键技术及发展方向,主要介绍了一种开源自动化控制软件Sedona在物联网的应用技术,包括在物联网架构中如何进行软件开发和应用程序设计,并介绍了该架构的技术特点。Sedona语言是一种通用的面向组件化的编程语言。Sedona虚拟机是一个小型解析器,具有良好的移植性,内嵌多种通信协议,可以运行在任何基于IP通信的网络上。最终实现各设备之间集中控制、分散管理的目标。     

Rapid software integration using structured methods

In this paper we discuss an approach to organizing the integration of 110,000 lines of C, SQL, Assembler, and microcode distributed over a network of 36 processors of four types so that it could be accomplished in six months. The software runs on a test system architecture consisting of a LAN-based workstation group and a set of VME-based embedded processors. By using structured methodology, parallelism in the integration process was achieved. The necessary stub tools were identified and developed before integration began. The principles followed and experiences of integrating the system are discussed.     

VB程序在铁路货车制造行业中小设备中的应用

介绍利用VB语言在铁路货车制造行业中小设备中的软件开发方案的实现,以及对铁路货车制造行业相关专业性要求适应的实现。     

提高计算机软件课程教学效果的思考

在信息技术时代的今天,伴随着计算机技术的迅猛发展以及在日常生活和工作中的普及,我们如何掌握常用的计算机应用软件成为每个人工作学习中不可缺少的课程。在该课程的教学过程中,教师应选择合适的版本,以培养学生的动手能力、自学能力和创新意识为出发点,综合运用实例教学法、任务驱动教学法等方法,同时给学生创造一个自主的学习环境,并建立灵活的评价体系,以增强教学效果。     

生产线试运行过程工艺分析软件的应用

介绍了生产线试运行过程中，用工艺分析软件解决所遇到的工艺问题，为工艺分析软件开拓了一个新的应用领域。     

PRO/Ⅱ软件在硫磺回收中的二次开发应用

硫磺回收装置的设备需要有较大的操作弹性。针对其过程气进口压力低，手工计算难于进行严格的全程压降计算，现以PRO／Ⅱ软件为开发平台，通过扩充数据库和建立模拟流程，成功地将其用于硫磺回收装置的设备选型和核算，为工程设计提供了先进的计算手段。     

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.