MVC assumes one application and one set of users. A framework design study shows what to add when neither holds.
There is a moment in every framework project when the team realises the standard pattern does not cover what the business actually does. The instinct is to start over. A study from Universitas Brawijaya argues for a smaller move.
Their starting point is ordinary. Web applications are the practical answer when units inside an organisation keep changing how they work. Information systems sit at the centre of that, supporting processes that shift as the organisation does.
Model-View-Controller is popular for good reasons. Splitting an application into model, view and controller makes the parts reusable and maintainable, and it keeps a change in one place from rippling into the others.
Two things are missing. One is business process choreography, the coordination of steps that span more than one system. The other is integration between applications. Neither is a display problem, so neither belongs neatly in the view or the controller.
The wider lesson is about how to touch a design pattern at all. Changing how objects of a class interact is exactly the kind of edit that breaks assumptions across a codebase, so the team's proposed pattern is a derivation, not a rewrite.
Aryo Pinandito, Ferdika Bagus Pristiawan Permana and Rizal Setya Perdana (2017). Framework Design for Modular Web-based Application Using Model-CollectionService-Controller-Presenter (MCCP) Pattern. Journal of Information Technology and Computer Science, 2(1), 41-65.
