Data Management and Data Analytics are of huge importance to Business Process Outsourcing Providers in Customer Relationship Management (CRM) in order to offer tailor-made CRM Solutions to their business clients during presales, sales and aftersales. These solutions support business clients to improve their internal processes, as well as their customer service in a variety of communication channels (including e-mail, chat, social media, private messages, etc.) to reach out to end customers in an efficient way.

Mobile devices have become ubiquitous not only in the consumer domain but also support the digitalization of business operations though business apps. Many frameworks for programming cross-platform apps have been proposed, but only few modeling approaches exist that focus on platform-agnostic representations of mobile apps. In addition, app development activities are almost exclusively performed by software developers, while domain experts are rarely involved in the actual app creation beyond requirements engineering phases.

The term Big Data has become pervasive in recent years as smart phones, televisions, washing machines, refrigerators, smart meters, diverse sensors, eyeglasses and even clothes connect to the Internet. However, their generated data is worthless without information retrieval through data analytics. As Big Data is too big for a single person to investigate, appropriate technologies are being used. Unfortunately, there is not one solution but a large variety of different tools, each of them with other functionalities, properties and characteristics.

We present a technique for checking the validity of Java assertions using an arbitrary automated test-case generator. Our framework transforms the program by introducing code that detects whether the assertion conditions are met by every direct and indirect method call within a certain depth level. Then, any automated test-case generator can be used to look for input examples that falsify the conditions. The program transformation ensures that the value obtained for these inputs represents a path of method calls that ends with a violation of some assertion.