 |
Page History
Overview
The Knowledge Repository (KR) project will produce software components (tooling and services) that are part of the caBIG Semantic Infrastructure version 2 (SI v2). The role of KR components will be to address the (recently) expanded NCI stakeholder community's needs for defining and sharing static semantics. The Cancer Data Standards Repository (caDSR) has, since the inception of the caBIG program, been responsible for addressing static semantic needs. The KR project will therefore, subsume the responsibilities of the caDSR and address the additional needs of the expanded stakeholder community.
The scale of caBIG's mission has expanded in both size (from national to international) and scope (including BIG Health, beyond NCI cancer centers). In order to address the expanded size of the community, the architecture of KR service components will support collaboration and sharing of metadata among distributed, federated repositories through a set of service interfaces that are specified according to the Services-Aware Interoperability Framework (SAIF). In order to address the expanded scope of caBIG's mission, these services will support expression of additional contextual semantics by focusing on high-level information models, such as Domain Analysis Models (DAMs), for example BRIDG. This additional context supports the capturing of semantics that goes beyond what has been captured in caDSR to date.
Current Status
This project is currently (2010) working to defining the road map for transitioning from the current semantic infrastructure to the SI v2. The inputs to our work include the analysis of the Semantic Infrastructure Requirements Elicitation effort and the static semantic needs of projects/groups such as caEHR, CDISC SHARE, HL7 CIC, and others.
| Table of Contents |
|---|
Project Summary
Background
...
Vision Statement
...
Documentation
...
ECCF Matrix
Topic Specification | Enterprise/Business View | Computational View | Engineering View |
|---|---|---|---|
Conceptual | Business Context, | Domain Analysis Information Model | Existing Platform Capabilities |
Platform Independent | Business Governance | Project-oriented Information Model, | Existing Platform Models |
Platform Specific | Rules, | Localized Information Model, | Execution Context, |
ECCF Documentation
Document | Artifact |
|---|---|
CFSS | Vision/Scope Document |
PIM | TBD |
PSM | TBD |
Project Planning
We engage in Agile project development, where we focus on time-boxed iterations that result in a deployable, testable application at the end of each iteration. As part of the iterative development, we actively engage with stakeholders on a regular basis. This section describes our project plan and meeting schedule.
Management Approach
In line with our Agile development methodology, we have adopted a modified version of Scrum. Checkout our Product Backlog of prioritized features and our Sprint Backlogs.
For additional information, please view our Project Plan and Communications Plan.
Team
...
Meetings
We have a daily scrum from 1:00-1:15. Contact the Project Manager if you feel you need the login details.
Deliverable Schedule
...
Deliverable Artifacts
...
Resources
The following are some resources that we have found useful in this project:
...
