| Page Properties | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
The purpose of this document is to record the results of the requirements gathering process carried out for the Open, Reusable Knowledge graph Annotator (ORKA) and NanoPub Store products in the context of the ODEX4all project, as well as describe the software specification for the two systems. This project uses an adapted version of the Agile and Scrum methodologies. This adaptation is required by some of the characteristics of the project such as the distributed nature of the development team, the collaboration with other teams from different products and projects, and the possibilities of dynamic variations of the team members. To adapt the classical Agile and Scrum methodologies to the characteristics and needs of ODEX4all, the two main changes has been defined as: (a) more time is dedicated to the analysis and design phase of the development to allow for more detailed specifications of the systems to be developed, and (b) instead of daily stand-up Scrum meetings and long Sprint and evaluation meetings, the team will rely more heavily on online Scrum supporting tools such as Jira, Jira Agile, Jira Portfolio and Atlassian Confluence, with a significant part of the team interaction taking place on electronic means such as Skype calls, instant messaging, etc.
Goals
- Allow users/curators to annotate any existing (RDF) graph.
- Should provide some UI to allow users to “edit” a triple and help the user to locate suitable RDF identifiers for S, P, O.
- Final annotation will be stored as an open-access nanopublication which may be ingested by the original source or used in other ways.
- To be implemented as a generic (web) service that can be called from other tools (e.g. BRAIN).
...
From the usage scenarios described in Section 2.1, the use cases depicted in Figure 1 have been derived.
 |
Figure 1 - Use cases |
The actors of the use case are divided in two types of users, namely, the NanoPub Author and the NanoPub User. While the former interacts with the system for the purpose of annotating an assertion, publishing the assertion or managing the assertions he published, the later consumes the published assertions by means of searching, retrieving and citing the assertions.
...
From the use cases described in the last session, we have decided to split the expected functionality of the system in two separate applications, namely, ORKA and NanoPub Store. ORKA is responsible for providing support to users who want to annotate a triple originated from a graph analysis tool by changing the triple's predicate. The edited triple is then transformed into a nanopublication adding the provenance of the author and keeping the relationship with the original triple. The NanoPub Store is responsible for storing the nanopublications created in the Triple Annotator as well as allowing users to search for stored nanopublications and cite them.
 |
Figure 2 - General architecture of ORKA and NanoPub Store applications |
Figure 2 depicts the general architecture of ORKA (yellow) and NanoPub (green) applications. The applications have been divided in the following three main integrated but independent layers:
...