## 5 Case Study of Applying the Proposed Scope Estimation Methodology  
The early phase project scope estimation methodology was applied in the information system development project performed in an international IT company department based in Lithuania. The IT company works on various software product development projects. The project analyzed in this case study started in 2022, and a minimum viable product (MVP) was developed. The project subject area is the pet shelter \"One Tail At A Time (OTAAT)\". The goal of the shelter is to end pet homelessness by making pet ownership a joyful and accessible experience for all. This is achieved by rescuing animals from overcrowded shelters, placing them in loving forever homes, and providing support and resources to pet owners in need. The pet adoption process has historically been outdated, and OTAAT is looking to tackle that via the digital space. They want to better manage applications, as well as quickly match and place pets into homes. In the existing process, people call the office to inquire about pet availability and schedule visits. Applications are downloaded, printed, filled out, and then sent back to the Adoption Center Director. The specialized software can help in optimizing and streamlining existing processes. After the requirements workshop, the initial requirements were gathered using Story map (prepared using Miro and exported as CSV file), UML Use case, UML domain Class, and UML Activity models (created using Magic Systems of Systems Architect and exported as XMI file). The requirements were gathered by the product manager, the product designer, the architect, the business analyst, and the technical delivery manager, in cooperation with several participants from the OTAAT side. One Story map model was created by the team working together with the client during the requirements workshop. Team members also prepared three Use case models (by product manager, business analyst, and architect) and nine Activity models (by product designer, business analyst, and technical delivery manager) that served as detailed information in addition to the Story map. There was only one domain Class model created by the architect. The fragments of the prepared models are presented in Figures 10-12. The prepared models have a lot in common, such as repeating users and similar action names. However, performing rapid manual model comparison and aggregation is difficult, time consuming, and inefficient. For this reason, the tool was used to import the source models and generate a list of requirements (Figure 13). Information about the number of requirements gathered from all prepared models is presented in Table 2.  
Figure 11: Examples of UML Use case models for OTAAT project prepared during the requirements workshop. Figure 10: Fragment of the Story map for OTAAT project prepared during the requirements workshop. In the next step, the synonyms were analyzed (Step S3 in Figure 2). Two overlapping actors, the Administrator and the Manager, were found. After unification, the Administrator in all requirements was renamed to Manager. In total, there were 19 changes. The naming of the Adopter actor was also unified, as several team members named it User (thus, User was changed to Adopter in 20 cases). Other overlapping nouns were also found and replaced, such as animal to pet (44 replacements); organization to shelter (1 replacement); confirmation to approval (1 replacement); registration to login (3 replacements); and document to form (9 replacements). In total, 97 changes were made during the unification of noun domain concepts. The unification of verbs also revealed usage of synonyms (e.g., add and create, search and find, ask and request, approve and confirm), but the number of replaced synonyms in verbs (in total, 18 replacements) was smaller than that of nouns. This is quite common, as in software development, the names of actions are typical, and development teams more often use verbs purposefully in the same way.