When developing an application using the MVC pattern, I often find myself adding a new model, a new controller, and a new set of views for the actions in the controller.
These changes are pretty atomic, as a new model is no use without changes a new controller (or at least changes to an existing controller). Similarly, I'm probably going to need some new views to make the most of my new model.
My problem is what to call this collection of things?
- Module, but this implies more, um, modularity than is strictly appropriate (I'm not building anything so loosely coupled that they'd work in other systems without modification)
- MVC triplet, which feels clumsy and glosses over the fact that the V part will expand to several things (i.e. it's not just three artefacts we've created).
- I've toyed with words like unit and entity too, but worry that these are already tightly associated with existing concepts (testing and framework respectively).
Is there an agreed upon name for this? If not (without wanting to become opinion-based) what do you call it / hear it called?