1 / 9

software for agile d ata management

software for agile d ata management. The JACAMAR (fka. SDV) is . A stand-alone tool to structure and display data in Tree-Tables. An alternative for overwhelming standard spreadsheet applications Add a level of confidence, workflow support and user friendliness Multi-user accessible

dusty
Télécharger la présentation

software for agile d ata management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. software for agile data management

  2. The JACAMAR (fka. SDV) is ... • A stand-alone tool to structure and display data in Tree-Tables. • An alternative for overwhelming standard spreadsheet applications • Add a level of confidence, workflow support and user friendliness • Multi-user accessible • Still document-based Office-tool approach • Still maintaining easy spreadsheet handling • Acts like a full blown database, but does not need the maintenance overhead (no server) • Everything is configurable • That is: • Data model, • view presentation and • filter definition • No offline programming required

  3. Technical features • Pure client application • data storage in multi-user-repository (LAN or cloud) • In Memory Technics • Real time processing • NoSQL Database • intuitive navigation language • Multi-threading user interface • Pure Java

  4. Excel is the worst case for professional Information Management • No central data storage concept (Where/What is the original?) • No real time multi user access • No user role / privileges concept • Very poor user friendliness for bigger lists • No support for structuring data cascades (trees) • No process robustness at all (no format restrictions) • No interoperability between similar lists (Much double work in different business areas to merge data) • High failure potential

  5. Design principles • Absorb principles from relational databases • Distinction between background data tables and virtual rule-based computation of view content. • Absorb principles from Office applications • No offline programming, everything is configurable at runtime • Document based process (Open – Edit – Save cycle) • Utilize client benefits: get best runtime performance All elements are loaded and finally connected at start-up; No reloading delays during working time • Interoperatibility with other office applications Direct clipboard-copy/paste; no separate import/export required. • Additional “unique selling points” • Data display in tree structures • “Think with the User”: Content proposals wherever obvious • Alternative data storage concept: Integrated upload functionality to web based Content Management systems

  6. Worldwide access by Web Based storage The JACAMAR tool has built in support for - local file system storage and web based storage systems Enterprise network North America domain Web based CMS system Europe domain Asia domain Shared drives (restricted to domain borders)

  7. User friendliness • Handling very similar to well known spreadsheet applications • Foldable tree structures • Scalable data focus • Sub-sets of data (multiple purpose specific views) • Show sub-trees only at runtime (“Go Into a branch”) • savable user defined Filters • Intuitive element relation with Drag & Drop • Intelligent content proposals

  8. Multi user saving and update concept Client B Client C Check for Change records Check for Change records Load record and update Client A Open Edit Data Edit Data Edit Data Open Load data Other clients close also. The last one deletes the change records and updates the table file. Client B edits and saves the next change record. Client A recognizes the new change and loads it. A third client opens reads first the table data and after that the change records. Client B checks regularly for updates and loads new change record Client A edits again - but saves now a change record Second Client opens session First Client edits and saves data (single user) First Client opens session One client closes. Please view in presentation mode Save Data Delete Change records Update Table file Save Change record Repository Last client Multiple clients Set session tag Only one client

  9. Kontakt Katla GmbH Immermannstraße 28 39108 Magdeburg Deutschland T: +49 391 - 50 55 83 53 F: +49 391 - 50 54 99 69 E: gl@katla.de.com www: katla-gmbh.de try.jacamar.de jacamar@katla.de.com jacamarsoftware @jacamarsoftware

More Related