Open System Engineering Environment
OSEE provides a tightly integrated environment that supports lean engineering.
It is integrated around a simple, user-definable data model to eloquently
provide bidirectional traceability across the full product life-cycle
including: architecture and design, requirements management, implementation,
verification, and validation.
OSEE Overview - This screencast provides an overview of OSEE including the driving forces that caused it's creation, it's architecture, the maturity of the application framework and the status and maturity of the different applications that use the framework.
V-Model - http://en.wikipedia.org/wiki/V_model
Bi-Directional Traceability
From the first requirement that comes in to the last deliverable, all artifacts are stored, manipulated and configuration
managed within OSEE. Traceability from System to Subsystem to Software Requirements is created at the time of decomposition
and maintained as an integral part of the engineering process. Through tightly integrated configuration management and
OSEE built-in workflow engine, users are more easily able to follow complex lifecycles of engineering. Graphical editors
allow the visualization and navigation of the artifacts in the system. Any user can walk the path in either direction from
the customer requirement down to the code unit and even the verification, validation and integration tests.
Integrated Process and Workflow
Integrating processes and workflow into OSEE allows engineers to focus more on engineering and less on process
training and manually reporting metrics. Workflows are graphically defined and stored in OSEE. Each individual
or team that is required to work on an improvement or problem can have a uniquely configured set of states and
transitions. Widgets needed to graphically view and edit data throughout the workflow is configured using a rich
widget XML specification that declares the widget type, it's storage object and certain display attributes.
OSEE reads these workflows and dynamically generates the necessary editor components to walk the user through
the process. Specific conditions necessary in the process are defined through these workflows, object permissions and
configured rules. These conditions can include the automatic creation of review workflows, kickoff of other
related workflows, automated notifications and even the generation or publication of reports.
Presentations, Articles, News and Events
The Cure for Your Disconnected Toolset Headache - EclipseCon 2008
Top 10 Deployment Secrets They Don't Want You To Know - EclipseCon 2008
Open System Engineering Environment: An Integrated Solution - EclipseCon 2008
Other News and Events
