%0 Conference Paper %1 zhu_creating_2008 %A Zhu, L. %A Staples, M. %A Tosic, V. %B 12th International IEEE Enterprise Distributed Object Computing Conference, 2008. EDOC '08 %D 2008 %I IEEE %K Architecture; Australia; Australian Centralized Computer Distributed Ecosystems; Software Standardization; Standards architectural architecture; architectures; business business-to-business commerce; computing; control; creating data development; e-business electronic exchange financial industries; industry-wide industry; interoperability; lending management; message models; organizations; patterns; quality-centric quality; reference rule-based rules; service standards; system ultra-large %P 24--30 %R 10.1109/EDOC.2008.14 %T On Creating Industry-Wide Reference Architectures %X Many industries have been developing e-business standards to improve business-to-business interoperability on a mass scale. Most such standards are composed of business data models with some message exchange patterns. Such data-only standards leave a very large interpretation space for the implementation stage at each individual organization. Thus, true industry-wide interoperability is still hard to achieve. In this industry report, we describe our experiences in creating and evaluating reference architectures for the Australian lending industry. To achieve the right level of prescriptiveness, our reference architectures are deliberately non-structural. Instead, they are based on a set of quality-centric architectural rules. We devised new methods for analyzing interoperability and evaluating such industry-level reference architectures. The first reference architecture has now been adopted and achieved positive effects. We also summarize several other lessons we learned, such as the need to align reference architectures with industry structures. %@ 978-0-7695-3373-5

@inproceedings{zhu_creating_2008, abstract = {Many industries have been developing e-business standards to improve business-to-business interoperability on a mass scale. Most such standards are composed of business data models with some message exchange patterns. Such data-only standards leave a very large interpretation space for the implementation stage at each individual organization. Thus, true industry-wide interoperability is still hard to achieve. In this industry report, we describe our experiences in creating and evaluating reference architectures for the Australian lending industry. To achieve the right level of prescriptiveness, our reference architectures are deliberately non-structural. Instead, they are based on a set of quality-centric architectural rules. We devised new methods for analyzing interoperability and evaluating such industry-level reference architectures. The first reference architecture has now been adopted and achieved positive effects. We also summarize several other lessons we learned, such as the need to align reference architectures with industry structures.}, added-at = {2013-02-28T11:13:35.000+0100}, author = {Zhu, L. and Staples, M. and Tosic, V.}, biburl = {https://www.bibsonomy.org/bibtex/21bcf901e20eee8d617f45574cebf9b00/fritzsolms}, booktitle = {{12th International {IEEE} Enterprise Distributed Object Computing Conference, 2008. {EDOC} '08}}, doi = {10.1109/EDOC.2008.14}, interhash = {cbbc8669155ff400103d8622fe933389}, intrahash = {1bcf901e20eee8d617f45574cebf9b00}, isbn = {978-0-7695-3373-5}, keywords = {Architecture; Australia; Australian Centralized Computer Distributed Ecosystems; Software Standardization; Standards architectural architecture; architectures; business business-to-business commerce; computing; control; creating data development; e-business electronic exchange financial industries; industry-wide industry; interoperability; lending management; message models; organizations; patterns; quality-centric quality; reference rule-based rules; service standards; system ultra-large}, month = sep, pages = {24--30}, publisher = {{IEEE}}, review = {{SUMMARY} {(Fritz)} - A paper with little details. - Discuss implemented reference architecture for mortgage industry. - Reference architecture introduces domain objects \& rules and defines tactics to realize qualities. - No clean separation between architecture \& functional though - Talk about rules-based architecture (guess this means that the rules engine is the core architectural component)}, timestamp = {2013-02-28T11:14:13.000+0100}, title = {{On Creating {Industry-Wide} Reference Architectures}}, year = 2008 }