Is it a DAO? As already mentioned, the DAO standard is used to separate APIs or data access operations (low level) from business logic (high level). Simple like that! An approach to implementing this pattern would be: An interface, a concrete class to implement it and a VO (Value Object), the latter being a POJO that will contain only attributes, getters, setters and nothing else.It will be Date Mapper? Imagine on one side a model class (the good and old POJO) and on the other side the database. In the middle, "mappers" objects that move the data between the objects of the model and the base, keeping one independent of the other. Well, simply that would be the essence of a Data Mapper. This pattern can become costly according to the complexity of the relational model.How is this object called?In the case of CentralDeAlarm, would be one D, or a BOY or who knows a V...DTO (Data Transfer Object) - Simple object to transfer data from one side to the other in the application.BO (Business Object) - Encapsulates business logic for an object. It contains only the properties of the business object, contains only business methods or both.VO (Value Object) - Used basically to display data in the presentation layer (there are controversy). In fact, the CentralDeAlarm object looks like a DTO.What is it called the pattern represented by this class?Something like a DAO or with particularities of one. As we know, Standards are not written on the rock. It will be that this approach, within a specific context, represents an evolution for something better. You're...