Defining object definition scope based on domain

Question

I had an architecture question about how to manage objects with different properties based on the services they are in. Is it okay to have an object defined in to different places with similar attributes but different scope based on the service.

As an example, a car has many parts. You might make a service that returns Car objects that them different attributes (Maker, Model, Parts, Color, etc).

Another service is made that returns Parts and attributes (Maker, Material, Appropriate Cars, etc.)

I understand that creating a Car Object with a list of Parts and a Parts object with a list of Cars will just cause the thing to blow up, I figure that there must be a better way to define the link.

For Car would a CarPart object with just information relevant to the part without the list of cars work? Same with a ApplyableCar object for the Parts object?

Any suggestions are helpful

Answer 1

It seems you are trying to define objects based on what data they have inside. This is not an object-oriented design process, therefore it will most likely not work in this context.

You have to think about two things:

1. Whether the object is something business-people familiar with your domain would understand.
2. What behavior (i.e. methods) those objects need to exhibit, again, that business people would understand.

These properties should hold for all objects in your project.

To your first question, it might be the case that the same concept ("Car" for example) might have different behavior (means different methods, different class) in different parts of an application. It usually happens when multiple business units try to collaborate in a project, it is however unlikely in smaller applications.