Web IS Development Methodology (WISDM):The WISDM matrix

3.3 The WISDM matrix

The IS development methods matrix in figure 3.2 categorizes methods in two dimensions: socio (organizations and people) and technical (the things), on the one hand analysis ('what' is required) and on the other design ('how' it will be achieved). Hard, engineering-based approaches to IS development concentrate on the right hand side of the matrix: the generation of a requirements specification and its stepwise refinement into a software model. The Multiview approach is more even-handed, to seek a sociotechnical solution giving balance to the left and right hand sides of the methods matrix.

3.3.1 Organizational analysis

Organizational analysis represents value creation. Vickers (1984) uses the word 'appreciation' to stress strategy as relationship building and maintaining, with a broad range of stakeholders that includes customers, employees, government, suppliers, labour organizations, and so on. The systems approach to organizational analysis is covered in chapter 5, where basic systems principles are introduced, and chapter 6, where systems theory is operationalized using the Soft Systems Methodology. A systems approach does not rule out goal-driven business strategies, but these are seen as a subset of a broader aim of relationship maintaining. Traditional business strategy frameworks, such as Porter's five forces and the many e-business models that have emerged, are

pre-packaged models that provide specific content. Traditional approaches to e-strategy planning are covered in chapter 4.

3.3.2 Work design

Work design represents user satisfaction. The traditional concern of the sociotechnical approach to IS development has been with job satisfaction and genuine user participation in the development process, as reflected in the ETHICS method (Mumford, 1995). WISDM extends this view to incorporate the interests of external users, such as customers, who may be using the information system as part of their social activities. Customer satisfaction with a web-based IS is assessed using the WebQual method. Both of these topics are covered in chapter 7.

3.3.3 Information analysis

Information analysis represents the requirements specification. This is a formalized specification of the information and process requirements of the organization. The specification might be in the form of a document with graphical notations, but it might also be in the form of a software prototype (an executable specification). The indicative approach in WISDM is to use UML, which is described in chapter 8.

3.3.4 Technical design

Technical design represents the software model. A formalized model of the software in terms of data structures and program design is needed to support software construction.

3.3.5 Human computer interface design

HCI design represents the user interface and is located as an overlapping space in technical design and work design. The shape of this space reflects its role in pointing toward analysis but also that its foundations are solidly in design. The interface design draws on web site design principles for page layout, navigation schemes, and usability in the context of work design. Technical design and interface design guidelines are described in chapter 9.

3.3.6 Moving around the methods matrix

There is no a priori ordering of the five aspects of the methods matrix. For example, an organization might acquire an enterprise resource planning (ERP) software package and implement it without modification – this is one way of bringing in the best practice that has been incorporated in software through development and use in a large number of organizations. In such a situation there is less emphasis on information system modeling and software development and more on adapting organizational working practices to the  software and learning from the experience of using the software in live operations.

We have found it useful to think of the methods matrix using the metaphor of a film camera. The focus of attention changes as the camera zooms in and then out of an aspect; moves from one aspect to another; revisits an aspect and finds the situation has changed. One particular aspect might be the focus of attention at a particular time, but the other aspects are in peripheral vision and can still make their presence felt even though they might be out of shot. It is possible to see all five aspects at the same time, but only by sacrificing the level of resolution. By contrast, it is possible to focus in and examine one particular aspect in great detail, but at the expense of losing some of the context. We can take the metaphor further and think of IS projects needing the services of a director to interpret the script and a producer to ensure that resources are available. Indeed, it might need all the other people that make up the 'film credits'. Perhaps IS projects are characterized better by multiple directors with multiple cameras endlessly re-making films for distribution straight to video or to sit on the shelf. Of course, this is only a metaphor, and can be stretched too far!