Conflicts Between Features and Program Requirements

While the idea of a feature features multiple aspects, the ‘feature’ is a system attribute representing a single set of system functionality. Yet , different lines of analysis have adopted another type of perspective concerning this concept. The feature-oriented computer software engineering community, for example , opinions features as a part of program requirements, even though the feature identification literature will take the opposite approach. In the following paragraphs, we discuss many of the most common conflicts between features and program requirements.

When choosing a software choice, 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 old software that aren’t working. For that reason, users could overlook different features that operate smoothly. Whether they’re aware of these people, these users can often neglect other facets of a software product. Using a feature-oriented approach, software program developers can easily focus their very own efforts around the features which might be most useful and effective for their target audience.

Leave a Comment

Your email address will not be published. Required fields are marked *