DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2011.7
Competing schools of thought in both research and industry advocate different approaches to requirements. Each favors one particular kind of artifact, such as scenarios, goals, priorities, and context models. But focusing on any one of these risks failing to discover critical project information that could readily be unearthed by other means. Perhaps a mix-and-match approach that combines requirement methods would be more effective.
Index Terms:
requirements methods, goal, scenario, context model
Citation:
Ian Alexander, "GORE, SORE, or What?," IEEE Software, vol. 28, no. 1, pp. 8-10, Jan.-Feb. 2011, doi:10.1109/MS.2011.7 Usage of this product signifies your acceptance of the Terms of Use. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||