There does,
however, remain some signi?¬?cant work to do. This work will not noticeably improve
the productivity of the solution in use, but it will make a big difference to how well
your DSM solution is accepted. Without that acceptance, getting the DSM solution
into use may take much longer or even fail to happen.
348 DSM DEFINITION PROCESS
Fancy symbols are, of course, completely unimportant to productivity. Provided
the symbols let you easily distinguish the concepts, and present the main properties of
their concepts in an easily readable format, you already have a good visual language.
We developers, however, are ?¬?nicky creatures, and the human race as a whole tends to
judge by ?¬?rst impressions. A sloppy, ugly set of symbols will have a large impact
on how your language is perceived. Even a perfectly decent set of symbols may
look rather simplistic to eyes used to Vista or OS X.With access to the right tools and
skills, you can turn a good language into a great one. For many of us, this is probably
an area best left to (semi)professionals??”providing that you can communicate to
them the real needs of the situation and that in this case function must always come
before form.
The symbols represent the static part of the language, how the users will see the
models. On top of this is the issue of how the users will create, edit, and navigate
around the models.
Pages:
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659