We can reduce these diagrams’ complexity by filtering the information in them.
	For example, TogetherSoft first shows everything, and then lets the programmer to filter out the parts of the diagram he doesn’t want to see.
	But this is not a very natural way of getting to the diagram the programmer wants.
	Instead, if the tool knew why the programmer wanted the diagram, it could create a diagram with only the relevant information.
	I’d like to explore the approach that starts with nothing and tries to show the programmer only what is relevant, instead of starting with everything and asking him to filter out what’s not.