# Effort Estimation Approach through Extracting Use Cases via Informal Requirement Specifications
## 3 Results
The verb list contains several verbs that are analyzed in the requirement sentences. Key words and related verbs are then found in a sentence containing the identified arguments. Figure 10 shows finding another argument in a sentence related to Postal Letter. Thus, as in Figure 10, 'postal letter' can find arguments such as 'deliver,''sort' and 'accept.' In addition, 'customer' can get related predicates like 'accept' and 'pay.' Figure 8: Key verb identification of requirement analysis. Figure 9: Assignment of argument’s role. Step 4-4 identifies the relationship between a verb and an argument. Steps 2 and 3 are repeated with the predicates (verbs) found in Step 3. It will stop until there is a relationship between a verb and a noun repeatedly on each sentence. In Figure 11, the sentence 'the postal system sorts postal letter  
Figure 10: Related verb extractions. from zip-code' is analyzed. The predicate'sort' affected by the argument is the 'postal system.' Its system acts as _Subject_ and 'postal letter' is Object. Zip-code is _Instrumental_. Finally, we can visualize them using a relationship. Step 4-5 shows the relevant use-case diagram. As shown in Figure 12, the extracted predicates and arguments have repeated relationships in clusters, which is assigned as a use-case unit. It can be used to analyze the relationship between a predicate which can identify a use-case and arguments. Figure 12 shows an example of identifying the 'Mails the postal letter' use-case. Figure 11: Verb and argument identification. Figure 12: Use case extraction. Step 6 represents the relationship between 'inclusion and extension.' Use cases represent Inclusions and Extension relationships. In other words, inclusion is a way of expressing similar systematic functions found in various use-cases. For example, the use-cases analyzed in the post information system have'mails letter' and 'banks financial service' with similar functions found in these two use-cases. In Figure 13, the inclusion information is defined as'register information.' Extension occurs when a use-case is extended under certain conditions. It is used to represent the addition of use-cases. In order to express extension, the use-case is analyzed and the use-case model is expressed as 'condition' in this study. Figure 14 shows the extension relationship between the 'Banks financial service' use-case and the 'Cancel transaction' use-case. Step 5: Software Effort Estimation:  
This step shows Software Effort Estimation. We calculate the total Man-Hours of software which means to spend the developing time based on the extracted use-cases. The calculation method uses use-case point to estimate man-hours. In other words, an estimate of the development effort is needed. [PERSON] [22] define this value as 20 h/UCP. Figure 14: Inclusion and extension relationship. Figure 13: Inclusion relationship. Equation (1) is a calculation method of Total Man-hours:  
\[\text{Total Man - Hours }=ER\ (Effort\ Rate)\times UCP \tag{1}\]  
There are four use-cases extracted from the above example. Table 5 shows the Total Man-hours.