having worked through the requirements of both the Adapt framework and the authoring tool, we have had our initial discussion on the essential requirements for the first release of the Adapt Framework (i.e. the minimum viable product). The high level outcome was captured as part of Deborah's notes. It's very positive to note that we were pretty well aligned at the high level.
I have attempted to capture how this translates into the detailed requirements in the attached documents. I have tried to make this as easy as possible to digest: there is one document, which lists all requirements associated to the MVP (including some non-functional success criteria) and also another document, which shows the requirements I propose as in scope in (green tick + bold) context with all known requirements.
Seeing as this release is focused on the Adapt Framework only (and excludes authoring tool functionality altogether), the ticks on the side of the authoring tool should be read as 'the framework has to include relevant functionality' according to these requirements.
I'd like to ask the project members with active roles as well as the steering group members to comment. I'd also very much welcome comments and questions from the community.
Our key aim is to get our priorities right and achieve a robust (well tested) and useful framework deliverable before Learning Technologies in order for us to launch to a developer audience. As part of this, we're hoping to attract developers into this open source project.