In engineering,hardware architecture refers to the identification of a system's physical components and their interrelationships. This description, often called ahardware design model, allows hardware designers to understand how their components fit into a system architecture and provides to software component designers important information needed for software development and integration. Clear definition of a hardware architecture allows the various traditional engineering disciplines (e.g., electrical and mechanical engineering) to work more effectively together to develop and manufacture new machines, devices and components.[1]
Hardware is also an expression used within the computer engineering industry to explicitly distinguish the (electronic computer) hardware from thesoftware that runs on it. Buthardware, within theautomation andsoftware engineering disciplines, need not simply be a computer of some sort. A modern automobile runs vastly moresoftware than the Apollo spacecraft. Also, modern aircraft cannot function without running tens of millions of computer instructions embedded and distributed throughout the aircraft and resident in both standard computer hardware and in specialized hardware components such as IC wired logic gates, analog and hybrid devices, and other digital components. The need to effectively model how separate physical components combine to form complex systems is important over a wide range of applications, including computers, personal digital assistants (PDAs), cell phones, surgical instrumentation, satellites, and submarines.
Hardware architecture is the representation of an engineered (orto be engineered) electronic or electromechanical hardware system, and the process and discipline for effectively implementing thedesign(s) for such a system. It is generally part of a larger integrated system encompassinginformation,software, and deviceprototyping.[2]
It is arepresentation because it is used to convey information about the relatedelements comprising a hardware system, the relationships among those elements, and therules governing those relationships.
It is aprocess because a sequence of steps is prescribed to produce or change the architecture, and/or a design from that architecture, of a hardware system within a set of constraints.
It is adiscipline because a body of knowledge is used to inform practitioners as to the most effective way to design the system within a set of constraints.
A hardware architecture is primarily concerned with the internal electrical (and, more rarely, themechanical)interfaces among the system'scomponents orsubsystems, and theinterface between the system and its external environment, especially the devices operated by or the electronic displays viewed by auser. (This latter, special interface, is known as thecomputer human interface,AKA human computer interface, orHCI; formerly called the man-machine interface.)[3] Integrated circuit (IC) designers are driving current technologies into innovative approaches for new products. Hence, multiple layers of active devices are being proposed as single chip, opening up opportunities for disruptive microelectronic, optoelectronic, and new microelectromechanical hardware implementation.[4][5]
Prior to the advent of digital computers, the electronics and other engineering disciplines used the terms system and hardware as they are still commonly used today. However, with the arrival of digital computers on the scene and the development of software engineering as a separate discipline, it was often necessary to distinguish among engineeredhardware artifacts,software artifacts, and the combined artifacts.
Aprogrammable hardware artifact, or machine, that lacks its computer program is impotent; even as a software artifact, or program, is equally impotent unless it can be used to alter the sequential states of a suitable (hardware) machine. However, a hardware machine and its programming can be designed to perform an almost illimitable number of abstract and physical tasks. Within the computer and software engineering disciplines (and, often, other engineering disciplines, such as communications), then, the terms hardware, software, and system came to distinguish between the hardware that runs acomputer program, the software, and the hardware device complete with its program.
A hardware can be controlled from a software with the help of a middle device called hardware controller, this hardware controller can be used to perform various automated task from hardware, generally hardware controller consist of GPIO(general purpose input and output) pins, these pin's behaviour controlled by the piece of code.[6]
Thehardware engineer or architect deals (more or less) exclusively with the hardware device; thesoftware engineer or architect deals (more or less) exclusively with the program; and thesystems engineer orsystems architect is responsible for seeing that the programming is capable of properly running within the hardware device, and that the system composed of the two entities is capable of properly interacting with its external environment, especially the user, and performing its intended function.
A hardware architecture, then, is an abstract representation of an electronic or an electromechanical device capable of running a fixed or changeable program.[7][8]
A hardware architecture generally includes some form of analog, digital, orhybrid electronic computer, along with electronic and mechanical sensors and actuators. Hardware design may be viewed as a 'partitioningscheme,' oralgorithm, which considers all of the system's present and foreseeable requirements and arranges the necessary hardware components into a workable set of cleanlyboundedsubsystems with no more parts than are required. That is, it is a partitioning scheme that is exclusive, inclusive, andexhaustive. A major purpose of the partitioning is to arrange the elements in the hardware subsystems so that there is a minimum of electrical connections and electronic communications needed among them. In both software and hardware, a good subsystem tends to be seen as a meaningful "object." Moreover, a clear allocation of user requirements to the architecture (hardware and software) provides an effective basis forvalidation tests of the user's requirements in the as-built system.
{{cite journal}}: CS1 maint: multiple names: authors list (link){{cite journal}}: CS1 maint: multiple names: authors list (link){{cite journal}}: CS1 maint: multiple names: authors list (link){{cite journal}}: CS1 maint: multiple names: authors list (link){{cite journal}}: CS1 maint: multiple names: authors list (link){{cite journal}}: CS1 maint: multiple names: authors list (link)