Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
OSEE/OSEE Milestones
OSEE Deployment Milestones
- 2002 - Initial discussions of needed integrated platform for managing Apache Mission Software data
- 2003 - Initial development of Action Tracking System for problem/change requests
- 2004 - Nov - Confirmed Java and Eclipse as development and tool platform
- 2004 - Nov - Test Environment successfully used to verify requirements in simulated environment
- 2004 - Dec - Deployed OSEE Training Tool to organize, schedule, and track program training
- 2005 - May - Action Tracking System (ATS) used for change management of program tools
- 2005 - Nov - System requirements imported using OSEE Define
- 2006 - Jan - Key users began requirements allocation
- 2006 - Mar - Test Environment successfully used to verify requirements on flight hardware
- 2006 - May - Message Tool deployed to high fidelity integration lab
- 2006 - Aug - Action Tracking System (ATS) used as sole tracking mechanism for development of OSEE
- 2006 - Aug - First Software requirements developed and managed in OSEE Define
- 2006 - Nov - Delivered OSEE and partial program database to US Army customer
- 2007 - Jan - Draft of Prime Item Development Specification (PIDS) published using OSEE for the US Army customer
- 2007 - Feb - Draft of Software Requirements Specification (SRS) published using OSEE for the US Army customer
- 2007 - Feb - Extended Action Tracking System to include build/release planning for OSEE
- CPCR
- TPCR
- Coverage
- Disposition
- Build Memo
- Product Line
- AH-6
- AOP
- OSEE Review