Leader in the European structured finance software market
Our clients’ needs
are our key incentive
How we work
Project approach. Our project approach is pragmatic and result driven. We believe that the most effective way to bring value to a client is to become its partner. Each project gives us the opportunity to transform the client’s mindset as well as our own, thereby shaping agendas and enabling meaningful, enduring impact.
Consultancy services. Our key focus is on consultancy services and analytical studies related towards the structured finance market and our software platform PRoMMiSe. For a number of key originators in the market portfolio mark-to-market valuations are carried out periodically. We also have experience in treasury topics, such as asset allocations, IFRS treatment and (pipeline) funding gap analysis. Hypoport can support originators, investors and other market participants with day-to-day administrative and management roles.
- Continued due diligence and verification of servicer data
- Cash reconciliation per loan
- Eligibility criteria verification
- Active origination tracking to ensure balanced portfolio build up
- Portfolio reporting
- Valuation and risk analysis
- Preparation for portfolio term-out
- Preparation and brokerage for private placements
- Stress-testing on loanlevel and portfolio level
PRoMMiSe development. Hypoport has been using the Agile/SCRUM methodology when it comes to software development. In short this method forces us to work in very short iterations (in our case 2 weeks) whereby after every iteration there is a potentially shippable product. This allows for frequent feedback and interaction between the developers/ information analysts and the customer, thereby detecting gaps between requirements and delivered code early on, minimizing the risk of projects running long and over budget resulting in:
- Better communication
- Better sprintresults and a lot more output
- Faster & higher quality to the market
- More fun in the process of creating new product and/or services
- Enriched working climate
Customer satisfaction is what drives us
Test Management / Quality Assurance. Quality control is key for PRoMMiSe development and testing in the continuous development- & improvement cycles Hypoport uses the Team Foundation Server suite of products for its source code control and work planning, this Microsoft product integrates very well with Visual Studio (our development tool) and Microsoft Test manager (our test platform). The scope of Hypoport’s testing is strategic.
Our specific testing services include: performance, regression and unit testing – read more about it below:
Is generally executed to determine how PRoMMiSe performs in terms of responsiveness and stability under a particular workload. It can also serve to investigate, measure, validate or verify other quality attributes of the system, such as scalability, reliability and resource usage. Data upload testing is primarily concerned with testing that the system can process all the data within a certain time interval. Changes in business logic can increase the time it takes to load all the batch data into the system. These tests determine this increase stays within acceptable limits and do not disrupt the rest of the work flow.
Regression testing focuses on finding defects after a major code change has occurred. Specifically, it seeks to uncover software regressions, as degraded or lost features, including old bugs that have come back. Such regressions occur whenever software functionality that was previously working, correctly, stops working as intended. Typically, regressions occur as an consequence of program changes, when the newly developed part of the software collides with the previously existing code. Common methods of regression testing include re-running previous sets of test-cases and checking whether previously fixed faults have re-emerged. The depth of testing depends on the phase in the release process and the risk of the added features. They can either be complete, for changes added late in the release or deemed to be risky, or be very shallow, consisting of positive tests on each feature, if the changes are early in the release or deemed to be of low risk.
Unit testing is often used as part of regression testing by (automatically) testing small pieces (units) of code. Every new or changed piece of code our software engineers store in our source code control system (Team Foundation Server by Microsoft) gets automatically compiled by our build server to determine if it does not break existing code on a syntax level. In other words making sure the new code is valid. Having the code built automatically saves the engineer time: he does not have to check with all of his or her colleagues whether or not his changes have adverse effects: the build server will tell him immediately. Automatically testing existing functionality by way of unit testing yields several benefits: should new code break existing code the engineer is notified immediately instead of when the new software is released to the client which could be months later. As the code is still ‘fresh’ in the engineers mind, fixing it right away will save time. Furthermore, automatically testing existing functionality saves up time to test new functionality or spend more time testing modules that are difficult to test automatically. Lastly, having code unit-tested forces the engineer to think of his work in small(er) units reducing the risk of creating long, complex pieces of code which get harder and harder to debug over time.