Effective communication is essential for information systems development crossing functional, org... more Effective communication is essential for information systems development crossing functional, organisational and national boundaries. As organisations attempt to overcome cultural barriers to communication across the world, communication with colleagues across the corridor remains problematic; cultural barriers between departments remain unchallenged. This paper introduces the concepts of 'culture ' and 'tribe ' into the discussion of the relationship between business users and information systems developers. Previous research has focused on identifying specific barriers to user-systems developer communication and on ways of eliminating these barriers. In contrast, this paper suggests that much can be learnt through the recognition of cultural differences inherent to the differing roles of user and systems developer. Maintenance of cultural identity is essential to the individual if he/she is to function effectively as a member of his/her tribe, whether it is the...
Effective communication is essential for information systems development crossing functional, org... more Effective communication is essential for information systems development crossing functional, organisational and national boundaries. As organisations attempt to overcome cultural barriers to communication across the world, communication with colleagues across the corridor remains problematic; cultural barriers between departments remain unchallenged. This paper introduces the concepts of 'culture' and 'tribe' into the discussion of the relationship between business users and information systems developers. Previous research has focused on identifying specific barriers to user-systems developer communication and on ways of eliminating these barriers. In contrast, this paper suggests that much can be learnt through the recognition of cultural differences inherent to the differing roles of user and systems developer. Maintenance of cultural identity is essential to the individual if he/she is to function effectively as a member of his/her tribe, whether it is the 'tribe' of developers or the 'tribe' of users. Communication problems within the systems development process may be addressed by a mutual understanding of cultural differences between the 'tribes' of users and systems developers. This degree of understanding cannot be achieved by attempting to change, persuade or convert the other tribe. The problems of user-systems developer communication need to be addressed through effective communication which acknowledges the differing cultures.
The shortcomings of conventional statistical packages are discussed to illustrate the need to dev... more The shortcomings of conventional statistical packages are discussed to illustrate the need to develop software which is able to exhibit a greater degree of statistical expertise, thereby reducing the misuse of statistical methods by those not well versed in the art of statistical analysis. U p to now the majority of the research into developing knowledge-based statistical software has concentrated on moving away from conventional architectures by adopting what can be termed expert systems approaches. This paper proposes an approach which is based upon the concept of semantic modelling.
The arguments for the soft systems approach in developing information systems are well known and ... more The arguments for the soft systems approach in developing information systems are well known and documented (see, for example, Checkland, 1981 and Checkland & Scholes, 1990). The proponents of this approach argue that a better understanding of complex problem situations is more likely to result using this approach than with the more simplistic structured or data orientated approaches commonly in use. But we are left with the following dilemma: most information systems development methods are reductionist but pragmatic; the soft systems approach, on the other hand, takes account of complexity but is difficult to use. Another reason for the adoption of conventional methods lies in the many support tools which make developing information systems using conventional methods easier. There are few tools supporting the soft systems approach.
Various methods have been proposed for making statistical packages more intelligent. One method d... more Various methods have been proposed for making statistical packages more intelligent. One method discussed in detail in this paper is to enrich the description of the data with the relevant semantic knowledge and equip the package to make use of this knowledge. This paper reports on a research project which explored in some details the structure of this metadata and the requirements of the processing modules. In particular the nature of knowledge needed to implement a range of bivariate statistical tests is examined and the features of the necessary software to validate these tests in a standard statistical package are described. The results of a prototype application of the method are also discussed.
... DAVID PODMORE, DAVID CHANEY, AND PAUL GOLDER It has been argued by Hoadley2 that people in Ho... more ... DAVID PODMORE, DAVID CHANEY, AND PAUL GOLDER It has been argued by Hoadley2 that people in Hong Kong are reluctant to make known their opinions on politically sensitive matters. ... Pp 55-139. 4 Shaw, M. E., & Wright, J. M. Scales for the Measurement of Attitudes. ...
An earlier paper (Avison and Golder, 1991) argues that there is a need for tool support for soft ... more An earlier paper (Avison and Golder, 1991) argues that there is a need for tool support for soft systems. It discusses the problems associated with the attempt to build such tools. However, there are a number of developments which would suggest that this is now plausible, for example.
In our capacities as teachers, researchers and advisors to researchers in the management and soci... more In our capacities as teachers, researchers and advisors to researchers in the management and social sciences we are frequently required to advise on the selection of the appropriate number of factors/components to be used in a factor analysis. Despite its well-publicized deficiencies the Guttman-Kaiser criterion is still, in our experience, the cut-off criterion most frequently used by practising social scientists. The popularity of the Guttman-Kaiser criterion, as against other more justifiable operational criteria, is its ease of use, its minimal judgemental element and its intuitively acceptable justification. In view of these factors favouring its use, we find that our theoretical argtument against its use and the offer of relatively more complex procedures (e.g. Bartlett, 1950; Cattell, 1966; Velicier, 1976) are often declined. As part of a larger simulation study we decided to examine more closely the behaviour of the Guttman-Kaiser criterion so that practising analysts could be informed, not just of the dangers in its use, but the likely direction and magnitude of the errors introduced.
Enterprises have architecture: whether it is visible or invisible is another matter. An enterpris... more Enterprises have architecture: whether it is visible or invisible is another matter. An enterprises' architecture determines the way in which it works to deliver its business objectives and the way in which it can change to continue to meet its evolving business objectives. Enterprise architectural thinking can facilitate effective strategic planning and information systems development. This paper reviews enterprise architecture (EA) and its concepts. It briefly considers EA frameworks. It describes the ADaPPT (Aligning Data, People, Processes and Technology) EA approach as a means to managing organisational complexity and change. Future research directions are discussed.
We discuss the growth, the benefits and risks, of business users taking a more active part in dev... more We discuss the growth, the benefits and risks, of business users taking a more active part in developing computerised information applications. After briefly discussing IS (information system) development management issues relating to user based IS development, we propose a framework for indicating the extent to which particular business users need to know about the process of developing IT systems. We then outline our recent research which addresses the measurement of BUD (Business User Development) success factors and identifies typical IT involvement levels of business users. We can conclude that BUD outcome effectiveness can be predicted using measures of contributing factors, a framework can be used to indicate the level of IT development process knowledge needed by business users, and that improved tool support would enable business users to be much more actively and directly involved in IS development. Given the current tool support environment, many agree that business users and managers need to be educated to acquire 'good' systems design and implementation techniques. An important assertion in this paper is that appropriately B.-Z. Barta et al. (eds.
Enterprises have architecture: whether it is visible or invisible is another matter. An enterpris... more Enterprises have architecture: whether it is visible or invisible is another matter. An enterprises' architecture determines the way in which it works to deliver its business objectives and the way in which it can change to continue to meet its evolving business objectives. Enterprise architectural thinking can facilitate effective strategic planning and information systems development. This paper reviews enterprise architecture (EA) and its concepts. It briefly considers EA frameworks. It describes the ADaPPT (Aligning Data, People, Processes and Technology) EA approach as a means to managing organisational complexity and change. Future research directions are discussed.
European Journal of Information Systems, Oct 1, 1993
We welcome the response of Kreher (1993) to our paper (Avison et al., 1992) and wish to respond. ... more We welcome the response of Kreher (1993) to our paper (Avison et al., 1992) and wish to respond. Our toolkit is intended to encourage users to create rich picture diagrams and to encourage discussion which might well lead to changes to the rich picture or soft systems document. These should be easier to do by using the diagrammer. The toolkit is not attempting to
European Journal of Information Systems, Sep 1, 1992
Soft systems methodology (SSM) attempts to make sense of complex problem situations which involve... more Soft systems methodology (SSM) attempts to make sense of complex problem situations which involve human activity. These problem situations are not well defined, often being described as 'fuzzy'. SSM uses models of these purposeful activity systems (human activity systems) to help their interpretation. Tools are not usually associated with this approach because problem situations are difficult to model and tools are considered inappropriate by many of the approache's proponents. In this paper we discuss the benefits of the soft systems approach and the use of tools in general, consider some of the issues relating to tools in the context of soft systems and describe our research in developing tools in this area, in particular, a tool supporting the drawing of rich picture diagrams called Get Rich Quick!
Taylor & Francis makes every effort to ensure the accuracy of all the information (the “Conte... more Taylor & Francis makes every effort to ensure the accuracy of all the information (the “Content”) contained in the publications on our platform. However, Taylor & Francis, our agents, and our licensors make no representations or warranties whatsoever as to the accuracy, completeness, or suitability for any purpose of the Content. Any opinions and views expressed in this publication are the opinions and views of the authors, and are not the views of or endorsed by Taylor & Francis. The accuracy of the Content should not be relied upon and should be independently verified with primary sources of information. Taylor and Francis shall not be liable for any losses, actions, claims, proceedings, demands, costs, expenses, damages, and other liabilities whatsoever or howsoever caused arising directly or indirectly in connection with, in relation to or arising out of the use of the Content.
Effective communication is essential for information systems development crossing functional, org... more Effective communication is essential for information systems development crossing functional, organisational and national boundaries. As organisations attempt to overcome cultural barriers to communication across the world, communication with colleagues across the corridor remains problematic; cultural barriers between departments remain unchallenged. This paper introduces the concepts of 'culture ' and 'tribe ' into the discussion of the relationship between business users and information systems developers. Previous research has focused on identifying specific barriers to user-systems developer communication and on ways of eliminating these barriers. In contrast, this paper suggests that much can be learnt through the recognition of cultural differences inherent to the differing roles of user and systems developer. Maintenance of cultural identity is essential to the individual if he/she is to function effectively as a member of his/her tribe, whether it is the...
Effective communication is essential for information systems development crossing functional, org... more Effective communication is essential for information systems development crossing functional, organisational and national boundaries. As organisations attempt to overcome cultural barriers to communication across the world, communication with colleagues across the corridor remains problematic; cultural barriers between departments remain unchallenged. This paper introduces the concepts of 'culture' and 'tribe' into the discussion of the relationship between business users and information systems developers. Previous research has focused on identifying specific barriers to user-systems developer communication and on ways of eliminating these barriers. In contrast, this paper suggests that much can be learnt through the recognition of cultural differences inherent to the differing roles of user and systems developer. Maintenance of cultural identity is essential to the individual if he/she is to function effectively as a member of his/her tribe, whether it is the 'tribe' of developers or the 'tribe' of users. Communication problems within the systems development process may be addressed by a mutual understanding of cultural differences between the 'tribes' of users and systems developers. This degree of understanding cannot be achieved by attempting to change, persuade or convert the other tribe. The problems of user-systems developer communication need to be addressed through effective communication which acknowledges the differing cultures.
The shortcomings of conventional statistical packages are discussed to illustrate the need to dev... more The shortcomings of conventional statistical packages are discussed to illustrate the need to develop software which is able to exhibit a greater degree of statistical expertise, thereby reducing the misuse of statistical methods by those not well versed in the art of statistical analysis. U p to now the majority of the research into developing knowledge-based statistical software has concentrated on moving away from conventional architectures by adopting what can be termed expert systems approaches. This paper proposes an approach which is based upon the concept of semantic modelling.
The arguments for the soft systems approach in developing information systems are well known and ... more The arguments for the soft systems approach in developing information systems are well known and documented (see, for example, Checkland, 1981 and Checkland & Scholes, 1990). The proponents of this approach argue that a better understanding of complex problem situations is more likely to result using this approach than with the more simplistic structured or data orientated approaches commonly in use. But we are left with the following dilemma: most information systems development methods are reductionist but pragmatic; the soft systems approach, on the other hand, takes account of complexity but is difficult to use. Another reason for the adoption of conventional methods lies in the many support tools which make developing information systems using conventional methods easier. There are few tools supporting the soft systems approach.
Various methods have been proposed for making statistical packages more intelligent. One method d... more Various methods have been proposed for making statistical packages more intelligent. One method discussed in detail in this paper is to enrich the description of the data with the relevant semantic knowledge and equip the package to make use of this knowledge. This paper reports on a research project which explored in some details the structure of this metadata and the requirements of the processing modules. In particular the nature of knowledge needed to implement a range of bivariate statistical tests is examined and the features of the necessary software to validate these tests in a standard statistical package are described. The results of a prototype application of the method are also discussed.
... DAVID PODMORE, DAVID CHANEY, AND PAUL GOLDER It has been argued by Hoadley2 that people in Ho... more ... DAVID PODMORE, DAVID CHANEY, AND PAUL GOLDER It has been argued by Hoadley2 that people in Hong Kong are reluctant to make known their opinions on politically sensitive matters. ... Pp 55-139. 4 Shaw, M. E., & Wright, J. M. Scales for the Measurement of Attitudes. ...
An earlier paper (Avison and Golder, 1991) argues that there is a need for tool support for soft ... more An earlier paper (Avison and Golder, 1991) argues that there is a need for tool support for soft systems. It discusses the problems associated with the attempt to build such tools. However, there are a number of developments which would suggest that this is now plausible, for example.
In our capacities as teachers, researchers and advisors to researchers in the management and soci... more In our capacities as teachers, researchers and advisors to researchers in the management and social sciences we are frequently required to advise on the selection of the appropriate number of factors/components to be used in a factor analysis. Despite its well-publicized deficiencies the Guttman-Kaiser criterion is still, in our experience, the cut-off criterion most frequently used by practising social scientists. The popularity of the Guttman-Kaiser criterion, as against other more justifiable operational criteria, is its ease of use, its minimal judgemental element and its intuitively acceptable justification. In view of these factors favouring its use, we find that our theoretical argtument against its use and the offer of relatively more complex procedures (e.g. Bartlett, 1950; Cattell, 1966; Velicier, 1976) are often declined. As part of a larger simulation study we decided to examine more closely the behaviour of the Guttman-Kaiser criterion so that practising analysts could be informed, not just of the dangers in its use, but the likely direction and magnitude of the errors introduced.
Enterprises have architecture: whether it is visible or invisible is another matter. An enterpris... more Enterprises have architecture: whether it is visible or invisible is another matter. An enterprises' architecture determines the way in which it works to deliver its business objectives and the way in which it can change to continue to meet its evolving business objectives. Enterprise architectural thinking can facilitate effective strategic planning and information systems development. This paper reviews enterprise architecture (EA) and its concepts. It briefly considers EA frameworks. It describes the ADaPPT (Aligning Data, People, Processes and Technology) EA approach as a means to managing organisational complexity and change. Future research directions are discussed.
We discuss the growth, the benefits and risks, of business users taking a more active part in dev... more We discuss the growth, the benefits and risks, of business users taking a more active part in developing computerised information applications. After briefly discussing IS (information system) development management issues relating to user based IS development, we propose a framework for indicating the extent to which particular business users need to know about the process of developing IT systems. We then outline our recent research which addresses the measurement of BUD (Business User Development) success factors and identifies typical IT involvement levels of business users. We can conclude that BUD outcome effectiveness can be predicted using measures of contributing factors, a framework can be used to indicate the level of IT development process knowledge needed by business users, and that improved tool support would enable business users to be much more actively and directly involved in IS development. Given the current tool support environment, many agree that business users and managers need to be educated to acquire 'good' systems design and implementation techniques. An important assertion in this paper is that appropriately B.-Z. Barta et al. (eds.
Enterprises have architecture: whether it is visible or invisible is another matter. An enterpris... more Enterprises have architecture: whether it is visible or invisible is another matter. An enterprises' architecture determines the way in which it works to deliver its business objectives and the way in which it can change to continue to meet its evolving business objectives. Enterprise architectural thinking can facilitate effective strategic planning and information systems development. This paper reviews enterprise architecture (EA) and its concepts. It briefly considers EA frameworks. It describes the ADaPPT (Aligning Data, People, Processes and Technology) EA approach as a means to managing organisational complexity and change. Future research directions are discussed.
European Journal of Information Systems, Oct 1, 1993
We welcome the response of Kreher (1993) to our paper (Avison et al., 1992) and wish to respond. ... more We welcome the response of Kreher (1993) to our paper (Avison et al., 1992) and wish to respond. Our toolkit is intended to encourage users to create rich picture diagrams and to encourage discussion which might well lead to changes to the rich picture or soft systems document. These should be easier to do by using the diagrammer. The toolkit is not attempting to
European Journal of Information Systems, Sep 1, 1992
Soft systems methodology (SSM) attempts to make sense of complex problem situations which involve... more Soft systems methodology (SSM) attempts to make sense of complex problem situations which involve human activity. These problem situations are not well defined, often being described as 'fuzzy'. SSM uses models of these purposeful activity systems (human activity systems) to help their interpretation. Tools are not usually associated with this approach because problem situations are difficult to model and tools are considered inappropriate by many of the approache's proponents. In this paper we discuss the benefits of the soft systems approach and the use of tools in general, consider some of the issues relating to tools in the context of soft systems and describe our research in developing tools in this area, in particular, a tool supporting the drawing of rich picture diagrams called Get Rich Quick!
Taylor & Francis makes every effort to ensure the accuracy of all the information (the “Conte... more Taylor & Francis makes every effort to ensure the accuracy of all the information (the “Content”) contained in the publications on our platform. However, Taylor & Francis, our agents, and our licensors make no representations or warranties whatsoever as to the accuracy, completeness, or suitability for any purpose of the Content. Any opinions and views expressed in this publication are the opinions and views of the authors, and are not the views of or endorsed by Taylor & Francis. The accuracy of the Content should not be relied upon and should be independently verified with primary sources of information. Taylor and Francis shall not be liable for any losses, actions, claims, proceedings, demands, costs, expenses, damages, and other liabilities whatsoever or howsoever caused arising directly or indirectly in connection with, in relation to or arising out of the use of the Content.
Uploads
Papers by paul golder
boundaries. As organisations attempt to overcome cultural barriers to communication across the world, communication
with colleagues across the corridor remains problematic; cultural barriers between departments remain unchallenged. This
paper introduces the concepts of 'culture' and 'tribe' into the discussion of the relationship between business users and
information systems developers. Previous research has focused on identifying specific barriers to user-systems developer
communication and on ways of eliminating these barriers. In contrast, this paper suggests that much can be learnt through
the recognition of cultural differences inherent to the differing roles of user and systems developer. Maintenance of
cultural identity is essential to the individual if he/she is to function effectively as a member of his/her tribe, whether it is
the 'tribe' of developers or the 'tribe' of users. Communication problems within the systems development process may be
addressed by a mutual understanding of cultural differences between the 'tribes' of users and systems developers. This
degree of understanding cannot be achieved by attempting to change, persuade or convert the other tribe. The problems of
user-systems developer communication need to be addressed through effective communication which acknowledges the
differing cultures.
boundaries. As organisations attempt to overcome cultural barriers to communication across the world, communication
with colleagues across the corridor remains problematic; cultural barriers between departments remain unchallenged. This
paper introduces the concepts of 'culture' and 'tribe' into the discussion of the relationship between business users and
information systems developers. Previous research has focused on identifying specific barriers to user-systems developer
communication and on ways of eliminating these barriers. In contrast, this paper suggests that much can be learnt through
the recognition of cultural differences inherent to the differing roles of user and systems developer. Maintenance of
cultural identity is essential to the individual if he/she is to function effectively as a member of his/her tribe, whether it is
the 'tribe' of developers or the 'tribe' of users. Communication problems within the systems development process may be
addressed by a mutual understanding of cultural differences between the 'tribes' of users and systems developers. This
degree of understanding cannot be achieved by attempting to change, persuade or convert the other tribe. The problems of
user-systems developer communication need to be addressed through effective communication which acknowledges the
differing cultures.