Throughout this past year I've presented various articles highlighting the high-performance computing requirements on Wall Street, where latency and temporal constraints are closely tied profit and compliance.
As many of you know, The Techdoer Times is...
In part 1 I covered how needs serve as the core to any good requirement. The restaurant example highlighted the key differences between needs, features and requirements. In part 2 I showed how features, or the range of options and constraints across...
In part 1 to the series on Clarifying Requirements we talked about stakeholder needs, both implicit and explicit and how these needs should be the core to any good requirement. We also talked about the importance of correctly defining the user group...
Many software teams struggle with the process of identifying and defining requirements. Independent of the development process they practice (e.g. Agile, RUP, Waterfall, SCRUM or MSF), correctly capturing, specifying and maintaining stakeholder...
Latest comments