Separation
between libraries and frameworks can sometimes be dif?¬?cult since they form a
continuum: sometimes a library can provide more sophisticated support for certain
application functionality than a framework.
In DSM, all these possible layers of a target environment are invisible
to application developers. They are not even black-box components since
modelers don??™t need to know anything about them. DSM hides them yet makes
their use automatic. However, the experienced developers creating the DSM
solution need to know them well. In Chapter 12, we discuss in detail how the
target environment and existing code can be integrated with models and generated
code.
Target Environment Already Narrows the Focus For DSM, a third-party
target environment is often not enough; it is usually too generic.We are not building
all the different kinds of applications we can run on a PC, J2EE, or .Net: we are
always more focused. Let??™s consider the case of developing mobile phone
applications as illustrated in Chapter 1. As a target environment the Symbian
operating system alone is too generic as we are building a certain kind of
application. So we have a narrower domain. It could be gaming, browsing, camera,
or enterprise applications as in Chapter 1. Depending on the choice, there are
different levels of language support, libraries, and components or even existing
frameworks, all providing a set of prefabricated software building blocks that
programmers can use, extend, or customize for speci?¬?c systems or applications.
Pages:
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188