TY - GEN
T1 - Software internationalization
T2 - 2009 International Conference on New Trends in Information and Service Science, NISS 2009
AU - Abufardeh, Sameer
AU - Magel, Kenneth
PY - 2009
Y1 - 2009
N2 - Many of the requirements of Globalized (Internationalized 1) software that have a crosscutting impact are scattered through the entire software. The impact of these requirements presents many challenges that manifest themselves throughout the software development lifecycle. Inherent properties of crosscutting requirements, such as scattering (where their support is scattered across multiple classes) and tangling (where their support is tangled with elements supporting other requirements), reduce the reusability, extensibility, and traceability of the software artifacts [1]. Scattering and tangling are evident in the design and code of internationalized software and must be addressed fully. To remove scattering and tangling properties, developers must first identify and then separate the design and code of crosscutting behavior into independent modules or components. This paper discusses two important issues; when developers should identify and document crosscutting requirements; and where it should be handled throughout the software lifecycle.
AB - Many of the requirements of Globalized (Internationalized 1) software that have a crosscutting impact are scattered through the entire software. The impact of these requirements presents many challenges that manifest themselves throughout the software development lifecycle. Inherent properties of crosscutting requirements, such as scattering (where their support is scattered across multiple classes) and tangling (where their support is tangled with elements supporting other requirements), reduce the reusability, extensibility, and traceability of the software artifacts [1]. Scattering and tangling are evident in the design and code of internationalized software and must be addressed fully. To remove scattering and tangling properties, developers must first identify and then separate the design and code of crosscutting behavior into independent modules or components. This paper discusses two important issues; when developers should identify and document crosscutting requirements; and where it should be handled throughout the software lifecycle.
KW - Aspect oriented programming (aop)
KW - Crosscutting requirements and functionality
KW - Dsdm lifecycle
KW - Internationalization
KW - Separation of concerns (soc)
UR - http://www.scopus.com/inward/record.url?scp=70449596266&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=70449596266&partnerID=8YFLogxK
U2 - 10.1109/NISS.2009.202
DO - 10.1109/NISS.2009.202
M3 - Conference contribution
AN - SCOPUS:70449596266
SN - 9780769536873
T3 - Proceedings - 2009 International Conference on New Trends in Information and Service Science, NISS 2009
SP - 447
EP - 450
BT - Proceedings - 2009 International Conference on New Trends in Information and Service Science, NISS 2009
Y2 - 30 June 2009 through 2 July 2009
ER -