EMBEDDED SYSTEM

EMBEDDED SYSTEM

ABSTRACT
                                                         
            The usual reason for embedding a computer is to interact with the environment, often by monitoring and controlling external machinery. Many embedded systems have substantially different design constraints than desktop computing applications. No single characterization applies to the diverse spectrum of embedded systems. Some combination of cost pressure, long life-cycle, real-time requirements, reliability requirements, and design culture dysfunction can make it difficult to be successful applying traditional computer design methodologies and tools to embedded applications there is currently little tool support for expanding embedded computer design to the scope of holistic embedded system design. Knowing the strengths and weaknesses of current approaches can set expectations appropriately, identify risk areas to tool adopters, and suggest ways in which tool builders can meet industrial needs. Many embedded systems have requirements that differ significantly both in details and in scope from desktop computers. The demands of the specific application and the interface with external equipment may dominate the system design. They must guarantee real time operation reactive to external events. Long life-cycles and in some cases extreme cost sensitivity require more attention to optimization based on these goals rather than maximizing the computational throughput.