The connected car can be defined as a car that can communicate with other systems, services or devices via a network. Today millions of connected vehicles can interact bidirectionally with any system over the internet. Bandwidth and costs for data transmission are no bottle necks anymore.
Therefore, it is quite essential to keep up with the cutting-edge technologies before the implementation turns to a legacy system. Concept Reply is specialized on IOT and has a great track record in the automotive industry – especially with developing vehicle connectivity solutions.
The need to transform an IT system can have various reasons: Better performance to handle new requirements, no flexibility to connect and/or expand within the IT architecture, no cloud support/ connection possible or simply costs to react onto new market demands.
Scalability and security aspects are very often underestimated by sizing an IT system to deliver a specific use case. Additionally, what needs to be considered, is the changing way of developing software (agile methods) or how to write and test code. And probably combined with edge to cloud technologies.
Many more examples can be added. Those are the main problems of legacy systems and most of the time since the legacy systems are running on production environments, it is not an easy task to replace them.
Moving to the new technologies is an important and difficult challenge in multiple aspects. Especially in such a fast-moving market like the connected car, where OEM´s must plan years in advance and size IT systems according to future demands and customer requirements.
Cloud computing (e.g. AWS, Microsoft Azure) massively drives development of software in order to scale and reduce admin effort and costs. CI/CD pipelines (e.g. Jenkins, Bamboo) help to avoid manual deployments. Modern infrastructure is created on Containers (e.g. Docker, Podman) to run software independently and NoSQL databases are there to store and get data faster as the total amount of data is continuously rising.
There is also important trend in software development from structured programming languages to functional programming languages. Additionally, it is necessary to follow design patterns and clean code principles in the implementation as well as code reviews and test coverages.
In waterfall methodology, there are one purpose or separated teams, covering certain responsibilities e.g., data analysis, design, development, testing and quality insurance. They are dependent on each other as the nature of sequential huge steps of the waterfall methodology.
On the other hand, in agile methodologies, there are small, cross-functional, self-organized teams of size 6 to 9 people. The methodology itself is iterative and in the end of each iteration there is a deployable piece of product. It has many advantages over waterfall, such as continuous development, testing and deployment iterations of the software even from sequential huge phases as well as flexibility to adapt the requirements changes.
The people are playing the most important role in the process of transformation. However, people in their comfort zone, working in the same area for a long time, closed to learn new technologies, against automation due to possible loss of occupation, offensive for criticism (code review comments, etc.) make it more difficult and long running process for switching to the cutting-edge technologies.
Concept Reply is an IoT software developer specializing in the research, development and validation of innovative solutions and supports its customers in the automotive, manufacturing, smart infrastructure and other industries in all matters relating to the Internet of Things (IoT) and cloud computing. The goal is to offer end-to-end solutions along the entire value chain: from the definition of an IoT strategy, through testing and quality assurance, to the implementation of a concrete solution.