Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products Embedded software within Upmarket.

Slides:



Advertisements
Similar presentations
Integration of MBSE and Virtual Engineering for Detailed Design
Advertisements

Component-Based Software Engineering Main issues: assemble systems out of (reusable) components compatibility of components.
The Datacenter Needs an Operating System Matei Zaharia, Benjamin Hindman, Andy Konwinski, Ali Ghodsi, Anthony Joseph, Randy Katz, Scott Shenker, Ion Stoica.
Component Oriented Programming 1 Chapter 2 Theory of Components.
A reconfigurable system featuring dynamically extensible embedded microprocessor, FPGA, and customizable I/O Borgatti, M. Lertora, F. Foret, B. Cali, L.
PRESENTED BY USHA GHIMIRE. Introduction-The need for MBSE MBSE now and present shortcomings A view of MBSE in the future Key advantages and disadvantages.
Chapter 13 Embedded Systems
System Level Design: Orthogonalization of Concerns and Platform- Based Design K. Keutzer, S. Malik, R. Newton, J. Rabaey, and A. Sangiovanni-Vincentelli.
1 Presentation for Professor Sergiu Dascalu IGT: The Company and Its Products.
H 1 Building Product Populations with Software Components, © 2002 Koninklijke Philips Electronics NV Building Product Populations with Software.
INTRODUCTION OS/2 was initially designed to extend the capabilities of DOS by IBM and Microsoft Corporations. To create a single industry-standard operating.
1 Software Architecture: a Roadmap David Garlen Roshanak Roshandel Yulong Liu.
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica System architectures Updated: November 2014.
Mobile Application Development
Page 1 Building Reliable Component-based Systems Chapter 12 - The Koala Component Model Chapter 12 The Koala Component Model.
Copyright Arshi Khan1 System Programming Instructor Arshi Khan.
SET TOP BOX What is set-top box ? An interactive device which integrates the video and audio decoding capabilities of television with a multimedia application.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse 2.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 18 Slide 1 Software Reuse.
Software Engineering Muhammad Fahad Khan
Software Reuse Prof. Ian Sommerville
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 14Slide 1 Design with Reuse l Building software from reusable components.
By Mihir Joshi Nikhil Dixit Limaye Pallavi Bhide Payal Godse.
Nurjana Technologies Company Presentation. Nurjana Technologies (NT) is a small business enterprise founded in 2012 and operating in Aerospace and Defence.
Distributed Systems 1 CS- 492 Distributed system & Parallel Processing Sunday: 2/4/1435 (8 – 11 ) Lecture (1) Introduction to distributed system and models.
An Introduction to Software Architecture
Components in Product Lines - The Next Steps Rob van Ommering Philips Research EuroMicro 2005, Porto, Portugal, September 1 st, 2005.
Panel Three - Small Businesses: Sustaining and Growing a Market Presence Open Interfaces and Market Penetration Protecting Intellectual Innovation and.
Presenter : Ching-Hua Huang 2013/7/15 A Unified Methodology for Pre-Silicon Verification and Post-Silicon Validation Citation : 15 Adir, A., Copty, S.
High Performance Embedded Computing © 2007 Elsevier Lecture 3: Design Methodologies Embedded Computing Systems Mikko Lipasti, adapted from M. Schulte Based.
High Performance Embedded Computing © 2007 Elsevier Chapter 1, part 2: Embedded Computing High Performance Embedded Computing Wayne Wolf.
1 Introduction to Middleware. 2 Outline What is middleware? Purpose and origin Why use it? What Middleware does? Technical details Middleware services.
Architectural Design lecture 10. Topics covered Architectural design decisions System organisation Control styles Reference architectures.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Introduction CS 3358 Data Structures. What is Computer Science? Computer Science is the study of algorithms, including their  Formal and mathematical.
1 Geospatial and Business Intelligence Jean-Sébastien Turcotte Executive VP San Francisco - April 2007 Streamlining web mapping applications.
Refining middleware functions for verification purpose Jérôme Hugues Laurent Pautet Fabrice Kordon
HRL © 2009 IBM Corporation Model-Driven Product-Lines for Embedded Software and for Supply-Chain Companies Tali Yatzkar-Haham Julia Rubin,
2006 Chapter-1 L1: "Embedded Systems - Architecture, Programming and Design", Raj Kamal, Publs.: McGraw-Hill, Inc. 1 Introduction to Embedded Systems.
Manag ing Software Change CIS 376 Bruce R. Maxim UM-Dearborn.
07/09/04 Johan Muskens ( TU/e Computer Science, System Architecture and Networking.
1 Computing Challenges for the Square Kilometre Array Mathai Joseph & Harrick Vin Tata Research Development & Design Centre Pune, India CHEP Mumbai 16.
By Dinesh Bajracharya Nepal Components of Information system.
Axel Jantsch 1 Networks on Chip Axel Jantsch 1 Shashi Kumar 1, Juha-Pekka Soininen 2, Martti Forsell 2, Mikael Millberg 1, Johnny Öberg 1, Kari Tiensurjä.
International Technology Centre Leuven Pg ??-?? ?Subject? By: ?.??? Philips ITCL SEESCOA checklist Piet Wauters Groupleader Embedded SW Tel.:+32.
© 2013, published by Flat World Knowledge Chapter 10 Understanding Software: A Primer for Managers 10-1.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Component-based Development Process and Component Lifecycle Ivica Crnkovic Mälardalen University, Department of Computer Engineering Sweden
Computer Science 340 Software Design & Testing Software Architecture.
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
Gerhard Dueck -- CS3013Architecture 1 Architecture-Centric Process  There is more to software development then going blindly through the workflows driven.
 Can access all API’s made available by OS vendor.  SDK’s are platform-specific.  Each mobile OS comes with its own unique tools and GUI toolkit.
1 Get All Answers Get All Answers. Contents History of Android Android Fragmentation The Role of Google Features and Architecture Android Software Development.
By Adam Reimel. Outline Introduction Platform Architecture Future Conclusion.
Component-based Software Engineering Process and Component Lifecycle Ivica Crnkovic Mälardalen University, Department of Computer Engineering Sweden
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
Embedded Systems. What is Embedded Systems?  Embedded reflects the facts that they are an integral.
Software Reuse. Objectives l To explain the benefits of software reuse and some reuse problems l To discuss several different ways to implement software.
SOA (Service Oriented Architecture)
Software Reuse ©Ian Sommerville 2006.
Programming Languages
Component-Based Software Engineering
Architecture Description Languages
An Introduction to Software Architecture
HIGH LEVEL SYNTHESIS.
Chapter 7 –Implementation Issues
4+1 View Model of Software Architecture
4+1 View Model of Software Architecture
Presentation transcript:

Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products Embedded software within Upmarket TV Guy Van Hooveld Based on a presentation by Rob Van Ommering

Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products Contact persons  Guy Van Hooveld - Software development manager Brugge  Aad Van Zanten - Technology manager Brugge  Erwin Raeds - ASD manager Brugge  Hans Aerts - Overall project manager E’ven

Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products Build a Variety of CE Video Products UTV Flat TV Projection TV DTV MG-R Products MG-R Products Basic TV TV/VCR VCR DVD LCD Projection ‘Potential’ MG-R Products ‘Potential’ MG-R Products Price Region Video Output Device Storage Device Broadcasting Standard Chip Technology Sound Features Dimensions of variation

Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products Upmarket TV  High-end TV application  large number of products (types)  growing regional diversity  dependency on local (regional) situation (signals, providers…)  several ranges to be covered by reuse  Technology 16 bits microprocessor architecture (today) RTOS embedded software C programming language - coding rules - QA-C many key components to implement the functionality (today) reuse necessary component based technology introduced ROM size 128K -> 4MB (doubling every 18 months) debugging host vs target / simulator vs ICE cost driven

Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products Organization  Multisite development 70 people in Brugge  specification  technology management  TV-platform  integration projects  end responsibility 15 people in E’ven  subsystem development  architectures 80 people in Bangalore  subsystem development  Several types of projects small - 5 manyears medium - 15 manyears large manyears  Profiles Majority Ing. + Ir. + Grad.

Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products Process and methodology  CMM standard used (level 2 KPAs - see hereunder)  Requirements management Internal tool used (formal description language) evolution to use cases and UML investigated  Configuration management Continuus package is being used New challenges related to subsystem oriented development and distributed multisite development  Subcontract management  Planning and tracking  Quality assurance  Other levels KPAs partially addressed if applicable

Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products Parts List Rom Solution: Use Components Audio Dolby Projection Tuner Teletext EPG Wide Flat Tuner Components Video 100 Hz Source Select Source Select Direct

Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products CE Distributes Software Development Involved now To be involved Bangalore Singapore Eindhoven Brugge Wien Knoxville Sunnyvale Briarcliff Hamburg Southampton

Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products Solution: Use Subsystems Products (configurations) Subsystems or Standard designs (deployment) Basic components (assembly) Advantages:  Hide low-level assembly complexity from product creators  Concentrate domain knowledge (TV, Txt, UI) in capability centres Is a subsystem a component? Yes and no (see later)!

Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products Overall View Common software architecture, coding conventions, tools,... Common software architecture, coding conventions, tools,... Reusable standard designs, to be used in various products Reusable standard designs, to be used in various products Commercial products, created from subsystems Commercial products, created from subsystems Architecture Projects Product Execution Projects MG Re-engineeringCE Common Platform Architecture & Design Implementation & Test Evolution & Integration Subsystem Projects

Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products ‘Layered’ Architecture A/V hardware uP hardware Applications Application software need UI peope  added value here! Application software need UI peope  added value here! Computing platform (OS) Computing platform (OS)  P API OS Software need OS people  buy in OS Software need OS people  buy in  P abstraction A/V & data platform A/V & data platform A/V API Signal processing software HW/SW guys and girls  Semiconductors A/V abstraction Signal processing hardware (general purpose) computing hardware (general purpose) computing hardware

Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products Applications Computing platform (OS) Computing platform (OS) A/V & data platform A/V & data platform Comparing Layered Architectures drivers Control Resources GFL A/V Comp. System A/V drivers Applications OS Calling hierarchy G+4 Phys. Dev. Applications General Mechanisms Log. Dev. Services OS Applications A/V drivers ‘Development’ hierarchy

Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products Actual Subsystems TvPlatform tvplf TvPlatform tvplf InfraStructure infra InfraStructure infra A/V and Data Platform Applications & Services A/V Platform API UIMS uims UIMS uims TeletextLvl25 txplf TeletextLvl25 txplf AnalogEPG epg AnalogEPG epg DealerService deal DealerService deal SDE sde SDE sde Factory fact Factory fact Computing Platform & Development Environment VBArtist vbart VBArtist vbart ATSC atsc ATSC atsc TvServices tvsvc TvServices tvsvc UI98Applications apps UI98Applications apps The following subsystems are currently defined within MG-R : Computing Platform API

Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products Subsystem and Product Projects XXX PL:X XXX PL:X InfraStructure Arch:X InfraStructure Arch:X TV Platform Arch:X TV Platform Arch:X MG-R Subsystems PL:X Status:Running Arch:X X MG-R Subsystems PL:X Status:Running Arch:X X XXX PL:X XXX PL:X XXX PL:X XXX PL:X XXX PL:X Status:X XXX PL:X Status:X SDE Arch:X SDE Arch:X TV Services Arch:X TV Services Arch:X Dealer/Service Arch:X Dealer/Service Arch:X Factory Arch:X Factory Arch:X UIMS Arch:X UIMS Arch:X UI98 Applications Arch:X UI98 Applications Arch:X XXX PL:X Status:X XXX PL:X Status:X Teletext Lvl2.5 Arch:X Teletext Lvl2.5 Arch:X XXX PL:X Status:X XXX PL:X Status:X Analog EPG Arch:X Analog EPG Arch:X Subsystem projects create one or more subsystem: XXX PL:X XXX PL:X ATSC Arch:X ATSC Arch:X XXX PL:X XXX PL:X Cluster8 Arch:X Cluster8 Arch:X MG-R Products (1) PL:X Status:X MG-R Products (1) PL:X Status:X XXX PL:X XXX PL:X XXX PL:X XXX PL:X Cluster9 Arch:X Cluster9 Arch:X Cluster 2b/6 Arch:X Cluster 2b/6 Arch:X Cluster 1/2a Arch:X Cluster 1/2a Arch:X Cluster 4 Arch:X Cluster 4 Arch:X Cluster 5 Arch:X Cluster 5 Arch:X MG-R Products (2) PL:X Status:X MG-R Products (2) PL:X Status:X XXX PL:X XXX PL:X EMG Arch:X EMG Arch:X Product projects create one (or more) product

Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products Subsystem and Product Roadmap Product and subsystem releases are carefully planned:

Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products Solutions Traditional Solution:  managers that control certain aspects Disadvantage:  most of the code resides in managers  these managers are very chassis specific! Traditional Solution:  managers that control certain aspects Disadvantage:  most of the code resides in managers  these managers are very chassis specific! tun hip picnic topic hop msp tuning program selection program selection video audio power system control Our Solution:  mirror the hardware composition  communicate through software signals Advantage:  creating a new chassis is nothing more than wiring the components Our Solution:  mirror the hardware composition  communicate through software signals Advantage:  creating a new chassis is nothing more than wiring the components tuner video ssl dec video featuring video output sound power srcdest

Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products Koala - Example

Philips Company Restricted Information and Software Technology MG-R: a Component Based Software Architecture for CE Products Conclusions - challenges  CMM and process improvement  continuous process to change the culture and the way of working  multi-site development  new subsystem/integration approach  consequences at configuration management level  consequences at requirements management level  managing technology change in a fast changing environment  new models/component development have to be proven (reuse…)  defects prevention to improve product quality