The project has been created. Please visit the project page.
The Open System Engineering Environment (OSEE) Project is a proposed open source project under the Eclipse Technology Project.
This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process document) and is written to declare its intent and scope. This proposal is written to solicit additional participation and input from the Eclipse community. You are invited to comment on and/or join the project. Please send all feedback to the http://www.eclipse.org/newsportal/thread.php?group=eclipse.technology.osee newsgroup.
Each large program that develops systems and software is currently required to assemble a wide array of software products to provide piecemeal capabilities necessary for completing different stages of the engineering lifecycle. Once installed, the daunting task of configuring and gluing them together begins. After years of effort, the program may have a toolset that is adequate for its current needs, but is ill-suited for growth and is far from optimized. In addition, the resulting tools are disconnected, sporadically maintained, and use an overwhelming array of disjointed user interfaces to access partially redundant data. Additionally, such a toolset often carries with it multi-million dollar software licensing, customization, configuration, and maintenance costs.
Despite the tremendous effort involved in piecing together an engineering environment, it is not enough. Lean engineering demands a truly integrated engineering environment. There is an increasing acceptance and adoption of lean principles in product development and engineering. Lean principles focus on reducing waste. A major waste when developing complex systems is handing off work between separate functional disciplines and the associated knowledge loss. Someone who knows this first hand is Jonathan Ive, head of design at Apple, who stated that "The historical way of developing products just doesn't work when you're as ambitious as we are. When the challenges are that complex, you have to develop a product in a more collaborative, integrated way." Engineering a product in a more collaborative and integrated way requires an engineering environment that is itself tightly integrated.
OSEE was designed and architected to provide Subject Matter Experts effective access to the data they need across the engineering lifecycle in a single, integrated environment. OSEE is being developed using a spiral methodology and deployed as those capabilities are needed to develop the next generation mission software for an existing Boeing aircraft. Key deployment milestones of OSEE achieved on this program are listed below.
|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|
OSEE provides a tightly integrated environment that supports lean engineering across the full product life-cycle. Since OSEE integrates all engineering areas, the full lifecycle data for a product is managed by a common platform allowing this data to be seamlessly combined to form a coherent, accurate view of a project in real-time. At the heart of the OSEE architecture are the OSEE core services and application framework which are available to all the OSEE applications and enable their tight integration.
The vision for OSEE finds concrete grounding in daily use by Subject Matter Experts developing next generation mission software for an existing Boeing aircraft. This direct involvement with a full-scale deployment of OSEE allows important user feedback to be rapidly incorporated back into both OSEE itself and as lessons learned for the development team.
Since OSEE has been developed for use by separate groups of end users, careful attention has been given to providing a proper separation of core OSEE capabilities and specific extensions made for various groups. The requirement to support separate groups has helped ensure that OSEE is extensible through standard Eclipse mechanisms. The OSEE architecture is designed to provide an integrated, extensible engineering environment that can be adopted by any group engaged in engineering.
The functional description of OSEE is provided in the following listings of its proposed components along with their key capabilities.
OTE is a powerful test solution within OSEE that integrates with existing Java, C, and C++ development environments to provide a seamless flow between developing, debugging, executing, and dispositioning of tests for complex hardware and software. The user is provided a common interface to the simulated and real-time environments for both functional and unit testing.Key Capabilities
ATS is a tightly integrated change tracking system that manages changes throughout a product's lifecycle. ATS provides integrated change management to all OSEE applications through user customizable workflows.Key Capabilities
Define provides requirements and process management with tightly integrated change management using the Action Tracking System (ATS). OSEE provides publishing capabilities that enable the creation of documents from smaller internal documents to the complex documents needed to meet military requirements for contract deliverables such as the Software Requirements Specification (SRS), System Performance Specification (SPS), Prime Item Development Specification (PIDS), and all the required traceability between them.Key Capabilities
Program and project management tightly integrated with the Action Tracking System and other OSEE components to provide services necessary for estimation, planning, execution, and delivery of products managed within OSEE.Key Capabilities
Services provided for allowing advanced learning and discovery using OSEE's abundant and inherent lifecycle data and metrics.Key Capabilities
The test environment leverages off JDT and CDT. OSEE utilizes Mylar's Zest viewer for 2D data visualization. Additional opportunities exist for integrations between ATS and Mylar. BIRT is an obvious choice for providing graphical representations of metrics produced by ATS. OSEE also utilizes advanced SWT widgets that could be contributed to the Nebula project.
|Ryan D. Brooks||Boeing: co-project lead|
|Donald G. Dunne||Boeing: co-project lead|
|Andrew M. Finkbeiner||Boeing|
|Jeff C. Phillips||Boeing|
|Ken J. Aguilar||Boeing|
|Michael P. Masterson||Boeing|
|Robert A. Fisher||Boeing|
|Roberto E. Escobar||Boeing|
|Arizona State University||Huan Liu, Ph.D.|
|Arizona State University||James S. Collofello, Ph.D.|
|Arizona State University||Peter Wonka, Ph.D.|
|Arizona State University||Susan D. Urban, Ph.D.|
|Auburn University||David Umphress, Ph.D.|
|Auburn University||Dean Hendrix, Ph.D.|
|Auburn University||James H. Cross II, Ph.D.|
|General Motors||Srinivas Chande|
|Lockheed Martin, Advanced Technology Laboratories||Alexei Samoylov|
|Rockwell Collins||Paul Streit|
We expect to extend the initial set of committers by actively supporting a developer community involving both industry and academia. We will seek to extend the developer community by building upon previous collaboration discussions with our interested parties listed above. We will make it easy for others to take an active role in the project by making our planning and process transparent and remotely accessible.
The OSEE user community includes both developers building applications on top of the OSEE application framework and end users of existing OSEE applications. The OSEE application framework is currently being utilized by a separate development group to develop aircraft maintenance software. OSEE is also currently used by Subject Matter Experts developing next generation mission software for an existing Boeing aircraft. A Principal Engineer at Leapfrog Enterprises expressed interest in using the capability to create BLAM workflows for automating tasks. The OSEE team will invest effort in helping other organizations, including the interested parties listed, to adopt both OSEE end user applications and the OSEE application framework.
The Boeing Company is offering a suite of Eclipse features (and their associated plug-ins) corresponding to 5 of the proposed components of this project as the initial code-base, namely: OSEE Application Framework, OSEE Test Environment, Action Tracking System, Define, and Program/Project Management.
|2007 - Jul||0.79.x||Remove dependencies on less friendly licenses|
|2007 - Aug||0.80.x||Separate into components; refactor into more focused features; ensure proper plug-in architecture and separation|
|2007 - Sep||0.81.x||Sanitize source code, general code cleanup|
|2007 - Oct||0.82.x||Initial public source-code commit|
|2007 - Nov||0.83.x||Add additional extension points; Document extension points|
|2008 - Jan||0.84.x||Public release for EclipseCon 2008 presentations|
Back to the top