Concept classix
motivation
The use of so-called "standard solutions" is beyond question for many corporate decision-makers. Behind this is the idea of "not wanting to reinvent the wheel again and again", but certainly also the experience that individual software development processes were and are not always completed on time or on budget.
Consequently, a wide range of application solutions with extensive functionality are available in the operational environment.
Many of these application solutions each fulfil specific, clearly defined tasks. If your own requirements differ from these, you have the choice of orienting the processes in your company according to the software or you try to find a software on the market that is better suited to your own company.
If one finds the standard solution that fits one's own company perfectly, the introduction of this new software more or less establishes the image of one's own company that is valid at that time.
The not infrequent desire of users for an "egg-laying wool-milk sow" is dismissed by the manufacturers of application solutions with this very term. Nevertheless, efforts are made to anticipate and ultimately implement all possible user ideas by means of parameterisation.
There is no clear answer as to whether a deployed application solution is efficient and at the same time user-friendly; opinions on this often differ widely. But simply having a quick and easy way to set up, improve or customise application solutions would be desirable.
The emergence of "object orientation" in the early 1990s was seen in the software industry as a paradigm shift in its own development processes. Especially in the field of business software, there was a conviction that a changed - i.e. object-oriented - view of the processes to be modelled, of the application solutions to be created, would provide a more modular, easier to configure and thus more suitable software for the requirements of the users.
A prominent example of this was the "San Francisco project" initiated by IBM. Within the framework of this project, "business objects" were developed that could be freely combined to create finished application solutions. After completion of over 7000 different classes with over 35,000 methods, the project was discontinued.
From our point of view, the "flexibility" of standard market software solutions is rather limited, but our concept classix had and still has the same objective as the "San Francisco project": to be able to digitally transform and maintain complex business processes quickly and efficiently.
The concept classix was successfully implemented and is characterised in particular by a high degree of rigidity in the abstraction of the company model.
Objective
Every experienced programmer knows the déja vu experience of having developed everything once before and yet having to start from scratch with every new project. Everything seems similar and yet it is difficult to work out the similarities. Our concept classix was to find precisely these similarities, the basic building blocks for business application solutions. Ultimately, this resulted in a software architecture to
- rapid application development,
- flexible software adaptations
- and thus tailor-made application solutions
which can keep up with the dynamics of the constantly changing companies. classix Software GmbH from Hamburg, Germany was founded specifically for the purpose of offering a new, very flexible type of software solution on the market.
Our CyberEnterprise Business OS architecture focuses specifically on the area of business applications. With a considerable investment volume, innovative concepts and the use of state-of-the-art software technology, we have worked over the last 30 years to achieve the desired efficiency and flexibility. Our success in the market confirms that this approach is the right one.
The traditional application development process, which is still widely used today, runs through all phases, from the definition of requirements and the design of the data model through to the finished application, again and again. In contrast, the CyberEnterprise Business OS architecture approach is based on the reuse of prefabricated, object-orientated components, starting with a highly abstract enterprise data model (with business objects and the more complex business patterns based on them) through to functional and UX (user experience) application modules of varying granularity that can be combined as required.
Another aspect of the concept classix is a strict technical division of labour in the process of developing a business application solution. Non-application-related developments - which we refer to as basic programming - should be created by pure IT specialists, specialised versions by business IT specialists - which we refer to as application developers - and the user-related UX operating layer by specially trained ergonomists.
Our concept classix is receiving a special boost from the rapid development of AI, as the high level of standardisation of the CyberEnterprise Business OS architecture is ideally suited to AI-supported pattern recognition from data and programmes. This means that not only data queries or changes, but also programme changes and creation can be controlled using natural language.
;){kind=link}