Understanding what industry wants from requirements engineers: an exploration of RE jobs in Canada

[Background] Prior research on the professional occupation of Requirements Engineering (RE) in Europe and Latin America indicated incongruities between RE practice as perceived by industry and as in textbooks, and conducted detailed analysis of both RE and non-RE job aspects. Relatively little is published on the RE competencies and skills industry expects, and seldom investigated the application domains calling for RE professionals. [Aims] We felt motivated by those findings to carry out research on RE job posts in a North-American market. Especially, we focused solely on RE-specific tasks, competencies and skills, from the perspective of defined position categories. Plus, we intend to explore the application domains in need for RE professionals to reveal the wide range of RE roles in industry. [Methods] Coding process, analysis, and synthesis were applied to the textual descriptions of the 190 RE job ads from Canada's most popular online job search site, especially to the text referring to tasks and competencies. [Results] We contribute to the empirical analysis of RE jobs, by providing insights from Canada's IT market in 2017. Using 109 RE job ads from the most popular IT job search portal T-Net, we identified the qualifications, experience and skills demanded by Canadian employers. Furthermore, we explored the distribution of those RE tasks and competences over the 11 categories of RE roles. [Conclusions] Our results suggest that the majority of the employers were big to very big companies in 29 business domains, and the most in-demand RE skills for them were related to RE methods and to project management aspects affecting requirements. In addition, employers placed much more emphasis on experience - both RE-specific and broad software engineering experience, than on higher education.

[1]  Alain Abran,et al.  The Guide to the Software Engineering Body of Knowledge , 1999, IEEE Softw..

[2]  Ban Al-Ani,et al.  So, You Think You Are a Requirements Engineer? , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).

[3]  A Straw,et al.  Guide to the Software Engineering Body of Knowledge , 1998 .

[4]  Carl K. Chang,et al.  Bluepring for the Ideal Requirements Engineer , 1996, IEEE Software.

[5]  Daniel M. Berry,et al.  The importance of ignorance in requirements engineering , 1995, J. Syst. Softw..

[6]  Lynette Kvasny,et al.  Changing patterns in IT skill sets 1988-2003: a content analysis of classified advertising , 2004, DATB.

[7]  Isabel Sofia Brito,et al.  Software Requirements Analyst Profile: A Descriptive Study of Brazil and Mexico , 2017, 2017 IEEE 25th International Requirements Engineering Conference (RE).

[8]  Suzanne D. Pawlowski,et al.  Building theory about IT professionals: is a taxonomy or typology the answer? , 2005, SIGMIS CPR '05.

[9]  Soren Lauesen,et al.  Software Requirements: Styles & Techniques , 2002 .

[10]  Barbara Kitchenham,et al.  Procedures for Performing Systematic Reviews , 2004 .

[11]  Richard E. Fairley,et al.  Guide to the Software Engineering Body of Knowledge (SWEBOK(R)): Version 3.0 , 2014 .

[12]  Birgit Penzenstadler,et al.  Soft Skills REquired: A Practical Approach for Empowering Soft Skills in the Engineering World , 1899, 2009 Collaboration and Intercultural Issues on Requirements: Communication, Understanding and Softskills.

[13]  Johnny Saldaña,et al.  The Coding Manual for Qualitative Researchers , 2009 .

[14]  Barbara Paech What Is a Requirements Engineer? , 2008, IEEE Software.

[15]  Jan Marco Leimeister,et al.  Towards a competency model for requirements analysts , 2012, Inf. Syst. J..

[16]  S. Lauesen Software Requirements Styles and Techniques , 2001 .

[17]  Sami Surakka,et al.  Analysis of Technical Skills in Job Advertisements Targeted at Software Developers , 2005, Informatics Educ..

[18]  Andrea Herrmann,et al.  Requirements Engineering in Practice: There Is No Requirements Engineer Position , 2013, REFSQ.

[19]  W. Duncan A GUIDE TO THE PROJECT MANAGEMENT BODY OF KNOWLEDGE , 1996 .

[20]  Colin J. Neill,et al.  State of practice in requirements engineering: contemporary data , 2014, Innovations in Systems and Software Engineering.

[21]  Phillip A. Laplante,et al.  Requirements Engineering for Software and Systems , 2009 .

[22]  Anat Rafaeli,et al.  Employment Ads , 1998 .

[23]  Chong Wang,et al.  What the Job Market Wants from Requirements Engineers? An Empirical Analysis of Online Job Ads from the Netherlands , 2017, 2017 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM).

[24]  KrcmarHelmut,et al.  Towards a competency model for requirements analysts , 2012 .

[25]  Mikio Suzuki,et al.  A Model and Architecture of REBOK (Requirements Engineering Body of Knowledge) and Its Evaluation , 2010, 2010 Asia Pacific Software Engineering Conference.

[26]  Narasimhaiah Gorla,et al.  Who should work with whom?: building effective software project teams , 2004, CACM.

[27]  Christof Ebert Requirements Engineering: Management , 2010, Encyclopedia of Software Engineering.