scholarly journals Source Code Comprehension and Appropriation by Novice Programmers: Understanding Novice Programmers’ Perception about Source Code Reuse

2019 ◽  
Vol 10 ◽  
pp. 96
Author(s):  
Luana  Müller ◽  
Milene  Selbach Silveira ◽  
Clarisse  S. de Souza

Software development practices rely extensively on reusing source code written by other programmers. One of the recurring questions about such practice is how much programmers, acting as users of somebody else’s code, really understand the source code that they inject it in their programs. The question is even more important for novices, who are trying to learn what programming is and how it should be practiced on a larger scale. In this paper we present the results of an ongoing research using a semiotic approach to investigate how novice programmers reuse source code, and how, through messages inscribed in the source code of the programs they write or reuse, they communicate, implicitly or explicitly, what such source code "means" to them and others. We carried out three studies with novice programmers, and results suggest that source code reuse may impact what programmers take their source code to mean.

2015 ◽  
Vol 101 ◽  
pp. 124-135 ◽  
Author(s):  
Tero Päivärinta ◽  
Kari Smolander

2012 ◽  
Vol 263-266 ◽  
pp. 1961-1968
Author(s):  
Yong Chao Song ◽  
Bu Dan Wu ◽  
Jun Liang Chen

According to the feature of the JBPM workflow system development, the target code generated is determined by analyzing the process of JBPM workflow development and the architecture of J2EE. The code generation tool generates code by parsing the static form source code and loading the code generation template. The code generation tool greatly shortens the JBPM workflow system development cycle and reduces the cost of software development which has the good practicality and scalability.


2016 ◽  
Vol 24 (3) ◽  
pp. 45-70 ◽  
Author(s):  
Delroy Chevers ◽  
Annette M. Mills ◽  
Evan Duggan ◽  
Stanford Moore

For software development firms to be competitive they must assure the quality of the software product. This has led many firms to adopt software process improvement (SPI) programs such as the capability maturity model integration (CMMI). However, for small software firms, especially those in developing countries with limited resources, these programs are often too cumbersome and costly to implement. To address this issue, this paper proposes a simplified SPI model for small firms (SPM-S) comprised of 10 key software development practices; with fewer practices, the proposed model should be more accessible and less costly to implement. Using data collected in four developing countries in the English-speaking Caribbean from 112 developer/user dyads, the model is evaluated with respect to its impact on software quality. The findings show that the software development process coupled with supporting technology (e.g. project management tools) significantly impact software product quality. Implications for software process improvement in small firms and future research are discussed.


Author(s):  
Jorge Melegati ◽  
Rafael Chanin ◽  
Afonso Sales ◽  
Rafael Prikladnicki

Abstract In this position paper, our goal is to argue the need for specific software development practices to early-stage startups. In order to reach this goal, we discuss the consequences of innovative and market-driven contexts, which are two of the key elements when describing software startups. We also argue that these practices could be applied to innovative initiatives within established companies since they share similar characteristics and challenges as those from startups.


Sign in / Sign up

Export Citation Format

Share Document