How to figure out correct interfaces for a component in UML component diagrams?
I have a doubt about UML component diagrams interfaces. I have a search component in my system which is responsible for search some product from the database and return the search result to the user. I have drawn search component in 3 different ways as I understood. I want to know which way is the correct one and best in practice and why others are not correct.
In this case I thought search component provides a Search interface to other components like User and they use that Search interface to search. Also the user passes search parameters through that interface and get the result through that interface as well.
In this case I thought Search component provides Search interface and and User uses that interface to pass search params. And it fetch data from the database. Then User component uses Search result interface to get the search result.
In this scenario, I thought Search component need search params to search something. So, It requires Search params. Therefore, I added Search params required interface. After fetching data Search component provides that result. So, I've added provide interface named search result.
These are the ways I thought about this Search Component. I don't have a Idea which one is the correct one. Please explain which one is the correct one and why others are not correct.
Thanks!!!
Lollipops and sockets do not tell what goes in and out but who provides or needs the interface definitions. So, simply spoken, the first variant would be correct. The Search interface offers some search(...) operations which yield some result. And the data must be provided via the Data interface. The component's task would then be to implement a search on data according to these interfaces.
It would help you if you would place the «interfaces» near the socket/lollipop and draw dependency/realization accordingly. For example like this:
- Why no compile error at CustomerService service = ServiceFactory.getInstance().getServiceType(ServiceType.CUSTOMER);
- Can a TypeScript interface be spread into another interface?
- How can I implement Interface for Node class
- Do PHP interfaces have properties?
- Map Properties Of a class to an interface
- Not implementing all of the methods of interface in Java, is it possible?
- How to only allow implementations of an interface in the same package
- Is it possible to use getters/setters in interface definition?
- Do all static members defined in an interface have to be defined with default implementation?
- Is there a language feature like Python's `issubclass` to cast instances of System.Type to the actual type (to access static methods w/o reflection)?
- How to extend a class in python?
- Interface naming convention Golang
- Requiring interface implementations to have a static Parse method
- In C++, is there a way to provide object member name as template parameter?
- Why are interfaces static?
- Struct field with multiple const types
- Wrapping a library using interfaces without needing downcasts
- Error when converting BehaviourSubjects in Angular
- Implementing two interfaces in a class with same method. Which interface method is overridden?
- Explanation of checking if value implements interface
- Spring Boot 3.4.0 Broken HTTP interface
- How to create an interface which is an array of a simpler interfaces?
- Typescript Interface SyntaxError: Unexpected identifier at interface name
- Is there such a thing as a "local interface" in Java?
- How does template specialization work for hierarchies of template classes?
- IntelliJ IDEA 'class' or 'interface' expected
- Is there a way to make sure classes implementing an Interface implement static methods?
- Optional Methods in Java Interface
- Two interfaces with same method signature implemented in Java class
- Using equals to compare map values returns false even when values and insertion order are the same