Business Applications

Process-oriented Implementation of Business Application Software

In many companies the implementation of business application software causes an inner breaking test: The planned project term is exceeded and the budget that was fixed in the run-up is blasted. The reasons are versatile. The business processes mapped in the business software are not consistent with the businesses processes, but they can only be adapted within fixed boundaries. The lacking transparency and a heterogenic IT system landscape demand for complex and time-consuming interface solutions. In addition, unclear requirement definitions from the departments delay the project. These obstacles can be overcome with a process-oriented implementation of the business software.

Minimize Project Terms, reduce Complexity, and ensure Quality

By using branch-specific Business Process Models in connection with Business Service Models the complexity of the implementation is drastically reduced. The project is accelerated and due to clear and structured documentation the result’s quality is noticeably increased. The key techniques of this approach are reference models, such as the Horus Knowledge Bases. These are geared to basic processes that are configurable with the modules of the respective business software, e.g. Oracle Applications. Therefore, unclear descriptions regarding functionalities and processes are avoided from the beginning. Now nothing can get in the way of a mode-based implementation of application landscapes and business process-oriented integration solutions.

Migration and Process Optimization in One

A process-oriented approach does not only bring advantages when implementing application software initially. The migration to a new release often comes along with an update of basic technologies and functional upgrades. Therefore it is necessary to examine the migration from a professional point of view. In order to optimize processes it is sensible to do the reengineering in the run-up to the migration. By means of model-supported documentation, problems are grasped at the basis and can be solved immediately.