System development

Make – Not Buy
There are many reasons leading to the decision to have a complete software system developed, for instance, resource bottlenecks or strategic considerations. We come into play if you are convinced that the solution for your current problem can most likely only be achieved through
the development of individual software. No matter if your company is found in an industry we are already familiar with or not, the first step for us in any case is to listen to you and understand and internalise your world – even beyond the problem needing to be solved. We incorporate the information you provide us and first create a model of the application domain – what “things” are we talking about, how do things relate to each other, what terminology should be used, how can the specific problem be described, and what might a future solution look and feel like? In this context, depending on the complexity, we also consider the direct project environment: where are the risks, which interests need to be taken into account, which professional, technical and perhaps even which political framework conditions prevail. Based on this model of your domain, we then go through the classic phases of system development: collection and analysis of requirements, validation of requirements, system design, implementation, test, pilot or field test if necessary, followed by a rollout, training programme and support.

Procedure
Taking into account modern system development methodology and above all our own project experience, we prefer not to run through these phases sequentially (waterfall) but attempt to run through smaller subsets of the phases using agile process modules from, for instance, Kanban or Scrum iteratively over shorter periods in tandem. With this procedure, we can be more efficient in reacting to changes and you have better options for reacting to changes by faster feedback cycles if the respective project status does not meet your expectations or other ideas begin percolating. Agile procedures and strict classical process specifications are not necessarily mutually exclusive. We have experience with process models for processes that can be certified, such as DO 178 B or the requirements of the MPG, which we have brought to a successful conclusion, both in line with the process manual and through the incorporation of agile elements. Insofar as we are not bound by any specifications from you or external framework conditions, we prefer to work over short release cycles whose development we organise according to Kanban.

If you entrust us with the full development of a system you need, then we take care of the daily detailed work, but keep our eyes firmly set on the overarching goals and the bigger picture. We have mastered the implementation of server-based multi-tier (database) systems that users access via a web browser, mobile app, client application, or a combination of these. We are also well versed in the development of standalone applications and/or tools for PCs. Our profile is rounded off by Baun’s ability to build embedded systems on more or less powerful devices such as SOCs or other IoT devices. Depending on your specifications, the project preparation or our own best practices, we work with the Strack Technologies that promises the best results for your project. We can use Java, C/C++, ObjectiveC, Swift and .NET/C#, on Windows, Linux or Mac OS, for the web, as an app, on the server or as a client application, store data in Oracle, MySQL, HANA, or in files, native or dockerised.
Depending on your requirements, we can also take care of accompanying material such as user or admin guides, create training documents and hold training courses, organise the rollout and support for you, or administer your markets.