Systems architect and systems analyst: are these comparable roles?

The aim of this paper is to define the role of the 'systems architect' in the Irish telecommunications software sector and to compare it with Misic's definition of a 'systems analyst' in the information systems arena. The architect definition is based on in-depth interviews with practicing architects. The interview instrument is informed by social cognitive theory and the interviews were analyzed using the method of triples. The conclusion is that there are noticeable similarities between the roles, suggesting that the Irish telecommunications software sector can benefit from the computer personnel research carried out in the information systems field.

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

[2]  S. Fiske,et al.  Social Psychology , 2019, Encyclopedia of Personality and Individual Differences.

[3]  Gerald M. Weinberg,et al.  Egoless Programming (Excerpt from the Psychology of Computer Programming, Silver Anniversary Edition). , 1998 .

[4]  Approved December.  IEEE Recommended Practice for Software Acquisition , 1994 .

[5]  Gerald M. Weinberg,et al.  Psychology of computer programming , 1971 .

[6]  Sarah Kuhn.  The Software Design Studio: An Exploration , 1998, IEEE Softw..

[7]  David Lorge Parnas,et al.  Software Engineering Programs Are Not Computer Science Programs , 1999, IEEE Softw..

[8]  Gary W. Dickson,et al.  Problem solving for effective systems analysis: an experimental exploration , 1983, CACM.

[9]  Robert L. Baber.  Software reflected - the socially responsible programming of our computers , 1982 .

[10]  Jack Downey,et al.  An artifact-centric framework for software development skills , 2007, SIGMIS CPR '07.

[11]  Michael Quinn Patton,et al.  How to use qualitative methods in evaluation , 1987 .

[12]  Ian Graham.  The Compleat Requirements Analyste , 2003, IEEE Softw..

[13]  Dick Bowman,et al.  Principles of software engineering management , 1989, APLQ.

[14]  Eileen M. Trauth,et al.  Critical Skills and Knowledge Requirements of IS Professionals: A Joint Academic/Industry Investigation , 1995, MIS Q..

[15]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[16]  Gordon W. Allport,et al.  Pattern and growth in personality , 1961 .

[17]  R. Belbin.  Beyond the Team , 2000 .

[18]  A. Bandura.  Social Foundations of Thought and Action: A Social Cognitive Theory , 1985 .

[19]  Erich C. Dierdorff,et al.  CARELESSNESS AND DISCRIMINABILITY IN WORK ROLE REQUIREMENT JUDGMENTS: INFLUENCES OF ROLE AMBIGUITY AND COGNITIVE COMPLEXITY , 2007 .

[20]  Marilyn Wilkins,et al.  Critical Skills of IS Professionals: A Model for Curriculum Development , 2002, J. Inf. Technol. Educ..

[21]  David Bennett,et al.  Requisite IS management knowledge and skills construct: a survey , 1998, CPRS.

[22]  Glenford J. Myers,et al.  Art of Software Testing , 1979 .

[23]  E. Schein.  The Corporate Culture Survival Guide , 1999 .

[24]  Eileen M. Trauth,et al.  The IS Expectation Gap: Industry Expectations Versus Academic Preparation , 1993, MIS Q..

[25]  Indira R. Guzman,et al.  Who is "the IT workforce"?: challenges facing policy makers, educators, management, and research , 2005, SIGMIS CPR '05.

[26]  Jason Bennett Thatcher,et al.  The role of the work itself: an empirical examination of intrinsic motivation's influence on IT workers attitudes and intentions , 2002, SIGCPR '02.

[27]  Mark Norris,et al.  Software Engineering Explained , 1992 .

[28]  P ? ? ? ? ? ? ? % ? ? ? ? , 1991 .

[29]  Tom DeMarco.  Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency , 2001 .

[30]  Jo Ellen Moore,et al.  Personality characteristics of information systems professionals , 1991, SIGCPR '91.

[31]  Choong Kwon Lee,et al.  Transferability of skills over the IT career path , 2005, SIGMIS CPR '05.

[32]  Ieee Std,et al.  IEEE Guide Adoption of PMI Standard A Guide to the Project Management Body of Knowledge , 2004 .

[33]  Mark M. Misic,et al.  Reading between the lines: an examination of systems analysis and design texts , 2000, J. Syst. Softw..

[34]  Patrick McGovern.  HRM, Technical Workers and the Multinational Corporation , 1998 .

[35]  Mary Shaw,et al.  Software engineering education: a roadmap , 2000, ICSE '00.

[36]  Nicholas P. Vitalari,et al.  Differences Between Novice and Expert Systems Analysts: What Do We Know and What Do We Do? , 1998, J. Manag. Inf. Syst..

[37]  T. Thrall.  Work redesign. , 2003, Hospitals & health networks.

[38]  U. Renker.  [Motivation for work]. , 1975, Zeitschrift fur die gesamte Hygiene und ihre Grenzgebiete.

[39]  S. Sawyer,et al.  Coporate IT skill needs: a case study of BigCo. , 1998, CPRS.

[40]  K. Eisenhardt.  Building theories from case study research , 1989, STUDI ORGANIZZATIVI.

[41]  R. Ries.  IEEE Standard for Software User Documentation , 1990, International Conference on Professional Communication,Communication Across the Sea: North American and European Practices.

[42]  Bryan Lawson,et al.  How Designers Think , 1980 .

[43]  A. Strauss,et al.  Basics of Qualitative Research , 1992 .

[44]  Jack Downey,et al.  A framework to elicit the skills needed for software development , 2005, SIGMIS CPR '05.