面向服务软件体系结构的接口模型

服务接口描述是面向服务软件体系结构描述的关键问题之一,形式化描述方法是保证服务接口描述准确性的重要手段.目前的接口模型并不支持事务信息的描述.通过对已有Web服务接口模型进行扩展,提出了通过错误处理和补偿支持事务信息描述的接口模型,能够分别在特征层、会话层和协议层3个层面对服务的接口进行描述,然后提出了服务接口在3个层面的相容性和可替换性条件,并针对会话接口和协议接口提出了接口规约及其验证方法.该接口模型不仅能够支持准确的事务信息描述,而且还支持灵活、有效的接口规约验证.     

ISDN网与普通电话接口(POTS)设计

POTS接口是连接网络和普通电话的必备接口。介绍了实现电话与ISDN连接的POTS接口,给出了实现POTS接口的硬件详细设计,并结合POTS及其接口信号叙述了POTS的工作过程。     

PCI总线接口芯片的应用研究

本文归纳了 PCI总线接口电路的核心功能 ,对常见的 PCI总线接口芯片进行了比较 ,结合 MPEG II实时编解码卡接口电路设计实例 ,总结了利用 PCI总线接口芯片设计接口电路的主要问题     

USB可以接驳eSATA接口？一起来侃侃USB/eSATA二合一接口

目前大多数笔记本电脑上都配备了USB接口和eSATA接口以供用户传输数据。除了上述的两类接口外,笔记本电脑上还有一种比较有趣的接口,它将USB2．0接口和eSATA接口来了个合体,这便是我们马上要介绍的USB／eSATA二合一接口。     

TMNF-Q3接口适配系统的研究与设计

本文介绍了TMN中两个重要的接口———F接口和Q3接口 ,以及它们之间的相互关系 ,并在此基础上对F -Q3接口适配系统进行了研究 ,提出了一个F -Q3接口适配系统模型。     

从USB-C看去接口化趋势

你有想过笔记本只配备一个接口吗？无论是充电还是数据传输,又或者影音传输,仅一个USB接口就可以解决？是的！苹果12英寸MacBook的出现,整个机身仅配备了一个名为“USB-C”的接口,无论是数据传输还是充电,都会通过这个接口完成,其不但替代了USB接口及Thunderbolt,更干掉了苹果自己的Lightning接口,从而完成了一统接口的霸业。     

基于BU-61580的1553B总线接口设计

为提高1553B总线接口的实时性并简化接口逻辑,从总线接口的应用需求出发,设计了一种基于专用接口芯片和DSP控制器的1553B总线接口。该接口采用BU-61580作为协议引擎,采用TMS320F2812作为主处理器,只有少量的粘合逻辑,无需CPLD即可完成无缝衔接。该接口实时性好,可靠性高,硬件电路简单。以远程终端模式为例,对设计的1553B总线接口进行了测试验证。     

COM设计中的二义性及其解决方法探讨

近年来,组件技术在软件开发中得到了广泛的应用,COM是由微软提出来的组件标准,它不仅定义了组件程序之间交互的规范,而且也提供了组件程序所运行的环境。根据COM规范接口都应该继承自IUnknown接口,在接口的继承中不支持接口的多重继承。即一个接口只能有一个父接口。并且规定在杏询IUnknown接口时,结果应该是惟一的。如果我们把     

无人飞行器伺服系统余度控制接口的设计与实现

介绍了一种在无人飞行器中设计应用的伺服系统余度控制接口,该接口实现了数字总线和模拟量两余度接口控制,可有效提高伺服系统的可靠性和抗干扰能力;分析了无人飞行器机载伺服系统的结构组成和工作模式,选择了CAN总线作为机载数字通讯总线,论述了机载伺服系统余度控制接口的工作原理,同时给出了伺服控制器的硬件接口电路及软件工作流程;实验结果表明余度控制接口工作稳定,控制通道转换平稳,该接口能满足无人飞行器控制系统的要求。     

协议测试方法在航空总线接口设计中的应用

航空总线接口模块为机载计算机的互联提供接口,随着航电系统的综合化、集成化发展,航空总线接口功能、性能不断增强,集成度也越来越高,为了保证航空总线接口的高稳定性、高可靠性.通过对协议测试方法的分析,结合航空总线接口的设计特点,实现了协议测试方法在航空总线接口设计中的应用,为设计人员提供了测试理论及方法,提高航空总线接口产品的性能.     

基于FPGA和EMIFA的SPI控制器系统设计

为了在现有C6000系列DSP芯片上扩展多路SPI外围设备,提出了一种基于FPGA和EMIF接口的多路SPI控制器系统方案。该方案采用C6000系列DSP上的EMIF接口与FPGA进行数据交互,扩展出多路SPI控制器。在FPGA上实现了接口模块、寄存器读写模块以及多路通用SPI模块。在ModelSim环境下对所设计的SPI控制器进行了仿真实验,仿真结果表明SPI控制器可以进行全双工通信。随之,在DSP-FPGA集成计算机上进行了实物测试,扩展的SPI控制器外接具有SPI接口的CAN控制器芯片MCP2515,通过扩展的SPI控制器控制MCP2515的数据收发,测试结果显示DSP可以通过MCP2515与其它CAN设备进行通信,扩展的SPI控制器工作正常。     

SPI总线接口扩展与应用

在众多型号的单片机中,有许多不带SPI串行总线接口,从而限制了其对SPI总线接口器件的使用.本文介绍了SPI串行总线的特征和时序,对无SPI总线接口的单片机采用其I/O端口,通过程序控制的方法,模拟SPI串行总线接口,使其能与SPI总线接口的器件之间进行数据传送,并以串行E2PROM应用为例,介绍了模拟SPI串行总线接口的使用方法.     

面向EEPROM应用的SPI主控制器设计与实现

串行同步总线SPI提供了微处理器和其他外设之间的接口标准。但许多微处理器或微控制器中没有SPI接口,造成了数据通信的不便,解决的办法是将SPI核集成到芯片中。鉴于此,在研究SPI总线协议的基础上,以外设EEPROM初始化外围部件互连总线PCI中的配置寄存器为例,介绍了集成在芯片中的SPI主控制器访问外设EEPROM的具体过程,给出了设计逻辑框图和各个模块的实现及电路综合情况。在modelsim中完成功能仿真,并进行FPGA验证,结果正确,达到了设计的预期目的。     

RT-Thread的SPI总线驱动结构分析 、移植及应用

介绍了串行外设接口SPI的通信原理,对RT Thread操作系统下的SPI总线驱动结构进行了详细的研究与分析.以STM32F407ZG对W25Q64的读写为例,介绍了硬件SPI总线驱动的移植步骤,并详细介绍了SPI应用程序设计及技术实施细节.最后通过实验,对SPI驱动移植及程序设计的可行性及有效性进行验证,实验结果表明,RT Thread操作系统下的SPI总线驱动结构设计合理,移植方便且应用程序设计简单,本文所介绍的移植与应用方法可行有效.     

Software Process Improvement barriers: A cross-cultural comparison

ContextSoftware Process Improvement initiatives have been around for many years with the growing globalisation of software development is making them increasingly important.ObjectiveThe objective of this exploratory research is to gain an in-depth understanding of barriers that can undermine SPI, in the context of Global Software Development, from the perspective of software development practitioners; this will enable SPI managers to better manage SPI initiatives. We intend to discover if the barriers to SPI initiatives in a developed country are different to those in a developing country.MethodIn an empirical study, Vietnamese software practitioners’ experiences of SPI barriers are compared with barriers identified by Australian practitioners. Face-to-face questionnaire-based survey sessions with 23 Vietnamese SPI practitioners were conducted. Our survey included barriers to SPI improvement initiatives identified in previous research. We asked the participants to rank each SPI barrier on a three-point scale (high, medium, low) to determine the importance of each barrier. We then compare our results, with results (identified in previous work), from 34 Australian software development practitioners.ResultsWe identify (1) lack of project management, (2) lack of resources, (3) lack of sponsorship, (4) inexperienced staff/lack of knowledge, and (5) lack of SPI awareness as ‘high’ value SPI barriers in Vietnam. The results also reveal similarities and differences between the experiences of Australian and Vietnamese practitioners regarding the importance of the SPI barriers identified. While the Australian practitioners were also concerned with (1) lack of SPI awareness, they were even more concerned with (2) organisational politics, and (3) lack of support.ConclusionsPractitioners identify SPI barriers based on previous SPI implementation experience. Their role(s) in their different organisations have helped them to understand the importance of that barrier. Vietnamese software practitioners cited more SPI barriers than their counterparts in Australia. The Vietnamese SPI barriers relate to project management, resources, and sponsorship while the Australian barriers are concerned with organisational politics and lack of support.     

Investigating software process in practice: A grounded theory perspective

This paper presents the results of a study of how software process and software process improvement (SPI) is applied in actual practice in the software industry using the indigenous Irish software product industry as a test-bed. The study used the grounded theory methodology to produce a theory, grounded in the field data, that explains how software processes are formed and evolve and when and why SPI is undertaken. Our research found that SPI programmes are implemented reactively and many software managers are reluctant to implement SPI best practice models because of the associated costs.     

Software Process Improvement Motivators: An Analysis using Multidimensional Scaling

In this paper we present an analysis of software practitioners' motivations for software process improvement (SPI). Our findings are based on an empirical study of SPI in 13 software companies where we conducted focus groups with nearly 200 software practitioners. Our aim is to better understand how companies can maximise practitioner support for SPI. This insight should help SPI managers establish more effective SPI implementation strategies. In this paper we introduce the use of multidimensional scaling (MDS) in SPI research. MDS is a social science data analysis technique designed to generate a rich visual understanding of human issues. By using MDS we found evidence to suggest distinct clusters of punitive and rewarding SPI motivators. Furthermore our analysis also suggests that different clusters of motivations exist for different staff groups.     

Managing change in software process improvement

Software process improvement has become the primary approach to improving software quality and reliability, employee and customer satisfaction, and return on investment. Although the literature acknowledges that SPI implementation faces various problems, most published cases report success, detailing dramatic improvements. Such best-practice cases are a great benefit when learning how to effectively implement SPI. On the basis of experiences from SPI initiatives and insights into organizational-change management, we offer the following advice for successful SPI implementation: software managers must appreciate that each SPI initiative is unique and carefully negotiate the context of change. Managers must also understand the elements of change involved. SPI can't succeed without managerial commitment and a mastery of appropriate change tactics.