and and/or from embedded WiFi functionality. In the audio domain, speech codecs and audio codecs may be and often are, separate entities. Micropositioning is separate from macropositioning. Imaging is separate from video. For example, most camera phones have two cameras, one for still-image capture, Future Trends, Forecasting, the Age of Adaptation and More Transformative Transforms one for lower-resolution video. The data domain may be distributed across several devices, for example, the application processor, the SIM card and SO on. This does not mean that domain value is not a valid approach for qualifying partitioning or integration decisions. Adding functionality to phones has increased the complexity of the decision process and implies a need for a level of interdomain understanding that is hard to achieve. Radio system specialists have not historically needed to know much about audio systems or positioning systems or imaging systems or data systems. So the domain-value approach can be useful at engineering level either to work through the mechanics of partitioning or integration or to decide how much functionality to support in any one domain and/or to decide how to allocate R and D effort to achieve a maximum return. Similarly, the domain-value approach can help in developing future market models. Forecasting the future sales volume and value of voice phones, audio phones, location devices, camera phones and business phones and/or personal organisers and smart phones and tablets and dongles can become muddled by a lack of descriptive clarity. Given that function determines form factor, domain-based functional descriptions provide a valid alternative approach allowing product families to be developed at the silicon and handset level with clearly differentiated functionally based cost and value metrics. The same applies in market research. The telecoms industry, in our case, the wireless telecoms industry, is a classic example of a technology-driven rather than customer-driven industry. This is altogether a