Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "OSEE"
(→Documentation) |
(→Documentation) |
||
Line 39: | Line 39: | ||
*[http://en.wikipedia.org/wiki/How_to_edit How to edit a Wiki] | *[http://en.wikipedia.org/wiki/How_to_edit How to edit a Wiki] | ||
*[http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet WikiText Cheatsheet] | *[http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet WikiText Cheatsheet] | ||
+ | *[http://en.wikipedia.org/wiki/Wikipedia:Formatting#Character_formatting WikiText Character Formatting] | ||
= External References = | = External References = |
Revision as of 12:27, 6 May 2009
What is OSEE
The Open System Engineering Environment (OSEE) project provides a tightly integrated environment supporting lean principles across a product's full life-cycle in the context of an overall systems engineering approach. The system captures project data into a common user-defined data model providing bidirectional traceability, project health reporting, status, and metrics which seamlessly combine to form a coherent, accurate view of a project in real-time. By building on top of this data model, OSEE has been architected to provide an all-in-one solution to configuration management, requirements management, testing, validation, and project management. All of these work together to help an organization achieve lean objectives by reducing management activities, eliminating data duplication, reducing cycle-time through streamlined processes, and improving overall product quality through work flow standardization and early defect detection.
Documentation
Users | FAQ | Developers | |
---|---|---|---|
OSEE | OSEE Users Guide | OSEE FAQ | OSEE Developers Guide |
OSEE Define | Define Users Guide | Define FAQ | Define Developers Guide |
OSEE ATS | ATS Users Guide | ATS FAQ | ATS Developers Guide |
OSEE OTE | OTE Users Guide | OTE FAQ | OTE Developers Guide |
External References
U.S. Department of Defense Open Technology Development
RoadMap
6 months
Client only connects to application server (no direct db connections) Event Service to Application Server Web interface for Artifacts / ATS Graphical branch view Derby integration Graphical Types editor Attribute editor -> XWidgets Add generic tagging to OSEE
1 year
Integration of Open Office Enterprise Manager ATS focus (de-cluttering based on role / task) Team Provider (like SVN/CVS)
Ideas
Virtual meeting board Timecards as artifacts Ability to have multiple repositories of mulitple projects and even personal tasks that integrate into ALM - Application Lifecycle Model - http://en.wikipedia.org/wiki/Application_Lifecycle_Management IEEE Software Stndrds Cmte