Trew, Tim; Botterweck, Goetz and Nuseibeh, Bashar
Due to copyright restrictions, this file is not available for public download
Click here to request a copy from the OU Author.
|Google Scholar:||Look up in Google Scholar|
Consumer electronics (CE) products must be appealing to customers, have features that distinguish them in the market and be priced competitively. However, this must be achieved with limited hardware resources, so requirements engineers and architects must work together to specify an attractive product within these constraints. This requires an architectural description from early in devel-opment. The creation of this description is hampered by the lack of consensus on high-level architectural concepts for the CE domain and the rate at which novel features are added to products, so that old descriptions cannot simply be reused.
This chapter describes both the development of a reference architecture that addresses these problems and the process by which the requirements and architec-ture are refined together. The reference architecture is independent of specific functionality and is designed to be readily adopted. The architecture is informed by information mined from previous developments and organised to be reusable in different contexts. The interplay between the roles of requirements engineer and architect, mediated through the reference architecture, is described and illustrated with an example of integrating a new feature into a mobile phone.
|Item Type:||Book Chapter|
|Copyright Holders:||2011 Springer|
|Academic Unit/Department:||Mathematics, Computing and Technology > Computing & Communications|
|Interdisciplinary Research Centre:||Centre for Research in Computing (CRC)|
|Depositing User:||Bashar Nuseibeh|
|Date Deposited:||02 Feb 2012 15:04|
|Last Modified:||03 Dec 2012 15:48|
|Share this page:|
Actions (login may be required)
|Report issue / request change|