Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "OSEE/Users Guide/Concepts"
| Line 1: | Line 1: | ||
=Artifact= | =Artifact= | ||
| − | The '''artifact''' is the fundamental object in OSEE. | + | The '''artifact''' is the fundamental object in OSEE. All data objects stored within OSEE are artifacts. Artifacts are strongly typed and can store any data throughout the systems engineering lifecycle. Any type of data can be stored in OSEE as an artifact; not only systems engineering data (such as processes and requirements), but also anything from meeting minutes to architecture diagrams. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
=Attributes= | =Attributes= | ||
| − | An '''attribute''' is | + | An '''attribute''' is data attached to an artifact. A "User" artifact might have "Email," "Name," and "Phone Number" attributes. A "Software Requirement" artifact might have attributes such as "Qualification Method," "Safety Criticality," or "Subsystem." |
| − | + | ||
| − | + | ||
The default attribute <tt>Name</tt> is required for all artifacts. Other attribute types can be created and associated with any artifact type in the system. | The default attribute <tt>Name</tt> is required for all artifacts. Other attribute types can be created and associated with any artifact type in the system. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=Relations= | =Relations= | ||
| − | A '''relation''' | + | A '''relation''' is a link between two artifacts. Like artifacts, they are strongly typed; a relation with the type "attend" might relate a "User" artifact to a "Meeting" artifact. Similarly, a "Customer Requirement" might be linked to the low-level "Software Requirement" that satisfies it. |
=Branch= | =Branch= | ||
| − | + | A fundamental feature provided by OSEE is the concurrent management of multiple variants or lines of a product. After a set of requirements is developed, it may become the baseline for variant sets of requirements for similar products. In other words, you may develop the same product for another customer, but have slight changes to the requirements, code, and test for features specific to that customer. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | Historically, this would mean maintaining completely separate "copies" of all the requirements and other artifacts. This is costly to maintain when changes from the baseline artifacts must be propagated to the other product line. The expense of this undertaking increases dramatically as more customers are added, each with their own set of requirements changes. | |
| − | + | For this reason, OSEE provides full '''branch''' functionality. Using OSEE, it is possible to create these variant branches, record where they originated, and to apply changes made to a baseline branch to its variants. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | By default, OSEE has two system branches. The <tt>System Root Branch</tt> is the parent of all other branches in the system. The <tt>Common</tt> branch is used to store OSEE configuration information, such as users. <tt>Common</tt> is a child of <tt>System Root Branch</tt>. | |
Revision as of 20:09, 11 September 2009
Contents
Artifact
The artifact is the fundamental object in OSEE. All data objects stored within OSEE are artifacts. Artifacts are strongly typed and can store any data throughout the systems engineering lifecycle. Any type of data can be stored in OSEE as an artifact; not only systems engineering data (such as processes and requirements), but also anything from meeting minutes to architecture diagrams.
Attributes
An attribute is data attached to an artifact. A "User" artifact might have "Email," "Name," and "Phone Number" attributes. A "Software Requirement" artifact might have attributes such as "Qualification Method," "Safety Criticality," or "Subsystem."
The default attribute Name is required for all artifacts. Other attribute types can be created and associated with any artifact type in the system.
Relations
A relation is a link between two artifacts. Like artifacts, they are strongly typed; a relation with the type "attend" might relate a "User" artifact to a "Meeting" artifact. Similarly, a "Customer Requirement" might be linked to the low-level "Software Requirement" that satisfies it.
Branch
A fundamental feature provided by OSEE is the concurrent management of multiple variants or lines of a product. After a set of requirements is developed, it may become the baseline for variant sets of requirements for similar products. In other words, you may develop the same product for another customer, but have slight changes to the requirements, code, and test for features specific to that customer.
Historically, this would mean maintaining completely separate "copies" of all the requirements and other artifacts. This is costly to maintain when changes from the baseline artifacts must be propagated to the other product line. The expense of this undertaking increases dramatically as more customers are added, each with their own set of requirements changes.
For this reason, OSEE provides full branch functionality. Using OSEE, it is possible to create these variant branches, record where they originated, and to apply changes made to a baseline branch to its variants.
By default, OSEE has two system branches. The System Root Branch is the parent of all other branches in the system. The Common branch is used to store OSEE configuration information, such as users. Common is a child of System Root Branch.