%0 Journal Article %1 mattsson_linking_2009 %A Mattsson, Anders %A Lundell, Bjorn %A Lings, Brian %A Fitzgerald, Brian %D 2009 %J IEEE Transactions on Software Engineering %K Architecture; MDD formal methods; %N 1 %P 83--93 %R 10.1109/TSE.2008.87 %T Linking Model-Driven Development and Software Architecture: A Case Study %V 35

@article{mattsson_linking_2009, added-at = {2013-02-28T11:13:35.000+0100}, author = {Mattsson, Anders and Lundell, Bjorn and Lings, Brian and Fitzgerald, Brian}, biburl = {https://www.bibsonomy.org/bibtex/2574f33791565e50e49a47e4b0d973fcf/fritzsolms}, doi = {10.1109/TSE.2008.87}, interhash = {7e45d48f86d22d297d2b72a659263491}, intrahash = {574f33791565e50e49a47e4b0d973fcf}, issn = {0098-5589}, journal = {IEEE Transactions on Software Engineering}, keywords = {Architecture; MDD formal methods;}, lccn = {0000}, month = {January}, number = 1, pages = {83--93}, review = {SUMMARY (Fritz) - Critically looks at MDD case study, identifying shot-comings of MDD approach used in that study - Conclude that it is important to formalize architectural design rules. - Highlight time-consuming error-prone manual practices required to keep system consistent with its architecture. - Nice summary statement of MDD: A basic premise of MDD is to capture all important design information in a set of formal or semi-formal models ...}, shorttitle = {Linking Model-Driven Development and Software Architecture}, timestamp = {2013-02-28T11:13:57.000+0100}, title = {Linking Model-Driven Development and Software Architecture: A Case Study}, volume = 35, year = 2009 }