search

i-adopt / core-group

For group administration and preparation of activities
0 stars 0 forks source link

Derive requirements #7

Open mabablue opened 4 years ago

mabablue commented 4 years ago

we focus on user story 20 and on use cases touched by this user story (facet semantic data search and semantic alignment)

graybeal commented 4 years ago

Two options for relatively formal requirements tracking: (A) For extended community discussion and management: GitHub tickets: It's awkward but allows long discussion threads, and you could use a template to define the fields. OR Google doc: Using comments for shorter discussion threads, and create a ticket for something contentious. (B) For capturing and managing requirements: I suggest something based on a spreadsheet, with a history. Which suggests Google sheet.

Things that could be useful to track in the requirements: ID (persistent, non-reusable, short); category; short name; definition (ideally this is a single, testable 'shall' statement); dependencies (other requirements); priority or order?

(If this enterprise grew even bigger you'd want a requirements management tool like DOORS, but that's probably not in the cards.)

mabablue commented 4 years ago

just because I was comparing tools. DOORS is out of scope because too expensive but ReqView (https://www.reqview.com/) could be an alternative