Mahdi-Kabootari commited on
Commit
7f34314
·
verified ·
1 Parent(s): f59b7fb

update read.me

Browse files
Files changed (1) hide show
  1. README.md +66 -20
README.md CHANGED
@@ -1,20 +1,66 @@
1
- ---
2
- license: afl-3.0
3
- task_categories:
4
- - text-classification
5
- language:
6
- - en
7
- tags:
8
- - Software-Engineering
9
- - Software-Requirements
10
- - Text-Calssification
11
- - Functional
12
- - Non-Functional
13
- - Requirements
14
- - NLP
15
- - Deep-Learning
16
- - Machine-Learning
17
- pretty_name: FNFC - (Functional - Non_Funtional Classification)
18
- size_categories:
19
- - 1K<n<10K
20
- ---
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # FNFC: Functional & Non-Functional Requirements Classification Dataset
2
+
3
+ **Link:** [Hugging Face – FNFC Dataset](https://huggingface.co/datasets/Mashhad-Azad-University/FNFC-Functional_Non-Functional_Classification)
4
+
5
+ ## Overview
6
+ The FNFC dataset is a labeled collection of **7,060 software requirement statements** categorized into **14 requirement classes**, designed for research and modeling in requirements classification. It was created by refining and re-labeling the **Fault-prone SRS Dataset** from [Kaggle](https://www.kaggle.com), ensuring high-quality annotations through expert review.
7
+
8
+ ## Data Collection & Labeling
9
+ The labeling process was carried out by **five professionals** with expertise in software project leadership, systems analysis, or software requirements engineering:
10
+
11
+ - **2 experts** with over **10 years** of experience
12
+ - **3 experts** with **2–3 years** of experience in requirements engineering
13
+
14
+ Each expert received:
15
+ - A **questionnaire**
16
+ - Relevant **documentation**
17
+ - Clear labeling **criteria** for identifying functional and non-functional requirements
18
+
19
+ Experts were given **20 days** to complete labeling at their own pace. Each record was assigned to one of the following classes:
20
+
21
+ ### Classes
22
+ - **F** – Functional Requirements
23
+ - **A** – Availability
24
+ - **AU** – Autonomy
25
+ - **FT** – Fault Tolerance
26
+ - **LF** – Look and Feel
27
+ - **LL** – Legal & Licensing
28
+ - **M** – Maintainability
29
+ - **O** – Inter-Operability
30
+ - **P** – Portability
31
+ - **PE** – Performance
32
+ - **R** – Reliability
33
+ - **SC** – Scalability
34
+ - **SE** – Security
35
+ - **US** – Usability
36
+
37
+ ## Dataset Structure
38
+ | Field | Description |
39
+ |-------------|-------------|
40
+ | `id` | Unique record identifier |
41
+ | `requirement` | Requirement statement text |
42
+ | `label` | One of the 14 defined classes |
43
+
44
+ *(Exact field names may vary — update based on dataset file.)*
45
+
46
+ ## Purpose
47
+ The dataset provides a robust benchmark for:
48
+ - Machine learning models for requirements classification
49
+ - Natural language processing experiments in software engineering
50
+ - Studies comparing classification methods for functional vs. non-functional requirements
51
+
52
+ ## Access
53
+ The dataset is publicly available:
54
+ [Hugging Face – FNFC Dataset](https://huggingface.co/datasets/Mashhad-Azad-University/FNFC-Functional_Non-Functional_Classification)
55
+
56
+ ## Citation
57
+ If you use this dataset in academic research, please cite:
58
+
59
+ ```bibtex
60
+ @dataset{fnfc_dataset_2025,
61
+ title={FNFC: Functional & Non-Functional Requirements Classification Dataset},
62
+ author={Mashhad Azad University},
63
+ year={2025},
64
+ url={https://huggingface.co/datasets/Mashhad-Azad-University/FNFC-Functional_Non-Functional_Classification}
65
+ }
66
+ ```