Second CAP meeting

Notes from the 2nd CAP meeting:

• brief report from past month: several meetings with individual experiments to understand requirements. First "brain dump" available in the google doc, final version now available here

considerations reg. draft:

• we need use cases and user stories to define and illustrate the functionalities better. This should not limit the functionalities to the described cases, but allow a first conceptual identification of "easy" cases and should avoid too detailed and endless requirement engineering for complex cases.
• current draft misses the executable preserved workflow elements. We should include examples built by DASPOS. They are currently focus on single path workflows, but that could easily be amended
• misses a systematic approach for high level analysis elements. This could be helpful for the discussion within the collaboration and across. There could be a use case where an analysis modules should be compared or reused.

Next steps:

• next step: investigate implementation of executable DASPOS workflows [who: separate discussion IT and DASPOS]
• next step: use cases and user stories [who: SIS, IT; collaborations for review and comments]
• next step: parallel discussions with collaborations to refine requirements, i.e. to get a first attempt of a comprehensive list of services that should be connected and examples of the (meta) data that will be found there. [who: all]
• next step: (based on the above) build data model(s) for the individual collabs and draft a mapping across. This should also include the identification of common analysis elements/modules (as suggested above). [who: GS, IT, DASPOS]
• next step: Proposal for information managment: Use github and github-wiki for specs and related comments. Code on github. E-group for discussions. Please let us know until the end of March if you have objections. [who: IT]
• To do: liaise with DPHEP for common grounds and involvement

Expected timeline:

• until next meeting (mid April): use cases and user stories; updated draft (please feel free to comment/revise any time!); planning for DASPOS/CAP meeting on data models
• spring: data models (probably workshop in mid-May with DASPOS) and more detailed tech specs
• late summer: early prototype for power testers

Next meeting: mid-April (doodle to come)

• Monthly plenary for updates across collaborations
• RECAST will present analysis workflows and templates in RECAST (could be used as a use case)