An Artifact is a "thing" that is stored in OSEE - a requirement, a design document, a test plan, a schematic, a diagram, etc.

+

OSEE is configured by an organization to have known types of Artifact.

+

+

=== Attributes ===

+

+

Each type of Artifact has a particular set of Attributes - the information that is pertinent to that sort of thing. All Artifacts have a Name attribute but other Attributes may vary, e.g. description, units, safety criticality, and rationale are applicable to some Artifact types but not others.

+

+

=== Relations ===

+

+

The power of OSEE is in the fact that Relations can be used to specify how Artifacts relate to one another. This allows, amongst other things, traceability from requirements into design, implementation, and testing.

+

OSEE is configured by an organization to have known sorts of relations between Artifact types. A warning is displayed if one attempts to create a relation between types for which a relation has not been configured.

*[[OSEE_Artifact_Explorer|'''Artifact Explorer''']] - a "branch aware" view from which Artifacts are edited

+

*[[OSEE_Artifact_Editor|'''Artifact Editor''']]- the window in which Artifacts are edited

+

*[[OSEE_Change_Report|'''Change Report''']] - how to see what you, or someone else, has changed on a branch

+

*Skywalker - a graphical presentation of the Relations between Artifacts

= Useful OSEE Views =

= Useful OSEE Views =

−

*Branch manager

+

*[[OSEE/Users_Guide/Features#Branch_Manager_View|'''Branch manager''']] - displays branches and allows operations between branches. Not usually needed to be used by most users because the ATS branch and commit widgets give the necessary capabilities and are less error-prone.

Essential concepts

Artifacts

An Artifact is a "thing" that is stored in OSEE - a requirement, a design document, a test plan, a schematic, a diagram, etc.
OSEE is configured by an organization to have known types of Artifact.

Attributes

Each type of Artifact has a particular set of Attributes - the information that is pertinent to that sort of thing. All Artifacts have a Name attribute but other Attributes may vary, e.g. description, units, safety criticality, and rationale are applicable to some Artifact types but not others.

Relations

The power of OSEE is in the fact that Relations can be used to specify how Artifacts relate to one another. This allows, amongst other things, traceability from requirements into design, implementation, and testing.
OSEE is configured by an organization to have known sorts of relations between Artifact types. A warning is displayed if one attempts to create a relation between types for which a relation has not been configured.

Branches

All work in OSEE is carried out on a branch. Development can be thought of as being like a tree. The trunk, called System Root branch in OSEE, is not visible to most users and is just there for the major branches to connect to.

Major branches are independent pieces of work, which may be separate products, product families, projects, etc. These branches then have their own sub-branches. At some level down the tree, users will have development branches on which they do their day-to-day work. These branches belong to the user(s) working on them and are not part of released development until they have been "committed" back to their parent.

Essential OSEE Views

Change Report - how to see what you, or someone else, has changed on a branch

Skywalker - a graphical presentation of the Relations between Artifacts

Useful OSEE Views

Branch manager - displays branches and allows operations between branches. Not usually needed to be used by most users because the ATS branch and commit widgets give the necessary capabilities and are less error-prone.