结对编程在软件工程专业实践课程改革中的探索

针对传统实践方式周期长、难度大、难以培养团队精神的弊端,提出在软件工程专业实践课程中引入结对编程模式。并选择多组学生结对编程完成同一项目,进行了对比试验。对比试验结果表明结对编程模式能有效提高学生的软件工程思想和质量意识,促进团队合作意识,参与学员的学习能力和沟通能力得到较大的提高。     

基于关联理论视角的结对编程及学习模式

针对计算机和软件工程专业学生在结对编程实践中的结对效率问题,运用关联理论分析结对交流模式和关键环节,提出结对交流过程中的干预策略和监督机制的实现模型,阐述监督机制中的监督指标、干预条件和事后分析。     

基于CDIO的面向对象软件工程实践教学模式研究

针对软件工程实践教学存在的学生动手能力不强、团队协作意识差等问题,从构思、设计、实施和运维这一横向维度以及目标、内容、培养过程和时间基线这一纵向维度出发,提出基于CDIO的面向对象软件工程实践教学模式,阐述在该模式指导下开展的面向对象软件工程实践教学活动和实际效果。     

浅析软件工程专业实践教学改革模式

针对当前软件工程实践教学中存在的问题,为了提高学生运用软件工程知识的能力以及创新意识,对实践教学的改革进行一些探索.     

极限编程中结对编程的不良现象分析及对策

结对编程是极限编程的特色实践之一。在极限编程活动中,对于中国学生,结对编程是组织难度最大的活动。为了更有效地组织结对编程,文章分析以往团队成员所出现的一些不良现象,并探讨可行对策,为大学软件实践教学和软件业者从事极限编程提供参考和指导。     

编程训练与课程学习的相互渗透

为了提高学生的编程能力,本文对C++、数据结构、离散数学、数值分析、软件工程等课程统筹考虑,将其教学过程整合为编程能力训练的综合平台,使课程教学与编程训练紧密结合,既提高教学效果,又提高学生的编程能力。     

结对编程的研究与扩展

讨论了极限编程理论重要的“结对编程”实践在国内推广中遇到的问题,根据对实际软件开发过程的观察和调查,从企业管理的角度说明“结对编程”可以节省时间、提高效率和质量。对“结对编程”实践的形式进行了扩展,提出了“轮转结对”、“多人极对”、“极限结对”等新的实践形式,用来自中国的实践对“结对编程”的实践进行了丰富。     

跨越软件工程教学到实践的鸿沟

介绍目前软件工程教学普遍存在的与实践相脱节现象,分析软件工程教学的现实困难,提出要以"学以致用"为原则,优化课程体系设计,合理衔接基础课程、综合性课程、技能课程。阐述以社会需求为导向,设置实践教学内容,加强师资教材建设,校企合作,提炼经典规范案例;采用团队分组与固定结对搭档相结合的组织方式,实行组内、组间两级全员评审的考核模式,促进学生在思考中学习提高。     

软件工程专业“3＋1”培养模式探究

当前软件工程专业传统培养模式存在一定的弊端,其培养的毕业生重理论轻实践,以致出现高校就业难和企业人才难的两难局面。软件工程专业＂3＋1＂培养模式针对该弊端提出特有的教学培养方案,从而保证了学生在学习完成理论知识后,能够及时的转化为实践能力。该模式通过工学结合、校企合作的理论教学方法和实践教学方法培养了学生的实践能力和创新能力,使得学生具有较强的软件设计、实现能力,团队合作能力等专业素养,进而提高了该专业毕业生的市场竞争力。     

软件工程专业“3+1”培养模式探究

当前软件工程专业传统培养模式存在一定的弊端,其培养的毕业生重理论轻实践,以致出现高校就业难和企业人才难的两难局面。软件工程专业"3+1"培养模式针对该弊端提出特有的教学培养方案,从而保证了学生在学习完成理论知识后,能够及时的转化为实践能力。该模式通过工学结合、校企合作的理论教学方法和实践教学方法培养了学生的实践能力和创新能力,使得学生具有较强的软件设计、实现能力,团队合作能力等专业素养,进而提高了该专业毕业生的市场竞争力。     

基于LabVIEW的数字滤波器示教软件设计

针对数字滤波器内容抽象、理论性强、不易掌握等问题,开发了基于LabVIEW的数字滤波器示教软件。对该软件的编程方法进行详细阐述,并利用其对含噪语音进行了处理,对处理结果进行了分析。实践表明,利用LabVIEW编写数字信号处理示教软件具有简单明了、易于上手的特点,将其应用于教学中可明显增强学生的学习兴趣、明确学习目的、提高感性认识、强化理论学习效果,对培养学员的实践意识和实践能力具有重要意义。     

小团队结对编程实践研究和重构

结对编程是两个软件开发者在一台电脑前一起工作的一种编程实践,是极限编程方法的基础。对于软件产品的开发,人的知识是项目成功的重要因素。在组织的软件过程改进中,合适地引入结对编程,有利于知识的共享并营造团队合作的氛围,进而改善产品质量和缩短完成时间。不同规模的组织采用的软件过程的不同,对结对编程的引入会有不同的影响,所以在实践中结对编程的重构是必需的。基于小型组织和敏捷过程的项目实践,给出了一个切合实际的结对编程重构方案,进而提高小团队的生产效率。     

中职生程序设计能力的培养与探究

程序设计语言课程在计算机学科中占有重要地位,但对中职生来说,它是一门较难学习的科目,该文就中职生的程序设计能力的培养提出了一些见解和做法,以就业为导向,要求教师要从更新教学理念入手,引入做中学,做中教的教学理念,改进教学方法和教学评价模式,深入探究中职生程序设计能力培养的可行性,通过各种学习渠道挖掘学生编写程序设计能力和天赋,培养和提高学生的程序设计能力。     

Forty years of research on personality in software engineering: A mapping study

In this article, we present a systematic mapping study of research on personality in software engineering. The goal is to plot the landscape of current published empirical and theoretical studies that deal with the role of personality in software engineering. We applied the systematic review method to search and select published articles, and to extract and synthesize data from the selected articles that reported studies about personality. Our search retrieved more than 19,000 articles, from which we selected 90 articles published between 1970 and 2010. Nearly 72% of the studies were published after 2002 and 83% of the studies reported empirical research findings. Data extracted from the 90 studies showed that education and pair programming were the most recurring research topics, and that MBTI was the most used test. Research related to pair programming, education, team effectiveness, software process allocation, software engineer personality characteristics, and individual performance concentrated over 88% of the studies, while team process, behavior and preferences, and leadership performance were the topics with the smallest number of studies. We conclude that the number of articles has grown in the last few years, but contradictory evidence was found that might have been caused by differences in context, research method, and versions of the tests used in the studies. While this raises a warning for practitioners that wish to use personality tests in practice, it shows several opportunities for the research community to improve and extend findings in this field.     

Controlled experimentation on adaptations of pair programming

The use of agile methods is growing in industrial practice due to the documented benefits of increased software quality, shared programmer expertise, and user satisfaction. These methods include pair programming (two programmers working side-by-side producing the code) and test-driven approaches (test cases written first to prepare for coding). In practice, software development organizations adapt agile methods to their environment. The purpose of this research is to understand better the impacts of adapting these methods. We perform a set of controlled experiments to investigate how adaptations, or variations, to the pair programming method impact programming performance and user satisfaction. We find that method variations do influence programming results. In particular, better performance and satisfaction outcomes are achieved when the pair programming is performed in face-to-face versus virtual settings, in combination with the test-driven approach, and with more experienced programmers. We also find that limiting the extent of collaboration can be effective, especially when programmers are more experienced. These experimental results provide a rigorous foundation for deciding how to adapt pair programming methods into specific project contexts.     

结对编程成本与收益之探

结对编程(Pair Programming)是极限编程(Extreme Programming)的十二个实践之一，是团队设计的基础。它是指两个开发人员共用一台计算机，其中一个人负责具体细节，另一个人关注整体，并且这两人的角色可以随时交换。本文通过一个项目的运作过程的试验实例，分析结对编程的成本和收益。结对编程的优势在于：改进设计质量、减少程序缺陷、降低人员风险、提高技术技能和团队合作精神。为中小型企业软件过程改进提供了具有相当经济意义的方案，推动企业生产力、企业文化改进。     

Exploring the underlying aspects of pair programming: The impact of personality

With the recent advent of agile software process methods, a number of seldom used and unorthodox practices have come to the forefront in the field of computer programming. One such practice is that of pair programming, which is characterized by two programmers sharing the same computer for collaborative programming purposes. The very nature of pair programming implies a psychological and social interaction between the participating programmers and thus brings into play a unique element that we do not see with the conventional individual programming model. This paper focuses on the effects that one of these psychosocial factors, a programmer’s personality type, may have on the pair programming environment. In this study, a group of university students, 68 undergraduate students and 60 master’s degree graduate students, each of whom had been personality type profiled using the Myers–Briggs Type Indicator (MBTI) model, was split into three sub-groups. One group consisted of subjects who were alike in MBTI type. Another group consisted of subjects who were opposite to each other in MBTI type, and the last group was comprised of subjects who were diverse – partially alike and partially opposite – in MBTI type. Through two pair programming sessions, the pairs in each group were assessed for their output, in code productivity. The result showed that the sub-group of subjects who were diverse in MBTI type exhibited higher productivity than both alike and opposite groups. In a comparison between alike and opposite groups, the productivity of the opposite group was greater than that of the alike group.     

Pair programming and the mysterious role of the navigator

Computer programming is generally understood to be highly challenging and since its inception a wide range of approaches, tools and methodologies have been developed to assist in managing its complexity. Relatively recently the potential benefits of collaborative software development have been formalised in the practice of pair programming. Here we attempt to ‘unpick’ the pair programming process through the analysis of verbalisations from a number of commercial studies. We focus particularly on the roles of the two programmers and what their key characteristics and behaviours might be. In particular, we dispute two existing claims: (i) that the programmer who is not currently typing in code (“the navigator”) is constantly reviewing what is typed and highlighting any errors (i.e. acting as a reviewer) and (ii) that the navigator focuses on a different level of abstraction as a way of ensuring coverage at all necessary levels (i.e. acting as a foreman). We provide an alternative model for these roles (“the tag team”) in which the driver and navigator play much more equal roles. We also suggest that a key factor in the success of pair programming may be the associated increase in talk at an intermediate level of abstraction.     

Cooperation,collaboration and pair-programming: Field studies on backup behavior

Considering that pair programming has been extensively studied for more than a decade, it can seem quite surprising that there is such a lack of consensus on both its best use and its benefits. We argue that pair programming is not a replacement of usual developer interactions, but rather a formalization and enhancement of naturally occurring interactions. Consequently, we study and classify a broader range of developer interactions, evaluating them for type, purpose and patterns of occurrence, with the aim to identify situations in which pair programming is likely to be truly needed and thus most beneficial. We study the concrete pair programming practices in both academic and industrial settings. All interactions between teammates were recorded as backup behavior activities. In each of these two projects, developers were free to interact when needed. All team interactions were self-recorded by the teammates. The analysis of the interaction tokens shows two salient features: solo work is an important component of teamwork and team interactions have two main purposes, namely cooperation and collaboration. Cooperative backup behavior occurs when a developer provides help to a teammate. Collaborative backup behavior occurs when the teammates are sharing the same goal toward solving an issue. We found that collaborative backup behavior, which occurred much less often, is close to the formal definition of pair programming. This study suggests that mandatory pair programming may be less efficient in organizations where solo work could be done and when some interactions are for cooperative activities. Based on these results, we discussed the potential implications concerning the best use of pair programming in practice, a more effective evaluation of its use, its potential benefits and emerging directions of future research.     

A comparative analysis of different gender pair combinations in pair programming

Over the last decade, there has been a steady stream of pair programming studies. However, one significant area of pair programming that has not received its due attention is gender. Considering the fact that pair programming is one of the major human-centric software development paradigms, this is a gap that needs to be addressed. This empirical study conducted quantitative and qualitative analyses of different gender pair combinations within pair programming context. Using a pool of university programming course students as the experiment participants, the study examined three gender pair types: female–female, female–male, and male–male. The result revealed that there was no significant gender difference in the pair programming coding output. But there were significant differences in the levels of pair compatibility and communication between the same gender pair type: female–female and male–male, and the mixed gender pair type, female–male. The post-experiment comments provide additional insights and details about gender in pair interactions.