The phrase "artifact cases" is correct and usable in written English.
It can be used when referring to containers or displays designed to hold or showcase artifacts, often in museums or collections.
Example: "The museum has several artifact cases that display ancient pottery and tools for visitors to admire."
Alternatives: "artifact displays" or "artifact containers".
So far we have concentrated on relating artifacts to cases and publications.
Bonifacio and Borba (2009) propose an approach, Modelling Scenario Variability as Crosscutting Mechanisms (MSVCM), to deal with the variability of scenarios as a composition of different artifacts: use cases model, feature model, product configuration, and configuration knowledge.
So, it is possible that, with the feature model, this structure had better results, because the approach of Bonifacio and Borba (2009) is defined as a composition of different artifacts: use cases model, feature model, product configuration, and configuration knowledge.
However, use of whole-sequence alignment for tree construction may generate artifacts in cases including significant amounts of deletions, insertions and domain rearrangements.
However, the conventional PAT reconstruction algorithms often provide distorted images with strong artifacts in cases when the signals are collected from few measurements or over an aperture that does not enclose the object.
The rectification unit can produce aliasing artifacts in case of extreme minification, e.g., if the pixel distances are reduced by more than a half.
This research uses the Sukhothai artifacts as case study to analyze the particular design features of chinaware in this period and utilizes it as visual reference, embedding its identity into modern household utensils.
As expected, we notice the strongest artifacts in case of the nearest-neighbor interpolation (blocky appearance of the interpolated pixels), while the other methods produce visually more appealing results.
The main contribution of our work, compared to the previous four studies, is in the assessment of the comprehensibility issues provided by the use case templates and the focus on an artifact (textual use cases) instead of the requirements engineering approach.
However, it was uncertain whether this was due to a true rise in case numbers or was an artifact of better case ascertainment.
