Systems Analysis for Everyone Else: Empowering Business Professionals through a Systems Analysis Method that fits their needs

Fundamental difficulties in understanding and communicating about IT-reliant systems contribute to longstanding problems with project management, user participation, specification of requirements, implementation in organizations, business/IT alignment, and IS failures. Those issues persist despite having been explored, described, theorized, and measured in hundreds of IS research articles. The paper reports on a design science research project demonstrating a possible path toward addressing these longstanding problems by empowering business professionals to analyze systems in business terms, and not in UML, BPMN, or other formalisms that were developed for IT specialists. In this research, 75 working business professionals with extensive business experience used the latest iteration of a work system analysis template to analyze IT-reliant work systems in their own work sites, and recommend improvements. Unlike earlier work system research at the original developer’s university, the current research occurred in conjunction with three MBA programs at a major east coast university in the United States. Analysis of 75 submissions confirmed that participants could use the work system analysis template effectively. As expected in design science research, the analysis of the submissions led to recommendations for improving the design artefact.

[1]  Joey F. George,et al.  Modern Systems Analysis and Design (4th Edition) , 2004 .

[2]  Jungwoo Lee,et al.  Exploring the impact of formal training in ISD methods on the cognitive structure of novice information systems developers , 2000, Inf. Syst. J..

[3]  Steven L. Alter Service system fundamentals: Work system, value chain, and life cycle , 2008, IBM Syst. J..

[4]  Alan R. Hevner,et al.  Design Science in Information Systems Research , 2004, MIS Q..

[5]  Neil Postman,et al.  Conscientious Objections: Stirring Up Trouble About Language, Technology and Education , 1988 .

[6]  Steven L. Alter How should business professionals analyze information systems for themselves? , 1995, ISCO.

[7]  Julie E. Kendall,et al.  Systems analysis and design , 1981 .

[8]  Cynthia Mathis Beath,et al.  The Contradictory Structure of Systems Development Methodologies: Deconstructing the IS-User Relationship in Information Engineering , 1994, Inf. Syst. Res..

[9]  Steven L. Alter 18 Reasons Why IT-Reliant Work Systems Should Replace "The IT Artifact" as the Core Subject Matter of the IS Field , 2003, Commun. Assoc. Inf. Syst..

[10]  Jeffrey Parsons,et al.  How UML is used , 2006, CACM.

[11]  Lars Mathiassen Object-oriented Analysis & Design , 2000 .

[12]  Steven L. Alter Defining information systems as work systems: implications for the IS field , 2008, Eur. J. Inf. Syst..

[13]  M. Lynne Markus,et al.  Participation in Development and Implementation - Updating An Old, Tired Concept for Today's IS Contexts , 2004, J. Assoc. Inf. Syst..

[14]  Shirley Gregor,et al.  The Nature of Theory in Information Systems , 2006, MIS Q..

[15]  Steven L. Alter A General, Yet Useful Theory of Information Systems , 1999, Commun. Assoc. Inf. Syst..

[16]  Keng Siau,et al.  Theoretical vs. Practical Complexity: The Case of UML , 2005, J. Database Manag..