试析计算机软件法律保护的途径

目前存在的计算机软件法律保护途径各有利弊。计算机软件的法律保护途径应当和计算机软件的法律本质相适应。为此,世界知识产权组织和一些国家都曾对计算机软件保护进行过单独立法的尝试。应该说单独立法保护计算机软件符合软件本身的特点,是未来立法的必然趋势。     

论计算机软件的法律保护

探讨了计算机软件及其法律特征、计算机软件的法律保护问题 ,指出在法律意义上应将计算机软件界定为计算机程序 ,基于计算机软件的特殊性应予其综合法律保护 ,最后分析了计算机软件版权保护存在问题并提出了相关的完善意见     

A software reliability model using mean residual quantile function

In this paper, we propose a class of distributions with the inverse linear mean residual quantile function. The distributional properties of the family of distributions are studied. We then discuss the reliability characteristics of the family of distributions. Some characterizations of the class of distributions are also discussed. The parameters of the class of distributions are estimated using the method of L-moments. The proposed class of distributions is applied to a real data set.     

Expatriate paternalistic leadership and gender relations in small European software firms in India

The study examines how European managers deliver paternalistic leadership in two small IT companies in India, a collectivist, high-power-distance culture where private lives are largely influenced by extended families. In particular, gender aspects are discussed in relation to recruitment and attrition, working hours and leave policies, and building company culture. These small companies experience a different set of challenges from those faced by the big multinationals, and they meet them in different ways, often translating Western management ideas to fit the Indian context. This article shows how managers of these two companies, with their European background, adapt their leadership to the Indian setting and how they handle gender issues. While some degree of paternalistic leadership appears to be a necessity in the Indian context, introducing European ideas of low power differences and regulated policies creates a mix which is appreciated by the employees.     

Optimal Coordination in Distributed Software Development

The construction of a software system requires not only individual coding effort from team members to realize the various functionalities, but also adequate team coordination to integrate the developed code into a consistent, efficient, and bug‐free system. On the one hand, continuous coding without adequate coordination can cause serious system inconsistencies and faults that may subsequently require significant corrective effort. On the other hand, frequent integrations can be disruptive to the team and delay development progress. This tradeoff motivates the need for a good coordination policy. Both the complexity and the importance of coordination is accentuated in distributed software development (DSD), where a software project is developed by multiple, geographically‐distributed sub‐teams. The need for coordination in DSD exists both within one sub‐team and across different sub‐teams. The latter type of coordination involves communication across spatial boundaries (different locations) and possibly temporal boundaries (different time zones), and is a major challenge that DSD faces. In this study, we model both inter‐ and intra‐sub‐team coordination in DSD based on the characteristics of the systems being developed by the sub‐teams, the deadline for completion, and the nature of division adopted by the sub‐teams with respect to development and integration activities. Our analysis of optimal coordination policies in DSD shows that integration activities by one sub‐team not only benefit that sub‐team (as is the case in co‐located development) but can also help the other sub‐teams by providing greater visibility, thereby resulting in a higher integration frequency relative to co‐located development. Analytical results are presented to demonstrate how the characteristics of the projects and the sub‐teams, and the efficiency of communication across the sub‐teams, affect coordination and productivity. We also investigate the pros and cons of using specialized integration sub‐teams and find that their advantage decreases as the project schedule becomes tighter. Decentralized decisions and asymmetric subsystems are also discussed.     

基于系统动力学的软件产业技术创新动力因素研究

软件产业技术创新动力机制是持续提升软件产业技术创新的内在动力源泉。运用系统动力学的研究方法,在对软件产业技术创新现状分析的基础上,提出了软件产业技术创新的5个内部动力要素：企业 R&D 投入、企业知识管理、企业家精神、企业科技人才和企业文化,以及4个外部动力要素：软件产业基地、市场需求、政府支持和知识产权保护。探讨了各个动力要素对软件产业技术创新的促进作用,建立了因果关系模型图,分析了反馈路径。在反馈环分析的基础上提出了增强软件产业技术创新能力的对策与建议。     

基于SCKey组态软件的电子产品高温老化室控制系统设计

针对现有的电子产品高温老化室控制系统在进行电子产品高温老化过程中存在的温度控制灵敏度低,温度变化 速率难以控制,操作过程可视性差等问题,提出了一种基于SCKey系统组态软件的电子产品高温老化室控制系统。设计 了基于PLC控制器的控制系统硬件结构,给出了电气控制线路图和PLC外部接线图;设计了基于SCKev系统组态软件 和AdvanTrol实时监控软件的现场控制组态界面。实际运行结果表明,该系统运行可靠,温度控制精度高,温度变化速率 符合高温老化工艺的技术要求,具有较好的控制效果。     

Product Life‐Cycle Management of Packaged Software

A software product becomes less valuable for its consumers over time due to technological and economic obsolescence. As a result, firms have an opportunity to introduce and sell upgrades that provide higher utility to consumers compared to an older and out‐of‐date software product. In a market that is growing and consists of homogeneous customers, we prove that the optimal upgrade intervals are monotonically increasing throughout the product's life cycle solely because of demand and cost considerations. This finding is in conformity with empirical evidence, thus validating our theoretical model. We then present comparative statics results to show that increase in the rate of obsolescence or network externalities may sometimes increase upgrade intervals for early upgrades and decrease these for later upgrades in the product's life cycle, but increase in market growth rate always decreases these intervals. Further, when successive software upgrades are forward compatible, upgrade intervals are longer than when they are not. Finally, we present three separate extensions of our model to showcase the robustness of our results. Since upgrade development costs depend on upgrade intervals, these insights help managers understand how costing for upgrades changes over the product's life cycle.