skip banner navigation  
National Cancer Institute Center for Bioinformatics
Search:
Site Map
RELATED LINKS 
caCORE SDK Project Page
caCORE Documentation
User Groups
Publications
DOWNLOADS     [more...]
caCORE SDK
GLOBAL QUICK LINKS 
caCORE Information Opens in New Window: caCORE Information
caGrid Information Opens in New Window: caGrid Information
Cancer Biomedical Informatics Grid™ (caBIG™) Opens in New Window: Cancer Biomedical Informatics Grid™ (caBIG™)
NCICB GForge Portal Opens in New Window: NCICB GForge Portal

HOME
ABOUT NCICB INFRASTRUCTURE TOOLS PROJECTS DOWNLOADS TRAINING SUPPORT  
Infrastructure > > ODI for caCORE SDK

caCORE SDK

NCICB would like to solicit contributions from external development teams! Put on your programming hat and help us build next generation tools that will be used by the bioinformatics community to develop n-tiered architecture that use controlled vocabularies and registered metadata. See the caCORE SDK Project Page to learn more about the caCORE SDK.

The expectations for a "unit" of contribution are described in the Unit of Contribution Section in more detail but essentially can be an extension to the code generation module, semantic connector module, service layer changes, a functional enhancement or a documentation enhancement

Wish List
We will consider proposals for any kind of contribution. However, here is a list of contributions we consider most important for our upcoming release:
  • Support additional versions of XMI for data loading and code generation
  • Support Mac based UML tool
  • Enhancements to semantic connector for UML loading
  • UI for the caCORE SDK
  • Enhancements to the Search paradigm.
Next Release Line-Up
Watch this space !! In this section we will update what projects and open source contributions have been approved for development in the late Fall release.

How can I participate?
First, Take a look at the Wish List posted on this page. Also understand thoroughly the Unit of Contribution descriptions to get a feel for the type of project you would like to work on and your preferred level of participation. Then contact the caCORE SDK team to discuss your interest and proposed scope.

Once development is agreed upon, we will work with you to develop a project plan and integration schedule. During development you will be asked to participate in caCORE Status Meetings and caCORE design meetings. Design Meetings are informal team meetings in which we discuss and review design plans, code, client deliverables, etc. These meetings will occur regularly as needed throughout the process.

Contact can be made regarding potential contributions at NCICBOpenDevelopment@mail.nih.gov to begin the process. Be sure to include "caCORE SDK" in the subject line. We look forward to hearing from you.

Unit of Contribution
A unit of contribution can be as small as a bug fix or be a new feature or whole new tool. Contributors will be asked to describe the requirements their proposal is intended to meet via a use case format. A proposed unit of contribution will be evaluated based on contributor skills and fit within each of following areas:

Contributor Skills:
  • The Model Driven Architecture (MDA) is expected to be understood and utilized by contributors
  • caCORE release cycles would be followed incorporating appropriate phases of design, development, testing and deployment
  • Demonstrated skills in appropriate programming languages
  • Understanding of existing applications and functionality and role of SDK within caCORE.
Code Generation
  • Improve the Java JET technology used for code generation of domain objects.
  • Enhance the Hibernate object relational mapping files to allow automated mapping to multiple data sources.
Semantic Connector
  • Enhancement to Semantic Connector for UML Model Concept validation.
Architecture/Code Changes
  • UI for caCORE SDK
  • New search or search paradigm
  • Generation of XML serialized data objects.
  • Enhanced tool to deploy data services in JBoss
  • Ability to deploy individual models in the application server
  • Bug fixes
Functional Enhancements
  • Extension to an existing tool (i.e., take existing functionality and add additional capabilities to it)
  • Enhanced testing
  • Performance improvements (for example, improve the caching mechanism used in Hibernate)
Documentation Enhancements
  • New or enhancements to Users Guides or Technical Documentation

CONTACT US PRIVACY NOTICE DISCLAIMER ACCESSIBILITY APPLICATION SUPPORT  
National Cancer Institute Department of Health and Human Services National Institutes of Health FirstGov.gov