Research Article
An Approach for Reconstructing Applications to Develop Container-Based Microservices
Table 1
UML design data collection and hierarchy mapping.
| Type | Description | Mapping layer by |
| <<Boundary>> | Class stereotype related to input/output (e.g., main screen UI and billing popup window) | Presentation layer |
| <<Control>> | Class stereotypes (e.g., payment, reservation, and membership process controller) that realize main function of application | Business logic layer |
| <<Entity>> | Class stereotypes for accessing and controlling the database (e.g., save member information and register reservation information) | Persistence layer |
|
|