%0 Conference Paper %1 liming_zhu_model_2009 %A Zhu, Liming %A Liu, Yan %B ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design, 2009. EA '09 %D 2009 %I IEEE %K Architecture Architecture; Australia; Computer Context Model Natural Programming; Software Unified about analysis; architecture; aspect code compilers; compositional cycle; description development development; diagnostics; driven framework; generation; language languages; life modeling modeling; nonfunctional program programs; reasoning science; software system systems; %P 49--54 %R 10.1109/EA.2009.5071584 %T Model Driven Development with non-functional aspects %X Model Driven Development (MDD) refers to the systematic use of models as primary engineering artifacts throughout a software development life cycle. In recently years, MDD has been increasingly employed to guide development with a focus on system modeling, code generation from models and white-box analysis of models. However, compositional system analysis regarding early Non-Functional Aspects/Properties (NFP) remains difficult. In this paper, we critically review the state-of-the-art of MDD in the context of non-functional aspects and shed some lights on the following two questions: 1) How to model Non-Functional Aspect/Property (NFP). The focus is to understand the different subtypes of a non-functional aspects and its compositional and emergent nature. 2) How models can be used for analyzing Non-functional Aspect/Property (NFP). This focuses on the analysis models in the form of reasoning frameworks (both qualitative and quantitative) behind each non-functional aspect. %@ 978-1-4244-3719-1

@inproceedings{liming_zhu_model_2009, abstract = {Model Driven Development {(MDD)} refers to the systematic use of models as primary engineering artifacts throughout a software development life cycle. In recently years, {MDD} has been increasingly employed to guide development with a focus on system modeling, code generation from models and white-box analysis of models. However, compositional system analysis regarding early {Non-Functional} {Aspects/Properties} {(NFP)} remains difficult. In this paper, we critically review the state-of-the-art of {MDD} in the context of non-functional aspects and shed some lights on the following two questions: 1) How to model {Non-Functional} {Aspect/Property} {(NFP).} The focus is to understand the different subtypes of a non-functional aspects and its compositional and emergent nature. 2) How models can be used for analyzing Non-functional {Aspect/Property} {(NFP).} This focuses on the analysis models in the form of reasoning frameworks (both qualitative and quantitative) behind each non-functional aspect.}, added-at = {2013-02-28T11:13:35.000+0100}, author = {Zhu, Liming and Liu, Yan}, biburl = {https://www.bibsonomy.org/bibtex/2bbdcc4482d6ca50cb490747f81dcdff6/fritzsolms}, booktitle = {{{ICSE} Workshop on {Aspect-Oriented} Requirements Engineering and Architecture Design, 2009. {EA} '09}}, doi = {10.1109/EA.2009.5071584}, interhash = {4376596c52d5f777c8f60173cc25e361}, intrahash = {bbdcc4482d6ca50cb490747f81dcdff6}, isbn = {978-1-4244-3719-1}, keywords = {Architecture Architecture; Australia; Computer Context Model Natural Programming; Software Unified about analysis; architecture; aspect code compilers; compositional cycle; description development development; diagnostics; driven framework; generation; language languages; life modeling modeling; nonfunctional program programs; reasoning science; software system systems;}, month = may, pages = {49--54}, publisher = {{IEEE}}, review = {Summary {(Fritz)} General review of non-functional aspects in {MDD} including approaches to requirements, provision, estimation, measurement \& model analysis for {NFRs.} Throughout they do not separate the design and architecture models. {NFRs} in requirements, models or {SLAs} (e.g. {WSDL)} Analysis models of systems are simplifications/abstractions which are useful to analyze aspects of the system - they are not necessarily a realistic model of the system. {NB:} Separation of {NFRs} for service \& service providers as infrastructure/architecture can realize client {NFRs} across diff service providers who themselves do not fulfill the client {NFRs} but some lower {NFR} required by the architecture in order to cumulatively realize client {NFRs.}}, timestamp = {2013-02-28T11:14:13.000+0100}, title = {{Model Driven Development with non-functional aspects}}, year = 2009 }