Welcome to the Android Notifications Concernification Study

A feature model modularizes and encapsulates the distinctive user-visible aspects and characteristics of a software (here a framework). It provides a high-level, formal, organized view of the user-relevant features that a framework provides.

The features are organized in a tree where the parent feature groups its children with a relationship: mandatory or optional, XOR or OR. In addition, there can also be cross-tree constraints (requires or excludes).

In our case, each feature encapsulates some specific use of the API from the user’s perspective. I.e., each feature provides the parts of the API (public classes, methods and constants) corresponding to that feature.

A child feature builds on the parent feature (and all its ancestors), therefore, the API of a feature adds on top of the API of the parent(s).

Thanks to this, it is possible to present to a user only those parts of the API of a framework that are relevant to the features that the user wants to use.

Thank you for being willing to participate in this study.

In essence, we would like to know from you, as someone who as in-depth knowledge of Android Notifications, what are the different distinctive features that a user of the NotificationCompat API might be interested in using.

On this page you can see a feature model of Android Notifications that our Concernification algorithm determined based on its public API and provided runnable examples that make use of the API. Our goal is to determine how accurate the algorithm detects features along with their corresponding API.

Please note that the API that you see here was limited to the NotificationCompat part, i.e., Notification.Builder and the corresponding classes were excluded.

Basically, each feature is connected to its corresponding API, i.e., the classes and methods that are needed when making use of this feature.

What do do

Please study the given feature model and provide the following feedback:

• whether you agree/disagree with the feature (including its name)
• whether you agree with the relationship to its parent (i.e., is it grouped under the correct parent and is the relationship type correct)
• whether any features are missing
• whether any cross-tree constraints that are displayed in the right top right window are incorrect or missing

Gray features are solely for grouping purposes, white features have a corresponding API. To open a feature and see the corresponding API, click on the feature.

Please study the given API and provide feedback when you believe an API element does not belong to that particular feature. In that case, please mention to what feature you think the API element belongs instead.

For example, it only makes sense to use the method NotificationCompat.Builder.setStyle(Style) if the user wants to use specific notification styles. Therefore, setStyle belongs to the feature that provides the relevant API for using styles, together with other related classes such as the NotificationCompat.Style class. It does not belong to the feature Android Compatibility Notifications (providing NotificationCompat.Builder), even though setStyle is a method of the Builder class.

Once you are finished, please submit your feedback using the appropriate button located on the top right.

Do I have to accept everything?

No. Anything that is not expliclity accepted or rejected is considered as accepted/ok once you submit.

Can I zoom/pan?

Yes. You can use your mouse wheel to zoom in the respective diagram and click-and-drag to pan.