thearod5 commited on
Commit
a0594dc
1 Parent(s): 738695d

Adding paper details to BERT4RE

Browse files
Files changed (1) hide show
  1. README.md +45 -136
README.md CHANGED
@@ -1,199 +1,108 @@
1
  ---
2
  library_name: transformers
3
- tags: []
4
  ---
5
 
6
- # Model Card for Model ID
7
-
8
- <!-- Provide a quick summary of what the model is/does. -->
9
-
10
-
11
 
12
  ## Model Details
13
 
14
  ### Model Description
15
 
16
- <!-- Provide a longer summary of what this model is. -->
17
-
18
- This is the model card of a 🤗 transformers model that has been pushed on the Hub. This model card has been automatically generated.
19
 
20
- - **Developed by:** [More Information Needed]
21
- - **Funded by [optional]:** [More Information Needed]
22
- - **Shared by [optional]:** [More Information Needed]
23
- - **Model type:** [More Information Needed]
24
- - **Language(s) (NLP):** [More Information Needed]
25
- - **License:** [More Information Needed]
26
- - **Finetuned from model [optional]:** [More Information Needed]
27
 
28
- ### Model Sources [optional]
29
 
30
- <!-- Provide the basic links for the model. -->
31
-
32
- - **Repository:** [More Information Needed]
33
- - **Paper [optional]:** [More Information Needed]
34
- - **Demo [optional]:** [More Information Needed]
35
 
36
  ## Uses
37
 
38
- <!-- Address questions around how the model is intended to be used, including the foreseeable users of the model and those affected by the model. -->
39
-
40
  ### Direct Use
41
 
42
- <!-- This section is for the model use without fine-tuning or plugging into a larger ecosystem/app. -->
43
-
44
- [More Information Needed]
45
 
46
- ### Downstream Use [optional]
47
 
48
- <!-- This section is for the model use when fine-tuned for a task, or when plugged into a larger ecosystem/app -->
49
-
50
- [More Information Needed]
51
 
52
  ### Out-of-Scope Use
53
 
54
- <!-- This section addresses misuse, malicious use, and uses that the model will not work well for. -->
55
-
56
- [More Information Needed]
57
 
58
  ## Bias, Risks, and Limitations
59
 
60
- <!-- This section is meant to convey both technical and sociotechnical limitations. -->
61
-
62
- [More Information Needed]
63
-
64
  ### Recommendations
65
 
66
- <!-- This section is meant to convey recommendations with respect to the bias, risk, and technical limitations. -->
67
-
68
- Users (both direct and downstream) should be made aware of the risks, biases and limitations of the model. More information needed for further recommendations.
69
-
70
- ## How to Get Started with the Model
71
-
72
- Use the code below to get started with the model.
73
-
74
- [More Information Needed]
75
 
76
  ## Training Details
77
 
78
  ### Training Data
79
 
80
- <!-- This should link to a Dataset Card, perhaps with a short stub of information on what the training data is all about as well as documentation related to data pre-processing or additional filtering. -->
81
 
82
- [More Information Needed]
 
 
 
83
 
84
  ### Training Procedure
85
 
86
- <!-- This relates heavily to the Technical Specifications. Content here should link to that section when it is relevant to the training procedure. -->
87
-
88
- #### Preprocessing [optional]
89
-
90
- [More Information Needed]
91
-
92
-
93
- #### Training Hyperparameters
94
-
95
- - **Training regime:** [More Information Needed] <!--fp32, fp16 mixed precision, bf16 mixed precision, bf16 non-mixed precision, fp16 non-mixed precision, fp8 mixed precision -->
96
-
97
- #### Speeds, Sizes, Times [optional]
98
 
99
- <!-- This section provides information about throughput, start/end time, checkpoint size if relevant, etc. -->
100
-
101
- [More Information Needed]
 
 
102
 
103
  ## Evaluation
 
104
 
105
- <!-- This section describes the evaluation protocols and provides the results. -->
106
-
107
- ### Testing Data, Factors & Metrics
108
-
109
- #### Testing Data
110
-
111
- <!-- This should link to a Dataset Card if possible. -->
112
-
113
- [More Information Needed]
114
-
115
- #### Factors
116
-
117
- <!-- These are the things the evaluation is disaggregating by, e.g., subpopulations or domains. -->
118
-
119
- [More Information Needed]
120
-
121
- #### Metrics
122
-
123
- <!-- These are the evaluation metrics being used, ideally with a description of why. -->
124
-
125
- [More Information Needed]
126
-
127
- ### Results
128
-
129
- [More Information Needed]
130
-
131
- #### Summary
132
-
133
-
134
-
135
- ## Model Examination [optional]
136
-
137
- <!-- Relevant interpretability work for the model goes here -->
138
-
139
- [More Information Needed]
140
 
141
  ## Environmental Impact
142
 
143
- <!-- Total emissions (in grams of CO2eq) and additional considerations, such as electricity usage, go here. Edit the suggested text below accordingly -->
144
-
145
- Carbon emissions can be estimated using the [Machine Learning Impact calculator](https://mlco2.github.io/impact#compute) presented in [Lacoste et al. (2019)](https://arxiv.org/abs/1910.09700).
146
-
147
- - **Hardware Type:** [More Information Needed]
148
- - **Hours used:** [More Information Needed]
149
- - **Cloud Provider:** [More Information Needed]
150
- - **Compute Region:** [More Information Needed]
151
- - **Carbon Emitted:** [More Information Needed]
152
 
153
  ## Technical Specifications [optional]
154
 
155
  ### Model Architecture and Objective
156
 
157
- [More Information Needed]
158
 
159
  ### Compute Infrastructure
160
 
161
- [More Information Needed]
162
-
163
  #### Hardware
164
 
165
- [More Information Needed]
166
 
167
- #### Software
168
-
169
- [More Information Needed]
170
 
171
  ## Citation [optional]
172
 
173
- <!-- If there is a paper or blog post introducing the model, the APA and Bibtex information for that should go in this section. -->
174
-
175
  **BibTeX:**
176
 
177
- [More Information Needed]
178
-
179
- **APA:**
180
-
181
- [More Information Needed]
182
-
183
- ## Glossary [optional]
184
-
185
- <!-- If relevant, include terms and calculations in this section that can help readers understand the model or model card. -->
186
-
187
- [More Information Needed]
188
-
189
- ## More Information [optional]
190
-
191
- [More Information Needed]
192
-
193
  ## Model Card Authors [optional]
194
-
195
- [More Information Needed]
196
 
197
  ## Model Card Contact
198
 
199
- [More Information Needed]
 
1
  ---
2
  library_name: transformers
3
+ tags: [requirements-engineering, domain-specific-lm, concept-extraction]
4
  ---
5
 
6
+ # Model Card for BERT4RE
 
 
 
 
7
 
8
  ## Model Details
9
 
10
  ### Model Description
11
 
12
+ BERT4RE is a domain-specific language model (LM) designed to support various requirements engineering (RE) tasks, including requirements classification, detection of language issues, identification of domain concepts, and establishment of requirements traceability links. BERT4RE is retrained from the generic BERTbase model using publicly available RE-related texts.
 
 
13
 
14
+ - **Developed by:** Muideen Ajagbe, Liping Zhao
15
+ - **Shared by [optional]:** Alberto Rodriguez
16
+ - **Model type:** Domain-specific language model
17
+ - **Language(s) (NLP):** English
18
+ - **License:** MIT
19
+ - **Finetuned from model:** BERTbase
 
20
 
21
+ ### Model Sources
22
 
23
+ - **Paper [optional]:** https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=9920081
 
 
 
 
24
 
25
  ## Uses
26
 
 
 
27
  ### Direct Use
28
 
29
+ BERT4RE can be used directly for various RE tasks such as requirements classification, detection of language issues, and identification of domain concepts from requirements text.
 
 
30
 
31
+ ### Downstream Use
32
 
33
+ BERT4RE can be fine-tuned for specific RE tasks, providing enhanced performance over generic models like BERTbase. An example is its application in a multiclass classification task to identify nine different requirements concepts.
 
 
34
 
35
  ### Out-of-Scope Use
36
 
37
+ The model may not perform well for tasks outside the domain of requirements engineering or on datasets with significantly different characteristics from the training data.
 
 
38
 
39
  ## Bias, Risks, and Limitations
40
 
 
 
 
 
41
  ### Recommendations
42
 
43
+ Users should be aware of the biases and limitations inherent in the model due to the nature of the training data. Further evaluation and fine-tuning may be necessary for specific applications.
 
 
 
 
 
 
 
 
44
 
45
  ## Training Details
46
 
47
  ### Training Data
48
 
49
+ The training data consists of four requirements-related datasets:
50
 
51
+ - **PROMISE NFR Dataset:** Contains 625 requirements from 15 software development projects.
52
+ - **PURE Dataset:** Contains 522,444 lexical words and 865,551 tokens, with 29,000 unique words extracted.
53
+ - **App Review Datasets:** Contains four million app reviews with over three million unique words.
54
+ - **Google Playstore App Reviews:** Contains 600,000 app reviews with more than two million unique words.
55
 
56
  ### Training Procedure
57
 
58
+ The retraining process follows the procedures used to train the original BERTbase model, involving the Masking LM (MLM) and Next Sentence Prediction (NSP) tasks. The model was retrained on Google Cloud TPU v3-8 with the following hyperparameters:
 
 
 
 
 
 
 
 
 
 
 
59
 
60
+ - **Batch size:** 128 sequences
61
+ - **Tokens per batch:** 3200 tokens (128 * 25 subword tokens)
62
+ - **Total sequence blocks:** 1.3M
63
+ - **Epochs:** 40
64
+ - **Optimization:** Adam with a learning rate of 1e-4, a weight decay of 0.01, and a dropout rate of 0.1
65
 
66
  ## Evaluation
67
+ Please see cited paper for evaluation details.
68
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
69
 
70
  ## Environmental Impact
71
 
72
+ - **Hardware Type:** Google Cloud TPU v3-8
73
+ - **Cloud Provider:** Google Cloud
 
 
 
 
 
 
 
74
 
75
  ## Technical Specifications [optional]
76
 
77
  ### Model Architecture and Objective
78
 
79
+ BERT4RE is based on the BERTbase architecture with 12 Transformer blocks, 768 hidden size, and 12 self-attention heads.
80
 
81
  ### Compute Infrastructure
82
 
 
 
83
  #### Hardware
84
 
85
+ Google Cloud TPU v3-8 with a single 8-core processor.
86
 
 
 
 
87
 
88
  ## Citation [optional]
89
 
 
 
90
  **BibTeX:**
91
 
92
+ @INPROCEEDINGS{9920081,
93
+ author={Ajagbe, Muideen and Zhao, Liping},
94
+ booktitle={2022 IEEE 30th International Requirements Engineering Conference (RE)},
95
+ title={Retraining a BERT Model for Transfer Learning in Requirements Engineering: A Preliminary Study},
96
+ year={2022},
97
+ volume={},
98
+ number={},
99
+ pages={309-315},
100
+ keywords={Deep learning;Bit error rate;Transfer learning;Natural language processing;Requirements engineering;Task analysis;Requirements Engineering;Requirements Classification;Language Models;BERT;Domain-Specific Language Models;Transfer Learning;Deep Learning;Machine Learning;Natural Language Processing},
101
+ doi={10.1109/RE54965.2022.00046}}
102
+
 
 
 
 
 
103
  ## Model Card Authors [optional]
104
+ Muideen Ajagbe, Liping Zhao
 
105
 
106
  ## Model Card Contact
107
 
108
+ Alberto Rodriguez (arodri39@nd.edu)