For example, a Defect artifact type may require you to enter a description and the name of the customer who reported the defect. An artifact instance is also referred to as an artifact.
Each piece of information that you enter in an artifact is known as an attribute. Attributes are characteristics of artifacts. For example, when you enter a new Defect, a Description may be one attribute of the Defect report and the Customer Name may be another attribute. Attributes may be used to check the database for duplicates.
When entering an artifact instance, keep in mind that the quality of the information that you enter is vital to a project's success. For example, the following may be appropriate guidelines for entering Defects:
Inappropriate example of a defect description:
"My browser crashed. I think I was on example.com. My computer uses Windows. I think that this is a really bad problem and you should fix it now. By the way, I don't like the icons. Nobody will use your software if you keep those ugly icons. Oh, and my grandmother's home page does not look right, either, it's all messed up. Good luck."
More appropriate example of a defect description:
"The system crashes when using an image link with the border=0 attribute. Steps to reproduce:
The system crashes.
Expected result: the system should not crash.
Obtained result: the system crashed.
Workaround: The system no longer crashes when I edit the index.html page and remove "border=0" attribute from the following image link:
<img src="http://example.com/images/topics/topicfoos.gif" width=34
height=44 border=0 alt="News">"