3 ms·
Exactly. But this is not fun, and being the next level requirements elicitator is not a prestigious career goal. Authoring a new javascript framework is.
by UweSchmidt 10y ago
Exactly.
But this is not fun, and being the next level requirements elicitator is not a prestigious career goal. Authoring a new javascript framework is.
- _pmf_ 10y agoIt's completely incomprehensible to me why research pussyfoots around the large elephant in the room. Commercial requirements tools (that are amenable to partial transformation into inputs for data driven code generation) do exist (DOORS, ReqIF), but there's a distinct lack of FOSS communities, which is something I cannot understand. The rise of the agile methodology has IMO worsened the problem by basically making throwing in the towel the default approach. (Throw in some "but, but, you're doing agile wrong!" here.)
- UweSchmidt 10y agoPeople 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