Oracle APEX and the Future of
Low-Code Development
In today’s rapidly evolving digital landscape, businesses face constant pressure to innovate and deliver software solutions faster, more efficiently, and at lower costs. Low-code platforms have emerged as a pivotal force in this transformation, offering a means to accelerate application development while reducing the dependency on specialized programming skills.
Oracle APEX, a long-standing player in the low-code arena, is uniquely positioned to thrive amidst emerging trends in low-code development.
Four Low-Code Development Trends to watch
The adoption of low-code platforms has been nothing short of transformative for organizations of all sizes, from different industries. Low-code empowers business users with minimal coding experience to build applications, while also enhancing productivity for professional developers.
Trend #1 : AI & Automation Integration
- Code suggestions: AI-driven tools will provide real-time recommendations to optimize code snippets or suggest prebuilt templates.
- Workflow automation: Machine learning models will analyze data patterns to automate routine workflows and streamline processes.
- Natural Language Processing (NLP): Users will describe desired functionalities in natural language, and AI will translate this into functional application components.
Trend #2 : Interoperability and Ecosystem expansion
Low-code platforms will increasingly focus on seamless integration with external tools, databases, and cloud services. Cross-platform compatibility and extended plugin ecosystems will allow organizations to customize their low-code solutions further.
- Extended plugin ecosystems to enhance functionality and customization, low-code platforms will offer an expanded marketplace of plugins and connectors. These plugins will provide ready-made solutions to integrate with third-party tools (e.g., CRM systems, ERP software, data analytics platforms) and external databases.
- API-first approach adopted by low-code platforms, including support for RESTful APIs, GraphQL, and other industry-standard protocols to ensure smooth data flow between systems.
Trend #3 : Emphasis on Governance and Security
Trend #4 : Enhanced Collaboration Tools
As low-code platforms are increasingly adopted by both technical and non-technical users, the need for collaboration among various stakeholders will be more important than ever. Developers, business users, and designers must be able to work together seamlessly to accelerate agile development.
- Cross-functional dashboards: Low-code platforms will provide centralized dashboards that offer an overview of project progress, including real-time analytics, metrics, and performance insights per business unit.
- Design and prototyping tools: Designers and developers will have access to prototyping and wireframing tools within the low-code platform, allowing them to quickly visualize app designs, user interfaces, and workflows.
84% of businesses are adopting low-code or no-code tools to fill the technical gap left by the shortage of developers.
Source: Forrester
How Oracle APEX Fits into the Future of Low-Code
Oracle APEX is a low-code platform that enables businesses to build enterprise-grade apps significantly faster than traditional hand coding using popular JavaScript frameworks.
1. AI-powered Development
Oracle APEX integrates with Oracle’s AI and machine learning services, providing users with capabilities such as predictive analytics, anomaly detection, and AI-driven recommendations for application development. As AI becomes more embedded in Oracle’s cloud ecosystem, APEX users will have a seamless way to incorporate AI into their low-code applications.
2. Seamless Cloud Integration
With Oracle Cloud Infrastructure (OCI), APEX users already benefit from a highly integrated ecosystem. Upcoming trends like multi-cloud strategies and hybrid cloud architectures will see APEX serving as a bridge, enabling smooth connectivity between Oracle Cloud and other cloud providers.
3. Governance and Security
4. Collaboration and Low-Code Democratization
think tank: Pioneering Low-Code Solutions with Oracle Expertise
The future of low-code is undeniably bright, characterized by increased AI integration, greater automation, and enhanced collaboration. Oracle APEX, with its robust database foundation, enterprise-grade capabilities, and integration with Oracle’s AI and cloud ecosystem, is well-positioned to remain a leader in the low-code revolution.
At think tank, we have consistently leveraged low-code platforms like Oracle APEX to deliver innovative, scalable, and secure applications tailored to our clients’ needs, operating in both private and public sectors. Our expertise spans:
- Custom Application Development: Building enterprise-grade solutions with Oracle APEX, streamlining operations and driving digital transformation.
- AI & Automation Integration: Implementing Oracle’s AI and internal tools to enhance the functionality and intelligence of low-code applications.
- Seamless Cloud Deployments: Helping organizations optimize their Oracle Cloud Infrastructure with integrated low-code applications.
Ready to transform your organization with Low-Code?
From AI-driven applications to seamless cloud deployments, we’ll guide your low-code journey every step of the way.
Content:
Mastering test automation in software development
In today’s software development, short development cycles are a prerequisite for meeting the demands of the market. Test automation is therefore essential to ensure the quality of the software in the long term. With automated tests, companies can develop faster and at the same time ensure higher software quality. As a result, savings of up to 30 and 90% respectively can be achieved in both test costs and test time. In addition, a return on investment (ROI) of up to 100% is possible within two years of test automation.
Advantages of test automation
The introduction of test automation has many advantages:
- Savings of up to 30-50% of test costs
- Return on investment (ROI): ROI of up to 100% within the first two years after the introduction of test automation.
- Reduction of test time by up to 90%, especially for recurring regression tests
- Quality assurance
- More frequent releases: shortening release cycles from months to weeks or even days
- Accelerated further development: through faster feedback to developers and the associated bug fixing.
- High level of standardisation through defined, proven processes and responsibilities
- Flexibility through short iterations and retros
- Clear communication and status reports
- Transparency of processes and those responsible
- Performance measurement thanks to reports
Challenges of test automation
The challenges of test automation are manifold and require careful planning and execution. One fundamental challenge is to build up the expertise of employees so that they can effectively develop and maintain automated test cases. No less important is defining the right test cases. Here, it is often more realistic to aim for 70% coverage of functionalities rather than pushing for full coverage, which is often neither practical nor cost-effective. In addition, the adaptation and maintenance of test cases requires continuous attention in order to keep pace with changes in the software applications.
The integration of the test team into the development process and the early planning of new features into the test concept are also crucial. This includes considering the impact of new features on existing test cases, which increases complexity and requires a well-thought-out test strategy and precise test planning.
Other critical aspects are the quality and maintainability of the test data and the test artefacts themselves. Guaranteeing valid test data for every scenario and ensuring a consistent structure and utilisation of the test libraries are essential for effective test runs. High maintenance efforts,
especially the editing and customisation of test scripts, are often challenging. Artificial intelligence (AI) can offer a solution here by supporting automated processes for the maintenance and optimisation of test cases, which can improve the efficiency and effectiveness of test automation overall.
Integration test automation
In order to meet these challenges, precise planning of the automation of tests for the development of a product is necessary. It is helpful to bundle the activities and roles in a test hub with the following steps:
1. Discovery Phase
The goals of the discovery phase are:
- Understanding the context, challenges and needs: Only with a full understanding of the specific context of the project can customised solutions be developed that cover the actual needs.
- Recognising and minimising risks: By proactively analysing risks negative impacts on the project can be avoided and a stable basis for development can be created.
- Holistic illumination of the project environment: A comprehensive illumination of the project environment with regard to both technical and organisational processes ensures a comprehensive understanding of the project landscape.
- Make the start of development as simple as possible: Clear processes, easy-to-understand instructions and a well-prepared infrastructure make it easier for everyone involved to get started.
2. Managing and planning
Issues such as the right test automation tools, definition of roles and responsibilities and the use of an appropriate test architecture must be clarified in advance.
Only then can the actual planning and control begin. The following aspects need to be considered during planning:
Development of automation strategies
Ensuring seamless integration of the tests in the build pipeline
Creation of a test concept
Specification of tests, taking into account the layer architecture (test pyramid)
The diagram shows that the costs, complexity, maintenance effort, duration/performance and fragility for GUI tests are far higher than for unit or API tests. Therefore, a sensible distribution taking into account the criteria mentioned above is absolutely essential:
- Layered architecture makes it possible to define test-specific layers that cover different aspects of the system
- Lowest level: Unit tests that test individual code sections and functions. By finding errors early on in this phase, problems can be rectified cost-effectively before they affect higher layers.
- Middle level: API tests that test the interfaces between the various components. Here it is checked whether the data is sent to the server and processed correctly, which ensures the integrity of the communication paths.
Requirements for test automation tools
- Ease of use of the tools, as this makes it easier to get started and shortens the learning curve for the test team.
- Comprehensive log output for detailed logging to analyse the test results in order to draw conclusions about the quality of the tested system.
- Recording of user tests to simplify the creation of test scenarios by recording user actions.
- Recording of test scripts and test activities for the systematic and repeatable execution of software tests.
- Recording of test execution through screenshots or videos for visual documentation of process steps.
- Simple programming language or low-code options to make it easier for less experienced team members to create and maintain the tests, thereby increasing the productivity of the team.
- Parameterisation to keep maintenance efforts low and achieve greater flexibility in the execution of test scripts
Roles and responsibilities
- The test manager is responsible for the test concept. He ensures that the software meets the quality standards and fulfils all requirements.
- The test engineer is responsible for defining the test cases and executing the test cycles as well as analysing the test reports
3. Project phase: realisation and implementation
In the project phase, the infrastructure and the tool chain are set up on the basis of the analyses and definitions carried out in the previous phases.
Piloting and stabilisation as part of a proof of concept (PoC) is also useful.
The implementation of a critical workflow (standard use case) is crucial in order to gain initial experience, avoid errors and be able to react quickly. It is equally important to adapt and create an operating manual and technical documentation.
Comprehensive training of all project members is essential to enable the test team to implement automated tests quickly. Training and know-how transfer sessions are crucial elements in enabling the test team to act quickly.
Test automation with artificial intelligence
In order to fully utilise the benefits of test automation, the use of AI is essential. AI offers numerous support approaches for carrying out test automation in a cost- and resource-efficient manner. It can support the following tasks, among others:
- Creation of test cases (guided test case design)
- Determination of test coverage
- Creation & implementation of the Gherkin tests
- Visualisation of test cases (test-based modelling)
- Determination of standard case deviation (GUI test)
- Analysing errors (classification)
Conclusion
Test automation is particularly important for long-term and medium-sized to large software development projects. With well thought-out structuring and planning, it offers numerous advantages: it speeds up the development process, reduces costs and significantly improves the quality of the software. However, successful test automation requires careful planning, a comprehensive test concept and the use of modern test tools and technologies.
Blue Print für your Test Automation
Easily integrate and implement test automation. How can you do this? Find out more in our e-paper!
Content:
Revolutionary development: How AI is changing software test automation
The exponential development of software also leads to an exponential increase in complexity and costs. This can be impressively observed in the development of video games. While the development costs for GTA 5 (2013) amounted to 200 million dollars, the costs for GTA 6 (2025) have already risen to over 2 billion dollars. Obviously Moore’s Law also applies here, but in terms of costs: a doubling roughly every two years!
One of the main cost drivers is quality. Software quality is largely dependent on a good test system, which is why professional manufacturers have been setting up highly automated test factories for years.
The next revolutionary step: AI-supported test methods and software
Thanks to artificial intelligence (AI), the next revolutionary step is now imminent: autonomous, AI-driven test methods and software. AI can recognise patterns in large amounts of data and automatically generate and optimise test cases from these findings, which significantly increases efficiency and accuracy. Another area of application is automatic error detection: AI systems can recognise and identify anomalies and errors that human testers can overlook. This leads to faster and more precise troubleshooting.
More than just detection: optimization and troubleshooting with AI
However, AI test software goes beyond mere error detection. It actively helps to eliminate vulnerabilities and optimises the code through direct interventions. AI-supported test automation tools can also simulate user behaviour in order to test user-friendliness and performance under realistic conditions. Machine learning allows these systems to continuously learn and improve their testing strategies, resulting in increasingly accurate and comprehensive test coverage.
Simplified creation and maintenance of test scripts
The creation and maintenance of test scripts is also made easier by the use of AI, as intelligent algorithms can automatically make adjustments when the application changes. AI-based test software also supports performance tuning and improves documentation through professional test methods.
Deeper insights through AI-supported analysis
An evolutionary step for software development
AI in software test automation is a logical evolutionary step and will be indispensable for professional software development in just a few years. This applies not only to large software houses, but also to small companies and software projects. AI has the wonderful characteristic that it hardly needs any economies of scale to be profitable.
The need for quality assurance
Software projects often neglect the aspect of testing. However, this is urgently required for quality assurance. AI offers numerous possibilities for this.
The future: convergence of AI-based code development and testing
A look into the future shows that AI-based code development and AI-based testing will converge, potentially reducing the number of coders required. Especially in areas where low-code or no-code methods are used, AI testing software will be indispensable. The designer of the software themselves will no longer be able to test their product and will be reliant on independent AI testing software, which should be built into the no/low-code tools.
Governance and Compliance
This development requires additional governance to ensure that the software meets a company’s general compliance rules and legal requirements, which are also growing exponentially. In addition, the independence of AI developers and AI testers must be guaranteed to avoid conflicts of interest.
Content:
The suitable integration platform for your company and your customers
Information security and data protection are key issues
Not only have customers’ expectations of their providers’ services increased, but environmental influences, which require a greater customer focus and the associated shorter time-to-market, also make it necessary for companies to react ever more flexibly to changes. In addition, at a time when information security and data protection are becoming increasingly important, it is essential to protect one’s own business processes and the data processed in them as securely as possible against unauthorised access. An integration platform provides the solution to many of these challenges.
It can effectively connect data and applications to increase efficiency, improve responsiveness and thus offer a competitive advantage. IT landscapes with complex, poorly networked systems and applications, on the other hand, often represent an obstacle in this context, as their adaptability and scalability are very low.
Integration platform: A definition
But what does an integration platform actually mean? An integration platform is a software solution that enables seamless connection and communication between different components, applications, systems and data sources. It serves as a central interface for collecting, integrating, transforming and exchanging information from different sources.
The main task of an integration platform is to overcome the heterogeneity of data formats, protocols and different technologies. It offers a comprehensive range of tools and functions to harmonise data.
Integration platforms in enterprise architecture management
Ultimately, an integration platform plays a decisive role in modern enterprise architecture management. It is the centrepiece from which all services and applications can be controlled, maintained and exchanged.
The importance of integration platforms lies primarily in the fact that they help companies to manage the complexity of their IT landscape and enable seamless integration and networking of their systems. By using an integration platform, companies can improve interoperable communication between their systems and thus exchange data seamlessly. This enables them to optimise operational processes and workflows, increase efficiency and make better business decisions based on up-to-date and consistent data.
This also makes a significant contribution to improving the quality and consistency of data. By centralising the collection, transformation and validation of data, companies can ensure that all systems have access to up-to-date and error-free data and applications and that data loss can be avoided.
Advantages of an integration platform
There are many examples of the advantages of integration platforms. Here are just a few:
- Simplifying the integration of applications and data
- Reduction of complexity and pre-processing of data
- Increased transparency and visibility of data flows
- Reduction of integration costs and time
- Increasing the scalability of the IT landscape
- Improving the efficiency and speed of business processes
- Increasing the possibility of automating many business processes
- Flexibility for rapid adaptation to changing business requirements
- Better integration of cloud and on-premise solutions
- Increased security through centralised control and monitoring of data exchange processes
- Improving data quality and consistency
- Reduction of time and costs for maintenance and development of interfaces
Choosing the right integration platform / solution
When choosing an integration platform/solution, companies should consider a number of things to ensure that it meets their requirements. Above all, the requirements and functionalities should take centre stage. Which features do the individual stakeholders need, which data formats, interfaces, transaction capability, etc. are involved? It is important to get all specialist departments on board right from the start.
The chosen solution should be flexible and scalable to ensure the easy integration of additional systems and applications. It should also be cloud-capable to further increase scalability and flexibility.
The security of company data and systems should also be a top priority. Accordingly, the platform should have sufficient security mechanisms in place to protect the data from unauthorised access and threats. Compliance requirements also play a major role here.
Last but not least, user-friendliness plays a major role for users in the company. This should always take centre stage when integrating a new solution.
Combination of different integration solutions
Often, a combination of different approaches to implementation can deliver better success than committing to one approach.
By using microservices, individual components of the solution can be scaled independently of each other and are very flexible. The combination of approaches also makes it possible to quickly drive forward the development and provision of new functions and services. In this way, the use of third-party providers offers the opportunity to fall back on proven solutions and save time and development effort.
Microservices can be developed, provided and scaled independently of each other, which enables efficient utilisation of resources. API interfaces also facilitate integration with other systems and services, both internally and externally. By distributing functionality across microservices, failures in individual components can also be isolated and rectified without affecting the entire solution.
The implementation of a solution can be both cloud-based and on-premise.
Application example: Integration along the customer life cycle
Especially for companies that offer their services and products online, an integration platform tailored to the needs of customers is a good way to improve the customer experience and thus increase their satisfaction. As a first step, it is particularly important to take a look at the customer life cycle and all of the steps required to optimise the customer experience. This is because covering all customer-related business processes with the help of a single platform solves several problems at once. On the one hand, the services and products are accessible via a “front door”, and on the other, the processes are easier to customise.
In our case, we are looking at the property universe with its various service areas.
Step 1: Integration of all external and internal stakeholders
In this case, it is important that by analysing the needs of all users and partners involved a system is created that meets everyone where they are. In the case of a property platform, both external and internal stakeholders must be taken into account, each of whom has a different view of the application.
Step 2: Automation of processes along the value chain
After analysing all of the stakeholders’ needs, it is possible to break down very precisely which service they require at each step of their customer journey. The integration platform with a front end to the customer is a best practice example of customer centricity.
Step 3: Initial situation IT infrastructure and IT systems
Companies often still struggle with data silos or disconnected applications. On the one hand, this prevents a smooth process, there is a risk of data loss and security gaps, and on the other hand, it is not possible to guarantee a satisfactory customer experience.
Step 4: Combination solution for integrating systems
The solution to this problem is obvious: with the help of microservices, applications can be replaced step by step and connected to the front end via API interfaces if a service or process needs to be customised. This significantly shortens time-to-market cycles, allowing the company to react flexibly to new challenges.
This is also in line with the principles of agility, which provides for an incremental approach and continuous adaptation of services in the interests of a high level of customer centricity and further contributes to ensuring a company’s competitiveness. In addition, the automation of many processes and the high scalability of the application make it possible to utilise the resources freed up to expand business activities, for example by entering markets in other countries and adding further services to the range, and to generate more revenue.
Enterprise architecture with an integration platform for greater customer satisfaction
The example of the real estate platform along the customer life cycle has made it very clear that it makes sense to take a closer look at your own IT landscape in order to find a better solution if necessary. It can also be valuable to take a closer look at which platform actually suits the company in order to use the technologies and developments that are best suited to its own business processes and thus possibly even play a pioneering role in terms of customer centricity on the market.
Content:
Challenges in the digitalisation of administrative processes
E-government as a means to more economic growth
The digitalisation of administrative processes in the public sector received a boost during the Corona pandemic, but much remains to be done. Especially on the African continent, administrative hurdles are an important factor for the low economic growth in many countries. The digitalisation of administrative processes such as lending or publicly available online information on trustworthy companies are therefore often an important prerequisite for economic growth.
Involving administrative staff in development
More and more governments are therefore making efforts to digitise the public sector, partly with the help of the World Bank and other organisations. For this to succeed, some hurdles need to be considered. Since the ultimate goal is to improve service for citizens, it is necessary to involve both administrative staff and citizens in order to develop applications that convince everyone.
Especially with regard to the employees, it is important to convince them that the new solution will make their work easier and will not pose a threat to their jobs from the beginning. This means that they should already be involved in the requirements analysis. In order to identify their needs, it is often necessary to observe the existing processes on site in order to be able to map them digitally on the one hand and optimise them on the other.
In order to increase the acceptance of the new systems and to reduce possible resistance, it is important to think about a strategy in advance. Particularly intensive training after the system has been implemented, which focuses on the advantages for the users, can be an important factor in this.
Cooperation of systems between government entities
Other pitfalls for the digitalisation of administrative processes are the legal requirements for them. In order to be able to take them into account accordingly in a system, a precise analysis and knowledge of the laws is necessary. In addition, the areas that refer to laws must be easily adaptable in order to be able to update them quickly in case of changes.
Last but not least, either missing data or data distributed in monolithic systems pose a challenge. Making these easy to find through high-performance search functions, as well as migrating data so that all legal requirements continue to be met, requires a great deal of planning and understanding of administrative processes.
Another important success factor for the use of digital administrative systems is the exchange of data between systems of different government entities. On the one hand, this saves users from having to travel back and forth between authorities, and on the other hand, information is retrieved directly from its sources, which guarantees the accuracy, correctness and up-to-dateness of the data.
Technical and content know-how
All these are reasons why it is often difficult for governments to find the right partner for the implementation of their digitisation strategy, because companies rarely bring both the know-how for the development of such a complex system and the necessary knowledge regarding the specific requirements for the digitisation of administrative processes.
In conclusion, it can be said that experience is crucial in the implementation of e-government projects in order to avoid problems. Precise knowledge of the legal situation and the processes is also essential.
Content:
Complexity needs new solutions
Comparison Individual Software vs. Standard Software
Advantages of customised software: tailor-made solutions
Advantages for individual software can be found quickly: If, for example, a company decides to have a software solution developed, it adapts optimally to its own needs. Business processes remain unaffected by it because it takes them into account right from the start and can even help to improve them – just think of digitalisation. Moreover, it can be seamlessly integrated into existing systems and structures or, again, help to make them more transparent and faster, for example when monolithic structures are merged into one system.
If, despite all the forward-looking planning, adjustments and extensions are necessary if something changes in the size of the company or its range of services, these are possible at any time because there is direct contact with the manufacturer. This also becomes important when companies have to react quickly to changes in the market, which is becoming more and more important in times of rapid change and many global crises, such as the Corona pandemic or the Ukraine war. Last but not least, the look and functions can also be tailored exactly to the company’s wishes.
Disadvantages of individual software reassessed
But what about the disadvantages? At first glance, implementing new software seems like a lengthy process that many would like to bypass. But anyone who has dealt with and experienced the introduction and implementation of standard software knows how many snags there can be before the product achieves the desired result. Because “bought quickly” does not mean that the solution will also run quickly and the seemingly cheaper standard product will quickly become a permanent construction site.
IIf one is also a smaller customer, the interest in successful support is often not very great, whereas the developers of one’s own solution are available for problems and enquiries in one’s own interest alone. Moreover, a standard programme often does not cover all areas of a company, so that one has to deal with a wide variety of providers and maintain different systems, whereas with an individual software solution everything is in one hand.
Cost savings through precise planning and nearshoring
In fact, it is possible for the costs of custom software development to exceed the planned budget. However, a precise needs analysis and planning as well as strict budget monitoring can avoid a cost explosion from the very beginning. Further savings can be made by using a partner who has outsourced his software development to a nearshoring region. In addition, the balance sheet quickly looks different when comparing customised software with standard products, taking into account maintenance, software updates, licences, etc., which are often incurred with the latter.
Close cooperation with a company that specialises in the development of complex software solutions therefore also prevents misunderstandings about what the finished product must be able to do and achieve. This is also helped by the agile way software companies work, where developers can react quickly to changing requirements.
Conclusion: Individual software is the solution of choice in complex environments
In some cases it can certainly make sense to choose standard software. The question of the complexity of one’s own structures and processes, based on the Cynefin framework, helps with the decision. Especially in times of digitalisation, the challenges are rarely simple, so that the approach of a best-practice solution no longer applies. Because in a complex Vuca world, what counts are procedures and structures that can be adapted easily and quickly. A solution tailored to the needs of the customer, which has already dealt with the special challenges of the company during development, is far more helpful than one developed for standard cases. This is true even if experience from many industries has gone into it, as nothing is as unique as a company’s structure and culture.
Content:
Nearshoring in Tunisia: Is it possible?
Six reservations reassessed
Many companies in Europe are now using nearshoring partners to outsource their software development or entire business processes due to the lack of skilled IT staff and high labour costs. The classic choice is Poland, Bulgaria or Ukraine. But locations such as Tunisia are also becoming increasingly important in this context. However, there are still reservations about non-European partners, which can easily be refuted, because nearshoring in Tunisia also offers many advantages.
Quality training and geographical proximity
Quality: In Tunisia, higher education is of high quality and absolutely comparable with Western European countries. 240,000 students graduate from higher education each year, of which 20,000 are engineers and scientists and 9,000 are information and communication technology graduates. Tunisia has more than 50 engineering schools that teach computer science, among other subjects. This guarantees high quality in the implementation of software projects.
Distance: Even though Tunisia is located on another continent, the time difference is a maximum of one hour in summer and a flight takes only a little more than two hours. Thus, in contrast to offshoring in countries like India, it is guaranteed that contact persons are available during European business hours to make arrangements or solve problems.
Multilingualism and stable infrastructure
Communication: Large parts of the Tunisian population speak fluent French, English is taught at school from grade 4 and there are certified as well as professional language institutions for the German language. In the technical professions, French and English can be assumed, and German and Italian are often added. The local distance can be bridged without problems thanks to digital means of communication, which have developed even further during the Corona pandemic. The good telecommunications infrastructure, in which Tunisia is a leader in the southern Mediterranean, also contributes to this.
Mentality: Without question, there are differences between the German and Tunisian mentality. However, companies like think tank Business Solutions now have decades of experience in implementing numerous projects with European partners. A German bridgehead consisting of product owners and IT consultants additionally guarantees that the cooperation with the customers runs smoothly.
Hands-on mentality and cost savings
Management: Managing a project is always challenging, especially when a hybrid, multinational team has to be managed. To ensure the smooth running of a project, an agile working model is a good choice, which has also become popular in Tunisia, especially in the development and implementation of software in companies like think tank. By having German colleagues manage the projects, it is ensured that the customer’s requirements are always in focus. The developers in Tunisia also have a “get the job done” mentality just like their colleagues in other countries and act in a goal-oriented manner.
The best of both worlds
Costs: Tunisia is also a very good alternative in terms of costs. The hourly rates for a Tunisian employee are attractive and competitive. Despite the good quality of the labour market, the average wage costs for a full-time employee, for example, are very low compared to Eastern European countries, making Tunis an attractive North African location for business process outsourcing. It should not be forgotten that with Tunisia we are in a politically stable area, whereas in the Eastern European area there have been tensions and uncertainties in recent times.
Overall, it can be said that Tunisia as a nearshoring partner is a good alternative to the classic Eastern European countries. In combination with a German bridgehead, which can act as a translator not only of culture but also of mentality if necessary, one is relying on the best of both worlds: Availability of skilled labour, cost savings and German know-how and quality.
Content:
Testing in Software Development
Mistakes and how to avoid them
Frequent arguments against extensive testing in software development are often that this is not necessary because a lot of value is placed on qualitative work in one’s own company. This would make it possible to save money on software tests. On closer inspection, however, it quickly becomes clear that both of these points can be refuted very quickly.
Consequences: Missing features and dissatisfied end-users
Because in the communication between the customer and the developer, misunderstandings can arise in the various steps, so that in the end the released application is missing features or cannot do what it should. In addition, the human factor cannot be neglected, i.e. people always make mistakes in their best work. Moreover, changes in an existing system can lead to malfunctions elsewhere, which only appear when an end user complains about them.
And this brings us to one of the consequences of companies trying to save on testing. Errors can lead to customer dissatisfaction and thus to a loss of image. In addition, bugs that occur after the release have to be fixed as quickly as possible. The developers are tied up during this time and cannot continue working on the development of new features, so that the further development of the project is delayed and thus costs money that should have been saved by testing.
Do's: Timely start and dedicated roles
All this makes it clear that testing is a necessary corrective in every software development. But what should you pay attention to in software testing and what should you avoid? It is important to create the test cases in good time, i.e. already when the user stories are created. In the best case, an independent test team is responsible for this, which is not too closely involved in the development, in order to exclude a certain operational blindness. The same applies to test execution. It is best if no one tests their own test cases, but always those created by someone else. In addition, this avoids a bottleneck being created by the product owner who has to approve the release and thus approve all test cases, which can lead to delays.
It is essential to ensure that the test cases are well developed. This means that the test cases are created on the basis of the user stories and, at best, all the steps listed there are covered. Testing should also begin immediately after the developer has implemented the user story in order to be able to meet the release date. Each test should also include a test report, in which exactly what worked and what did not work is recorded, in order to keep an overview of the errors in a development sprint. Automation of test cases for standard use cases, e.g. “I can download a text” or for errors that occur again and again, can be a great help.
Plan 20% of the project volume for software testing
Of course, testing should not be rampant; a test coverage of 95% negates all cost savings, as such a rate can only be achieved through intensive testing. 20% of the project volume is a good guideline to follow when introducing a testing procedure. However, it is pointless to try to save money by testing less, as this is not worthwhile due to the possible loss of image, the resources tied up in development for bug fixing and the associated time-delayed release of a downstream application.
Content:
Do you need a Blockchain?
Do you need a Blockchain?
- Decentralisation,
- security and
- trust.
In order to get a better overview of the different areas of application, the categories to which most use cases can be assigned, regardless of the industry, are listed below:
Digital Identity Management: Many people have certainly come up with the idea of managing digital identities. Not least Facebook and Google, which are integrated as registration services in many online services. From the user’s point of view, this is both convenient and questionable, as it is not always obvious when which data is passed on to third parties and for what purpose. The decisive factor in this category is the purpose, namely the storage of personal data that can be validated and thus used for authentication for other services.
Market creation and digital currencies: This category refers to the creation of new markets. Usually, this is a blockchain-based market on which goods or services can be traded. All cryptocurrency applications are examples of this category. Initial Coin Offerings (ICOs) in which investor funds are collected in an initial funding phase are also examples of market development.
Origin and tokenisation: In tokenisation, a real object that represents an asset is converted into a digital asset. The value is transferred to tokens and uniquely assigned to an owner. The tracking mechanism can be used to prove the origin and ownership of an object at any time (provenance).
Meta-consensus: Meta-consensus is one of the fundamental paradigms of the blockchain, as all participants must agree on a “chain”. This use case category is about finding and reaching consensus on a specific issue without being able to manipulate the outcome of the election. Examples are parliamentary elections, referendums or the votes of shareholders or contracts between several parties.
Tracking. Tracking is about the transparent, permanent storage and traceability of information that is relevant for several organisations. A good example is use cases from supply chain management, as data on transport goods is necessary both for individual suppliers and for checking adherence to laws and guidelines (compliance).
IoT – Internet of Things: Machines that interact on the blockchain like we humans do in real life and exchange goods and services via a wallet are part of the IoT category. An example is the automatic payment of tolls or parking fees, which can be paid by the car, which has a unique ID. Smart contracts, which are executed automatically without external intervention, also belong to this category.
Intermediary trust: Due to the characteristics outlined at the beginning, the blockchain has the potential to reduce the participants in a value chain to those that are really necessary, i.e. only those that actually contribute to an increase in value. Services and goods can thus be offered much more cheaply. One example is the energy sector, where it is possible to directly connect producers and consumers thanks to the blockchain.
We don't need a Blockchain!
The use of a blockchain solution should be viewed critically if it involves the storage of large amounts of data, there are many write accesses and a real-time data set is necessary or only a few participants are involved.
Conclusion
The applications of blockchain are as diverse as our lives. Nevertheless, it is often difficult to judge when its use really makes sense. “If trust or robustness are not important, then there is nothing which a blockchain offers that can’t be done with a regular database.” Gideon Greenspan – Founder of Coin Science.
Quellen: Ulrich Gallersdörfer Masterthesis: Analysis of Use Cases of Blockchain Technology in Legal Transactions https://wwwmatthes.in.tum.de/pages/z0tgbukmqlbr/Master-s-Thesis-Ulrich-Gallersdoerfer, zuletzt geprüft am: 05.02.2020
Cathy Mulligan (April 2018) These 11 questions will help you decide if blockchain is right for your Business https://www.weforum.org/agenda/2018/04/questions-blockchain-toolkit-right-for-business, zuletzt geprüft am 05.02.2020
T. Koens & E. Poll 2018 What Blockchain Alternative Do You Need? http://tommykoens.com/wp-content/uploads/2018/09/blockchain-alternative.pdf, zuzletzt geprüft am: 05.02.2020
DHS model (~end 2017) Dylan Yaga Peter Mell Nik Roby Karen Scarfone Blockchain Technology Overview https://nvlpubs.nist.gov/nistpubs/ir/2018/NIST.IR.8202.pdf , zuletzt geprüft am: 05.02.2020
Scaling frameworks Nexus, LeSS and SAFe
Tabular comparison
Megatrends such as digitalisation, globalisation and flexibilisation are rapidly changing our working world today. The expectations and demands of customers are adapting to digital possibilities at ever shorter intervals. New demands are also constantly being placed on products. Teams can be scattered all over the world and still work together excellently. Everything is becoming faster, more interactive and more agile – accordingly, product development cycles are also becoming shorter and shorter.
One method that meets these requirements – today on everyone’s lips – is Scrum. However! What do you do when the product is so large and comprehensive that many teams, different departments or even the whole organisation has to work together on it? The right scaling for efficient and satisfying collaboration provides orientation and support for the teams. But: how do you decide which scalable framework is best? Which framework can be used when the processes of Scrum for 3, 4, 5, … teams are too small? The search for the most optimal approach is a big challenge for many.
To give you a rough overview of the common scalable frameworks, I have summarised an overview that highlights the differences of each framework: Nexus (Framework for Scaling Scrum), LeSS (Large-Scaled Scrum) and SAFe (Scaled Agile Framework).
Nexus
The father of the Nexus framework, Ken Schwaber, describes it as an exoskeleton that connects three to nine Scrum teams to develop a product. It is a process framework based on the agile manifesto and Scrum.
Nexus captivates through its simplicity. Scrum is scaled in its roles, events and artefacts. It focuses on cross-team dependencies and integration issues that arise when scaling across multiple teams and emphasises transparency.
LeSS
LeSS aims to impress with its simplicity (more with less) and relies on clear principles. The teams under a product owner are responsible for the complete product development and bear a great responsibility, which also includes communication towards customers and the environment. If there are more than eight teams, the system is expanded to LeSS Huge in an additional scaling phase.
SAFe
SAFe is economically oriented and has the continuous improvement of value streams in mind. With its hierarchical structure, it looks beyond the team to the programme, solution and portfolio levels as well as the overall embedding in the organisation. Roles, methods and artefacts are clearly described and support the introduction to scaled agile working.
Agile scaling frameworks Nexus, LeSS and SAFe × This comparison is intended to provide you with an orientation to make it easier for you to take the first steps regarding the decision in which direction you want to go – Nexus, LeSS or SAFe. The advantages, disadvantages and limitations of these frameworks have deliberately not been discussed here.
However, before you can choose one of the scaling frameworks, you need to think carefully about which one fits your company culture and values. Check what your goal is, what do you want to achieve? What is the environment like and which agile methods are already used in your company?
My recommendation is to take the elements that best fit your organisation from the known frameworks and adapt an agile scaling framework.
Sources:
SAFe – https://www.scaledagileframework.com
LeSS – https://less.works/de
THE NEXUS™ GUIDE – https://www.scrum.org/resources/nexus-guide
Agile Skalierungsframeworks: Safe, Less und Nexus im Vergleich – https://t3n.de/news/agile-skalierungsframeworks-safe-less-nexus-1150190/
Das beste agile Framework – 5 Large-Scale Ansätze im Überblick – https://www.mosaiic.com/agile_framework/
