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/Users Guide/Features"
| Line 1: | Line 1: | ||
= What is OSEE = | = What is OSEE = | ||
| − | [http://www.eclipse.org/osee OSEE] provides a tightly integrated environment | + | The [[http://www.eclipse.org/osee 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. |
== Artifact == | == Artifact == | ||
Revision as of 15:35, 20 April 2009
Contents
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.
Artifact
The artifact is the top level object in OSEE. It represents any data object that is to be stored.
Example: a single requirement, a user object, a piece of code (or class), a document
Attributes
Attributes are meta-data attached to an Artifact. They are strongly typed and new types can be added through extension points.
The default attribute "Name" is required for all Artifacts. Other attribute types can be created and associated with any Artifact Type in the system.
Example: Artifact representing a "User" of an application may have attributes such as "Phone", "Address", "City", etc...
Relations
Relations are how one Artifact relates to another. They are strongly typed and have validity defined which allows only appropriate artifact types to be added to the relations as well as the min/max number that are allowed on each side of the relation.
Views and Editors
Artifact Editor
The Artifact Editor is the default editor for the editing of Artifact's attributes and relations. This editor can be opened by double-clicking any artifact or right-click Open With "Artifact Editor".
Attributes Tab
The attributes tab allows for editing of Artifact Attributes. All attributes that are valid for the artifact are shown. New attributes can be added by right-click, "Add" and selecting the attribute to add.
Attribute values can be edited by selecting in the attribute value cell.
Attributes can be deleted by right-click, "Delete"
Relations Tab
The relations tab allows for editing of Relations. All relations that are defined as being valid for the artifact are shown. Opening relation groups will show all artifacts that are currently related. Double-clicking a related artifact will open it in it's default editor (normally the Artifact Editor).
Relations can be added by dragging any set of artifacts into the appropriate relation group.
Relations can be deleted by right-click "Delete Relation". This removes the link, but not the artifact.