Question

Let’s say that I want to implement following interface:

public interface ICar
{
   bool IsMoving();
   bool IsRegistered();
   int CurrentSpeed {get; set;}
} 

   public class Car : ICar
   {
       public int CurrentSpeed {get; set;}        
       public bool IsMoving()
       {
         // some logic here
       }
   }

Does this IsMoving() method break poco definition?

Answer 1

Check this link DTO ver POCO

POCO vs DTO

The cite (but read the link and follow other links there)

…A POCO follows the rules of OOP. It should (but doesn’t have to)
have state and behavior. POCO comes from POJO, coined by Martin
Fowler…

Other words, it is absolutely OK, if POCO has behavior. The requirement for POCO is unaware of the persistence