Goal based RE!
This is a recent paper i read on RE; Requirements Engineering in the Year 00: A Research Perspective (http://dl.acm.org/citation.cfm?id=337184).
And this was my response:
Overall while reading this paper, one could feel a sense of pity that we (software folk) allowed programming paradigms to drive the paradigms of RE. I am talking of Object Oriented techniques here. When clearly, it should have been the other way around. Goal based approaches including responsibility assignment and goal dependencies seem to be a far more natural way of doing things rather than relying on scenarios. And when grounded in formal methods such as AND/OR relationships they form the bridge to the implementation landscape thus driving software architectures and eventually programing.