Object-oriented software engineering
Object-oriented software engineering
Why is Software Late? An Empirical Study of Reasons for Delay in Software Development
IEEE Transactions on Software Engineering
Communications of the ACM
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Managing Process Inconsistency Using Viewpoints
IEEE Transactions on Software Engineering
Investigating information systems with action research
Communications of the AIS
Decision Tables in Software Engineering
Decision Tables in Software Engineering
Requirements Engineering: Processes and Techniques
Requirements Engineering: Processes and Techniques
Seven More Myths of Formal Methods
IEEE Software
Applying Formal Specification in Industry
IEEE Software
The Art of Requirements Triage
Computer
Viewpoints for Requirements Elicitation: A Practical Approach
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
Improving information requirements determination: a cognitive perspective
Information and Management
Towards Modeling and Reasoning Support for Early-Phase Requirements Engineering
RE '97 Proceedings of the 3rd IEEE International Symposium on Requirements Engineering
TOOLS '99 Proceedings of the Technology of Object-Oriented Languages and Systems
Requirements interaction management
ACM Computing Surveys (CSUR)
Market research for requirements analysis using linguistic tools
Requirements Engineering
The affordable application of formal methods to software engineering
Proceedings of the 2005 annual ACM SIGAda international conference on Ada: The Engineering of Correct and Reliable Software for Real-Time & Distributed Systems using Ada and Related Technologies
Communications of the ACM - Two decades of the language-action perspective
How do practitioners use conceptual modeling in practice?
Data & Knowledge Engineering - Special issue: ER 2004
Model-driven systems development
IBM Systems Journal - Model-driven software development
Experiences from introducing UML-based development in a large safety-critical project
Empirical Software Engineering
Mastering the Requirements Process (2nd Edition)
Mastering the Requirements Process (2nd Edition)
The Economics of Architecture-First
IEEE Software
ITNG '09 Proceedings of the 2009 Sixth International Conference on Information Technology: New Generations
Formal methods: Practice and experience
ACM Computing Surveys (CSUR)
Software Engineering: A Practitioner's Approach
Software Engineering: A Practitioner's Approach
From "formal methods" to system modeling
Formal methods and hybrid real-time systems
Visual syntax does matter: improving the cognitive effectiveness of the i* visual notation
Requirements Engineering - RE'09 Special Issue; Guest Editor:Kevin T Ryan
Software Engineering
User requirements modeling and analysis of software-intensive systems
Journal of Systems and Software
Hi-index | 0.00 |
A number of approaches were proposed in past years to document user requirements. Choosing the most suitable one is difficult, and frequently based on ad-hoc decision. In order to assist the way requirements engineers choose, an evaluation is necessary. The purpose of this paper is to analyze methods and languages used for user requirements documentation considering a number of criteria. This analysis was performed after extensive literature research and action research at companies that develop software-intensive systems. The objective is not to show how to find the best technique, the one that will perfectly suit all software projects. Instead, our purpose is to propose a critical view on a number of chosen techniques that might be useful for practitioners when choosing which technique to use on a specific project. The assumption is that stakeholders can benefit from knowing which techniques fit better a number of pre-determined evaluation criteria.