A12 is an enterprise low code platform for the development, integration, maintenance and operation of enterprise applications in complex IT landscapes. A12 combines a low-code approach where subject matter experts can create parts of an application without programming knowledge, with professional custom software development and systems integration. A12 provides an answer to the question of how applications can become become fully integrated, business-critical enterprise applications in the long term. The combination of low code and custom development opens up new possibilities in the digitization of digitization of companies and business processes.
Fields of application
The use of A12 in comprehensive scenarios is particularly advantageous. Due to the model-driven approach, the modeled functionality can be used across applications. This ensures consistency, avoids duplications, simplifies release and dependency management, and reduces the testing effort. testing effort. Business experts and business analysts can use modeling tools to independently map the technical core of the software and maintain it over the long term. and maintain it over the long term.
- Adaptation of technical aspects without programming knowledge
- Fast implementation of technical changes
- Extensive automation of the software development process
- Detached innovation from technology
The A12 modeling concept encompasses the complete business application.
Business entities, their relationships to each other and key aspects of their value creation are depicted in models.
With the help of specialized editing tools and a powerful rules, validation and calculation language, the models can be used over the entire life cycle of the application, regardless of the technology.
Plasma is a design system for business applications with high information density and large Complexity.
Plasma includes UI/UX components, usage patterns, and style guides for the Application framework, navigation elements, notifications as well as the handling of business objects and their typical workflows.
Plasma thus addresses essential design principles of ergonomics, accessibility, Scalability, complexity and device independence.
Platform & Components
The A12 runtime platform consists of modular client- and server-side components that Use and combine flexibly and in a targeted manner via project-specific individual development expand.
The kernel, for example, provides functionality around documents, document models and rule-based validation ready. The services provide persistence, indexing and data access. UAA includes authentication and authorization and controls user management.
Architecture & Technology
The platform components rely on modern technologies, clear interfaces and seamless Integration with other technologies and systems. Together they form an integrated Client-Server Architecture.
Both classic and cloud infrastructure (Docker, Kubernetes) are supported.
Wherever possible, standards are used, e.g. JSON, XML, REST, JDBC, LDAP, SAML, OpenId Connect, OAuth2, JWT and BPMN2.
Why Enterprise Low Code Platform A12 in the Business Domain?
Cost comparison development with enterprise low code platform A12 vs. individual software development
- TCO with A12 Low Code development 54% lower
- Go to Market 75% faster
- Running costs 50% lower
References & Customers
Who is A12 aimed at?
A12 is aimed at medium-sized and large companies and public authorities that require individual software. software. With A12, you can quickly prototype and build simple applications that can grow into complex, fully integrated enterprise applications.
How does A12 differ from other low code platforms?
A12 combines a low-code approach, where subject matter experts can create an application without programming with professional custom software development and system integration. The focus of A12 is not on easily clickable apps for temporary use, A12 rather provides A12 provides an answer to the question of how applications can become fully integrated, business-critical enterprise applications in the long term. In doing so, mgm is pursuing a different path A12 is not a Platform as a Service (PaaS) service in which simple applications are clicked together and deployed. simple applications can be clicked together and deployed. It is not a closed ecosystem. As an enterprise low code platform, A12 is only used in professional and individual software development projects. Another special feature is that A12 projects can place direct requirements on the A12 basis - analogous to the requirements on the their own project software. This means that the projects are much more closely involved and can influence the further development of A12 very directly. With the Plasma design system, A12 is also specially tailored in the UI/UX, A12 is specifically designed to meet the requirements of full-blown business applications.
Can my department use A12 independently?
When an A12 application has been created as part of a project, the business department is able to, adapt the application independently using modeling tools. However, A12 is not an app construction kit that allows the application to be clicked together and deployed at the push of a button. at the push of a button. The use of A12 outside of a software development project is not envisaged in this form. intended.
Are there optional add-ons?
Yes, A12 supports the development of additional add-ons built on top of the core of A12. So code editor for the ANTLR4 parser generator and chat integration as an add-on. add-on. This makes it very easy to add chat functionality to A12-based applications. functionality. Extensions can be activated in addition to other A12 products and can be and can include both server-side and client-side components. The chat bot service uses in the server for example the open source product Rocket Chat. The chat frontend is designed for use both on a desktop PC as well as for mobile devices.
What are the security features of A12?
A12 follows the principle of security by design. Security requirements are taken into account from the from the beginning to prevent potential vulnerabilities. preventive measures. Security experts accompany all phases of the development - from early requirements, architecture decisions and acceptance tests. In addition, the Enterprise Low Code Platform is continuously tested intensively. A12 uses the security toolset ATLAS which integrates a number of tools such as OWASP Dependency Check, ZAP and sqlmap. It enables automated security tests and provides consolidated reporting. reporting. Among other things, ATLAS checks for known vulnerabilities in third-party components, detects configuration problems such as missing HTTP security headers and tests how robust APIs are against attacks such as injection attacks.
How does the surface design work in A12?
A12 relies on special interface models to design the user interface. They also also implement the idea of a separation of technology. They allow an abstracted representation of the interaction structure - for example, the structure of a form - without being hardwired to a specific technical implementation. technical implementation. This has the advantage that the technical details and the design can be developed independently of the interface models. can be further developed. This makes it much easier to implement a consistent and accessible user interface across the board. user interface can be realized much more easily. The Plasma design system is used for the display.
What modeling tools are available?
Currently, A12 provides two modeling tools: the A12 Simple Model Editor (SME) and the A12 UI Designer. The functionality of the A12 UI Designer will be transferred to the SME in the near future, in order to to bundle all modeling functionality in one tool.
What can I model with A12 and what not?
The current modeling scope includes the entire business and parts of the application interface. The decision as to what can be modeled in A12 is based on the added value that the that modelability would bring. In complex business applications there are always aspects that can be developed individually faster, more efficiently and more sustainably. With the data models and the rule language for validations and calculations can be used to depict very complex technical interrelationships can be mapped. Trained subject matter experts and business analysts are thus in a position to to use the modeling tools to independently define the business aspects of an application - without having to without having to rely on developers. Only in exceptional cases - for example calculations with very complex formulas - it can be more convenient to perform the calculations directly in the code and not via the modeling tools. and not via the modeling tools. The modeling of the surface is limited currently limited to the areas in which model-driven components are used.
Can A12 models be reused?
Yes. Reuse is possible for all model types. Especially with the A12 data models it is a common common practice. Data models can be built in a modular way. Subordinate submodels can be for example, can be reused in several other models. In addition, special definitions - for example, for central country lists and legal forms - that can be used in several models. can be used in several models. This allows cross-model aspects to be defined in a single This way, cross-model aspects can be defined in a single place to avoid duplications and possible inconsistencies.