Different users may also require different views and languages, especially if their
roles in making speci?¬?cations are different. For example, there can be one language
that focuses on hardware structures, another that speci?¬?es communication networks, a
third the device architecture, and a fourth the application functionality. In DSM, such
different views can be integrated by integrating the modeling languages or by using
separate languages and integrating the speci?¬?cations during code generation.
Scaling and Information Hiding Graphical diagrams, matrics, and tables also
scale better than pure text by offering different levels of detail. This can be offered
with submodels, hiding unnecessary information, providing different views, or
linking related speci?¬?cations. Rather than copying the same data to multiple
speci?¬?cations or places, aDSMlanguage (and related tools) can minimize the need for
specifying explicit links between speci?¬?cations and keeping them up-to-date.
Concepts in the modeling languages can be integrated so that reuse is guided or
enforced: rather than giving newdesign data, modelers are forced to choose from data
already given elsewhere. For example, in the mobile phone case, the content of the
SMS message is selected from the variable data already given elsewhere in the
application.
Pages:
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115