Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Obsolete COSMOS SDD Tooling BTG Line Items"
(→Iteration 6) |
(→Iteration 16) |
||
Line 134: | Line 134: | ||
|- bgcolor=lightgrey | |- bgcolor=lightgrey | ||
! Item !! Owner !! Sizing (days) !! Iteration !! Comments | ! Item !! Owner !! Sizing (days) !! Iteration !! Comments | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
| JUnit test cases || || || || '''Functions provided:'''<br>Test Cases | | JUnit test cases || || || || '''Functions provided:'''<br>Test Cases | ||
|- | |- | ||
Line 178: | Line 153: | ||
|- | |- | ||
| BTG Design Doc || || 3 || || '''Functions provided:'''<br>User documentation | | BTG Design Doc || || 3 || || '''Functions provided:'''<br>User documentation | ||
− | |||
− | |||
|- | |- | ||
| determine how profiles will work, implement profiles || || 5 || 3+ || '''Functions provided:'''<br>Profile support | | determine how profiles will work, implement profiles || || 5 || 3+ || '''Functions provided:'''<br>Profile support | ||
|- | |- | ||
| ANT task that calls the BTG || || 3 || 3 || '''Functions provided:'''<br>Startup scripts/ANT scripts | | ANT task that calls the BTG || || 3 || 3 || '''Functions provided:'''<br>Startup scripts/ANT scripts | ||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
| Determine how user will write custom rules || || 4 || 3+ || '''Functions provided:'''<br>User can define custom rules | | Determine how user will write custom rules || || 4 || 3+ || '''Functions provided:'''<br>User can define custom rules | ||
Line 194: | Line 163: | ||
|- | |- | ||
| Determine the rules that plug-ins should be constrained by || || 3 || 3+ || '''Functions provided:'''<br>New custom plug-ins | | Determine the rules that plug-ins should be constrained by || || 3 || 3+ || '''Functions provided:'''<br>New custom plug-ins | ||
− | |||
− | |||
|- | |- | ||
| Handle versioning for plug-ins || || 2 || 3+ || '''Functions provided:'''<br>New custom plug-ins | | Handle versioning for plug-ins || || 2 || 3+ || '''Functions provided:'''<br>New custom plug-ins | ||
Line 202: | Line 169: | ||
|- | |- | ||
| Resolve translated bundle names for comparison || || 2 || 3+ || '''Functions provided:'''<br>Language bundle support | | Resolve translated bundle names for comparison || || 2 || 3+ || '''Functions provided:'''<br>Language bundle support | ||
− | |||
− | |||
|- | |- | ||
| Modify SDDReader plugin to handle bundles || || || 3+ || '''Functions provided:'''<br>Language bundle support | | Modify SDDReader plugin to handle bundles || || || 3+ || '''Functions provided:'''<br>Language bundle support |
Revision as of 14:32, 28 March 2008
This page contains the work items for the BTG. The item name, owner, sizing, the iteration it's scheduled to appear in and any associated comments are contained in the table. In the comments section we've included the major function that this item contributes. The list of functions is the following:
- Merging of two simple, but useful, SDDs
- Merging of many SDDs
- Merging of complex SDDs
- User can define custom rules
- User can add additional plug-ins
- Parse overridden command line parms
- New custom plug-ins
- Language bundle support
- Startup scripts/ANT scripts
- Logging
- Test Cases
- Profile support
- User documentation
Once the SDD types are broken down into what would be useful for basic vs complex vs more complex (and on and on) descriptors, the items referring to rules will change to expose that information. We'll be able to schedule our iterations at that time as well.
In the iteration column, we currently list 1, 2, 3, and 3+. The iterations 1, 2, and 3 correspond to next iterations. Iteration 3+ means it's not scheduled yet, but will not be done until iteration 3 has completed.
Contents
BTG Line Items
Iteration 6
Item | Owner | Sizing(days) | Start Date | End Date | Comments |
---|---|---|---|---|---|
Rules | Eric, Yan, Josh, Robert | 25 | 0000/00/00 | 0000/00/00 | Rules checklist |
Determine logging framework and format | 2 | 0000/00/00 | 0000/00/00 | Functions provided: Logging | |
Determine command line options for logging. | 2 | 0000/00/00 | 0000/00/00 | Functions provided: Parse overridden command line parms Logging | |
Write start-up scripts (get examples from SAS) | 2 | 0000/00/00 | 0000/00/00 | Functions provided: Startup scripts/ANT scripts | |
ID Conflict Resolution | 4 | 0000/00/00 | 0000/00/00 | Functions provided: Merging of two simple, but useful, SDDs Merging of many SDDs Merging of complex SDDs | |
Handle missing information | 2 | 0000/00/00 | 0000/00/00 | Functions provided: Merging of two simple, but useful, SDDs Merging of many SDDs Merging of complex SDDs |
Iteration 7
Item | Owner | Sizing(days) | Start Date | End Date | Comments |
---|---|---|---|---|---|
Rules | Eric, Yan, Josh, Robert | 3 | 0000/00/00 | 0000/00/00 | Rules checklist |
Define format for command line parms that override properties file | 2 | 0000/00/00 | 0000/00/00 | Functions provided: Parse overridden command line parms | |
Code to parse command line parms that override properties file | 2 | 0000/00/00 | 0000/00/00 | Functions provided: Parse overridden command line parms | |
Provide the ability to specify one properties file or a directory of properties files. | 2 | 0000/00/00 | 0000/00/00 | Functions provided: Parse overridden command line parms |
Iteration 8
Item | Owner | Start Date | End Date | Comments |
---|---|---|---|---|
Rules | Eric, Yan, Josh, Robert | 0000/00/00 | 0000/00/00 | Rules checklist |
Iteration 9
Item | Owner | Start Date | End Date | Comments |
---|---|---|---|---|
Rules | Eric, Yan, Josh, Robert | 0000/00/00 | 0000/00/00 | Rules checklist |
Iteration 10
Item | Owner | Start Date | End Date | Comments |
---|---|---|---|---|
Rules | Eric, Yan, Josh, Robert | 0000/00/00 | 0000/00/00 | Rules checklist |
Iteration 11
Item | Owner | Start Date | End Date | Comments |
---|---|---|---|---|
Rules | Eric, Yan, Josh, Robert | 0000/00/00 | 0000/00/00 | Rules checklist |
Iteration 12
Item | Owner | Start Date | End Date | Comments |
---|---|---|---|---|
Rules | Eric, Yan, Josh, Robert | 0000/00/00 | 0000/00/00 | Rules checklist |
Iteration 13
Item | Owner | Start Date | End Date | Comments |
---|---|---|---|---|
Rules | Eric, Yan, Josh, Robert | 0000/00/00 | 0000/00/00 | Rules checklist |
Iteration 14
Item | Owner | Start Date | End Date | Comments |
---|---|---|---|---|
Rules | Eric, Yan, Josh, Robert | 0000/00/00 | 0000/00/00 | Rules checklist |
Iteration 15
Item | Owner | Start Date | End Date | Comments |
---|---|---|---|---|
Rules | Eric, Yan, Josh, Robert | 0000/00/00 | 0000/00/00 | Rules checklist |
Iteration 16
Item | Owner | Sizing (days) | Iteration | Comments | JUnit test cases | Functions provided: Test Cases | |||
---|---|---|---|---|---|---|---|---|---|
RPMReader | 5 | Functions provided: Test Cases | |||||||
SDDReader | 1 | This sizing is for additional work to test language bundles associated with the SDDReader plug-in. Functions provided: Test Cases | |||||||
Aggregator | 8 | Functions provided: Test Cases | |||||||
Rules | 40 | Functions provided: Test Cases | |||||||
Command line parms | 2 | Functions provided: Test Cases | |||||||
additional plugins | 5 | Functions provided: Test Cases | |||||||
Validator Design Doc | 2 | Functions provided: User documentation | |||||||
SPI Design Doc | 8 | Functions provided: User documentation | |||||||
BTG Design Doc | 3 | Functions provided: User documentation | |||||||
determine how profiles will work, implement profiles | 5 | 3+ | Functions provided: Profile support | ||||||
ANT task that calls the BTG | 3 | 3 | Functions provided: Startup scripts/ANT scripts | ||||||
Determine how user will write custom rules | 4 | 3+ | Functions provided: User can define custom rules | ||||||
Determine the rules that custom rules should be constrained by | 2 | 3+ | Functions provided: User can define custom rules | ||||||
Determine the rules that plug-ins should be constrained by | 3 | 3+ | Functions provided: New custom plug-ins | ||||||
Handle versioning for plug-ins | 2 | 3+ | Functions provided: New custom plug-ins | ||||||
Combine language bundles | 5 | 3+ | Functions provided: Language bundle support | ||||||
Resolve translated bundle names for comparison | 2 | 3+ | Functions provided: Language bundle support | ||||||
Modify SDDReader plugin to handle bundles | 3+ | Functions provided: Language bundle support | |||||||
examples and samples | 13(each) | Functions provided: User documentation |
Other BTG Work Items
- Green = On schedule
- Yellow = Danger of missing schedule
- Red = Has missed schedule
- Blue = Complete
Item | Owner | Scheduled start date (actual) | Scheduled end date (actual) | Comments |
---|---|---|---|---|
Label each SDD type as either CL1 or CL2 | Josh and Robert | 2008/03/26 | ||
Re-order SDD types for rules creation | Josh and Robert | 2008/03/26 | The order we write the rules for the SDD types should be in such a way that they fit into logical milestones or iterations. | |
Scan code and send to Eclipse review board | Chris | 2008/03/21 (2008/03/21) | 2008/03/21 (2008/03/21) |