Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "OSEE/OSEE Milestones"

Line 1: Line 1:
 
OSEE Deployment Milestones
 
OSEE Deployment Milestones
  
 +
* <b>2020 - May  - Onboard first F18 OSEE Developer
 +
* <b>2020 - May  - Create REST API to get commit data from a git change id
 +
* <b>2020 - Apr  - Provide a link between Cameo and OSEE
 +
* <b>2020 - Apr  - Create types in support of FACE
 +
* <b>2020 - Mar  - Convert to using full type tokens</b>
 +
* 2020 - Feb  - Setup and run Coverity Scans against OSEE
 +
* 2019 - Dec  - Performed a Posgres database initialization in the Cloud
 +
* <b>2019 - Sept  - Add ability to deploy OSEE to a CITRIX environment for US Navy access</b>
 +
* 2019 - Aug  - Add ability to save ATS searches
 +
* 2019 - Jul  - Create Web UI for PL Config including Edit
 +
* <b>2019 - Mar  - Import first set of requirements for F18</b>
 
* <b>2019 - Feb  - Analyze use of OSEE for modernization of US Navy's Operations tooling</b>
 
* <b>2019 - Feb  - Analyze use of OSEE for modernization of US Navy's Operations tooling</b>
 
* 2019 - Apr  - Create GIT commit hooks into OSEE to track commit history for Boeing AvionX
 
* 2019 - Apr  - Create GIT commit hooks into OSEE to track commit history for Boeing AvionX
Line 25: Line 36:
 
* 2008 - Jun  - Develop advanced requirement merging capabilities
 
* 2008 - Jun  - Develop advanced requirement merging capabilities
 
* 2008 - Jul  - Incorporate System Safety into Apache Mission Software OSEE model
 
* 2008 - Jul  - Incorporate System Safety into Apache Mission Software OSEE model
* 2008 - Jan  - Initial integration of requirement signal db (CDB) and verification in OSEE
 
* <b>2008 - Feb  - Create ability to view and disposition output results from test run in OTE</b>
 
* <b>2007 - Oct  - Import and manage Apache Process Assets in OSEE</b>
 
* 2007 - Nov  - Create initial demo database for demos and testing
 
* 2007 - May  - Creation of simple BLAM Lightweight Artifact Manipulation (BLAM) interface and operation
 
* 2007 - Mar  - Create and use simple and customize-able table viewer (XViewer)
 
* 2007 - Jun  - Import Sub-System Design Document into OSEE
 
* <b>2007 - Jun  - Add message recording to Test Environment</b>
 
* <b>2007 - Jul  - Submittal of OSEE as Eclipse project</b>
 
* 2007 - Jan  - Draft of Prime Item Development Specification (PIDS) published using OSEE for the US Army customer
 
* 2007 - Feb  - Extended Action Tracking System to include build/release planning for OSEE
 
* 2007 - Feb  - Draft of Software Requirements Specification (SRS) published using OSEE for the US Army customer
 
* <b>2007 - Aug  - Initial tracking of Code Problem Change Requests (CPCRs) in OSEE</b>
 
* <b>2007 - Aug  - Creation of OSEE Review for peer to peer review tracking</b>
 
* <b>2006 - Nov  - Delivered OSEE and partial program database to US Army customer</b>
 
* 2006 - Nov  - Create mass artifact attribute editing using Mass Editor
 
* 2006 - May  - Message Tool deployed to high fidelity integration lab
 
* <b>2006 - Mar  - Test Environment successfully used to verify requirements on flight hardware</b>
 
* 2006 - Jan  - Key users began requirements allocation
 
* <b>2006 - Aug  - First Software requirements developed and managed in OSEE Define</b>
 
* 2006 - Aug  - Action Tracking System (ATS) used as sole tracking mechanism for development of OSEE
 
* <b>2005 - Nov  - System requirements imported using OSEE Define</b>
 
* 2005 - May  - Action Tracking System (ATS) used for change management of program tools
 
* <b>2004 - Nov  - Test Environment successfully used to verify requirements in simulated environment</b>
 
* 2004 - Nov  - Confirmed Java and Eclipse as development and tool platform
 
* 2004 - Dec  - Deployed OSEE Training Tool to organize, schedule, and track program training
 
* <b>2003        - Initial development of Action Tracking System for problem/change requests</b>
 
* <b>2002        - Initial discussions of needed integrated platform for managing Apache Mission Software data</b>
 

Revision as of 09:45, 1 June 2023

OSEE Deployment Milestones

  • 2020 - May - Onboard first F18 OSEE Developer
  • <b>2020 - May - Create REST API to get commit data from a git change id
  • <b>2020 - Apr - Provide a link between Cameo and OSEE
  • <b>2020 - Apr - Create types in support of FACE
  • <b>2020 - Mar - Convert to using full type tokens
  • 2020 - Feb - Setup and run Coverity Scans against OSEE
  • 2019 - Dec - Performed a Posgres database initialization in the Cloud
  • 2019 - Sept - Add ability to deploy OSEE to a CITRIX environment for US Navy access
  • 2019 - Aug - Add ability to save ATS searches
  • 2019 - Jul - Create Web UI for PL Config including Edit
  • 2019 - Mar - Import first set of requirements for F18
  • 2019 - Feb - Analyze use of OSEE for modernization of US Navy's Operations tooling
  • 2019 - Apr - Create GIT commit hooks into OSEE to track commit history for Boeing AvionX
  • 2017 - Nov - Analyze and deploy OSEE toolset for F18 tool modernization
  • 2017 - Feb - Create Data Rights support in OSEE
  • 2016 - May - Create ORCS Writer for external/mass artifact editing and re-importing
  • 2016 - Apr - Deploy Product Line approach using OSEE to Apache and AOP
  • 2016 - Apr - Add Product Line capabilities to OSEE branches and artifacts
  • 2015 - Jan - Create Agile tracking in OSEE and move OSEE dev team to Agile
  • 2013 - Mar - Move disposition of test failure UI to Web
  • 2012 to Now - BOSCH-RBEI begins using OSEE within the automotive industry
  • 2012 - Jun - Add ability to easily port changes from one branch to another
  • 2012 - Feb - Create RESTful interfaces on OSEE server for any client use
  • 2012 - Feb - Create RESTful artifact query feature (ORCS Script)
  • 2012 - Apr - Convert OSEE build and test to use Maven and continuous integration
  • 2011 - Jan - Migrate all Software Test change report tracking to OSEE ATS
  • 2010 - Sep - Create ability in OTE to batch selected set of Mission Software tests overnight
  • 2010 - Nov - Deploy OSEE tool suite to new AH-6 program/platform for use in all areas of engineering
  • 2010 - Aug - Create customer facing web interface for live delivery of project data
  • 2010 - Aug - Add ability to store mission software code coverage results over time and disposition
  • 2009 - Mar - Add automated historical Test Script Development Metrics generation
  • 2009 - FEb - Add automated code build memo generation for mission software
  • 2009 - Aug - Auto-generate OSEE Help from existing OSEE Wiki documentation
  • 2008 - Jun - Develop advanced requirement merging capabilities
  • 2008 - Jul - Incorporate System Safety into Apache Mission Software OSEE model

Back to the top