ID Primary study,artifactName,systemType,Extraction,Comments PS3,Database model,Industry system," - The isolated service is located in domain layer. (PS-3 Joselyne, M. I., Bajpai, G., & Nzanywayingoma, F. (2021). , P. 6: 261) - A database model with their corresponding domain model is considered as bounded context (PS-3 Joselyne, M. I., Bajpai, G., & Nzanywayingoma, F. (2021). , P. 3: 4401) ",The process follows a procedure that specify the use of Domain model and Database model to create a bounded context that's a microservice PS3,DDD Domain model,Industry system," - The isolated service is located in domain layer. (PS-3 Joselyne, M. I., Bajpai, G., & Nzanywayingoma, F. (2021). , P. 6: 261) - A database model with their corresponding domain model is considered as bounded context (PS-3 Joselyne, M. I., Bajpai, G., & Nzanywayingoma, F. (2021). , P. 3: 4401) ","The process follows a procedure that specify the use of Domain model and Database model to create a bounded context that's a microservice DDD domain model per microservice" PS3,Sketching Rough descriptions,Industry system," - Through brainstorming, sketching rough descriptions of the domain to informal analysis of the transactions of hotel domain, the following entities with their vocabulary are abstracted (PS-3 Joselyne, M. I., Bajpai, G., & Nzanywayingoma, F. (2021). , P. 5: 145)",None PS3,Source model,Industry system," - A tactical DDD pre-sentation of the source model is composed with modules containing entities, value objects with their relations. (PS-3 Joselyne, M. I., Bajpai, G., & Nzanywayingoma, F. (2021). , P. 5: 2017) - To visualize data dependency in the database graph, different aggregates of the system are to be located. This graph is the presentation of the source model that show entities as nodes and CRUD operation as links. (PS-3 Joselyne, M. I., Bajpai, G., & Nzanywayingoma, F. (2021). , P. 3: 1941) - The source model of the HMS is composed with the ubiquitous language (PS-3 Joselyne, M. I., Bajpai, G., & Nzanywayingoma, F. (2021). , P. 4: 4380) ",Custom tool -> CRUD Diagram PS4,DDD Domain model,Example system," - We have modeled DDD domain models, microservice API models, and the mapping of DDD domain models to API models for each case. (PS-4 Singjai, A., & Zdun, U. (2022). Conformance Assessment of, P. 3: 3277) ",None PS4,DDD Domain model,Example system," - We have modeled DDD domain models, microservice API models, and the mapping of DDD domain models to API models for each case. (PS-4 Singjai, A., & Zdun, U. (2022). Conformance Assessment of, P. 3: 3277) ",None PS4,DDD Domain model,Example system," - We have modeled DDD domain models, microservice API models, and the mapping of DDD domain models to API models for each case. (PS-4 Singjai, A., & Zdun, U. (2022). Conformance Assessment of, P. 3: 3277) ",None PS4,DDD Domain model,Example system," - We have modeled DDD domain models, microservice API models, and the mapping of DDD domain models to API models for each case. (PS-4 Singjai, A., & Zdun, U. (2022). Conformance Assessment of, P. 3: 3277) ",None PS4,DDD Domain model,Example system," - We have modeled DDD domain models, microservice API models, and the mapping of DDD domain models to API models for each case. (PS-4 Singjai, A., & Zdun, U. (2022). Conformance Assessment of, P. 3: 3277) ",None PS4,DDD Domain model,Example system," - We have modeled DDD domain models, microservice API models, and the mapping of DDD domain models to API models for each case. (PS-4 Singjai, A., & Zdun, U. (2022). Conformance Assessment of, P. 3: 3277) ",None PS4,DDD Domain model,Example system," - We have modeled DDD domain models, microservice API models, and the mapping of DDD domain models to API models for each case. (PS-4 Singjai, A., & Zdun, U. (2022). Conformance Assessment of, P. 3: 3277) ",None PS4,DDD Domain model,Example system," - We have modeled DDD domain models, microservice API models, and the mapping of DDD domain models to API models for each case. (PS-4 Singjai, A., & Zdun, U. (2022). Conformance Assessment of, P. 3: 3277) ",None PS4,DDD Domain model,Example system," - Expose Domain Model Subset as API (Singjai, A., & Zdun, U. (2022). Conformance Assessment of Archi, P. 4: 927) ",Key: BAS PS4,DDD Domain model,Example system," - For some API resources it is unclear on which domain model elements they are based (Singjai, A., & Zdun, U. (2022). Conformance Assessment of Archi, P. 4: 2054) ",Key: ESCS PS4,DDD Domain model,Example system," - Domain Model Subset Exposed to API (Singjai, A., & Zdun, U. (2022). Conformance Assessment of Archi, P. 4: 2392) ",Key: COS PS4,DDD Domain model,Example system," - Map Domain Model Fully to the API (Singjai, A., & Zdun, U. (2022). Conformance Assessment of Archi, P. 4: 3372) ",Key: DSA PS5,DDD Domain model,Example system," - The Cargo domain model exhibits three Bounded Contexts, four relationships between them, one of which being substantiated by an association class, and a total of ten domain concepts (cf. Fig. 1) (Rademacher, F., Sachweh, S., & Zundorf, A. (2020). Deriving Mic, P. 6: 3987) ","Key: CS This is a DDD domain model - DDD Domain Model Structures: The constructed DDD domain models can be characterized as follows (PS-5 Rademacher, F., Sachweh, S., & Zundorf, A. (2020). Derivin, P. 6: 3891)" PS5,DDD Domain model,Example system," - LM’s domain model has five contexts, seven intercontext relationships with two association classes, and a total of 27 domain concepts. (Rademacher, F., Sachweh, S., & Zundorf, A. (2020). Deriving Mic, P. 6: 4190) ","Key: LMS This is a DDD domain model - DDD Domain Model Structures: The constructed DDD domain models can be characterized as follows (PS-5 Rademacher, F., Sachweh, S., & Zundorf, A. (2020). Derivin, P. 6: 3891)" PS5,Class model,Example system," - we employed Eclipse Papyrus to construct the Cargo and LM DDD domain models as UML class diagrams that apply our UML profile (Rademacher, F., Sachweh, S., & Zundorf, A. (2020). Deriving Mic, P. 6: 2127) ","Key: LMS This is a proposed exemplification about how to translate DDD model to UML model" PS5,Class model,Example system," - we employed Eclipse Papyrus to construct the Cargo and LM DDD domain models as UML class diagrams that apply our UML profile (Rademacher, F., Sachweh, S., & Zundorf, A. (2020). Deriving Mic, P. 6: 2127) ","Key: CS This is a proposed exemplification about how to translate DDD model to UML model" PS9,Actor context model,Industry system," - We used the actor context diagram in additional interviews to discover more of in|FOCUS’ internals and behavior. The collected information of the Familiarization phase provided us with domain knowledge (Krause, A., Zirkelbach, C., Hasselbring, W., Lenga, S., & Kroge, P. 3: 575) ",Actor Context diagram PS9,Context map,Industry system," - In the final Partitioning phase, we used the collected domain knowledge to identify target boundaries in the context map. These boundaries represent scopes in which each domain term has a unique definition, i.e., bounded contexts. (Krause, A., Zirkelbach, C., Hasselbring, W., Lenga, S., & Kroge, P. 3: 1875)",None PS9,Use cases model,Industry system," - we first identified the use cases of the lottery application actor towards the remaining actors. Then, we defined domain contexts, i.e., groups for related behavior or structure, and mapped the use cases onto these (Krause, A., Zirkelbach, C., Hasselbring, W., Lenga, S., & Kroge, P. 3: 1017) - we already assigned the use cases to the domain contexts (see Sec. III) as well as partitioned them into bounded contexts (Krause, A., Zirkelbach, C., Hasselbring, W., Lenga, S., & Kroge, P. 3: 2943) ",Use cases diagram PS10,Database model,Industry system,,They show the relational model per microservice PS10,DDD Domain model,Industry system," - Each subdomain is mapped to a microservice (bounded context), which has its domain model, as shown in Figure 5 (Li, C. Y., Ma, S. P., & Lu, T. W. (2020). Microservice Migratio, P. 4: 1700) ","This is a DDD domain model In the image showed in the paper they're using DDD patterns in the domain model" PS10,Use cases model,Industry system," - we wrote the description for the use case diagram and marked all nouns to determine whether they are vital classes, and used them to create an abstract domain model (Li, C. Y., Ma, S. P., & Lu, T. W. (2020). Microservice Migratio, P. 4: 1225) ",Use cases diagram and descriptions PS11,Class model,Industry system," - Class diagrams show system classes and their logical relationships. (Rahmatulloh, A., Sari, D. W., Shofa, R. N., & Darmawan, I. (202, P. 3: 2889)","The diagrams are modeled in the paper, they apply te artifacts to define de system detailed design: ""After the domain-driven design stage has been completed, the next step is to design the Unified Modeling Language (UML) [22], including use case, sequence, class, and deployment diagrams."" (Rahmatulloh, A., Sari, D. W., Shofa, R. N., & Darmawan, I. (202, P. 3: 2531)" PS11,Context map,Industry system, - The diagram shows a context map in terms of flows. (The name comes with a mistake), PS11,Deployment model,Industry system," - Deployment diagrams describe the various processes in the system and how the relationships that exist in these processes (Rahmatulloh, A., Sari, D. W., Shofa, R. N., & Darmawan, I. (202, P. 3: 2959)","The diagrams are modeled in the paper, they apply te artifacts to define de system detailed design: ""After the domain-driven design stage has been completed, the next step is to design the Unified Modeling Language (UML) [22], including use case, sequence, class, and deployment diagrams."" (Rahmatulloh, A., Sari, D. W., Shofa, R. N., & Darmawan, I. (202, P. 3: 2531)" PS11,System interaction model,Industry system," - Sequence diagrams describe interactions that detail how an operation is performed (Rahmatulloh, A., Sari, D. W., Shofa, R. N., & Darmawan, I. (202, P. 3: 2802)","The diagrams are modeled in the paper, they apply te artifacts to define de system detailed design: ""After the domain-driven design stage has been completed, the next step is to design the Unified Modeling Language (UML) [22], including use case, sequence, class, and deployment diagrams."" (Rahmatulloh, A., Sari, D. W., Shofa, R. N., & Darmawan, I. (202, P. 3: 2531)" PS11,Use cases model,Industry system," - Use case diagram used to model systems created with object-based concepts (Rahmatulloh, A., Sari, D. W., Shofa, R. N., & Darmawan, I. (202, P. 3: 2725) - The use case diagram shown in Figure 4 describes the interaction between actors, namely admins and guest users, devices or nodes, or third-party applications with IoT monitoring applications created (Rahmatulloh, A., Sari, D. W., Shofa, R. N., & Darmawan, I. (202, P. 4: 994)","The diagrams are modeled in the paper, they apply te artifacts to define de system detailed design: ""After the domain-driven design stage has been completed, the next step is to design the Unified Modeling Language (UML) [22], including use case, sequence, class, and deployment diagrams."" (Rahmatulloh, A., Sari, D. W., Shofa, R. N., & Darmawan, I. (202, P. 3: 2531) diseño" PS11,Microservices interaction model,Industry system," - Next, making microservices workflow diagrams and designing API specifications to be used. (Rahmatulloh, A., Sari, D. W., Shofa, R. N., & Darmawan, I. (202, P. 3: 3085) ",Workflow diagram PS12,Context map,Industry system," - Coarse system capability is broken down into different components in respect to its context map, in the same context map study well how components are going to interact with each other in loose coupling possible. (Josélyne, M. I., Tuheirwe-Mukasa, D., Kanagwa, B., & Balikuddem, P. 4: 2679) - A well designed bounded context in a context map will end up being a microservice (Josélyne, M. I., Tuheirwe-Mukasa, D., Kanagwa, B., & Balikuddem, P. 3: 1163) ",None PS12,Sketching Rough descriptions,Industry system," - Through brainstorming, sketching rough descriptions of the domain and informal analysis of the transactions of the domain, we abstract the following entities and their vocabulary (PS-12 Josélyne, M. I., Tuheirwe-Mukasa, D., Kanagwa, B., & Bali, P. 6: 956) ",None PS15,Class model,Example system," - A domain model in the form of UML use cases and domain classes is created (Chantamunee, S., Doung-in, S., Thanathamathee, P., Mahāwitthay, P. 2: 129)",Class diagram PS15,Class model,Example system," - Before the microservices are specified in detail, a UML profile for microservices is presented. UML profiles [14] are a light-weight mechanism for the extension of UML metamodel elements. (Chantamunee, S., Doung-in, S., Thanathamathee, P., Mahāwitthay, P. 2: 1585) ",None PS20,DDD Domain model,Industry system," - The first step in the modelling process involved translating the logical data model IMKAD (IMKAD, 2019) into a DDD domain model. IMKAD (2019) was in the draft version available during development. (Oukes, P., Andel, M. van, Folmer, E., Bennett, R., & Lemmen, C., P. 7: 969) - DDD primarily builds from a domain model divided into several subdomains (Oukes, P., Andel, M. van, Folmer, E., Bennett, R., & Lemmen, C., P. 7: 1551) ",None PS20,Use cases model,Industry system," - In retrospect, as Bittner and Spence (2003) described, it was essential to develop the Use Case model and Use Case specifications, from which the commands could be derived and the business rules and validation rules. (PS-20 Oukes, P., Andel, M. van, Folmer, E., Bennett, R., & Lemm, P. 7: 2880) diseño ",Use cases diagram PS22,Database model,Industry system," - As shown in Figure 4, the database schema is divided into three parts, similar to the results of DDD (PS-22 Fan, C. Y., & Ma, S. P. (2017). Migrating Monolithic Mobi, P. 3: 2378)",The have a relational model PS25,Database model,Industry system," - In order to realize the sharing, synchronization and updating of specimen data, this study designed the spatio- temporal database model of the SPDSWC based on the theoretical approach of spatio-temporal database (Fig. 4), established the spatio-temporal database and deployed it on the server (PS-25 Li, Q., Sun, W., & Ma, R. (2022). Sharing platform of dig, P. 4: 34)",None PS27,DDD Domain model,Industry system," - The migration process was carried out based on Domain- Driven Design (DDD), which helps to map business do- main concepts into software artifacts by dividing the domain model into multiple semantically consistent parts, the so-called bounded contexts [12] (PS-27 Batista, C., Proenca, B., Cavalcante, E., Batista, T., M, P. 2: 5279)",None