Open architecture

From HandWiki
Revision as of 21:11, 6 February 2024 by Steve2012 (talk | contribs) (over-write)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Short description: Software design paradigm emphasizing ease of swapping out and modifying components

Open architecture is a type of computer architecture or software architecture intended to make adding, upgrading, and swapping components with other computers easy.[1] For example, the IBM PC,[2] Amiga 2000[3] and Apple IIe have an open architecture supporting plug-in cards, whereas the Apple IIc computer has a closed architecture. Open architecture systems may use a standardized system bus such as S-100, PCI or ISA or they may incorporate a proprietary bus standard such as that used on the Apple II, with up to a dozen slots that allow multiple hardware manufacturers to produce add-ons, and for the user to freely install them. By contrast, closed architectures, if they are expandable at all, have one or two "expansion ports" using a proprietary connector design that may require a license fee from the manufacturer, or enhancements may only be installable by technicians with specialized tools or training.

Computer platforms may include systems with both open and closed architectures. The Mac mini and Compact Macintosh are closed; the Macintosh II and Power Mac G5 are open. Most desktop PCs are open architecture.

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.[4] 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 U.S. Navy.[5]

See also

References

  1. Clifton A. Ericson, II (12 April 2011). Concise Encyclopedia of System Safety: Definition of Terms and Concepts. John Wiley & Sons. p. 272. ISBN 978-1-118-02865-0. https://books.google.com/books?id=uousK00QAREC&pg=PA272. 
  2. Michael J. Miller (August 8, 2011). "Why the IBM PC Had an Open Architecture". pcmag.com. https://forwardthinking.pcmag.com/pc-hardware/286065-why-the-ibm-pc-had-an-open-architecture. ""In some ways, the most far-reaching decision made by the team that built the IBM PC was to use an open architecture, rather than one that was proprietary to IBM. That decision led to the market for add-in boards, for large numbers of third party applications, and eventually to a large number of competitors all creating "IBM-compatible" machines. Bill Lowe went to IBM's Corporate Management Committee in July 1980 to propose the project"" 
  3. Computer History: From The Antikythera Mechanism To The Modern Era on tomshardware.com by Aris Mpitziopoulos "Amiga was one of the first computers with an open architecture. It had two expansion slots, one on the side and one on the bottom." (July 3, 2016)
  4. Sakamura, Ken (6 December 2012). TRON Project 1987 Open-Architecture Computer Systems: Proceedings of the Third TRON Project Symposium. ISBN 9784431680697. https://books.google.com/books?id=Zk2qCAAAQBAJ&pg=PP6. 
  5. "The HOW and WHY of OPEN ARCHITECTURE". navy.mil. http://www.navy.mil/navydata/cno/n87/usw/spring08/HowAndWhy.html.