But in every Indonesia Email List company I’ve ever studied, there are only a few hundred key concepts and relationships that the entire business runs on. Once you understand that, you realize all of these millions of distinctions are just slight variations of those few hundred important things. In fact, you discover that many of the slight variations aren’t variations at all. They’re really the same things with different names, different structures, or different labels. So it’s desirable to describe those few hundred concepts and relationships in the form of a declarative model that small amounts of code refer to again and again. Software is just a means to an end. A business runs on data, and you make decisions based on data.
Keeping up with the growing volume of the rise
You should be employing software to gulf email list make better use of that data and create new data. You’ll need to unearth and inventory the rules in your enterprise, then determine which rules are still valid. The rules you keep the few hundred key concepts and relationships need to be declared at the data layer so they can be updated, reused, and managed. If you leave them buried in the application code, they won’t be visible or replaceable. In older systems, huge percentages of all of these buried rules are obsolete. They specified something that was true years ago. You don’t do things this way anymore, but you’re still supporting all that code and trying to manage the data associated with it. That’s just waste.
The rise will require delivery companies to disrupt their long
Tools that interpret legacy software help you comb through this code and find these little rules. Once you’ve done that, you do the same kind of rationalization and then some model-driven integration on the data side. Sifting through that amount of data and organizing it is a chore in and of itself, but incredibly worth doing, because if you don’t do it, next year it’s going to be worse. The model-driven integration that ties everything together takes the few hundred rules you’ve kept and maps them to the data you’ve rationalized. If the model- and data-driven approach I’m advocating is well designed and managed, the enterprise can end up with 50 or 100 tiny applets that each do one thing.