Search

In June 2015 a group of experts in Software Process Improvement (SPI) and Education from all over the world gathered at the 1st International Workshop on Software Process Education, Training and Professionalism held in connection with 15th International Conference Software Process Improvement and Capability Determination. Discussions with key players in the relevant professional and personal certification fields, as well as experienced educators led to a consensus that it is time for the industry to rise to the new challenges and set out in a manifesto a common vision for educators and trainers together with a set of recommendations to address the challenges faced. At the workshop 14 “experts” from education and industry presented and discussed their “wisdom and experience” of the challenges faced for software process education, training and professionalism, especially with the background of the new modes of learning and teaching in higher education. Based on the presentations, 32 workshop participants brainstormed core values and principles specifically addressing the needs of software process education, training and professionalism. Via affinity analysis and group thinking exercises we identified an initial manifesto, consisting of 10 values and 4 principles. It is expected that this draft manifest will give expression to state-of-the-art knowledge on software process education, training and professionalism. It is based on hundreds of person-years of practice and experience from educators and industry professionals globally. Further work is currently being undertaken to extend and validate this draft manifesto with a view to publishing in its entirety by 2016.

peer-reviewed In work that is ongoing, the authors are examining the extent of software development process terminology drift. Initial findings suggest there is a degree of term confusion, with the mapping of concepts to terms lacking precision in some instances. Ontologies are concerned with identifying the concepts of relevance to a field of endeavour and mapping those concepts to terms such that term confusion is reduced. In this paper, we discuss how ontologies are developed. We also identify various sources of software process terminology. Our work to date indicates that the systematic development of a software development process ontology would be of benefit to the entire software development community. The development of such an ontology would in effect represent a systematic refactoring of the terminology and concepts produced over four decades of software process innovation.

The practice of software development has evolved considerably in recent decades, with new programming technologies, the affordability of hardware, pervasive internet access and mobile computing all contributing to the emergence of new software development processes. The newer process initiatives, which include those which are sometimes referred to as agile or lean methods, have brought with them new terms, which sometimes reflect the introduction of novel concepts. Other times, new terms correspond to long established concepts that have been repackaged. The net position is that we have a proliferation of language and term usage in the software development process domain, a problem which has implications for assessors and assessment frameworks, and for the broader community. In this paper, we explore this problem, finding that it is worthy of further research. Plus, we identify a technique suited to addressing this concern: the establishment of a canonical software process ontological model.