![](\"https:\/\/referenzen.mgm-tp.com\/wp-content\/uploads\/Infografik.jpg\")
Requirements and key challenges<\/h3>\n
After an internal analysis had been conducted, there was a preference in terms of application development for a Java-based open source portal system. However, it was questionable whether or not the functionality of the Content Management System (CMS) supplied was sufficient to address the given requirements.<\/p>\n
The following – not untypical – challenges faced the joint team:<\/p>\n
- \n
- A high degree of innovation:<\/strong>
\nLimited experience with the portal and CMS technologies to be selected.<\/li>\n- Complex requirement management:<\/strong>
\nA high number of applications for potential integration by a range of different departments.<\/li>\n- Technical uncertainty: <\/strong>
\nLack of maturity of standard open source products available, for example documentation still in preparation.<\/li>\n<\/ul>\nProof-of-concept by means of functional prototyping<\/h3>\n
\u201cAfter initial consolidation of the requirements, we followed the recommendation of mgm to try out the interaction of various CMS with the portal system using functional prototypes\u201d, Frank Mielke, project manager for HanseMerkur, states.
\nThe decision-making process comprised the following main working stages:<\/p>\n- \n
- Draw up relevant use cases.<\/li>\n
- Derive critical functionality, assess relevance to decision.<\/li>\n
- Technical realization of application examples with documentation of results.<\/li>\n
- Presentation of decision matrix for portal- and CMS-selection.<\/li>\n<\/ul>\n
Within two months it was possible to arrive at a binding decision on the technology to be used. The chosen decision-making process also allowed outstanding weak points to be identified and taken into account in further project planning.<\/p>\n
Chosen development approach<\/h3>\n
HanseMerkur is planning to implement various applications in the portal, so jointly a development approach was selected which provides for intensive communication with departments close to sales operations.<\/p>\n
Similarly to the functional prototyping used in the proof-of-concept phase, the defined processes were visualized for departments and subsequently developed.<\/p>\n
The architecture of a portal application and its integration as a future component of the portal are crucial to technical implementation. For this reason, the philosophy adopted required a conceptual breakdown of an application into reusable portlets with a definition provided for their various interfaces. The main advantage here was to achieve a controllable degree of complexity in development and in later operation. Even after a short time it was possible for application development to integrate two use cases of the existing business intelligence solution into the portal as a spike application.<\/p>\n
In terms of the serviceability and development process of the portal, mgm recommended a separate portal application development operation. This allows for the greater interdependence of individual portal applications. For example, changes to the rights concept or distribution of page reproduction caused changes across several portal levels and instances. Portal aspects were added to the automated build and release management function, which already exists in the HanseMerkur environment, and harmonized with the internal editorial process. In this way, portal content and individual portlets can be incorporated.<\/p>\n
Results<\/h3>\n
Within the limited amount of time available, mgm assisted the HanseMerkur team in the selection of suitable technology as well as the preparation of a development approach compliant with the organization. As a result, the first portal application – the corporate website www.hansemerkur.de – was brought into production within only three months.<\/p>\n
\u201cmgm technology partners, within a short amount of time, helped us acquire the necessary insights and knowledge to prepare us for the operation of a portal at HanseMerkur\u201d, summarizes Dr. Horst Karaschewski, Manager of application development at HanseMerkur, the project.<\/p>\n
* This reference has been officially confirmed by HanseMerkur Versicherungsgruppe.<\/p>\n
[\/et_pb_text][\/et_pb_column][et_pb_column type=”1_3″][et_pb_text use_border_color=”off” module_class=”sidebar” background_position=”top_left” background_repeat=”repeat” background_size=”initial” _builder_version=”3.1.1″]<\/p>\n
![](\"https:\/\/referenzen.mgm-tp.com\/wp-content\/uploads\/Hanse-Merkur-logo_500.png\")
<\/p>\nThe HanseMerkur Insurance Group in Hamburg is Germany\u2019s second oldest private insurance company and well-known for its powerful standing in the market for supplementary insurance. HanseMerkur mainly markets its products indirectly through partners such as brokers, cooperation partners and agencies who are provided with individual support by the HanseMerkur sales department.<\/p>\n
<\/p>\n
- Complex requirement management:<\/strong>
![](\"https:\/\/referenzen.mgm-tp.com\/wp-content\/uploads\/HanseMerkur-Download-1.png\")
<\/p>\n