Posts related to application support, how to make it easier and more transparent
There are activities that dramatically improve the outcomes when a priority issue arises with the enterprise platform.
We believe that simplification of solution design, including clean separation of concerns, and relying on automated unit testing are the keys to long-lasting, low cost platform support.
In a recent engagement, we delivered a suite of custom PFE (potential future exposure) risk reports to a client including about 500 JUnit automated test cases.
Most Openlink clients report frustration with the difficulty of introducing a new financial instrument to the application.
Over time, messy code gets messier. The problem with deteriorating code is that future enhancements and bug fixes take longer and longer to deliver.
Code duplication can arise fairly easily when more than one developer is working on a project. The simple solution is for developers to collaborate to a minimal degree, to subject code to consistent standards, and to have a code reviewer enforce standards.
Modern project management methodology and development techniques are able to mitigate the concern that business leaders have when they find it necessary to extend enterprise software functionality, or integrate an enterprise application with a new platform to handle niche functionality.
In this paper, we describe no technology, technique or pattern that is bleeding-edge, or in any way controversial.
Sim Tasks are a business object in Openlink’s system that handles end-of-day and ad-hoc simulations.
Compared to the previous method, sim tasks are easy to create on-the-fly via API for a newly created portfolio.
Sim tasks are also easy to execute from the desktop and via API.
Do not use Openlink’s Table.select(..) method. Retire the Table.select(..) technical debt to the ash heap to which it belongs.
