Software requirements: analysis and specification
Software requirements: analysis and specification
Requirements engineering: social and technical issues
Requirements engineering: social and technical issues
Information systems development and data modeling: conceptual and philosophical foundations
Information systems development and data modeling: conceptual and philosophical foundations
Requirements engineering
Mastering the requirements process
Mastering the requirements process
Requirements engineering: a roadmap
Proceedings of the Conference on The Future of Software Engineering
Requirements engineering in the year 00: a research perspective
Proceedings of the 22nd international conference on Software engineering
Requirements Engineering: A Good Practice Guide
Requirements Engineering: A Good Practice Guide
Requirements Engineering: Processes and Techniques
Requirements Engineering: Processes and Techniques
Information Technology and the Future Enterprise: New Models for Managers
Information Technology and the Future Enterprise: New Models for Managers
Computers in Context: The Philosophy and Practice of Systems Design
Computers in Context: The Philosophy and Practice of Systems Design
Requirements Engineering: The Emerging Wisdom
IEEE Software
Guest Editors' Introduction: Requirements Engineering
IEEE Software
A Paradigmatic Analysis Contrasting Information Systems Development Approaches and Methodologies
Information Systems Research
Information Systems Research
Innovations for Requirement Analysis. From Stakeholders' Needs to Formal Designs
Hi-index | 0.00 |
Traditional approaches to requirements elicitation stress systematic and rational analysis and representation of organizational context and system requirements. This paper argues that (1) for an organization, a software system implements a shared vision of a future work reality and that (2) understanding the emotions, feelings, values, beliefs, and interests that drive organizational human action is needed in order to invent the requirements of such a software system. This paper debunks some myths about how organizations transform themselves through the adoption of Information and Communication Technology; describes the concepts of emotion, feeling, value, and belief; and presents some constructionist guidelines for the process of eliciting requirements for a software system that helps an organization to fundamentally change its work patterns.