i-adopt / requirements

Repository used for Task 3 of the I-ADOPT workplan to define terminology requirements for given use cases
0 stars 1 forks source link

Build a matrix between key terminology requirements and I-ADOPT use cases (UC) #22

Open gwemon opened 4 years ago

gwemon commented 4 years ago

Following action agreed at our last meeting (4 June 2020), a matrix between key terminology requirements and User Cases has been started and is available in this shared spreadsheet

In one tab, I have copied the draft list of FAIR semantic requirements extracted from Le Franc et al as a reference; in the other tab we have the beginning of a matrix of requirements (first row) vs User Cases. Highlighted in yellow are requirements which are currently covered by the essential FAIR semantic requirements. We might need more of these added to the matrix. The important thing is to only list the key requirements for a given UC, those without which the UC cannot be successfully addressed.

The proposal is to look at each use case and select the key requirements that apply by putting an "x" in the appropriate cells. If a requirement is missing, then a new column is added and the UC to which it applies is selected.

We need to have this matrix completed by the date of our next meeting on 16 June 2020. At the last meeting, it was suggested to work in pairs (or small groups) on a selected subset of use cases. I have therefore added a third tab to the spreadsheet where we can say which UC we want to focus on as pairs or as small groups.

mariutzica commented 4 years ago

Thank you Gwen for setting this up! I worked on a few use cases (6, 9, 13) and jotted down and uploaded some of my thoughts behind each choice here. There were quite a few for which I was not sure about how to distinguish between "required" and "highly highly desirable".

gwemon commented 4 years ago

Thanks @mariutzica I like your idea of listing your notes/thoughts in one doc too. We can follow the same format for the other UC.

gwemon commented 4 years ago

The preliminary list of requirements have now been transferred from the spreadsheet to the individual Use Cases issue tickets. This is to enable us to comment/question/discuss more easily individual selections for a given UC.