QUALIFICATIONS PACK - OCCUPATIONAL STANDARDS FOR ELECTRONICS INDUSTRY

Contents
1. Introduction and Contacts.…….P1
2. Qualifications Pack……….….......P2
3. OS Units……………..………….....….P3
4. Glossary of Key Terms.……….…P12
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.

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
info@essc-india.org
 Qualifications Pack For Embedded Software Engineer

Qualifications Pack Code ELE/Q1501

Job Role Embedded Software Engineer

Job Details

Credits(NVEQF/NVQF/NSQF)
TBD Version number 1.0
[OPTIONAL]
Sector Electronics Drafted on 10/03/14
Semiconductor and
Sub-sector Last reviewed on 24/03/15
Active components
System software
Occupation Next review date 24/03/16
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
National Occupational Standard

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

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
KA3. importance of individual’s role in the work flow
company /
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/15
Active components

Next review date 24/03/16

7
ELE/N9909 Coordinate with colleagues and co-workers
--------------------------------------------------------------------------------------------------------------------

Overview
This unit is about the individual’s level of communication with colleagues and other
departments within the organisation. It determines the ability to work as a team member to
achieve the required deliverables on schedule.

8
 ELE/N9909 Coordinate with colleagues and co-workers
Unit Code ELE/N9909
Unit Title
National Occupational Standard

Coordinate with colleagues

(Task)
Description This OS unit is about communicating with colleagues and seniors in order to achieve
smooth work flow
Scope This unit/ task covers the following:

 Interact with supervisor or superior

 Coordinate with colleagues

Performance Criteria(PC) w.r.t. the Scope

Element Performance Criteria
Interacting with To be competent, the user/ individual must be able to:
supervisor PC1. understand and assess work requirements
PC2. understand the targets and incentives
PC3. understand new operating procedures and constraints
PC4. report problems in the field
PC5. resolve personnel issues
PC6. receive feedback on work standards and customer satisfaction
PC7. communicate any potential hazards at a particular location
PC8. meet given targets
PC9. deliver work of expected quality despite constraints
PC10. receive positive feedback on behaviour and attitude shown during
interaction

Coordinating with To be competent, the user/ individual must be able to:

colleagues PC11. interact with colleagues from different functions and understand the nature
of their work
PC12. receive spares from tool room or stores; deposit faulty modules and tools to
stores
PC13. pass on customer complaints to colleagues in a respective geographical area
PC14. assist colleagues with resolving field problems resolve conflicts and achieve
smooth workflow
PC15. follow the company policy during cross functional interaction
Knowledge and Understanding (K)
A. Organizational The individual on the job needs to know and understand:
Context KA1. company’s policies on: incentives, delivery standards, and personnel
(Knowledge of the management
company / KA2. importance of the individual’s role in the workflow
KA3. reporting structure
organization and
its processes)

9
ELE/N9909 Coordinate with colleagues and co-workers
B. Technical The individual on the job needs to know and understand:
Knowledge KB1. how to communicate effectively
KB2. how to build team coordination

Skills (S) [Optional]

A. Core Skills/ Teamwork and multitasking
Generic Skills The individual on the job needs to know and understand how:
SA1. to deliver product to next work process on time
B. Professional Skills Decision making
The individual on the job needs to know and understand:
SB1. how to report potential areas of disruptions to work process
SB2. when to report to supervisor and when to deal with a colleague depending
on the type of concern
Reflective thinking
The individual on the job needs to know and understand:
SB3. how to improve work process
Critical thinking
The individual on the job needs to know and understand:
SB4. how to spot process disruptions and delays

10
ELE/N9909 Coordinate with colleagues and co-workers

NOS Version Control

NOS Code ELE/N9909

Credits(NVEQF/NVQF/NSQF)
TBD Version number 1.0
[OPTIONAL]
Industry Electronics Drafted on 10/03/14
Industry Sub-sector IT Hardware Last reviewed on 24/03/15

Next review date 24/03/16

11
 Qualifications Pack For Embedded Software Engineer

Keywords /Terms Description

Definitions

Sector Sector is a conglomeration of different business operations having similar

business and interests. It may also be defined as a distinct subset of the
economy whose components share similar characteristics and interests.
Sub-sector Sub-sector is derived from a further breakdown based on the
characteristics and interests of its components.
Occupation Occupation is a set of job roles, which perform similar/ related set of
functions in an industry.
Function Function is an activity necessary for achieving the key purpose of the
sector, occupation, or an area of work, which can be carried out by a
person or a group of persons. Functions are identified through functional
analysis and form the basis of OS.
Sub-function Sub-functions are sub-activities essential to fulfil the achieving the
objectives of the function.
Job role Job role defines a unique set of functions that together form a unique
employment opportunity in an organisation.
Occupational Standards OS specify the standards of performance an individual must achieve
(OS) when carrying out a function in the workplace, together with the
knowledge and understanding they need to meet that standard
consistently. Occupational Standards are applicable both in the Indian
and global contexts.
Performance Criteria Performance criteria are statements that together specify the standard of
performance required when carrying out a task.
National Occupational NOS are occupational standards which apply uniquely in the Indian
Standards (OS) context.
Qualifications Pack (QP) QP comprises the set of OS, together with the educational, training and
other criteria required to perform a job role. A QP is assigned a unique
qualifications pack code.
Unit Code Unit code is a unique identifier for an Occupational Standard, which is
denoted by an ‘N’
Unit Title Unit title gives a clear overall statement about what the incumbent
should be able to do.
Description Description gives a short summary of the unit content. This would be
helpful to anyone searching on a database to verify that this is the
appropriate OS they are looking for.
Scope Scope is a set of statements specifying the range of variables that an
individual may have to deal with in carrying out the function which have
a critical impact on quality of performance required.
Knowledge and Knowledge and understanding are statements which together specify the
Understanding technical, generic, professional and organisational specific knowledge
that an individual needs in order to perform to the required standard.
Organisational Context Organisational context includes the way the organisation is structured
and how it operates, including the extent of operative knowledge
managers have of their relevant areas of responsibility.
Technical Knowledge Technical knowledge is the specific knowledge needed to accomplish 12
specific designated responsibilities.
 Qualifications Pack For Embedded Software Engineer
Core Skills/ Generic Core skills or generic skills are a group of skills that are the key to learning
Skills and working in today’s world. These skills are typically needed in any
work environment in today’s world. These skills are typically needed in
any work environment. In the context of the OS, these include
communication related skills that are applicable to most job roles.
Keywords /Terms Description
NOS National Occupational Standard(s)
Acronyms

NVQF National Vocational Qualifications Framework

NSQF National Qualifications Framework
NVEQF National Vocational Education Qualifications Framework
QP Qualifications Pack

13
 Qualifications Pack For Embedded Software Engineer

Annexure

Nomenclature for QP and NOS

Qualifications Pack
9 characters
[ABC]/ Q 0101

[Insert 3 letter codes for SSC] QP number (2 numbers)

Q denoting Qualifications Pack Occupation (2 numbers)

Occupational Standard

An example of NOS with ‘N’ 9 characters

[ABC] /N0101

[Insert 3 letter code for SSC] OS number (2 numbers)

N denoting National Occupational Standard Occupation (2 numbers)

Back to top…
14
 Qualifications Pack For Embedded Software Engineer

The following acronyms/codes have been used in the nomenclature above:

Range of Occupation
Sub-sector
numbers

Passive Components 01 - 10
Semiconductors 11 - 20
PCB Manufacturing 21 - 30
Consumer Electronics 31 - 40
IT Hardware 41 - 50
PCB Assembly 51 - 55
Solar Electronics 56 - 60
Strategic Electronics 61 - 65
Automotive Electronics 66 - 70
Industrial Electronics 71 - 75
Medical Electronics 76 - 80
Communication Electronics 81 - 85
PCB Design 86 - 90
LED 91 - 95

Sequence Description Example

Three letters Industry name ELE

Slash / /

Next letter Whether QP or NOS Q

Next two numbers Occupation code 01

Next two numbers OS number 01

15
 Qualifications Pack For Embedded Software Engineer

CRITERIA FOR ASSESSMENT OF TRAINEES

Job Role Embedded Software Engineer
QP # ELE/Q1501
Sector Skill
Council
Electronics Sector Skills Council of India

Guidelines for Assessment:

1. Criteria for assessment for each Qualification Pack will be created by the Sector Skill Council. Each Performance Criteria (PC) will be
assigned marks proportional to its importance in NOS. SSC will also lay down proportion of marks for Theory and Skills Practical for each PC.
2. The assessment for the theory part will be based on knowledge bank of questions created by the SSC.
3. Individual assessment agencies will create unique question papers for theory part for each candidate at each examination/training center
(as per assessment criteria below)
4. Individual assessment agencies will create unique evaulations for skill practical for every student at each examination/training center
based on this criteria
5. To pass the Qualification Pack , every trainee should score a minimum of 70% in every NOS
6. In case of successfully passing only certain number of NOS's, the trainee is eligible to take subsequent assessment on the balance NOS's
to pass the Qualification Pack.

Marks Allocation
Total Skills
Element Performance Criteria Marks Out Of Theory Practica
(400) l
ELE/N1501 Develop embedded system software
Understanding PC1. understand the work flow of the company’s software development process 2 1 1
work PC2. interact with the technical lead engineer in order to understand the work schedules,
100 3 1 2
requirement shifts and delivery dates
visit PC3. understand the roles and responsibilities of persons involved in the work 3 1 2

16
 Qualifications Pack For Embedded Software Engineer
Marks Allocation
Total Skills
Element Performance Criteria Marks Out Of Theory Practica
(400) l
PC4. plan work activities based the work flow and deliverables 3 1 2
PC5. understand broad level activities involved in the software development 3 1 2
PC6. list the various department to interact with for completing the work 3 1 2
PC7. minimise absenteeism and report to work on time 3 1 2
PC8. interact with project lead and design lead to understand the project specific 3 1 2
embedded system mandate
Understanding PC9. understand the software module requirement for the embedded system 3 2 1
embedded
PC10. establish module requirement and constraints 3 1 2
system design
specifications PC11. understand circuit design, functionality, logic involved in the system 4 2 2
PC12. understand the Business Requirement Specification (BRS), Software Requirement 4 2 2
Specification (SRS) for the project
PC13. understand the software system requirement for coding, testing, debugging 3 1 2
PC14. define the design flow for the specific system 4 2 2
PC15. use agreed language and application as per standards 4 2 2
PC16. define the requirement specification of the embedded system 4 2 2
PC17. develop a software design as per requirement specification 4 2 2
PC18. get approval from superior and relevant department on the software design 3 1 2
Developing developed for the embedded system
software PC19. access reusable components, code generation tools and unit testing tools from 3 1 2
modules company’s database
PC20. develop software modules to meet the requirement specification 4 1 3
PC21. develop unit test cases (UTC) as per specification and requirement 4 1 3
PC22. ensure that software module meets the requirement specification 4 1 3
PC23. assist in code reviews 3 1 2
PC24. rework the code to fix identified defects 3 1 2

17
 Qualifications Pack For Embedded Software Engineer
Marks Allocation
Total Skills
Element Performance Criteria Marks Out Of Theory Practica
(400) l
PC25. interact with the embedded system design engineers to understand the system and 3 1 2
software requirement
Coordinating
PC26. understand the functionality of the embedded system 3 1 2
with design team
PC27. coordinate with system design engineers for system integration 2 1 1
PC28. assist in system testing, product verification and validation 2 1 1
PC29. create documents using standard templates and agreed language standards 2 1 1
PC30. submit documents for approval as per organisational standards 2 1 1
Completing
PC31. ensure completion of work as per quality, standards, delivery time agreed 2 1 1
documentation
PC32. publish documents in agreed formats 2 1 1
PC33. follow company policies, guidelines and standards during documentation 2 1 1
TOTAL 100 40 60
ELE/N9909 Coordinate with colleague and co-workers
PC1. understand and assess work requirements 5 2 3
PC2. understand the targets and incentives 5 2 3
PC3. understand new operating procedures and constraints 5 2 3
PC4. report problems in the field 5 2 3
Interacting with PC5. resolve personnel issues 5 2 3
100
supervisor PC6. receive feedback on work standards and customer satisfaction 5 2 3
PC7. communicate any potential hazards at a particular location 5 2 3
PC8. meet given targets 5 2 3
PC9. deliver work of expected quality despite constraints 5 2 3
PC10. receive positive feedback on behaviour and attitude shown during interaction 5 2 3

18
 Qualifications Pack For Embedded Software Engineer
Marks Allocation
Total Skills
Element Performance Criteria Marks Out Of Theory Practica
(400) l
PC11. interact with colleagues from different functions and understand the nature of their
10 4 6
work
PC12. receive spares from tool room or stores; deposit faulty modules and tools to stores 10 4 6
Coordinating 10 4 6
PC13. pass on customer complaints to colleagues in a respective geographical area
with colleagues
PC14. assist colleagues with resolving field problems resolve conflicts and achieve smooth 10 4 6
workflow
PC15. follow the company policy during cross functional interaction 10 4 6
TOTAL 100 40 60

19