Loading...

Digital Platforms

Your experts for developing digital platforms.

Your experts for developing digital platforms.

Teaming up with you, we analyse your requirements and design and develop your customised platform to suit your needs. We’re your partner for designing, developing, maintaining and providing support for your platform.

Our many years of experience mean we can help you to manage your data efficiently and provide it to your users – on time, anywhere. Our systems help you keep track of everything, even with very high volumes of data. Our digital platforms are scalable and grow as you do. Larger data volumes, changing requirements and new functions, increasing user numbers – all this goes without saying and is our goal right from the start.

We’re conscious of how important openness is and can work flexibly with interfaces to existing systems. Reinventing the wheel is not on our agenda; we want to get the ball rolling for you. Our optimal way forward – focussing on what we do best, and using other’s excellent products to solve the remaining tasks.

But openness means more than that to us: open, honest and trust-based cooperation with you is our modus operandi and underpins our long-term success. It’s also reflected in our corporate guidelines.

In collaboration with our customers, we’ve developed and supported a wide range of successful software solutions.
Find out more about our customers and the projects we’ve implemented.

We employ a transparent approach to our software development projects. This enables us to perform projects with our customers in a structured and efficient way. We keep a close eye on treating our customers fairly and for minimising their project risks.

Projects run through the following phases:

Assessing requirements

At the beginning of a software development project, mbi focuses on the requirements phase. The technical requirements of the customer are compiled and coordinated in a technical concept. Often a joint conceptual workshop is held to coordinate the requirements and framework conditions.

Delivering

The version accepted by the customer is delivered in an installation package for activating the system. If required, we can also perform or support the software rollout. Detailed technical documentation, as well as a user manual, are created and provided to the customer.

Testing

After completing the features the software is checked by our quality assurance. Errors are reported to the development department and are retested after successful correction. After the checks have been completed by our quality assurance, a test version is created for the customer. Faults can be efficiently corrected by utilising an error management system. When the customer accepts the system, the test phase is completed.

Developing

The system is developed based on the detailed concept. Current and robust technologies are used, and we attach great importance to adhering to our source code conventions. In feature-based programming, the development steps are regularly checked and controlled. Continuous project management, together with regular status reports for the customer, provide a high degree of transparency.

Designing

In the conceptual phase, a detailed design is created by collaborating with the customer. The structure and functionality of the future system are described in as much detail as possible. Prototype screens are created and integrated into the detailed concept to illustrate the system to be implemented. The detailed design is presented to the customer in a meeting and agreed upon together. The conceptual phase is concluded when the customer gives its final approval.

Commissioning

Based on the technical requirements, the results of the conceptual workshop and ultimately the resulting technical concept, an offer for a detailed design can be made. In addition, this stage includes a cost estimate for the development phase. To guarantee our customers a reliable basis for financial planning, we aim to submit fixed price offers.

Assessing requirements

At the beginning of a software development project, mbi focuses on the requirements phase. The technical requirements of the customer are compiled and coordinated in a technical concept. Often a joint conceptual workshop is held to coordinate the requirements and framework conditions.

Commissioning

Based on the technical requirements, the results of the conceptual workshop and ultimately the resulting technical concept, an offer for a detailed design can be made. In addition, this stage includes a cost estimate for the development phase. To guarantee our customers a reliable basis for financial planning, we aim to submit fixed price offers.

Designing

In the conceptual phase, a detailed design is created by collaborating with the customer. The structure and functionality of the future system are described in as much detail as possible. Prototype screens are created and integrated into the detailed concept to illustrate the system to be implemented. The detailed design is presented to the customer in a meeting and agreed upon together. The conceptual phase is concluded when the customer gives its final approval.

Developing

The system is developed based on the detailed concept. Current and robust technologies are used, and we attach great importance to adhering to our source code conventions. In feature-based programming, the development steps are regularly checked and controlled. Continuous project management, together with regular status reports for the customer, provide a high degree of transparency.

Testing

After completing the features the software is checked by our quality assurance. Errors are reported to the development department and are retested after successful correction. After the checks have been completed by our quality assurance, a test version is created for the customer. Faults can be efficiently corrected by utilising an error management system. When the customer accepts the system, the test phase is completed.

Delivering

The version accepted by the customer is delivered in an installation package for activating the system. If required, we can also perform or support the software rollout. Detailed technical documentation, as well as a user manual, are created and provided to the customer.

Our many successfully performed software development projects and our satisfied customers regularly confirm this tried and tested approach.

In a dynamic and rapidly changing world, software requirements can also change, or are still unclear at the beginning of a project. Based on agile values, we use methods and tools that allow our customers to remain flexible and actively participate in the progress of the software development project. This enables us to sharpen our view for the greatest possible use of the software and to react promptly to changes.

We use the following, in addition to other agile methods:

Shortdevelopment cyclesSoftware functions are developedin iterations of a few weeks.The main focus here is gettingour software up and running anddelivered to our customerswithin short turnarounds. Wecan thus incorporate feedbackinto the development process,and continuously improve thesoftware quality.ContinuousIntegration (CI)Our software developers work ona common source code level inkeeping with standardised sourcecode conventions. This is qualityassured by automated tests andanalysis for each change and isfully integrated with all thecomponents. Working like thisprevents the incompatibility ofsoftware components and delaysfurther down the line.ContinuousDeployment (CD)Right from the start, we focus onbeing able to deliver the developedsoftware to our customers at anytime. For this purpose, the deliveryis automated up to the finishedsetup, or up to the functioning webapplication. Quality assurance alsobenefits from the constantly updatedsoftware status, which occursseveral times a day.Feature DrivenDevelopmentFeatures are at the heart of feature-driven development. The entireproject is broken down into features,with each feature offering addedvalue to the customer. Features arealso kept small enough to allowimplementation within a few days.This contributes to short developmentcycles with software that can berun at any time.Inter-functionalteamsOur teams are multi-skilled andconsist of software analysts, softwaredevelopers and testers working closelyto deliver the best possible softwareto our customers. Direct channels ofcommunication ensure that all projectparticipants can always keep trackof a project’s progress.Test-drivendevelopmentIn test-driven software development,automated software tests are createdbefore the actual program code. Thisis particularly useful for complexfunctionalities, for which expectationsof the software are clearly definedin advance and are required of the,as yet, unwritten code.RefactoringsRegular refactorings are an integralpart of our software development andincrease code quality as well aslong-term maintainability andexpandability of the software. Bycovering the source code withautomated tests, we guaranteepermanent functionality despiteregular refactorings.Code Reviews“Two heads are better than one”is the saying – one which fitshere, with code reviews offeringmany benefits in the softwaredevelopment process. By regularlyreading and reviewing code ofother software developers, codequality is improved, problems areidentified early on and understandingof the overall project is boostedwithin the team.Regularproject reviewsAfter each development cycle, feedbackfrom customers and the softwaredevelopment team is collected,discussed and concrete steps arerecorded. The foundation for acontinuous improvement of thesoftware and the software developmentprocess is thus already laidduring the project term.

Short development cycles

Software functions are developed in iterations of a few weeks. The main focus here is getting our software up and running and delivered to our customers within short turnarounds. We can thus incorporate feedback into the development process, and continuously improve the software quality.

Continuous Integration (CI)

Our software developers work on a common source code level in keeping with standardised source code conventions. This is quality assured by automated tests and analysis for each change and is fully integrated with all the components. Working like this prevents the incompatibility of software components and delays further down the line.

Continuous Deployment (CD)

Right from the start, we focus on being able to deliver the developed software to our customers at any time. For this purpose, the delivery is automated up to the finished setup, or up to the functioning web application. Quality assurance also benefits from the constantly updated software status, which occurs several times a day.

Feature Driven Development

Features are at the heart of feature- driven development. The entire project is broken down into features, with each feature offering added value to the customer. Features are also kept small enough to allow implementation within a few days. This contributes to short development cycles with software that can be run at any time.

Inter-functional teams

Our teams are multi-skilled and consist of software analysts, software developers and testers working closely to deliver the best possible software to our customers. Direct channels of communication ensure that all project participants can always keep track of a project’s progress.

Test-driven development

In test-driven software development, automated software tests are created before the actual program code. This is particularly useful for complex functionalities, for which expectations of the software are clearly defined in advance and are required of the, as yet, unwritten code.

Refactorings

Regular refactorings are an integral part of our software development and increase code quality as well as long-term maintainability and expandability of the software. By covering the source code with automated tests, we guarantee permanent functionality despite regular refactorings.

Code Reviews

“Two heads are better than one” is the saying – one which fits here, with code reviews offering many benefits in the software development process. By regularly reading and reviewing code of other software developers, code quality is improved, problems are identified early on and understanding of the overall project is boosted within the team.

Regular project reviews

After each development cycle, feedback from customers and the software development team is collected, discussed and concrete steps are recorded. The foundation for a continuous improvement of the software and the software development process is thus already laid during the project term.

From comprehensive business web applications to backend development and complex, desktop-based client-server systems, mbi GmbH offers a broad and comprehensive range of solutions.

When implementing database-type systems, our team also draws on many years of experience in dealing with relational database systems.

We have developed and accompanied countless successful software solutions together with our customers.

Do you have any questions?

Our team will be happy to help you.

Call us.
We’re ready to take your call Mon-Fri 09:00–17:00.

+49 (0) 6441 7809-0

Send us a message.
We promise a swift response.

Contact

back-to-top