Skip to main content
Jump to: navigation, search

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
  • 2006 - Nov - Create mass artifact attribute editing using Mass Editor
  • 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
  • 2007 - Mar - Create and use simple and customize-able table viewer (XViewer)
  • 2007 - May - Creation of simple BLAM Lightweight Artifact Manipulation (BLAM) interface and operation
  • 2007 - Jun - Add message recording to Test Environment
  • 2007 - Jun - Import Sub-System Design Document into OSEE
  • 2007 - Jul - Submittal of OSEE as Eclipse project
  • 2007 - Aug - Initial tracking of Code Problem Change Requests (CPCRs) in OSEE
  • 2007 - Aug - Creation of OSEE Review for peer to peer review tracking
  • 2007 - Oct - Import and manage Apache Process Assets in OSEE
  • 2007 - Nov - Create initial demo database for demos and testing
  • 2008 - Jan - Initial integration of requirement signal db (CDB) and verification in OSEE
  • 2008 - Feb - Create ability to view and disposition output results from test run in OTE
  • 2008 - Jun - Develop advanced requirement merging capabilities
  • 2008 - Jul - Incorporate System Safety into Apache Mission Software OSEE model
  • 2009 - FEb - Add automated code build memo generation for mission software
  • 2009 - Mar - Add automated historical Test Script Development Metrics generation
  • 2009 - Aug - Auto-generate OSEE Help from existing OSEE Wiki documentation
  • 2010 - Aug - Add ability to store mission software code coverage results over time and disposition
  • 2010 - Aug - Create customer facing web interface for live delivery of project data
  • 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
  • 2011 - Jan - Migrate all Software Test change report tracking to OSEE ATS
  • 2012 to Now - BOSCH-RBEI begins using OSEE within the automotive industry
  • 2012 - Feb - Create RESTful artifact query feature (ORCS Script)
  • 2012 - Feb - Create RESTful interfaces on OSEE server for any client use
  • 2012 - Apr - Convert OSEE build and test to use Maven and continuous integration
  • 2012 - Jun - Add ability to easily port changes from one branch to another
  • 2013 - Mar - Move disposition of test failure UI to Web
  • 2015 - Jan - Create Agile tracking in OSEE and move OSEE dev team to Agile
  • 2016 - May - Create ORCS Writer for external/mass artifact editing and re-importing
  • 2016 - Apr - Add Product Line capabilities to OSEE branches and artifacts
  • 2016 - Apr - Deploy Product Line approach using OSEE to Apache and AOP
  • 2017 - Feb - Create Data Rights support in OSEE
  • 2017 - Nov - Analyze and deploy OSEE toolset for F18 tool modernization
  • 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

Back to the top