Content deleted Content added
→top: updated link |
Citation bot (talk | contribs) Added publisher. | Use this bot. Report bugs. | Suggested by Dominic3203 | Category:Computer architecture | #UCB_Category 26/88 |
||
Line 7:
Similarly, an open software architecture is one in which additional software modules can be added to the basic framework provided by the architecture. Open APIs (Application Programming Interfaces) to major software products are the way in which the basic functionality of such products can be modified or extended. The [[Google APIs]] are examples. A second type of open software architecture consists of the messages that can flow between computer systems. These messages have a standard structure that can be modified or extended per agreements between the computer systems. An example is IBM's [[Distributed Data Management Architecture]].
Open architecture allows potential users to see inside all or parts of the architecture without any proprietary constraints.<ref>{{cite book|url=https://books.google.com/books?id=Zk2qCAAAQBAJ&pg=PP6 |title=TRON Project 1987 Open-Architecture Computer Systems: Proceedings of the Third TRON Project Symposium|isbn=9784431680697|last1=Sakamura|first1=Ken|date=6 December 2012|publisher=Springer }}</ref> Typically, an open architecture publishes all or parts of its architecture that the developer or integrator wants to share. The [[open business]] processes involved with an open architecture may require some license agreements between entities sharing the architecture information. Open architectures have been successfully implemented in many diverse fields, including the [[United States Navy|U.S. Navy]].<ref>{{cite web|url=http://www.navy.mil/navydata/cno/n87/usw/spring08/HowAndWhy.html|title=The HOW and WHY of OPEN ARCHITECTURE|work=[[navy.mil]]|access-date=2015-07-02|archive-url=https://web.archive.org/web/20150705034123/http://www.navy.mil/navydata/cno/n87/usw/spring08/HowAndWhy.html|archive-date=2015-07-05|url-status=dead}}</ref>
==See also==
| |||