Skip to main content

New answers tagged

4 votes

Mixing up UML and non-UML diagrams

Diagrams are only tools to express ideas, and you should always use tools that best suit your needs. Some modeling languages, such as C4 even explicitly foresee a mix of diagrams, with high level ...
Christophe's user avatar
  • 78.3k
4 votes

Mixing up UML and non-UML diagrams

Someone did a survey : A survey on the practical use of UML for different software architecture viewpoints While the top popular viewpoints for the UML-based software architecture modeling are the ...
Ewan's user avatar
  • 77k
5 votes

Mixing up UML and non-UML diagrams

Design documentation is meant for people. Machines don't care. People care because these documents help them build the system or maintain it. Worse case scenario, the documents are a box-ticking ...
Greg Burghardt's user avatar
0 votes

Why are there two abstract interfaces in the observer pattern?

Subjects and Observers don't exist by themselves The abstract Subject interface doesn't exist to decouple ConcreteObserver from ConcreteSubject, but to decouple the source of notification triggers ...
Ben Cottrell's user avatar
  • 11.9k
1 vote
Accepted

Why are there two abstract interfaces in the observer pattern?

Lets use the wikipedia diagram. Here the diagram clearly shows observers calling the getState method on the concrete Subject1 class. A method which is not on the subject base class/interface, so it ...
Ewan's user avatar
  • 77k
-2 votes

Why are there two abstract interfaces in the observer pattern?

The abstract observer and subject allow to specify the general interaction principle (contract) that all subjects and observers must implement, i.e. registration and notification, while leaving ...
Christophe's user avatar
  • 78.3k
-2 votes

Why are there two abstract interfaces in the observer pattern?

Things that interact must be coupled in some way. Much of software engineering is about how to keep the coupling to the minimally necessary one-way coupling. Implementing state change propagation in ...
Kilian Foth's user avatar
2 votes

Confirmation of the request with the client. Use use case diagram or not?

Use case diagrams don't have much value for any purpose. I'd point out some words from Martin Fowler: Use cases appear in the UML in the form of use case diagrams, but these diagrams are of little ...
Thomas Owens's user avatar
  • 83.3k

Top 50 recent answers are included