24.07.2014 Views

COMPIT 2003 in Hamburg/ Germany - TUHH

COMPIT 2003 in Hamburg/ Germany - TUHH

COMPIT 2003 in Hamburg/ Germany - TUHH

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

This shows that the development of tools must follow a bottom up approach to be successful,<br />

whereas top down views tend to tackle the problem too academically and therefore often fail.<br />

This bottom-up development can obviously only be carried out if sufficiently skilled designers<br />

of high process knowledge are will<strong>in</strong>g to make their knowledge available. But if the same people<br />

def<strong>in</strong>e the development scenario for a tool that will be the end users (or close to the way<br />

of th<strong>in</strong>k<strong>in</strong>g of the possible end users), this is twice efficient. On the other hand, such k<strong>in</strong>d of<br />

development can lead to anarchism and unclear software structures (typically most developments<br />

<strong>in</strong> the IT scene are top-down approaches). It must therefore be guided by a clear, open and<br />

modular system architecture with a high level of standardization at suitable granularity.<br />

From these f<strong>in</strong>d<strong>in</strong>gs, the follow<strong>in</strong>g conclusions can be drawn:<br />

• Tool development should follow a bottom up approach, to reflect the necessities of the<br />

design process as far as possible and to identify beneficial applications. So humans and<br />

computers contribute where they are most efficient.<br />

• Low level optimization leads to higher level optimization, provided the system architecture<br />

prevents the process from anarchism.<br />

• The development must be based on highly skilled design eng<strong>in</strong>eers with sufficient system<br />

and process knowledge.<br />

6. Data model <strong>in</strong>terfac<strong>in</strong>g versus complete product model<br />

One major play<strong>in</strong>g field <strong>in</strong> IT development is the development of product data models and the<br />

related <strong>in</strong>terfaces. Data models are subject to standardization (e.g. ISO APs) and the same<br />

holds for the required <strong>in</strong>terface programs. Most of today’s problems regard<strong>in</strong>g IT developments<br />

are believed to be solved if an appropriate, standardized product data model is developed that<br />

reflects most of the views needed for today’s applications and if the data <strong>in</strong>terfaces required would<br />

exist. This op<strong>in</strong>ion strongly co<strong>in</strong>cides with the fact that most IT development was carried out<br />

for the detailed design phase or the data exchange with sub-suppliers (e.g. classification society),<br />

where <strong>in</strong> fact most of the exist<strong>in</strong>g problems are data management problems.<br />

Damage Stability<br />

Export<br />

Pip<strong>in</strong>g<br />

Plann<strong>in</strong>g<br />

...<br />

Steel Design<br />

Pa<strong>in</strong>t<strong>in</strong>g and<br />

<strong>in</strong>sulation<br />

Compartmentation<br />

Load Cases<br />

Tank Capacities<br />

Slosh<strong>in</strong>g<br />

<strong>in</strong> Tanks<br />

Heat−<br />

Transfer<br />

Ventilation<br />

530

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!