The power of feedback.

It represents a universally applicable attitude and skill set everyone, not just computer scientists, would be eager to learn and use.

/pdf/computational-thinking-ji-suan-lun-de-si-kao-3qvv34ha3s.pdf

Computational Thinking 計算論的思考

App Store Analysis studies information about applications obtained from app stores. App stores provide a wealth of information derived from users that would not exist had the applications been distributed via previous software deployment methods. App Store Analysis combines this non-technical information with technical information to learn trends and behaviours within these forms of software repositories. Findings from App Store Analysis have a direct and actionable impact on the software teams that develop software for app stores, and have led to techniques for requirements engineering, release planning, software design, security and testing. This survey describes and compares the areas of research that have been explored thus far, drawing out common aspects, trends and directions future research should take to address open problems and challenges.

/pdf/a-survey-of-app-store-analysis-for-software-engineering-4mwd81w21w.pdf

A Survey of App Store Analysis for Software Engineering

Mind mapping is a thinking technique that nursing leaders can use to improve their decision-making and problem-solving abilities, and to better organise their ideas.

The mind map book.

Context: Ever since the emergence of agile methodologies in 2001, many software companies have shifted to Agile Software Development (ASD), and since then many studies have been conducted to investigate effort estimation within such context; however to date there is no single study that presents a detailed overview of the state of the art in effort estimation for ASD. Objectives: The aim of this study is to provide a detailed overview of the state of the art in the area of effort estimation in ASD. Method: To report the state of the art, we conducted a systematic literature review in accordance with the guidelines proposed in the evidence-based software engineering literature. Results: A total of 25 primary studies were selected; the main findings are: i) Subjective estimation techniques (e.g. expert judgment, planning poker, use case points estimation method) are the most frequently applied in an agile context; ii) Use case points and story points are the most frequently used size metrics respectively; iii) MMRE (Mean Magnitude of Relative Error) and MRE (Magnitude of Relative Error) are the most frequently used accuracy metrics; iv) team skills, prior experience and task size are cited as the three important cost drivers for effort estimation in ASD; and v) Extreme Programming (XP) and SCRUM are the only two agile methods that are identified in the primary studies. Conclusion: Subjective estimation techniques, e.g. expert judgment-based techniques, planning poker or the use case points method, are the one used the most in agile effort estimation studies. As for the size metrics, the ones that were used the most in the primary studies were story points and use case points. Several research gaps were identified, relating to the agile methods, size metrics and cost drivers, thus suggesting numerous possible avenues for future work.

/pdf/effort-estimation-in-agile-software-development-a-systematic-4d3vpnkfof.pdf

Effort estimation in agile software development: a systematic literature review

Failure prediction based on log files using Random Indexing and Support Vector Machines

Computational Thinking (CT) has been recognized as one of the fundamental skills that all graduates should acquire. For this reason, motivational concerns need to be addressed at an early age of a child, and reaching students who do not consider themselves candidates for science, technology, engineering, and mathematics disciplines is important as well if the broadest audience possible is to be engaged. This article describes a framework for teaching and assessing CT in the context of K-12 education. The framework is based on Agile software engineering methods, which rely on a set of principles and practices that can be mapped to the activities of CT. The article presents as well the results of an experiment applying this framework in two sixth-grade classes, with 42 participants in total. The results show that Agile software engineering methods are effective at teaching CT in middle schools, after the addition of some tasks to allow students to explore, project, and experience the potential product before using the software tools at hand. Moreover, according to the teachers’ feedback, the students reached all the educational objectives of the topics involved in the multidisciplinary activities. This result can be taken as an indicator that it is possible to use computing as a medium for teaching other subjects, besides computer science.

Teaching Computational Thinking Using Agile Software Engineering Methods: A Framework for Middle Schools

In the last decade, there has been increasing interest in pair programming (PP). However, despite the existing work, there is still a lack of substantial evidence of the effects of PP in industrial environments. To address this issue, we have analyzed the work of a team of 17 industrial developers for 14 months. The team is part of the IT department of a large Italian manufacturing company; it adopts a customized version of extreme programming (XP). We have investigated the effects of PP on software quality in five different scenarios. The results show that PP appears to provide a perceivable but small effect on the reduction of defects in these settings.

Pair Programming and Software Defects--A Large, Industrial Case Study

In this paper, we propose a method for predicting development effort based on user stories. Such approach is well suited for Agile software projects where requirements are developed along with the project and only sketched in a rough manner. We apply the proposed method to two industrial Agile software projects of very different size and structure. We show that such effort estimation works reasonably well if user stories are written in a structured way.

Predicting Development Effort from User Stories

In this paper we present a study on how Pair Programming (PP) facilitates the introduction of new developers (novices) in a team. Data has been collected non-invasively on how people paired in an industrial team of developers for 10 months; during such time novices joined the team. We focused on spontaneous PP, that is, on PP occurring when developers think it is most effective. Social network analysis techniques are used to analyze developers interactions and infer possible conclusions. It appears that initially PP is used to initiate novices, then it is drastically reduced to be resumed eventually when novices “feel” they have reached a significant level of maturity in the team. These phases are coherent with available works on group development and confirm existing findings on the importance of PP in the introduction of novices in teams, and, more generally, on team dynamics.

Ilenia Fronza

Papers

Failure prediction based on log files using Random Indexing and Support Vector Machines

Teaching Computational Thinking Using Agile Software Engineering Methods: A Framework for Middle Schools

Pair Programming and Software Defects--A Large, Industrial Case Study

Predicting Development Effort from User Stories

An interpretation of the results of the analysis of pair programming during novices integration in a team