|
This page proposes the candidate Trackers for inclusion in iterations constituting version 4.0 of the caDSR database. These requirements reflect not only database changes but also support for enhancements across the entire caDSR tool set including the caDSR and UML Project domain models.
This page lists the scope of work for the caDSR Database. This scope includes activities assigned to specific releases as well as ongoing parallel activities that span iterations.
Development Iterations
The following sections identify the tasks organized into specifics.
Database 4.0.0.0
The principal tasks for the caDSR Databasel 4.0.0.0 are related to following database changes:
New Features:
Value Meanings as Administered Components (GF 6820 )
The approach and scope for this change at the database level is examined in a separate design document.
Preliminary Level of Effort estimate: 10 days
Make Classification Scheme Items Administered Components (GF 6808)
As of 1/7/2008 the basic database changes for this item are in place on DSRDEV and have passed an initial round of testing as documented here. The remaining changes include modifications to the materialized views and their refresh logic, and [caCORE:???].
Preliminary Level of Effort estimate:(Since the bulk of it is already done, 2 days to review + 2 day for domain model changes and APIs)
Expose Registration Metadata (GF 7088)
Support requirement to export and import the registration authority information for a given Administered component. This will include all the parts necessary to meet 11179 requirements, plus any additional attributes deemed necessary to support multiple registries in the caBIG community.
An initial design review of the existing Registration business area model was held in December 2008 and comments from that review are being factored into a revised design. The next steps are to agree that final design and implement in the database..
Preliminary Level of Effort estimate : Need Requirements. Based on what we have cuurently have 5 days
New Forms Metadata
The Forms Next Generation (NG) analysis is pointing out additional form level metadata that will be used to enhance searching for Forms. Those data items need to be formally added to the caDSR data model and database.
Preliminary Level of Effort estimate: Need Requirements
Ongoing Enhancements
Some changes are made outside of and in parallel to the enhancements planned for each iteration release. This can include bug fixes or longer term enhancements. These enhancements will be assigned a release number when they are ready to be deployed.
| GF ID |
Summary |
Priority |
Comments |
| 7120 |
Add RAI to Organization class in domain model |
5 |
Organization identifiers need to be visible to the APIs. This field will be added to the domain model (4 hrs) |
| 6724 |
Add support for Application Specific Datatypes |
4 |
The 11179 Value Domain registered datatype is intended to be language independent. There is a need to be able to keep track of the implementation specific datatype for a particular CDE; this may include domain model changes (Need to understand this) |
| 8307 |
Allow ability to add concept to classification schemes and classification scheme items |
4 |
(This is already there) |
| 7737 |
Increase the length of RAI in the organizations table |
3 |
The current Registration Authority Identifier is limited to 36 characters because it is generated by the same process that creates database identifiers generally. Consider in conjunction with Tracker #7088 above (1 day) |
Bug Fixes
Bug fixes to be addressed
| GF ID |
Summary |
Priority |
Comments |
| 7014 |
Write a script to fix all Property Alternate name type = UML Class |
5 |
should be closed |
| 4023 |
Change data views name from caBIOxx to caDSRxx so code generated will not be ambiguous |
4 |
5 days |
| 9924 |
All columns in the administered components table should be in sync with the individual table columns |
4 |
SA: Link to 5883? |
| 819 |
When object classes or property is changed, the preferred name for data element concept is not changes |
3 |
NEed requirements |
| 7354 |
Duplicate results for UMLClassMetadata |
3 |
Usually a result of bad data. IS already done |
| 7822 |
GUEST account is recorded creating types of metadata when it should not be able to do tha |
3 |
Need investigation |
| 
