The importance of ignorance in requirements engineering
Journal of Systems and Software
Component software and the way ahead
Foundations of component-based systems
A Discipline of Programming
Test Driven Development: By Example
Test Driven Development: By Example
The Scrum Software Development Process for Small Teams
IEEE Software
The Role of Emotion, Values, and Beliefs in the Construction of Innovative Work Realities
Soft-Ware 2002 Proceedings of the First International Conference on Computing in an Imperfect World
Component-Oriented Programming
Proceedings of the Workshop on Object-Oriented Technology
Application of Linguistic Techniques for Use Case Analysis
RE '02 Proceedings of the 10th Anniversary IEEE Joint International Conference on Requirements Engineering
Lessons Learned from Real DSL Experiments
HICSS '03 Proceedings of the 36th Annual Hawaii International Conference on System Sciences (HICSS'03) - Track 9 - Volume 9
Agile, open source, distributed, and on-time: inside the eclipse development process
Proceedings of the 27th international conference on Software engineering
Moving from a plan driven culture to agile development
Proceedings of the 27th international conference on Software engineering
Refactoring Databases: Evolutionary Database Design
Refactoring Databases: Evolutionary Database Design
Research Directions in Requirements Engineering
FOSE '07 2007 Future of Software Engineering
Natural language processing: mature enough for requirements documents analysis?
NLDB'05 Proceedings of the 10th international conference on Natural Language Processing and Information Systems
Metamodel adaptation and model co-adaptation
ECOOP'07 Proceedings of the 21st European conference on Object-Oriented Programming
| Hi-index | 0.00 |
This paper sketches a recent successful requirements analysis of a complex industrial automation system that mainly required a talented expert, with a beginner's mind, who has been willing to dig into the domain details together with a committed customer and a motivated team. With these key factors and the application of an appropriate combination of well-established and some newer methods and tools, we were able to efficiently elicit, refine, and validate requirements. From this specific context, we try to derive implications for innovative requirements analysis. We argue that in projects that go beyond simple, well defined, and well understood applications, automated requirements analysis is unlikely to lead to a successful specification of a system.