An embedded system is an applied computer system, as distinguished from other types of computer systems such as personal computers (PCs) or supercomputers. The definition of “embedded system” is fluid and difficult to pin down, as it constantly evolves with advances in technology and dramatic decreases in the cost of implementing various hardware and software components. In recent years, the field has outgrown many of its traditional descriptions. Electronic devices in just about every engineering market segment are classified as embedded systems. In short, outside of being “types of computer systems,” the only specific characterization that continues to hold true for the wide spectrum of embedded system devices is that there is no single definition reflecting them all. When approaching embedded systems architecture design from a systems engineering point of view, several models can be applied to describe the cycle of embedded system design. The embedded system design and development process is divided into four phases: creating the architecture, implementing the architecture, testing the system, and maintaining the system. The architecture of an embedded system is an abstraction of the embedded device, meaning that it is a generalization of the system that typically doesn’t show detailed implementation information such as software source code or hardware circuit design. At the architectural level, the hardware and software components in an embedded system are instead represented as some composition of interacting elements. Elements are representations of hardware and/or software whose implementation details have been abstracted out, leaving only behavioral and inter-relationship information. An embedded systems architecture can be used to resolve the challenges early in a project. Without defining or knowing any of the internal implementation details, the architecture of an embedded device can be the first tool to be analyzed and used as a high-level blueprint defining the infrastructure of a design, possible design options, and design constraints. What makes the architectural approach so powerful is its ability to informally and quickly communicate a design to a variety of people with or without technical backgrounds, even acting as a foundation in planning the project or actually designing a device. Because it clearly outlines the requirements of the system, an architecture can act as a solid basis for analyzing and testing the quality of a device and its performance under various circumstances. Examples of Embedded systems in different fields include following: · Automotive: ignition system, engine control, brake system. · Consumer electronics: PDAs, Telephones, Cameras etc. · Medical: Dialysis machines, prosthetic machines etc.
works at ISRO
Institute of Engineering and Technology Lucknow
Qis college of engineering and technology