15.01.2013 Views

U. Glaeser

U. Glaeser

U. Glaeser

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

FIGURE 38.22<br />

display device; that is, these functions of application software can operate and confirm with virtual<br />

operation panel with dummy signal dialog, and voice guide dialog.<br />

The man machine builder tool is also used to make automakers decide the specification of the man<br />

machine interface in the early stage of the software development because man machine builder tool can<br />

give them virtual MMI and show how it works. For example, using the virtual display, drivers can input<br />

their destinations and their requests to search optimum routes or restaurants near their present locations.<br />

MMI serves drivers to do these interactively using several icons in Fig. 38.21. Generally speaking, the<br />

specification of man machine interface is often not determined until the end of development because the<br />

determination needs ergonomic studies. So it is desirable for providers to make a virtual environment<br />

to simulate the operation of man machine interface to be developed.<br />

The man machine builder tool consists of both user interface design tool and state chart CASE tool.<br />

The missions of the user interface design tool are graphical object design, operation confirmation, and<br />

code generation.<br />

On the other hand, the mission of the state chart CASE tool are production of operative transition,<br />

graphical confirmation of transition, and code generation of state transition.<br />

Before explaining the function of the man machine builder tool briefly, we will explain about the<br />

conventional way to build MMI using Fig. 38.22. In the conventional method, the man machine module<br />

including graphical object design for user interface and state transition is designed from requirement<br />

analysis in the beginning. After both graphical object design and state transition are proceeded, software<br />

code of man machine module are coded separately by manual operation (hand coding).<br />

Then the software code is combined with other application software. Finally, its operational test is<br />

performed on a display of target hardware. If some unexpected behavior or shape occurs in the user<br />

interface, its correction of design and coding are reprocessed. And, though this is a more important issue,<br />

additional requests by customers are often added to the specification to MMI. In order to cope with this,<br />

a new environment to build MMI differently from the conventional method is indispensable.<br />

By using the new development environment of building MMI, one can generate the man machine<br />

module throughout from design to software code. With this tool, a graphical object is designed with the<br />

menu object editor, as shown in Fig. 38.23. This means both the graphic objects for MMI and the<br />

animation of their graphic objects are defined simultaneously with production of objects.<br />

State transition is defined in the state chart editor in the right part of Fig. 38.23. In the state chart editor,<br />

both the animation parameters of graphic objects and navigation function behavior are defined following<br />

the state transition. After the graphical confirmation of both these graphic behaviors and state transition,<br />

these tools can generate the software code for man machine module automatically. Thus, you can show<br />

© 2002 by CRC Press LLC<br />

����������<br />

��������� ������<br />

������<br />

������ ��<br />

������ ���������<br />

�������� ����<br />

��� ��� ������� ������<br />

����������� ���� ��<br />

������ ��������<br />

Conventional method for man machine module.<br />

����� ����������<br />

������

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

Saved successfully!

Ooh no, something went wrong!