Library Oriented Architecture

<h2 id="principles">Principles</h2>
<p>Three principles rule Library Oriented Architecture frameworks:
</p>
<ol><li>A <a href="/facts/Software_library/xRzL3P7q">software library</a> implementation and subject area expertise must be constrained to only one <a href="/facts/Ontology_(information_science)/SQlhl6lp">ontology domain</a>.</li>
<li>A software library that needs to use concepts and <a href="/facts/Artifact_(software_development)/Y0osnVU0">artifacts</a> from a different ontology domain than the one it belongs to, must interface and reuse the library corresponding to that specific ontology domain.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a></li>
<li>All domain specific software libraries must be maintained and supported with separate <a href="/facts/Software_development_process/cIDtuNPN">life-cycles</a>.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a></li></ol>
<h2 id="benefits">Benefits</h2>
<p>Library Oriented Architecture may provide different process improvements to existing software engineering practices and <a href="/facts/Software_development_process/cIDtuNPN">software development life-cycle</a>. Some tangible benefits from its adoption are:
</p>
<ol><li>Simplify <a href="/facts/Configuration_management/BRDwuKRk">configuration management</a> of distributed systems.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a></li>
<li>Build highly <a href="/facts/Software_quality/7yoRvIuz">reliable software systems</a> because of the inherent properties and constraints of the LOA principles.</li>
<li><a href="/facts/Information_system/apcSzFLh">Information Systems</a> built using LOA are <a href="/facts/Software_Architecture/1Hokp0Ed">technology-independent</a>. These systems can easily replace or swap entire libraries and domain implementations with localized impact and minimal upstream ripple effect.</li>
<li>Increase the <a href="/facts/Software_maintenance/Uv39zQb0">Maintainability Index</a><a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a>  of your distributed systems and integration repositories.</li>
<li>Minimize the risk of <a href="/facts/Coupling_(computer_programming)/QEeSaXF3">high coupling</a>, this can be more evident on large <a href="/facts/Enterprise_system/RGa1b0bC">enterprise systems</a>.</li>
<li>Bring developers up to speed orders of magnitude more quickly than a traditional system. Move developers and teams across libraries and domain ontologies and collaborate seamlessly.</li>
<li>Spot bugs and zero-in on the problem almost instantly. There is something to be said about the amount of time a developer spends debugging.</li>
<li>Maximization of the <a href="/facts/Bus_factor/dKEMnHoV">Bus Factor</a> of the software engineering team.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a></li></ol>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Ontology_(information_science)/SQlhl6lp">Ontology (information science)</a></li>
<li><a href="/facts/Service-oriented_architecture/g8krR0dk">Service-oriented architecture</a></li>
<li><a href="/facts/Distributed_system/o5nyhqTF">Distributed system</a></li>
<li><a href="/facts/Modular_programming/sNoqKvRD">Modular programming</a></li>
<li><a href="/facts/Software_library/xRzL3P7q">Software library</a></li>
<li><a href="/facts/Software_design_pattern/mV7r4egw">Software design pattern</a></li>
<li><a href="http://micheltriana.com/2010/12/05/writing-elegant-code-and-the-maintainability-index/">Writing Elegant Code and the Maintainability Index</a></li>
<li><a href="http://blogs.msdn.com/b/zainnab/archive/2011/05/26/code-metrics-maintainability-index.aspx">Code Metrics – Maintainability Index</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>Gruber, Thomas Robert (1992). "Toward Principles for the Design of Ontologies Used for Knowledge Sharing" (PDF). International Journal of Human-Computer Studies. 43 (5–6): 907–928. doi:10.1006/ijhc.1995.1081. S2CID 1652449. <a href="http://tomgruber.org/writing/onto-design.pdf" target="_blank">http://tomgruber.org/writing/onto-design.pdf</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>Triana, Michel (2012-04-09). "Library Oriented Architecture". Archived from the original on 2014-06-26. Retrieved 2012-04-09. <a href="https://web.archive.org/web/20140626074722/http://micheltriana.com/2012/04/09/library-oriented-architecture/" target="_blank">https://web.archive.org/web/20140626074722/http://micheltriana.com/2012/04/09/library-oriented-architecture/</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
<li id="fn:3"><p>Crowley, Richard. "Developing Operability". Retrieved 2012-04-09. <a href="http://rcrowley.org/2012/02/25/superconf.html" target="_blank">http://rcrowley.org/2012/02/25/superconf.html</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li>
<li id="fn:4"><p>Triana, Michel (2010-12-05). "Writing Elegant Code and the Maintainability Index". Light of Bytes. WordPress. Archived from the original on 2014-05-25. Retrieved 2012-04-12. <a href="https://web.archive.org/web/20140525223141/http://micheltriana.com/2010/12/05/writing-elegant-code-and-the-maintainability-index/" target="_blank">https://web.archive.org/web/20140525223141/http://micheltriana.com/2010/12/05/writing-elegant-code-and-the-maintainability-index/</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li>
<li id="fn:5"><p>Redmond, Matthew C.; Paul Newton (2003). "Integrating GIS in the Engineering, Planning and Design Processes" (PDF). Retrieved 2012-04-12. {{cite journal}}: Cite journal requires |journal= (help) <a href="http://proceedings.esri.com/library/userconf/proc03/p0559.pdf" target="_blank">http://proceedings.esri.com/library/userconf/proc03/p0559.pdf</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li>
</ol>

Library Oriented Architecture open-in-new

Library Oriented Architecture