DOCSLIB.ORG

QP-Embedded Software Engineer

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

QUALIFICATIONS PACK - OCCUPATIONAL STANDARDS FOR ELECTRONICS INDUSTRY Contents 1. Introduction and Contacts.…….P1 2. Qualifications Pack……….….......P2 What are 3. OS Units……………..………….....….P3 Occupational 4. Glossary of Key Terms.……….…P12 Standards(OS)? 5. Nomenclature for QP & OS…..P14 OS describe what individuals need to do, know and understand in Introduction order to carry out a particular job Qualifications Pack- Embedded Software Engineer role or function SECTOR: ELECTRONICS OS are SUB-SECTOR: Semiconductor Design and Active Components performance standards that OCCUPATION: System software development individuals must REFERENCE ID: ELE/Q1501 achieve when carrying out ALIGNED TO: NCO-2004/NIL functions in the workplace, Embedded Software Engineer: Also called ‘Embedded Software together with Developer’, the Embedded Software Engineer is responsible for developing specifications of software module for the embedded system. the underpinning knowledge and Brief Job Description: The individual at work assesses the embedded understanding systems’ specification requirement, develops software, tests and validates the software in coordination with design engineers for system integration. Contact Us: ESSCI, New Delhi Personal Attributes: The job requires the individual to have: attention to Electronics Sector Skills details, good communication skills, logical thinking, and ability to work for Council of India long hours on computer. 422, Okhla Industrial Estate, Phase-III, New Delhi-110020 E-mail: 1 [email protected] Qualifications Pack For Embedded Software Engineer Qualifications Pack Code ELE/Q1501 Job Role Embedded Software Engineer Credits(NVEQF/NVQF/NSQF) TBD Version number 1.0 [OPTIONAL] Sector Electronics Drafted on 10/03/14 Job Details Job Semiconductor and Sub-sector Last reviewed on 24/03/14 Active components System software Occupation Next review date 24/03/15 development Job Role Embedded Software Engineer Also called, ‘Embedded Software Developer’ Understanding the embedded system specifications, developing software module as per the requirement, testing Role Description and validating the software module; coordinating with design engineers for system integration NVEQF/NVQF level 5 Minimum Educational Qualifications B.E. / B. Tech (Computer Science / IT) Maximum Educational Qualifications M.E / M. Tech Training Not applicable Experience Not applicable Compulsory: 1. ELE/N1501 Develop embedded system software Applicable National Occupational 2. ELE/N9909 Coordinate with colleague and co-workers Standards (NOS) Optional: Not applicable Performance Criteria As described in the relevant OS units 2 ELE/N1501 Develop embedded system software -------------------------------------------------------------------------------------------------------------------- Overview This OS unit is about developing the embedded system software to meet the required specification. It is also about testing the software and coordinating with design team for system integration. 3 ELE/N1501 Develop embedded system software Unit Code ELE/N1501 Unit Title Develop embedded system software (Task) Description This OS unit is about developing the software module for embedded system to meet the required specification; testing of software; and coordinating with design team for system integration. Scope This unit/ task covers the following: Understand the work requirement Understand the embedded system design Develop software for embedded system as per specification Report and document completion of work Ensure quality, standards and safety procedures are followed Performance Criteria(PC) w.r.t. the Scope National Standard Occupational Element Performance Criteria Understanding work To be competent, the user/ individual must be able to: requirement PC1. understand the work flow of the company’s software development process PC2. interact with the technical lead engineer in order to understand the work schedules, shifts and delivery dates PC3. understand the roles and responsibilities of persons involved in the work PC4. plan work activities based the work flow and deliverables PC5. understand broad level activities involved in the software development PC6. list the various department to interact with for completing the work PC7. minimise absenteeism and report to work on time Understanding To be competent, the user/ individual must be able to: embedded system PC8. interact with project lead and design lead to understand the project specific design specifications embedded system mandate PC9. understand the software module requirement for the embedded system PC10. establish module requirement and constraints PC11. understand circuit design, functionality, logic involved in the system PC12. understand the Business Requirement Specification (BRS), Software Requirement Specification (SRS) for the project PC13. understand the software system requirement for coding, testing, debugging Developing software To be competent, the user/ individual must be able to: modules PC14. define the design flow for the specific system PC15. use agreed language and application as per standards PC16. define the requirement specification of the embedded system PC17. develop a software design as per requirement specification PC18. get approval from superior and relevant department on the software design developed for the embedded system PC19. access reusable components, code generation tools and unit testing tools from company’s database PC20. develop software modules to meet the requirement specification 4 ELE/N1501 Develop embedded system software PC21. develop unit test cases (UTC) as per specification and requirement PC22. ensure that software module meets the requirement specification PC23. assist in code reviews PC24. rework the code to fix identified defects Coordinating with To be competent, the user/ individual must be able to: design team PC25. interact with the embedded system design engineers to understand the system and software requirement PC26. understand the functionality of the embedded system PC27. coordinate with system design engineers for system integration PC28. assist in system testing, product verification and validation Completing To be competent, the user/ individual must be able to: documentation PC29. create documents using standard templates and agreed language standards PC30. submit documents for approval as per organisational standards PC31. ensure completion of work as per quality, standards, delivery time agreed PC32. publish documents in agreed formats PC33. follow company policies, guidelines and standards during documentation Knowledge and Understanding (K) A. Organizational The individual on the job needs to understand: Context KA1. company’s policies on: incentives, personnel management (Knowledge of the KA2. company’s code of conduct company / KA3. importance of individual’s role in the work flow KA4. organisation culture organization and KA5. company’s reporting structure its processes) KA6. company’s documentation policy KA7. company’s different department and concerned authority KA8. company’s license on usage of software and design tools KA9. company’s license on IP core library B. Technical The individual on the job needs to know and understand: Knowledge KB1. embedded system KB2. system design modules KB3. concepts of circuit design KB4. computer architecture KB5. design and implementation of embedded software system KB6. design flow involved in design stages KB7. design, develop, test, debug software components KB8. software module library KB9. system testing, product verification and validation KB10. software programming languages such as C, C++ KB11. operating system such as windows, linux KB12. system level integration KB13. software fundamentals such object-oriented design, data structures, algorithm design KB14. end-product application, i.e., industry for which embedded system is designed KB15. Schematics and data sheets KB16. Documentation procedure and ERP package usage 5 ELE/N1501 Develop embedded system software KB17. quality, standards policies of the organisation Skills (S) A. Core Skills/ Reading and writing skills Generic Skills The individual on the job needs to know and understand how to: SA1. read job sheets, flow charts and process documents SA2. interpret design drawings SA3. fill in design drawing sheets B. Professional Skills Using software and tools The individual on the job needs to know and understand: SB1. specifications and use of licensed software for design as specified by the organisation SB2. licensed software and application tools used for design, their performance Using software / computer languages The individual on the job needs to know and understand: SB3. programming language such as C, C++ SB4. operating system such as windows, linux Interpersonal skills The individual on the job needs to know and understand: SB5. how to interact with lead and project head to understand the work requirement and to consult for issues SB6. how to interact with co employees in order to co-ordinate work processes Reflective thinking The user/individual on the job needs to know and understand how: SB7. to improve work processes SB8. to reduce repetition of errors 6 ELE/N1501 Develop embedded system software NOS Version Control NOS Code ELE/N1501 Credits(NVEQF/NVQF/NSQF) TBD Version number 1.0 [OPTIONAL] Industry Electronics Drafted on 10/03/14 Semiconductor and Industry Sub-sector Last reviewed on 24/03/14 Active components Next review date 24/03/15 7 ELE/N9909 Coordinate with colleagues and co-workers --------------------------------------------------------------------------------------------------------------------
Recommended publications
  • Application Note: QP/C MISRA-C:2004 Compliance Matrix

    Application Note: QP/C MISRA-C:2004 Compliance Matrix

    QP/C MISRA Compliance Matrix Application Note QP/C™ MISRA-C:2004 Compliance Matrix Document Revision D February 2013 Copyright © Quantum Leaps, LLC [email protected] www.state-machine.com MISRA”, “MISRA C”, and the triangle logo are registered trademarks of MISRA Limited Table of Contents 1 Introduction ..................................................................................................................................................... 1 1.1 About MISRA-C:2004 ............................................................................................................................... 1 1.2 About QP™ ............................................................................................................................................... 1 2 Checking MISRA Compliance with PC-Lint/FlexeLint .................................................................................. 2 2.1 Structure of PC-Lint Options for QP/C ...................................................................................................... 2 2.2 QS Software Tracing and the Spy (Q_SPY) Configuration ....................................................................... 6 2.3 Checking MISRA Compliance of a QP/C Source Code ............................................................................ 6 2.4 Checking MISRA Compliance of a QP/C Application Code ...................................................................... 7 2.5 Testing Rule Coverage Against the MISRA-C Exemplar Suite ................................................................
  • Embedded Operating Systems

    Embedded Operating Systems

    7 Embedded Operating Systems Claudio Scordino1, Errico Guidieri1, Bruno Morelli1, Andrea Marongiu2,3, Giuseppe Tagliavini3 and Paolo Gai1 1Evidence SRL, Italy 2Swiss Federal Institute of Technology in Zurich (ETHZ), Switzerland 3University of Bologna, Italy In this chapter, we will provide a description of existing open-source operating systems (OSs) which have been analyzed with the objective of providing a porting for the reference architecture described in Chapter 2. Among the various possibilities, the ERIKA Enterprise RTOS (Real-Time Operating System) and Linux with preemption patches have been selected. A description of the porting effort on the reference architecture has also been provided. 7.1 Introduction In the past, OSs for high-performance computing (HPC) were based on custom-tailored solutions to fully exploit all performance opportunities of supercomputers. Nowadays, instead, HPC systems are being moved away from in-house OSs to more generic OS solutions like Linux. Such a trend can be observed in the TOP500 list [1] that includes the 500 most powerful supercomputers in the world, in which Linux dominates the competition. In fact, in around 20 years, Linux has been capable of conquering all the TOP500 list from scratch (for the first time in November 2017). Each manufacturer, however, still implements specific changes to the Linux OS to better exploit specific computer hardware features. This is especially true in the case of computing nodes in which lightweight kernels are used to speed up the computation. 173 174 Embedded Operating Systems Figure 7.1 Number of Linux-based supercomputers in the TOP500 list. Linux is a full-featured OS, originally designed to be used in server or desktop environments.
  • AN QP™/QM™ and the Qt™ GUI Framework

    AN QP™/QM™ and the Qt™ GUI Framework

    QP state machine frameworks for Arduino Application Note QP/C++™ and the Qt™ GUI Framework Document Revision K May 2014 Copyright © Quantum Leaps, LLC [email protected] www.state-machine.com Table of Contents 1 Introduction ..................................................................................................................................................... 1 1.1 About Qt .................................................................................................................................................. 1 1.2 About QP/C++™ ...................................................................................................................................... 1 1.3 About QM™ ............................................................................................................................................. 2 1.4 Licensing QP™ ........................................................................................................................................ 3 1.5 Licensing QM™ ....................................................................................................................................... 3 2 Getting Started ................................................................................................................................................ 4 2.1 Installing Qt .............................................................................................................................................. 4 2.2 Installing QP/C++ Baseline Code ...........................................................................................................
  • Getting Started with QP/C

    Getting Started with QP/C

    Application Note: Getting Started with QP Getting Started with QP™ Real-Time Embedded Frameworks Document Revision G October 2019 Copyright © Quantum Leaps, LLC www.state-machine.com [email protected] Table of Contents 1 Introduction.................................................................................................................................................... 1 2 Downloading and Installing QP and QTools................................................................................................2 2.1 Downloading QP and QTools...................................................................................................................2 2.2 Installing QP............................................................................................................................................. 3 2.3 Downloading QTools................................................................................................................................ 4 2.4 Installing QTools...................................................................................................................................... 5 3 Building and Running the Blinky Example..................................................................................................6 3.1 Blinky on Windows with MinGW (GNU C/C++ for Windows)...................................................................7 3.2 Blinky on Tiva LauchPad with GNU-ARM (command-line)......................................................................8 3.3 Blinky on Tiva LauchPad
  • AN QP and ARM7/9 With

    AN QP and ARM7/9 With

    QP state machine frameworks for ARM7/ARM9 with GNU Application Note QP™ and ARM7/9 with GNU Document Revision I March 2014 Copyright © Quantum Leaps, LLC www.quantum-leaps.com www.state-machine.com Table of Contents 1 Introduction ..................................................................................................................................................... 2 1.1 About the ARM Port ................................................................................................................................... 3 1.2 What’s Included in the Accompanying Code .............................................................................................. 4 1.3 About QP™ ................................................................................................................................................ 4 1.4 About QM™ ............................................................................................................................................... 5 1.5 Licensing QP .............................................................................................................................................. 6 1.6 Licensing QM™ .......................................................................................................................................... 6 2 Directories and Files ....................................................................................................................................... 7 2.1 Building the QP Libraries ...........................................................................................................................
  • Application Note: QP and Threadx®

    Application Note: QP and Threadx®

    QP state machine frameworks for ThreadX Application Note QP and ThreadX Document Revision D May 2014 Copyright © Quantum Leaps, LLC www.quantum-leaps.com www.state-machine.com Table of Contents 1 Introduction..................................................................................................................................................... 1 1.1 About QP™................................................................................................................................................ 1 1.2 About QM™............................................................................................................................................... 2 1.3 About the QP-ThreadX Integration.............................................................................................................3 1.4 Licensing QP.............................................................................................................................................. 4 1.5 Licensing QM™.......................................................................................................................................... 4 2 Directories and Files....................................................................................................................................... 5 2.1 Installation.................................................................................................................................................. 5 3 Executing the Examples................................................................................................................................
  • Real Time Operating Systems

    Real Time Operating Systems

    School of Electrical and Computer Engineering N.T.U.A. Embedded System Design Real Time Alex Bartzas Operating Systems Microlab/NTUA Άδεια Χρήσης Το παρόν εκπαιδευτικό υλικό υπόκειται σε άδειες χρήσης Creative Commons. Για εκπαιδευτικό υλικό, όπως εικόνες, που υπόκειται σε άδεια χρήσης άλλου τύπου, αυτή πρέπει να αναφέρεται ρητώς. What is an Embedded OS? An "embedded system" is any computer system or computing device that performs a dedicated function or is designed for use with a specific embedded software applica tion. Embedded systems may use a ROM-based operating system or they may use a disk-based system, like a PC. But an embdddbedded sys tem is no t usa ble as a commercillially v ibliable substitute for general purpose computers or devices. 3 Aspects of embedded system design 4 Metrics •Performance can be measured in multiple ways –Latency vs. throughput –Average vs. worst-case vs. best-case –Peak vs. sustained •Power/energy –Power consumption is important for heat generation –Energy consumption is important for battery life –ItIntegra tdted me titrics suc h as Energy-De lay Pro duc t (EDP) •Cost –Des ign time vs. life time •Reliability –Avail a bility, depen da bility, performabilit y 5 Hardware/software codesign •Goals –Optimizing design process –Oppggtimizing design •Tasks –Cospecificationand comodeling –Codesign –Cosynthesis, optimization, interfacing –Verification 6 Codesign flow 7 What makes a good Embedded OS? Modular Scalable Configurable Small footprint CPU support Device drivers etc,,, etc, etc... 8 What is Real Time? “A real time system is one in which the correctness of the computations not only depends upon the logical correctness of the computation but also upon the time at which the result iddIfthtiititfthtis produced.
  • Application Note: QP and SEGGER Embos

    Application Note: QP and SEGGER Embos

    QP state machine frameworks for embOS Application Note QP™ and SEGGER embOS Document Revision A June 2014 Copyright © Quantum Leaps, LLC www.quantum-leaps.com www.state-machine.com Table of Contents 1 Introduction..................................................................................................................................................... 1 1.1 About QP™................................................................................................................................................ 2 1.2 About QM™............................................................................................................................................... 3 1.3 About the QP-embOS Integration...............................................................................................................4 1.4 Licensing QP.............................................................................................................................................. 4 1.5 Licensing QM™.......................................................................................................................................... 4 2 Directories and Files....................................................................................................................................... 5 2.1 Installation.................................................................................................................................................. 5 3 Building the DPP Example............................................................................................................................
  • Comparing Windows NT, Linux, and QNX As the Basis for Cluster Systems

    Comparing Windows NT, Linux, and QNX As the Basis for Cluster Systems

    Comparing Windows NT, Linux, and QNX as the Basis for Cluster Systems Avi Kavas Dror G. Feitelson School of Computer Science and Engineering The Hebrew University, 91904 Jerusalem, Israel Abstract Clusters use commodity hardware and software components to provide an environment for parallel processing. A major issue in the development of a cluster system is the choice of the operating system that will run on each node. We compare three alternatives: Windows NT, Linux, and QNX — a real-time microkernel. The comparison is based on expressive power, performance, and ease-of-use metrics. The result is that none of these systems has a clear advantage over the others in all the metrics, but that each has its strong and weak points. Thus any choice of a base system will involve some technical compromises, but not major ones. 1 Introduction Rapid improvements in network and processor performance are causing clustered commodity workstations and PCs to become an increasingly popular platform for executing parallel applica- tions. In the past, Unix was used as the platform for almost all parallel systems implementations. Recently, however, it is becoming more common to use Windows NT as the base platform. The decision which operating system to use involves many considerations, including the oper- ating system’s cost and personal experience with the different systems. But there are also technical implications. Our goal is to illuminate these technical issues, by providing a broad comparison of the capabilities and characteristics of the different systems. Throughput, the emphasis is on those features deemed to be important for the implementation of computational clusters.
  • QP and ARM Cortex-M with IAR

    QP and ARM Cortex-M with IAR

    QP state machine frameworks for ARM Cortex-M Application Note QP™ and ARM Cortex-M with IAR Document Revision L February 2013 Copyright © Quantum Leaps, LLC www.quantum-leaps.com www.state-machine.com Table of Contents 1 Introduction ..................................................................................................................................................... 1 1.1 About the QP Port to ARM Cortex-M ........................................................................................................ 2 1.2 The Use of the FPU (Cortex-M4F) ............................................................................................................ 2 1.3 Cortex Microcontroller Software Interface Standard (CMSIS) ................................................................... 2 1.4 About QP™ ............................................................................................................................................... 3 1.5 About QM™ .............................................................................................................................................. 4 1.6 Licensing QP ............................................................................................................................................. 5 1.7 Licensing QM™ ........................................................................................................................................ 5 2 Directories and Files ......................................................................................................................................
  • QP and POSIX

    QP and POSIX

    QP state machine frameworks for POSIX Application Note QP™ and POSIX Document Revision E November 2012 Copyright © Quantum Leaps, LLC www.quantum-leaps.com www.state-machine.com Table of Contents 1 Introduction ..................................................................................................................................................... 1 1.1 About QP™ .................................................................................................................................................... 1 1.2 About QM™ ................................................................................................................................................... 2 1.3 About the QP™ Port to POSIX ....................................................................................................................... 3 1.4 Licensing QP™ and QP port to POSIX .......................................................................................................... 4 1.5 Licensing QM™ .............................................................................................................................................. 4 2 Directories and Files ....................................................................................................................................... 5 2.1 Building the QP Libraries ............................................................................................................................... 6 2.2 Building the QP Applications .........................................................................................................................
  • Third Party License Terms List

    Third Party License Terms List

    QNX® THIRD PARTY LICENSE TERMS LIST Version 2.14a Includes: Supplement for Screen Graphics Subsystem for QNX Software Development Platform 6.5 Service Pack 1 (“Screen”) (See Publication History for version details) Table of Contents 1. Introduction 2. Tables 2.1 Condensed Version of File Mapping Tables (Summarized by License Family) 2.2 Complete Version of File Mapping Tables (Includes Full Legal ID Codes) 3. Licenses 3.1 License Types and Codes 3.2 License Texts © 2015 QNX Software Systems Limited, a subsidiary of BlackBerry Limited. All rights reserved. QNX, QNX CAR, Momentics, Neutrino and Aviage are trademarks of BlackBerry Limited, which are registered and/or used in certain jurisdictions, and are used under license by QNX Software Systems Limited. All other trademarks belong to their respective owners. 1. Introduction This version 2.14a of the QNX Third Party License Terms List (“TPLTL”) is the companion document to version 2.14a of the QNX License Guide (“License Guide”) (see http://licensing.qnx.com/document-archive/). As explained in the License Guide, QNX Software Systems Limited (“QSS”) incorporates certain third-party software in our products. The license terms associated with some of the third-party software requires that we provide the recipient with additional information such as attributions, copies of licenses, or source code (“Compliance”). This document encapsulates Compliance for Screen. This TPLTL is divided into two sections as follows: 1. The summary tables in section 2.1 provide an overview of types of licenses (“Legal ID Codes”) for third-party software that QSS has reused and that have Compliance requirements.