|Question "What are Artifacts, Attributes and Relations?" [message #569143]
||Thu, 10 April 2008 19:24
| Donald Dunne
Registered: July 2009
OSEE's definition of Artifacts, Attributes and Relations:|
Artifacts: Any data object stored within OSEE. This is a strongly typed
object that can store any data throughout the lifecycle of systems
engineering. From meeting minutes to architecture diagrams, processes
to requirements, artifacts are the main object within OSEE's data store.
There may be a "Software Requirement" artifact defined to hold the
requirements at a software level or a "User" artifact defined to hold
data associated to an OSEE user.
Attributes: Metadata attached to any Artifact. With the example of a
"Software Requirement" artifact, the attributes may be "Qualification
Method", "Safety Criticality" or "Subsystem". For a "User" artifact,
the attributes would be "Email", "Name" and "Phone".
Relations: The link between artifacts. These too are strongly typed
such that you can relate a "User" to a "Meeting" that they attended. Or
relate the high level customer requirements to the lower level
software requirements that satisfy them. These relations can also have
"Rationale" stored which gives the user the ability to note why the
Powered by FUDForum
. Page generated in 0.04114 seconds