Requirements engineering
Design at Work: Cooperative Design of Computer Systems
Design at Work: Cooperative Design of Computer Systems
| Hi-index | 0.00 |
Setting the boundaries of a system and clearly scoping its requirements have been consistently identified as principal factors in successful information systems projects. Yet systems can and do fail to meet user expectations even when requirements are reviewed by clients and are signed off as being complete and correct. In this paper we discuss this paradox and outline initiatives that have been undertaken by one major organization to improve the requirements elicitation phase of system development. In particular, we discuss the steps that should be taken to ensure that all stakeholders are confident that the defined requirements are the right ones and how a better understanding of different stakeholders‘ perceptions of quality can contribute to a project‘s success. It is now widely recognized that getting these ‘soft‘ factors right directly leads to quantum improvements in organizational performance and quality systems. But little is being done in most organizations to measure quality from that perspective. Measurement of the quality of the process tends to favour the product rather than the drivers that influence the process. We discuss several strategies that can be used to monitor movement towards better quality and discuss approaches that are being used to actively involve all stakeholders in system processes and make them more responsible and accountable for quality improvements. Managers and users put their own ideas for improving system development processes and they identify some danger signs often overlooked by system developers.