Business-Information Systems Professional Differences: Bridging the Business Rule Gap

Group differences have often been cited between information system professionals and junctional-business professionals. Now perspectives of what constitutes business rules must be added to the list of group differences. In many organizations,junctional business professionals and information systems professionals disagree as to what constitutes a business rule. Functional personnel express business rules in terms of how business processes are defined and constrained. Alternatively, information system professionals view business rules in terms of the constraints that the rules place on manipulating the organization's data resources. Each of these perspectives is essentialfor the effective management ofafirm' s resources, but each perspective-independent of the otherfails to acknowledge the interreliance of business processes and the information systems that support them. This research develops a theoretical basis for this gap based on structural learning theory's definition of directive rule types: problem definition rules and solution rules. Structural learning theory is used to illustrate how these perspectives can be bridged. Based on the resulting model, the paper discusses the knowledge, skills and abilities that information systems professionals must have to enable bridging the gap.

[1]  Malcolm A. Jeeves,et al.  Analysis of structural learning , 1983 .

[2]  David P. Hale,et al.  Towards a model of programmers' cognitive processes in software maintenance: A structural learning theory approach for debugging , 1991, J. Softw. Maintenance Res. Pract..

[3]  Martin Richards,et al.  The ten most valuable components of an information systems education , 1994, Inf. Manag..

[4]  Donna B. Stoddard,et al.  Business reengineering at CIGNA Corporation: experiences and lessons learned from the first five years , 1994 .

[5]  Robert P. Bostrom,et al.  Personality Characteristics of MIS Project Teams: An Empirical Study and Action-Research Design , 1982, MIS Q..

[6]  Joseph M. Scandura,et al.  Problem solving: A structural/process approach with instructional implications , 1977 .

[7]  David A. Taylor Business engineering with object technology , 1995 .

[8]  Ye-Sho Chen,et al.  Visualizing Business Rules in Corporate Databases , 1992 .

[9]  Alan Snyder,et al.  The essence of objects: concepts and terms , 1993, IEEE Software.

[10]  David P. Hale,et al.  Integrating islands of automation , 1989 .

[11]  Joseph M. Scandura,et al.  Problem solving in schools and beyond: Transitions from the naive to the neophyte to the master , 1981 .

[12]  Varun Grover,et al.  The strategic use of information resources: an exploratory study , 1991 .

[13]  Alistair Cockburn The Impact of Object-Orientation on Application Development , 1999, IBM Syst. J..

[14]  Munindar P. Singh,et al.  Automating workflows for service order processing: integrating AI and database technologies , 1994, IEEE Expert.

[15]  Ben Tandowski How clean is your data , 1992 .

[16]  Thomas W. Ferratt,et al.  Are Information Systems People Different? An Investigation of How They Are and Should Be Managed , 1988, MIS Q..

[17]  Leon A. Kappelman,et al.  Converging end-user and corporate computing , 1993, CACM.

[18]  L. Manelis,et al.  Analysis of expository prose and its relation to learning , 1984 .

[19]  Joseph M. Scandura,et al.  Deterministic Theorizing in Structural Learning: Three Levels of Empiricism. , 1971 .

[20]  David P. Hale,et al.  Human-centered knowledge acquisition: a structural learning theory approach , 1996, Int. J. Hum. Comput. Stud..

[21]  S. Haeckel,et al.  Managing by wire , 1993 .

[22]  Seymour Papert,et al.  Teaching Children Thinking , 1972 .

[23]  J. M. Scandura Structural (cognitive task) analysis: a method for analyzing content , 1984 .

[24]  Benn R. Konsynski,et al.  Strategic Control in the Extended Enterprise , 1993, IBM Syst. J..

[25]  J. M. Scandura,et al.  On the representation of higher order knowledge , 1990 .

[26]  Robert Shane Sharpe A structural learning theory approach to problem solving: An investigation in software maintenance , 1992 .

[27]  Kate M. Kaiser,et al.  User-Analyst Differences: An Empirical Investigation of Attitudes Related to Systems Development1 , 1982 .

[28]  Robert L. Leitheiser,et al.  MIS Skills for the 1990's: A Survey of MIS Managers' Perceptions , 1992, J. Manag. Inf. Syst..

[29]  Richard Leifer,et al.  A Framework for Linking the Structure of Information Systems with Organizational Requirements for Information Sharing , 1992, J. Manag. Inf. Syst..

[30]  Wellesley R. Foshay What we know (and what we don't know) about training of cognitive strategies for technical problem-solving , 1987 .

[31]  J. Scandura An Analysis of Exposition and Discovery Modes of Problem Solving Instruction , 1964 .

[32]  James L. Fozard,et al.  Effects of age upon retrieval from short-term memory. , 1972 .

[33]  Janice M. Burn,et al.  Information systems skills: achieving alignment between the curriculum and the needs of the IS professionals in the future , 1995, DATB.

[34]  Paul H. Cheney,et al.  Knowledge, skills and abilities of information systems professionals: past, present, and future , 1990, Inf. Manag..

[35]  Michael Hammer,et al.  Reengineering Work: Don’t Automate, Obliterate , 1990 .

[36]  J. Daniel Couger,et al.  Invited Article: Motivation Levels of MIS Managers Versus Those of Their Employees , 1979, MIS Q..