Affiliation:
1. Queen's University Belfast, Northern Ireland, UK
2. Independent Researcher, Izmir, Turkey
3. Bilkent University, Ankara, Turkey
Abstract
Context:
Knowledge level and productivity of the software engineering (SE) workforce are the subject of regular discussions among practitioners, educators, and researchers. There have been many efforts to measure and improve the knowledge gap between SE education and industrial needs.
Objective:
Although the existing efforts for aligning SE education and industrial needs have provided valuable insights, there is a need for analyzing the SE topics in a more “fine-grained” manner; i.e., knowing that SE university graduates should know more about requirements engineering is important, but it is more valuable to know the exact topics of requirements engineering that are most important in the industry.
Method:
We achieve the above objective by assessing the knowledge gaps of software engineers by designing and executing an opinion survey on levels of knowledge learned in universities versus skills needed in industry. We designed the survey by using the SE knowledge areas (KAs) from the latest version of the Software Engineering Body of Knowledge (SWEBOK v3), which classifies the SE knowledge into 12 KAs, which are themselves broken down into 67 subareas (sub-KAs) in total. Our analysis is based on (opinion) data gathered from 129 practitioners, who are mostly based in Turkey.
Results:
Based on our findings, we recommend that educators should include more materials on software maintenance, software configuration management, and testing in their SE curriculum. Based on the literature as well as the current trends in industry, we provide actionable suggestions to improve SE curriculum to decrease the knowledge gap.
Publisher
Association for Computing Machinery (ACM)
Subject
Education,General Computer Science
Reference69 articles.
1. Priorities for the education and training of software engineers
2. Skills for success at different stages of an IT professional's career
3. Why is software late? An empirical study of reasons for delay in software development
4. S. McConnell. 2010. What does 10x mean? Measuring variations in programmer productivity. In Making Software: What Really Works and Why We Believe It A. Oram and G. Wilson Eds. O'Reilly Media. S. McConnell. 2010. What does 10x mean? Measuring variations in programmer productivity. In Making Software: What Really Works and Why We Believe It A. Oram and G. Wilson Eds. O'Reilly Media.
Cited by
18 articles.
订阅此论文施引文献
订阅此论文施引文献,注册后可以免费订阅5篇论文的施引文献,订阅后可以查看论文全部施引文献