Towards the Identification of Software Requirements' Abstractions with a Span Categorisation Approach

Dataset of software requirements. They have been annotated with the main abstractions defined below: Purpose The rationale why a particular detail in the software requirement (or the whole software requirement) needs to be implementer. Condition Something that limits the scope of application of the software requirement, or that conditions its implementation. Precondition Condition that defines the context of operation of the software requirement. Action Something that happens in the context described by the software requirement. Trigger An event, typically involving an Action, that indicates when the system behaviour described by the software requirement should take place. Entity Human or system element involved by the software requirement. Main_actor User that interacts with the system in the context described by the software requirement. System_response The Action accomplished by the system in the context of the software requirement. ------------- They have been randomly sourced from: Public REquirements (PURE) (https://www.kaggle.com/datasets/computerscience3/public-requirementspure-dataset?resource=download) Software Requirements Dataset (https://www.kaggle.com/datasets/iamvaibhav1090/software-requirements-dataset) Land Management Readiness Assessment and Supporting Services – Future State “To-Be” Business User Stories and Use Cases (https://www.loudoun.gov/DocumentCenter/View/131287/APPENDIX-A-3---Future-State-To-Be-Business-User-Stories-and-Use-Cases?bidId=)