Competence development program for designers and system architects

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    What is your ambition? It is not realistic to think that you can educate everyone to the level of a top architect. SW-architects often have a supporting role and are not leading in innovation. Try to make the presentation more concrete by mentioning and positioning some roles and grow-paths of a system architect.

    Give insight in the development path. What are the qualifications? Make clear that it is a modular approach. A 4 – 7 years program is a very long time. What is the starting level. Make it more explicit (profiles) How do you decide if someone can start. Are you going to develop an specific intake, physiological test ????? How do you define the potential of the student early in the program. The title “Industrial Master System Architecting” must have value. This requires not only content but also exposure and marketing. Soft skills and leadership must also be a part of the program. There are too much architects who are technical experts with a supporting attitude.

    When we look at ASML we want to have 15-20 people who are participating in the program. This means that ASML has to deliver 5 new students every year. To have a pipeline of 15-20 man we need 5-10 new students every year 5 people in yr 1 4 people in yr 2 3 people in yr 3 2 people in yr 4 1 people in yr 5

    1 Favorite

    Competence development program for designers and system architects - Presentation Transcript

      • Competence Development Program
      • for
      • Designers & Systems Architects
      Digital Television Lithography Systems Medical Systems Mobile Phones Automotive Systems Digital Printers Control Systems
      • Program vision, mission and approach
      • Competence Development Program outline
      • Target groups
        • Positioning designers & architects
        • System engineering on multiple levels
        • Extending responsibilities
        • Responsibility hierarchy
        • Functional profiles
      • Competence development program
        • Learning goals
        • Way of working
        • Program designer level
        • Program domain architect level
        • Program system architect level
      • Vision System architecture is a key asset for high-tech systems industry.
      • Mission of the program To provide a world-class competence development program for (system) architects
      • Approach
        • A 3-level competence development program for high-tech professionals
        • Content is based on latest embedded system engineering insights
        • Top level teachers & coaches
        • Combination of theory with practical assignments
        • Both individual as group assignments
        • Based on partnership with high-tech systems industry & knowledge providers
      Program vision, mission & approach
      • Competence development program with 3 stages
      • Competence levels:
          • Designer (component)
          • Domain architect (discipline, subsystem, function)
          • System architect (system)
      • Target group
        • High potentials from industry with a bachelor or master of science degree
        • Minimum of 5/7 years of working experience.
      • Industry as classroom TM concept
        • Theory based on latest system engineering insights
        • Teaching and individual coaching by senior professionals with industrial background
        • Learning directly applied to current projects
      • Access to professional network to broaden the scope
      Competence development program outline
    1. Positioning designers & architects Business context small large Technical context small large Mono engineer Technical specialist Program manager Team leader Project leader Business manager Senior engineer System architect poor defined design/integration assignment Domain architect less defined design/integration assignment Designer well defined design/integration assignment Business responsibility Technical responsibility Product responsibility broadening Balancing the ilities Business context
    2. Market business/strategic operational Product global focus local focus Process & organization company level group level Technology mono multi Personal skills team member leadership System engineering on multiple levels
    3. Test Build & Integration Component Design System Design System Requirements Product Concept 11 yrs 9 yrs 7 yrs 5 yrs 0 yrs Extending responsibilities Project stages system architect (poor defined design/integration assignment) business/strategic, company level, system/value chain, multi technology, leadership, environment poor defined domain architect (Less defined design/integration assignment) tactic, department, system properties, guiding, (multi) technology, guiding, environment less defined designer (well defined design/integration assignment) operational, group level, single element, group member, (mono) technology, environment well defined Engineer (well defined technology)
    4. Business & technology roadmap User needs System roadmap Domain needs Responsibility hierarchy User requirements System requirements System architecture System design Implementation System integration System test Comp. requirements Component design Implementation Test System Architect Domain requirements Domain architecture Domain design Implementation Integration Test Designer Domain Architect
    5. Key characteristics Designer
      • Keeps abreast of technical matters relevant for his technical domain, showing interest in other technical domains.
      General
      • Eager
      • Team player
      • Accepts feedback
      • Communicative
      • Flexible
      • Negotiation skills
      Personal skills
      • In-depth knowledge of technical discipline and interfaces
      • Knowledge of existing and upcoming development concepts, design methods, technology patterns and tools
      • Knowledge of existing technology/components
      Technology
      • Defines & deploys the components requirements + design and keeps track on implementation
      • Knowledge of integration and test of the component in a broader sub-system context
      Product
      • Has knowledge of (multi-disciplinary) development processes, features, benefits and constraints on a department level
      • Interacts with and influences the relationship between component, process and department
      Process & organization
      • Is interested in market, user needs and product
      • Has insight in user needs that affect his technical domain.
      • Has knowledge of the (sub) system context in which the component is situated
      Market
    6. Key characteristics Domain Architect
      • Keeps abreast of technical, application and competition developments regarding architectural and industrial matters relevant for the domain showing interest in the business aspects
      Overall
      • Has conceptual and analytical capabilities and is a creative thinker
      • Is a team player
      • Is able to challenge well-trodden paths
      • Natural preponderance, listener, communicative, business minded, improvement attitude, flexible, …
      + Personal skills
      • Has sufficient in-depth knowledge of all technical disciplines and interfaces relevant for the domain
      • Has knowledge of existing and upcoming development concepts, design methods, technology patterns and tools that are relevant for the domain
      • Understands and interacts with other technologies
      • Has knowledge of existing technology/components
      + Technology
      • Has knowledge of the product context in which the domain is situated
      • Defines & deploys the domains architecture & requirements in its multi-domain product context
      • Decomposes & integrates the domain design into multiple views and keeps track on implementation
      • Balances the views of the domain in a broader product & technology context
      + Product
      • Has knowledge of multidisciplinary development processes, features, benefits and constraints relevant for the domain
      • Interacts with and influences the relationship between domain, process and related departments
      + Process & organization
      • Has a domain related market insight with an appropriate horizon (1 to 3 years)
      • Has insight in market trends and can translate them into domain specific long term consequences
      • Has insight in relation between customer needs, product and relevant domain(s)
      • Contributes to the alignment between company research & development program and relevant domain(s)
      + Market
    7. Key characteristics System Architect
      • Keeps abreast of technical, application, market, competition and social developments in the relevant technological and industrial areas showing understanding of the companies position and business interests
      Overall
      • Has conceptual and analytical capabilities and is a creative thinker
      • Is able to challenge well-trodden paths
      • Technical leadership in a product context
      • Natural preponderance, listener, communicative, business minded, improvement attitude, decisiveness, flexible, …
      + Personal skills
      • Has sufficient in-depth knowledge of all relevant technical disciplines and interfaces
      • Has knowledge of development concepts, design methods, technology patterns and tools
      • Has interest in up-coming concepts, design methods, technology patterns and tools
      + Technology
      • Defines & deploys the product/technology roadmap
      • Defines & deploys the top level architecture + requirements
      • Decomposes the product design into multiple (system) views and keeps track on implementation
      • Defines integration strategy and keeps track on the following steps
      • Decides on architectural issues with a strategic impact
      • Balances synergy and market specialization in the relation between product, product family, component/technology, re-use, lifecycle, make-buy, …
      + Product
      • Has knowledge of development processes, features, benefits and constraints on an organizational level
      • Interacts with and influences the relationship between product, process and organization
      + Process & organization
      • Has a market insight with an appropriate horizon (3-5 years)
      • Has insight in relation between social and market trends, customer needs and products
      • Contributes to the alignment between company strategy and research & development program
      • Has knowledge of the application context in which the product is used
      + Market
    8. Learning goals CDP Design flow & Risk reduction System thinking & holistic lifecycle view System design, trade offs & integration Architecting in a changing business context Operational excellence Personal & communication skills Technical leadership Influence & balancing stakeholders Broadening technology scope
      • Architecting in a new changing business context
      • Influence & balancing stakeholders
      • System thinking
      • System design & integration
      • System qualities & trade offs
      • Operational excellence
      • Personal skills & communication
      • Design flow & risk management
      • Broadening technology scope
      Main learning goals Designer Domain Architect System Architect Personal skills Technology Product Process & organization Market Competence topic
    9. courses Architectural assignment Experience sharing Way of working Courses + practical case Design assignment Guru's Strategic personal assignment & peer review Thematic working group Courses provided by others Theory Learning on the job Professional Network 1,5 year 1,5 year 1 year Designer Domain Architect System architect (well defined) (less defined) (poor defined) broadening system thinking + architecting in a (technology) scope trade-offs changing bus. context
    10. Robot design contest Reflection Design assignment within the own company Theory Designer level overview and way of working (duration 1,5 yrs) Design flow & risk management (# days) System Control (2 days) Electronics (5 days) System Software (3 days) Embedded Software (3 days) System Control (1 day) Electronics (3 days) System Software (2 days) Embedded Software (2 days) Design assignment V1 Design assignment V2 Networking day 1 Networking day 2 Networking day 3 Networking day 4 Integrated practical case 15- 25 days 9 days 4 days # wks Design assignment V3 Design assignment V4 Introduction Design case (1 day) Personal & communication skills (# days)
    11. Integrated assignment within own company Reflection Networking assignment Theory Domain architect level overview and way of working (duration 1,5 yrs) System Architecting System Integration & Test Modeling System Architectures Supply chain, Service & Logistics Modeling & Analysis Networking assignment Networking assignment Networking day 1 Networking day 2 Networking day 3 Networking day 4 32 days # days 4 days 4 days Networking assignment Networking assignment Technology & Innovation Management Software Architecting Architecting for System Performance Architecting for System Reliablility
    12. Strategic personal assignment within own company Peer review Guru’s System architect level overview and way of working (duration 15 yr) To be defined

    + jorisvandenakerjorisvandenaker, 5 months ago

    custom

    304 views, 1 favs, 0 embeds more stats

    This presentaion gives an overview of the competenc more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 304
      • 304 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 1
    • Downloads 9
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories