Incorporating Agile with MDA Case Study: Online Polling System

Nowadays agile software development is used in greater extend but for small organizations only, whereas MDA is suitable for large organizations but yet not standardized. In this paper the pros and cons of Model Driven Architecture (MDA) and Extreme programming have been discussed. As both of them have some limitations and cannot be used in both large scale and small scale organizations a new architecture has been proposed. In this model it is tried to opt the advantages and important values to overcome the limitations of both the software development procedures. In support to the proposed architecture the implementation of it on Online Polling System has been discussed and all the phases of software development have been explained.Comment: 14 pages,1 Figure,1 Tabl

A discovery and analysis of influencing factors of pair programming

The exploration into the underlying psychosocial links of pair programming. a new and unorthodox programming paradigm in which two programmers share one keyboard and monitor during real-time programming sessions, is undertaken. These complex psychosocial relationships, along with cognitive process exchanges, ultimately mold the programming output as well as determine the level of communication, satisfaction. confidence and compatibility. Laying the framework for this research, a through review of traditional and contemporary paradigms with a special focus on their limitations and a list of current software development problems are presented. Next, a detailed summary of pair programming and related agile software paradigms, such as extreme programming, which lists pair programming as one of its twelve principles, is given. From earlier pair programming studies, a number of programming benefits have been unveiled and these are listed and discussed. However, a lack of formal studies pertaining to the psychosocial aspects of pair programming exists. Given this void, a field survey is administered to a group of professional programmers and a resulting list of influencing factors on pair programming emerges. From the list, the most popular factor, personality, and two other factors, communication and gender, have been selected in order to study their impact on pair programming product outcome and the level of communication, satisfaction, confidence and compatibility. An experiment focusing on these factors is designed and implemented. From the experimental findings, the personality of the two partners in pair programming is found to have a significant impact on the pair programming output. Also, it is discovered that same gender pairs exhibited an unusually high level of communication, satisfaction and compatibility between each other, especially among female-female pairs. A detailed statistical experiment result based on research hypotheses is reported

Attributes Contributing to Students’ Use of Quality Software Development Practices

In 2001 the “McCracken group”, through a multi-institutional study, concluded that many students finishing their introductory programming courses could not program due to a lack of problem solving skills. In 2004 Lister established that students have a fragile grasp of skills to read and interpret code. Humphrey suggests that educators must shift their focus from the programs that the students create to the data of the processes the students use. This paper addresses the problem of poor performing students through an investigation of their quality appraisal techniques (QATs) and development processes. Firstly, a survey was conducted to determine the current software development practices used by a group of undergraduate Computer Science students. Numeric data collected revealed that the current practices used by the majority of students would not be sufficient to produce quality programs. Secondly, a case study was conducted to gain a deeper understanding of the various factors that are likely to influence students’ intention to use QATs. Analysis of numeric data collected through a survey revealed that students’ intentions to use QATs are driven by ease of use, compatibility, usefulness, result demonstrability, subjective norm and career consequences. Thirdly, an experiment was conducted to determine students’ perceptions on the use of process measurement data to improve their current software development practices. Analysis of numeric and narrative data revealed that performance measurement data could provide students with useful information to adopt proper development practices

Eşli Programlamanın Ortaokul Öğrencilerinin Bilgisayar Programlama Özgüven ve Başarısına Etkisi

DergiPark: 575098tredBu araştırmada iç içegeçmiş durum çalışması yapılarak eşli programlamanın ortaokul öğrencilerininbilgisayar programlama özgüven ve başarısına etkisi araştırılmıştır.  Beşinci sınıf seviyesinde 35 öğrenci bireysel(n=13) ve eşli (n=22) programlama gruplarına ayrılmış, Scratch programlamaetkinlikleri kullanılarak sekiz haftalık bir uygulama yürütülmüştür.Araştırmada nitel veri görüşmelerle, nicel veri ise özgüven anketi verubriklerle toplanmıştır. Veri analizi için bağımsız örneklemler t testi ve içerik analizikullanılmıştır. Uygulama sonunda eşli programlama öğrencilerinin özgüven vebaşarısının, bireysel programlama öğrencilerinden daha yüksek olduğubulunmuştur. Bu çalışma, ortaokul seviyesinde bilgisayar programlama özgüvenive başarısını artırmak için eşli programlama yönteminin kullanımınıdesteklemekte, özellikle bilgisayar sayısı yetersiz olan okullara, rekabetçiöğrencilere ve programlamayı yeni öğrenenlere bu yöntemi önermektedir.The purpose ofthis embedded case study is to explore the possible influence of pairprogramming on secondary school students’ confidence and achievement incomputer programming. A total of 35 students in a fifth-grade class weredivided into individual (n=13) andpair programmers (n=22), who then usedScratch programming activities during an eight week implementation. Qualitativedata were collected with interviews and quantitative data were collected with aconfidence questionnaire and rubrics. Content analysis and independent-samples t tests were conducted for dataanalysis. The results showed that pair programmers’ confidence and achievementfor computer programming was higher compared to individual programmers afterthe implementation. The study supports the use of pair programming in secondaryschools, especially where there are limited numbers of computers, competitivestudents, and novice programmers to increase the confidence and achievement incomputer programming

Enhancing Collaborative Learning Using Pair Programming: Who Benefits?

Incoming university students who have not previously studied computer programming often find it a challenging subject, leading to high failure rates. Research has suggested that the lack of a formalised structure for collaborative learning may be one of the factors responsible for students’ negative impressions of computer science. In this study we investigated whether the use of pair programming in practical laboratories would facilitate peer learning and enhance students’ confidence in their programming ability. Results showed that this intervention was generally well received, although the weaker programmers (as measured by prior exam grades) perceived it to be of more benefit than the stronger ones. Students who reported a lower initial level of enjoyment and confidence in programming were more likely to report learning from the paired intervention, though this did not necessarily lead to enhanced performance. The most frequently reported positive feature of pair programming was that it allowed students to meet more people in the class. Although there was no significant increase in final exam grades for male students, there was a significant increase for female students, suggesting this teaching strategy may have asymmetrical gender benefits

The long and winding road : accidents and tinkering in software standardization

Software is based on universal principles but not its development. Relating software to hardware is never automatic or easy. Attempts to optimize software production and drastically reduce their costs (like in hardware) have been very restricted. Instead, highly-skilled and experienced individuals are ultimately responsible for project success. The long and convoluted path towards useful and reliable software is often plagued by idiosyncratic accidents and emergent complexity. It was expected that software standardisation would remove these sources of unwanted diversity by aiming at controllable development processes, universal programming languages, and toolkits of reusable software components. However, limited adoption of development standards suggests that we still do not understand why software is so difficult to produce. Software standardisation has been limited by our poor understanding of humans? role at the origin of technological diversity

Understanding the impact of strategic team formation in early programming education

This evidence based research looks at the impact of a team-based instruction on learning to program in a first year engineering course designed under the Bauhaus studio model. Each team is formulated with a “more knowledgeable other” [1], or for this paper the “ringer” based on selfreported prior learning. The ringer is intended to support the team through early programming challenges. In addition to the professor and teaching assistants, having a peer mentor can yield higher satisfaction and confidence in learners [2]. Our analysis evaluates learning outcomes as student progress through the term, comparing performance based on the performance and prior knowledge reported by the ringer. The major research questions investigate the role of the ringer in the success of the team, as well looking to see if teams that include a low performing student have any common characteristics. Findings include data from 2013, 2014, and 2015 with trends apparent in each of the years across major topics. This study shows that the formulation of teams around a carefully selected more knowledgeable other can improve the learning of the entire team. In general, ringer score correlates to an increase in the rest of the team’s average. The ringer score only supports learning to a certain degree where if the gap in score is too larger compared to the rest of the team, lower performing members can suffer. In general the formation of teams using prior programming experience seems to do no harm and even possibly improve learning outcomes, and the data may also suggest additional improvements on the use of teams

Experiences in Teaching eXtreme Programming in a Distance Learning Program

As university-level distance learning programs become more and more popular, and software engineering courses incorporate eXtreme Programming (XP) into their curricula, certain challenges arise when teaching XP to students who are not physically co-located. In this paper, we present our experiences and observations from managing such an online software engineering course, and describe some of the specific challenges we faced, such as students' aversion to using XP and difficulties in scheduling. We also present some suggestions to other educators who may face similar situations

The LaTeX project: A case study of open-source software

This is a case study of TeX, a typesetting software that was developed by Donald E. Knuth in the late 70's. Released with an open source license, it has become a reference in scientific publishing. TeX is now used to typeset and publish much of the world's scientific literature in physics and mathematics. This case study is part of a wider effort by academics to understand the open-source phenomenon. That development model is similar to the organization of the production of knowledge in academia; there is no set organization with a hierarchy, but free collaboration that is coordinated spontaneously and winds up generating complex products that are the property of all who can understand its functioning. The case study was led by gathering qualitative data via interviews with TeX developers and quantitative data on the TeX community -- the program's code, the software that is part of the TeX distribution, the newsgroups dedicated to the software, and many other indicators of the evolution and activity in that open-source project. The case study is aimed at economists who want to develop models to understand and analyze the open-source phenomenon. It is also geared towards policy-makers who would like to encourage or regulate open- source, and towards open-source developers who wonder what are the efficient strategies to make an open-source project successful.TeX, LaTeX, case study, open source, software, innovation, organisational structure, economic history, knowledge production, knowledge diffusion.