Closed codingAku closed 1 year ago
The dependency parser program has been implemented, and the Results for the requirements of BUcademy have been added. The comparison and analysis of the usage will be discussed in Meeting 7.
Additionally, word frequency program was implemented, to extend the stopword list.
Update: The results of word frequency for 5 keywords and 10 keywords on BUcademy requirements are as follows:
Using the dependency links and Part-of-Speech Tagging, enhanced keyword extractor pipeline implemented.
First results with new keywords added to repo. First impressions:
email address
phrase, email is kept and address is removed from keywords. We should keep both or remove both.email verification process
, produces two phrase like email verification
and verification process
edit profile page
, produces edit pageenter verification codes
produces enter codesagree to privacy policy
link is missing, can be recovered with pobj link from 'to' prepositionUPDATE: Keyword lemmatizer implemented in PR #17
Keyword extraction completed.
Issue Description
With Issue #11, the keywords of requirements for tracing is extracted. However, the initial trace results are noisy to operate. The noise needs to be reduced with more relevant keywords. One way to provide this is with dependency parsing links.
Step Details
Steps that will be performed:
Final Actions
The findings need to be documented in Wiki page.
Deadline of the Issue
10.04.2023 - 23.59