3 ms·
While I see your point pointing out potential exceptions, your examples imo sound least suitable for something like "I as user want to sort my notes alphabetica
by jdthedisciple 3y ago
While I see your point pointing out potential exceptions, your examples imo sound least suitable for something like "I as user want to sort my notes alphabetically" aka User Stories.
Rather, for those critical cases you mention, frameworks like the Waterfall- or V-model, in combination with proper testing, perhaps seem much more called for to ensure compliance, security, and rigidity.
- EddieEngineers 3y agoThat's fair, I was focused on defending requirements engineering in general than just user stories. But yes you'd follow something like the V-model and you'd need these requirements, that could resemble something like user stories, to fill out a remarkably boring requirements traceability matrix on the other side. If you look at Appendix C of IBMs manual on writing requirements in DOORS [0] you'll see they can easily turn into something similar to "I as a user...". Not that I think that fits everything, nor do I think anyone should need to use DOORS lol. [0] https://www.ibm.com/docs/en/SSYQBZ_9.7.0/com.ibm.doors.requirements.doc/topics/get_it_right_the_first_time.pdf https://www.ibm.com/docs/en/SSYQBZ_9.7.0/com.ibm.doors.requi...
- slothtrop 3y agoYou'll admit however that User Stories =/= Requirements Engineering, or by extension AGILE/SOLID. Stories may be a component of those, but there are alternatives.
- jdlshore 3y ago“Agile” is not an acronym, FYI. (And SOLID is a collection of five object-oriented design principles. Not sure why you put them together like that.)
- codyb 3y agoI as a user would like to maintain a beating heart is a pretty compelling story though.
- jdthedisciple 3y agoNot a very useful thing to write down though, is it? I mean sure, if there truly was some uncertainty about this left.