People don't want to do requirement engineering for their FOSS project, of course - that's the boring part. To actually provide value the requirement world sho

People don't want to do requirement engineering for their FOSS project, of course - that's the boring part. To actually provide value the requirement world should offer a higher abstraction level - say, map requirements on "business objects" that are already implemented and configurable, and build software out of those. Workflow descriptions, relations between entities should result in actual code. Otherwise, you know why doing agile sounds attractive to many developers. Otherwise