Empirical studies on the use of social software in global software development – A systematic mapping study

BackgroundIn Global Software Development (GSD), informal communication and knowledge sharing play an important role. Social Software (SoSo) has the potential to support and foster this key responsibility. Research on the use of SoSo in GSD is still at an early stage: although a number of empirical studies on the usage of SoSo are available in related fields, there exists no comprehensive overview of what has been investigated to date across them.ObjectiveThe aim of this review is to map empirical studies on the usage of SoSo in Software Engineering projects and in distributed teams, and to highlight the findings of research works which could prove to be beneficial for GSD researchers and practitioners.MethodA Systematic Mapping Study is conducted using a broad search string that allows identifying a variety of studies which can be beneficial for GSD. Papers have been retrieved through a combination of automatic search and snowballing, hence a wide quantitative map of the research area is provided. Additionally, text extracts from the studies are qualitatively synthesised to investigate benefits and challenges of the use of SoSo.ResultsSoSo is reported as being chiefly used as a support for collaborative work, fostering awareness, knowledge management and coordination among team members. Contrary to the evident high importance of the social aspects offered by SoSo, socialisation is not the most important usage reported.ConclusionsThis review reports how SoSo is used in GSD and how it is capable of supporting GSD teams. Four emerging themes in global software engineering were identified: the appropriation and development of usage structures; understanding how an ecology of communication channels and tools are used by teams; the role played by SoSo either as a subtext or as an explicit goal; and finally, the surprising low percentage of observational studies.     

Trustworthiness of Internet-based software

Recent years see an increasing concern over the trustworthiness of Inter- net-based software. By analyzing the trustworthiness of Internet-based software and the nature of the Internet applications, we point out that, on the one hand, due to the open- ness and dynamic nature of the Internet, the identity trustworthiness and the capability trustworthiness of the software are facing serious challenges; on the other hand, in order to ensure the trustworthiness of the whole system, emerging computing paradigms based on the collaboration of autonomous software need some impacts on the behavior of the software. Here we put forward a conceptual model for the trustworthiness of Inter- net-based software, and propose a trustworthy assurance framework for Internet-based virtual computing environment (iVCE). This framework deals with the trustworthy proper- ties of software on identity, capability and behavior in a combinated way. The authorization management in inter-domain computing environment, assurance on high availability of service and incentive mechanism for autonomic collaboration are taken as three core mechanisms of iVCE trustworthy assurance.     

Optimal stopping of multi-project software testing in the context of software cybernetics

Software cybernetics explores the interplay between control theory/engineering and software theory/engineering. The controlled Markov chains (CMC) approach to software testing follows the idea of software cybernetics and treats software testing as a control problem. The software under test serves as a controlled object and the software testing strategy serves as the corresponding controller. The software under test and the software testing strategy make up a closed-loop feedback control system, and the theory of controlled Markov chains can be used to design and optimize software testing strategies in accordance with testing/reliability goals given a priori. In this paper we apply the CMC approach to the optimal stopping problem of multi-project software testing. The problem under consideration assumes that a single stopping action can stop testing of all the software systems under test simultaneously. The theoretical results presented in this paper describe how to test multiple software systems and whe     

Empowering the users? A critical textual analysis of the role of users in open source software development

This paper outlines a critical, textual approach for the analysis of the relationship between different actors in information technology (IT) production, and further concretizes the approach in the analysis of the role of users in the open source software (OSS) development literature. Central concepts of the approach are outlined. The role of users is conceptualized as reader involvement aiming to contribute to the configuration of the reader (to how users and the parameters for their work practices are defined in OSS texts). Afterwards, OSS literature addressing reader involvement is critically reviewed. In OSS context, the OSS writers as readers configure the reader and other readers are assumed to be capable of and interested in commenting the texts. A lack of OSS research on non-technical reader involvement is identified. Furthermore, not only are the OSS readers configured, but so are OSS writers. In OSS context while writers may be empowered, this clearly does not apply to the non-technical OSS readers. Implication for research and practice are discussed.

---

Investigating Knowledge Management practices in software development organisations – An Australian experience

This study, using both quantitative and qualitative methods, investigates current practice of Knowledge Management (KM) in Software Engineering (SE) processes in two Australian companies on the basis that they both claimed to apply KM practices in their software development work. It also describes the KM activities and KM process used in SE practice, and examines the enablers of KM process for SE in terms of leadership, technology, culture, process and measurement.One of the main findings showed that software developers believe in the usefulness of knowledge sharing; however, their ability to utilise some of the KM systems was limited. The most commonly used systems included personal networks, informal networks, groupware and third-party knowledge. There is a need to formalise knowledge sharing of practices, while also supporting informal and ad-hoc knowledge sharing. While KM was considered to be important, the tools, techniques and methodologies currently employed for software development were inadequate to address effective management of knowledge in these organisations. In both organisations, a uniform model of the KM process did not exist. Among the four KM enablers, leadership was considered to be the most significant as top-down KM strategies were seemingly being pursued by management. Technology was also considered to be an obvious mechanism for KM, despite some of their current KM systems either being unsuitable or inaccessible. In addition, the crucial role that personal networks played in accessing tacit and implicit knowledge was seen as a key reason to foster a culture that encourages participants to share their knowledge with others.     

software软件

删除开机“一键恢复系统”,输入法状态条不能自动移动,清除WinRAR历史记录,重新注册DLL文件,“发送到”菜单问题,     

software软件

双系统下显示器分辨率有差异 Q我电脑中安装的是Windows XP和Windows 2003的双系统,现在在Windows XP系统下设置好桌面分辨率显示是正常的,但是切换到Windows 2003后却又显示异常,每次都需要再次设置。请问这是什么原因？     

software软件

快速访问已免疫的目录；备份Word工具栏设置；DownloadRAR无法设置保存位置；成功删除Norton杀毒软件；如何去除PDF中的水印；提取Flash中的声音。     

软件software

如何卸载输入法程序,文档片断无法删除，将全屏游戏以窗口方式运行，扫描的小说如何编辑，WPS图片无法正常浏览，彻底删除诺顿软件，为何显示微软拼音输入法。     

Coopetitive relationships in cross-functional software development teams: How to model and measure?

Understanding simultaneous cooperative and competitive (coopetitive) dynamics in cross-functional software development teams is fundamental to the success of software development process. The recent coopetition research is, however, hampered by a lack of conceptual focus, and the corresponding inconsistent treatment of the constructs associated with cross-functional coopetitive relationships. This study conceptualizes and operationalizes the multi-dimensional construct of cross-functional coopetition, and then presents an instrument for measuring this construct. Cross-functional coopetition is conceptualized with 5 distinct and independent constructs; 3 of them are related to cross-functional cooperation, and 2 are associated with cross-functional competition. The data collected from 115 software development project managers in Australia confirms the applicability of the constructs and their measures. This study contributes to the extant literature by providing a consensus on the conceptualization of cross-functional coopetitive behaviors, particularly in multi-party software development teams. The conceptual basis for cross-functional coopetition and its instrument will aid researchers and project managers interested in understanding coopetition in cross-functional collaborative contexts. Research and practical implications are discussed.     

Acceptance of software process innovations – the case of extreme programming

Extreme programming (XP), arguably the most popular agile development methodology, is increasingly finding favor among software developers. Its adoption and acceptance require significant changes in work habits inculcated by traditional approaches that emphasize planning, prediction, and control. Given the growing interest in XP, it is surprising that there is a paucity of research articles that examine the factors that facilitate or hinder its adoption and eventual acceptance. This study aims to fill this void. Using a case study approach, we provide insights into individual, team, technological, task, and environmental factors that expedite or impede the organization-wide acceptance of XP. In particular, we study widely differing patterns of adherence to XP practices within an organization, and tease out the various issues and challenges posed by the adoption of XP. Based on our findings, we evolve factors and discuss their implications on the acceptance of XP practices.