Clashes Between Features and Program Requirements


While the concept of a feature seems to have multiple aspects, the ‘feature’ is a program attribute addressing a single set of system functionality. Nevertheless , different lines of homework have adopted an alternate perspective regarding this concept. The feature-oriented application engineering community, for example , landscapes features as a subsection, subdivision, subgroup, subcategory, subclass of program requirements, even though the feature recognition literature usually takes the opposite methodology. In the following paragraphs, we discuss the most common disputes between features and program requirements.

Think about a software formula, users typically focus on the 10 percent of functionality however work. That could be a problem mainly because users often focus on the parts of an old software that aren’t operating. Because of this, users could overlook different features that work efficiently. Whether they’re aware of all of them, these users can often ignore other aspects of a software merchandise. Using a feature-oriented approach, application developers can focus their particular efforts at the features that are most useful and effective for his or her target audience.