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.
Obsolete COSMOS SDD Tooling BTG Line Items
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
Contents
BTG Iterations
| Green = On schedule |
| Yellow = Danger of missing schedule |
| Red = Has missed schedule |
| Blue = Complete |
The start date and end date for items is the current scheduled date. If a date ends up being different, the date should be crossed out with a strikethrough font and a new date should be placed under it. If the date is in the future, it is an expected date. If the date is in the past, it is the actual date the start or end has happened.
| Item | Sizing (days) | Start Date | End Date | Comments |
|---|---|---|---|---|
| Iteration 6 | 64 | 2008/03/24 | 2008/05/27 2008/06/23 2008/06/25 2008/07/03 |
Working through JUnit test case errors that surfaced after the removal of Tuscany. |
| Iteration 7 | 15 | 2008/06/24 2008/06/23 2008/06/23 |
2008/07/01 2008/07/01 |
|
| Iteration 8 | 8 | 2008/07/02 2008/07/02 |
2008/07/08 2008/07/07 |
|
| Iteration 9 | 24 | 2008/07/09 2008/07/08 |
2008/07/17 2008/07/17 |
|
| Iteration 10 | 23 | 2008/07/18 2008/07/18 |
2008/07/24 2008/07/28 |
|
| Iteration 11 | 24 | 2008/07/25 2008/07/30 |
2008/08/01 2008/08/07 |
|
| Iteration 12 | 11 | 2008/08/04 2008/08/08 |
2008/08/08 2008/08/13 |
|
| Iteration 13 | 11 | 2008/08/11 2008/08/14 |
2008/08/15 2008/08/19 |
|
| Iteration 14 | 12 | 2008/08/18 2008/08/20 |
2008/08/22 2008/08/25 |
|
| Iteration 15 | 10 | 2008/08/25 2008/08/26 |
2008/08/29 2008/08/29 |
BTG Line Items
| Green = On schedule |
| Yellow = Danger of missing schedule |
| Red = Has missed schedule |
| Blue = Complete |
The start date and end date for items is the current scheduled date. If a date end up being different, the date should be crossed out with a strikethrough font and a new date should be placed under it. If the date is in the future, it is an expected date. If the date is in the past, it is the actual date the start or end has happened.
Iteration 6
| Item | Owner | Sizing (days) | Start Date | End Date | Comments |
|---|---|---|---|---|---|
| Label each SDD type as either CL1 or CL2 | Josh and Robert | 2008/03/19 | 2008/03/26 | ||
| Re-order SDD types for rules creation | Josh and Robert | 2008/03/19 | 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. | |
| Rules | Eric, Yan, Josh, Robert | 25 | 0000/00/00 | 2008/06/03 | Rules checklist |
| Determine logging framework and format | Robert | 2 | 2008/03/31 | 2008/04/02 | Decided to use Log4J because of the enhanced flexibility it provides. Functions provided: Logging |
| ID Conflict Resolution | Josh | 4 | 2008/03/31 | 2008/04/04 | Functions provided: Merging of two simple, but useful, SDDs Merging of many SDDs Merging of complex SDDs |
| Handle missing information | Josh | 2 | 2008/04/07 | 2008/04/09 | Functions provided: Merging of two simple, but useful, SDDs Merging of many SDDs Merging of complex SDDs Analyze aggregate SDD and determine if there is missing information that is required. If so, throw an error to the user. |
| Remove Tuscany from SPI | Eric/Yan | 15 | 2008/05/12 | 2008/06/25 |
Don't want to burden the SDD Runtime with extra dependencies. |
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 |
| Write start-up scripts (get examples from SAS) | Chris S. | 2 | 2008/06/23 | 2008/06/25 | Functions provided: Startup scripts |
| JUnit test cases for rules | Josh, Robert | 14 | 2008/06/04 | 2008/07/03 |
Moved to iteration 7 due to no reliable end date |
| JUnit test cases for rules | Eric, Yan, Josh, Robert | 2 | 0000/00/00 | 0000/00/00 | |
| Remove Tuscany from BTG | Eric, Yan | 10 | 2008/06/30 | 0000/00/00 | Drools should be the only dependency for the BTG. |
| Remove Tuscany from Validator | Eric | 5 | 2008/06/26 | 2008/07/03 |
Iteration 8
| Item | Owner | Sizing (days) | Start Date | End Date | Comments |
|---|---|---|---|---|---|
| Rules | Eric, Yan, Josh, Robert | 2 | 0000/00/00 | 0000/00/00 | Rules checklist |
| JUnit test cases for rules | 1 | 0000/00/00 | 0000/00/00 |
Iteration 9
| Item | Owner | Sizing (days) | Start Date | End Date | Comments |
|---|---|---|---|---|---|
| Rules | Eric, Yan, Josh, Robert | 10 | 0000/00/00 | 0000/00/00 | Rules checklist |
| JUnit test cases for rules | 6 | 0000/00/00 | 0000/00/00 | ||
| JUnit test cases for Aggregator | Josh, Robert | 8 | 0000/00/00 | 0000/00/00 | Functions provided: Test Cases |
Iteration 10
| Item | Owner | Sizing (days) | Start Date | End Date | Comments |
|---|---|---|---|---|---|
| Rules | Eric, Yan, Josh, Robert | 6 | 0000/00/00 | 0000/00/00 | Rules checklist |
| JUnit test cases for rules | 4 | 0000/00/00 | 0000/00/00 | ||
| JUnit test cases for RPMReader | Josh, Robert | 5 | 0000/00/00 | 0000/00/00 | Functions provided: Test Cases |
| JUnit test cases for command line parms | 2 | 0000/00/00 | 0000/00/00 | Functions provided: Test Cases | |
| Define format for command line parms that override properties file | 2 | 0000/00/00 | 0000/00/00 | Functions provided: Parse overridden command line parms | |
| Determine command line options for logging. | 2 | 0000/00/00 | 0000/00/00 | Functions provided: Parse overridden command line parms Logging | |
| Code to parse command line parms that override properties file | 2 | 0000/00/00 | 0000/00/00 | Functions provided: Parse overridden command line parms |
Iteration 11
| Item | Owner | Sizing (days) | Start Date | End Date | Comments |
|---|---|---|---|---|---|
| Rules | Eric, Yan, Josh, Robert | 8 | 0000/00/00 | 0000/00/00 | Rules checklist |
| JUnit test cases for rules | 5 | 0000/00/00 | 0000/00/00 | ||
| JUnit test cases for SDDReader | Josh, Robert | 1 | 0000/00/00 | 0000/00/00 | This sizing is for additional work to test language bundles associated with the SDDReader plug-in. Functions provided: Test Cases |
| determine how profiles will work, implement profiles | 5 | 0000/00/00 | 0000/00/00 | Functions provided: Profile support | |
| ANT task that calls the BTG | 3 | 0000/00/00 | 0000/00/00 | Functions provided: Startup scripts/ANT scripts | |
| 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 12
| Item | Owner | Sizing (days) | Start Date | End Date | Comments |
|---|---|---|---|---|---|
| Rules | Eric, Yan, Josh, Robert | 3 | 0000/00/00 | 0000/00/00 | Rules checklist |
| JUnit test cases for rules | 2 | 0000/00/00 | 0000/00/00 | ||
| Determine how user will write custom rules | 4 | 0000/00/00 | 0000/00/00 | Functions provided: User can define custom rules | |
| Determine the rules that custom rules should be constrained by | 2 | 0000/00/00 | 0000/00/00 | Functions provided: User can define custom rules |
Iteration 13
| Item | Owner | Sizing (days) | Start Date | End Date | Comments |
|---|---|---|---|---|---|
| Rules | Eric, Yan, Josh, Robert | 7 | 0000/00/00 | 0000/00/00 | Rules checklist |
| JUnit test cases for rules | 4 | 0000/00/00 | 0000/00/00 |
Iteration 14
| Item | Owner | Sizing (days) | Start Date | End Date | Comments |
|---|---|---|---|---|---|
| Rules | Eric, Yan, Josh, Robert | 3 | 0000/00/00 | 0000/00/00 | Rules checklist |
| JUnit test cases for rules | 2 | 0000/00/00 | 0000/00/00 | ||
| Combine language bundles | 5 | 0000/00/00 | 0000/00/00 | Functions provided: Language bundle support | |
| Resolve translated bundle names for comparison | 2 | 0000/00/00 | 0000/00/00 | Functions provided: Language bundle support | |
| Modify SDDReader plugin to handle bundles | ? | 0000/00/00 | 0000/00/00 | Functions provided: Language bundle support |
Iteration 15
| Item | Owner | Sizing (days) | Start Date | End Date | Comments |
|---|---|---|---|---|---|
| Rules | Eric, Yan, Josh, Robert | 3 | 0000/00/00 | 0000/00/00 | Rules checklist |
| JUnit test cases for rules | 2 | 0000/00/00 | 0000/00/00 | ||
| Determine the rules that plug-ins should be constrained by | 3 | 0000/00/00 | 0000/00/00 | Functions provided: New custom plug-ins | |
| Handle versioning for plug-ins | 2 | 0000/00/00 | 0000/00/00 | Functions provided: New custom plug-ins |
Unassigned Iterations
See COSMOS SDD Tooling Work Items for additional work items that aren't assigned to one of the iterations above.
Other BTG Work Items
| Green = On schedule |
| Yellow = Danger of missing schedule |
| Red = Has missed schedule |
| Blue = Complete |
The start date and end date for items is the current scheduled date. If a date ends up being different, the date should be crossed out with a strikethrough font and a new date should be placed under it. If the date is in the future, it is an expected date. If the date is in the past, it is the actual date the start or end has happened.
| Item | Owner | Start date | End date | Comments |
|---|---|---|---|---|
| Scan code and send to Eclipse review board | Chris M. | 2008/03/21 | 2008/03/21 |