What are the key challenges?

Address tightly coupled MVC components where records bind to specific forms, form sections tie to business object fields, forms cannot be replaced without breaking workflows, requiring decoupling into separate components.

In other words, MVC components are too tightly coupled to each other. We have too many elements in the model (business objects) and controller (workflows) that directly impact the view (forms) and vice versa.

Here are a few examples:

  • Records are bound to a single specific form.
  • Form sections and fields are tied to BO sections and fields.
  • Forms cannot be replaced without breaking workflows.
  • The Modify Metadata task in the workflow is tied to a single form.

Now, if we redraw the basic MVC diagram with this lack of separation, our existing Maximo® Real Estate and Facilities framework might look similar to this. As you can see, the key challenges lie in decoupling these interconnected pieces into their separate MVC components. This is where UX comes in!

Basic diagram with lack of MVC separation