Penn CIS 700 - Integration of Embedded System Components

Unformatted text preview:

1CIS 700: Integration of Embedded System Components: Principles and PracticeFall '05CIS 7002CIS 700, Fall 2005 Class: Towne 307, 3-4:30 MW Instructor: Insup Lee Email: [email protected] Office: 602 Levine Office Hours: 2-2:55 TTh Course web: tbd2Challenges and Opportunities for Embedded SystemsInsup LeeDepartment of Computer and Information ScienceUniversity of PennsylvaniaSeptember 7, 2005Fall '05CIS 7004Embedded Systems Embedded system are o devices used to control, monitor or assist the operation of appliances, gadgets, equipment, machinery or plant;o an integral part of the system. The next frontiero Mainframe computing (60’s-70’s)y Large computers to execute big data processing applicationso Desktop computing (80’s-90’s)y One computer at every desk to do business/personal activitieso Ubiquitous computing (00’s-?)y Numerous computing devices in every room/persony “Invisible” part of the environment3Fall '05CIS 7005A Variety of Application Domains Hybrid and embedded systemso Aerospace, automobiles, robotics, process control, sensor networks, smart spaces Multimediao Virtual reality, immersive environment Consumer electronicso Mobile phones, office electronics, digital appliances Network componentso Bridges, routers, switches, hubs Medical devices and instrumentso Patient monitoring, MRI, infusion pumps, artificial organs E-businesso ATM, vending machines Distributed and grid computingo Critical infrastructure defense system, air traffic control, intelligent highway systems, emergence response systemFall '05CIS 7006Characteristics of Embedded Systems Tightly coupled to the physical world; i.e., interacts with (or reacts to) its environment Correct operation is subject to o Physical constraints imposed by the environmento Resource constraints of the device Heterogeneity, networked at larger scale Sociological and ethical requirementso Users are not system expertso Security and privacy4Fall '05CIS 7007Key Trends and Economic Impact Growing importance of software Great variety of component types Increasing complexity Increasing number of non-functional constraints Open standards Shortening time to market Increasing integration and networking Dependability Reuse of existing hardware and software componentsFall '05CIS 7008Example: Automotive Telematics In 2005, 30-90 processors per caro Engine control, Break system, Airbag deployment systemo Windshield wiper, door locks, entertainment systemso Example: BMW 745iy 2,000,000 LOCy Window CE OSy Over 60 microprocessors 53 8-bit, 11 32-bit, 7 16-bity Multiple networksy Buggy? Problemso Disparity between the design cycle of a car and the design cycle of embedded componentso Difficult to upgradeo Not possible to integrate the user’s own devices into a car5Fall '05CIS 7009Challenges Three aspects of embedded system developmento Embedding for smart controlo Creating new computing gadgetso Connecting the physical world to the computing infrastructure The goal is to make them invisible cost-effectively!o Trustworthy: should not fail (or gracefully degrade), and safe to use. The existence of embedded software becomes apparent only when anembedded system fails.o Context Aware: should be able to sense people, environment, and threats and to plan/notify/actuate responses to provide real-time interaction with the dynamically changing physical environment with limited resources.o Seamless Integration: should be invisible at multiple levels of a hierarchy: home systems, metropolitan systems, regional systems, and national systems.Fall '05CIS 70010Example: Home and Personal AppliancesYr~2025~2015Volume / Diversity2005Smart homes, home theaters, games, smart cars, etc.Intelligent devices, tools, appliances and software for assisted livingHome care facilities[Liu]6Fall '05CIS 70011Justifications Rapid advances in component technologies, e.g., o Smart gadgets, wearable sensors and actuators, robotic helpers, mobile devices o Wireless, wideband interconnects Increasing critical needs due too Aging baby-boom generation o Long life expectancyo New safety, security, and privacy concernsFall '05CIS 70012Embedded Home Environment7Fall '05CIS 70013Observations Number of users: 10 – 1000 million Types of sensors and actuators: 100’s Number of suppliers: 10 – 100’s Required reliability: <10,000 recalls/year User tolerance to glitches: minimum Product life cycles: 3 – 20 yrs Tolerable upgrade effort: minimumThe environment must be open and evolvable, & capable of self diagnosis, healing, maintenanceFall '05CIS 70014Desired Trends~20152005~2025Volume & DiversityQuality & UsabilityUnit costMaintenance cost8Fall '05CIS 70015R&D Needs Predictability and manageability Self-configuration and adaptive coordinationo Monitoring and system health New abstraction and computation models Incorporation of network geometry Interoperability for system integration Integration of technical, social, ethical, and public policy issues“Embedded, Everywhere: A Research Agenda for Networked Systems of Embedded Computers,”National Research Council, U.S.A.Fall '05CIS 70016Embedded Software The impact of information technology on embedded systems is exploding. Software development stands for 70-80 % of the overall development cost for some embedded systems. The development of embedded software components is neededo To help structured system design and system developmento To reduce the cost of overall system development and maintenance effortso To support the reuse of components within product families9Fall '05CIS 70017Pathological Interaction between RT and sync. protocols Pathfinder caused repeated resets, nearly doomed the missionUnexpected interactionsIncompatible assumptions of HW & SW regarding the operation of legs led to the loss of the Mars Polar Lander Implicit and inconsistent assumptions and abstractionsIncompatible Cross Domain Protocols[Sha]Fall '05CIS 70018Sources of difficulties  Unsound compositionalityo incompatible abstractions, incorrect or implicit assumptions in system interfaces.o incompatible real time, fault tolerance, and security protocols.o combination of components do not preserve functional and para-functional properties; unexpected feature interactions. Inadequate development infrastructureo the lack of domain specific-reference architectures, tools, and design patterns


View Full Document

Penn CIS 700 - Integration of Embedded System Components

Documents in this Course
Lists

Lists

19 pages

Actors

Actors

30 pages

Load more
Download Integration of Embedded System Components
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Integration of Embedded System Components and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Integration of Embedded System Components 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?