Veri.data email format

The work started 2011 when the object oriented approach veri.mcore was translated into a tabular form and deployed to Excel as a second implementation platform. The first case study on its usage in a major Swiss bank dates from 2012. Veri.data´s goal is to provide out of the box Excel based data modeling & management approach that scales to most complex industrial scenarios, as well as ready to use example models within the health-care and finance sector. Mission Our mission is to evolve and document the approach with an agile team consisting of talented students from leading universities. Currently a team of master students from University of Mannheim works actively on the project. The leader of the Software Technology chair Prof. Dr. Colin Atkinson whom supports the activities as well. What is veri.data? A pragmatic, daily work oriented approach to manage domain and data models. A domain model is the business view on the domain, with all business concepts. Visible mostly as business glossary, and in the high level business requirements. A data model is a concrete way how to store information in a persistence layer such as db, files, e.t.c. What are the components of veri.data? There is the specification part, and the operationss part. Specification of methodology is done with mcore as a conceptual data model (in EMF/OCL). This model documents the methodology, and the structure of the excel sheet in the operations part. From the model we generate an editor, that some time shall replace the excel sheet. Operations is done with an excel sheet, which manages both the domain model and the data model, and generates the a DB structure (as DDL), and initial objects of the DB (as CSV files). Operation is done by extending the excel sheet, regenerating the DB, and then use the DB. Additionally there are generic SQL statements, to reassemble the records from the DB to trees of objects, in the form of JSON.