Design pattern for grouping resources and functionality

Imagine you have a WinForm with a PictureBox. That PictureBox has an image associated with it (displayed on it) and a click event that does something and calls other methods and etc.

I was wondering if there is some sort of design pattern or best practice on how to group all these resources and functionality so that it would be apparently clear what uses what, without having to delve into the code.

I could just write dev documentation but I wondered if there is some other way to do it. Of course my resource and method names are using proper coding conventions, but I imagined something that can tell me "this picture box uses this image, calls this method on click and that click methods calls etc...".