Do Design-Rules have an Impact on the Understandability of RESTful APIs? A Controlled Experiment
<p>This publication contains the artifacts to reproduce a study, that investigated the impact of design-rules on the understandability of REST APIs. For this study the tool limesurvey (https://www.limesurvey.org/) was used. The following files are provided: </p> <ul> <li><strong>limesurvey_study_archive_final.zip: </strong>This archive contains the survey structure (.Iss file), which can be imported in limesurvey</li> <li><strong>API_Following_Rules.yaml:</strong> The API description for the version that follows the rules</li> <li><strong>API_Ignoring_Rules.yaml:</strong> The API description for the version that ignores the rules</li> <li><strong>Result_Data.csv:</strong> The untouched dataset exported from limesurvey</li> <li><strong>Adjustments_to_Result_Data.txt:</strong> A description of changes that were made to the result data in order to filter out invalid answers and make the data easier to analyze</li> <li><strong>Result_Data_Adjusted.csv:</strong> The adjusted dataset based on the changes described in the above file</li> <li><strong>experiment_analysis_final.R</strong>: The analysis script used to get the results of the study. This script only works with the Result_Data_Adjusted.csv, because it was created based on the adjusted dataset </li> </ul>
ShareScore
40/100
Overall dataset sharing score
Score breakdown
These five areas show where the dataset supports — or may limit — practical reuse.
- Stewardship
- 4
- Harmonization
- 4
- Access
- 20
- Reuse readiness
- 8
- Engagement
- 4