Disputes Between Features and System Requirements

While the notion of a feature contains multiple facets, the ‘feature’ is a system attribute symbolizing a single set of system functionality. However , different lines of analysis have adopted a different perspective regarding this concept. The feature-oriented application engineering community, for example , perspectives board software features as a subsection, subdivision, subgroup, subcategory, subclass of system requirements, even though the feature identification literature requires the opposite approach. In the following paragraphs, we all discuss probably the most common conflicts between features and program requirements.

When choosing a software answer, users typically focus on the 10 percent of functionality certainly not work. That could be a problem since users are inclined to focus on the parts of an older software that aren’t operating. Subsequently, users may possibly overlook various other features that operate smoothly. Whether they’re aware of all of them, these users can often ignore other aspects of a software product. Using a feature-oriented approach, computer software developers can focus all their efforts over the features which have been most useful and effective for their target audience.