Information
English (United States)
Description
In Automotive Systems Engineering office documents are very often applied for capturing and maintaining engineering data, in most cases spreadsheets. Reason behind is that they are always accessible on the desktop and every developer knows how to use them. Difficulties coming into the game if complexity increases to a level, where a single human person looses overview due to a high number of data in one spreadsheet or multiple spreadsheets with many inherited dependencies. This complexity is driven by different views (e.g. Functional Safety) and a growing level of detail along development. These derived dimensions span an area of engineering data which have multiple relations to each other caused by view related engineering methods (e.g. traceability of requirements). As a consequence those multiple spreadsheets containing engineering data need consistency checks inside and to other sheets flying around. We call this sum of dependent engineering data an Integrated Item. Unfortunately it's not just one big Spreadsheet... Powerful tools, off-the-shelf or self-written, are available at those engineering companies, but typically they need much computational power and they are sometimes hard to handle for an engineer who just works on some pieces of engineering data. The EEsysApp is dedicated to serve the these engineers by analyzing their spreadsheet data at the desk or maybe somewhere underway, before he feeds those data back to the company's engineering data backbone.