Transnational Skill Standards Software Developer

Transcription

1 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY Transnational Skill Standards Software Developer REFERENCE ID: TOS/SSC/Q0501

2 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY Mapping for Software Developer (SSC/Q0501) with UK ESKITP5023 Link to Indian Qualification Pack: Link to UK Qualification: How to Read this Document This document has two sections - Section I and Section II. Section I: Compares the listing in the Indian QP -Software Developer (SSC/Q0501) with Software Development ESKITP5023. Section II: Compares the competencies described in each of the Indian with those of UK. The language of the compared competencies of the two countries differs. However, the competency pointers of the described competency can be mapped. Wherever the competency pointer maps it is reported as underthe column Gap in Indian. Wherever the competency pointers do not map, it is identified as a gap and the corresponding UK competency is noted under the column Gap in Indian. Usage of Benchmarked Transnational Standards There will be two types of users of these benchmarked standards. One type will be of those individuals who are already trained and are certified on the corresponding Indian QP. This set of individuals will have to undergo a bridge course comprising of the identified gaps only. Thereafter, they will be assessed under the aegis of a UK Awarding body through the Indian SSC on the competency portions acquired via the bridge course. All qualifying individuals will be awarded a co-branded certificate comprising of logo of Skill India, Indian SSC and UK Awarding Body. Those individuals who wish to be certified afresh will have to undergo training on both the Indian QP and the gaps in the Indian with regard to UK competencies. Thereafter, they will be assessed under the aegis of a UK Awarding body through the Indian SSC and they will obtain a co-branded certificate comprising of logo of Skill India, Indian SSC and UK Awarding Body. 1

3 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY Section I: Mapping of Software Developer (SSC/Q0501) with ESKITP5023 Software Development Level 3 Indian Code SSC/N0501 SSC/N0502 SSC/ N9001 SSC/ N9002 SSC/ N9003 SSC/ N9004 SSC/ N9005 Mapping: A Summary Indian UK Code UK Remarks, if any Contribute to the design of software products and applications Develop Software code to Specification Manage your work to meet requirements Work effectively with colleagues Maintain a healthy, safe and secure working environment Provide data/information in standard formats Develop your knowledge, skills and competence ESKITP5023 Software Development Two of Indian s are covered in one UK. 2

4 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY Section II:Compares the competencies in Indian with those of UK. Mapping Descriptions Indian QP Title Software Developer UK Qualification Not Specified Indian QP Code SSC/Q0501 UK Qualification Code Not Specified Indian Title Contribute to the design of software products and applications UK Title Software Development Indian Code SSC/N0501 UK Code ESKITP5023 Scope This unit/task covers the following: Appropriate people: line manager peers subject matter experts Software Requirements Specification includes: functional requirements non-functional requirements High Level Design includes: Overview This is the entry level Software Developer role, suitable for those in the role for 0-2 years This sub discipline covers the core competencies required to create software to address the needs of business problems and opportunities, resulting in a variety of software solutions, ranging from operating and control software to web based or specialist applications, such as accounting software and games software. technical solution selected and its rationale assumptions Development produce software that translates the design deliverables from HCI design, data design and software design, 3

5 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY Scope constraints dependencies interfaces Requirements where: business impact is low technical complexity is low Overview into working software. These designs will include, at a detailed level, functions and processing, interfaces, data handling and storage needs and how the system will be used by and interact with people, as appropriate. Development involves the translation of the designs into working software solutions that meet the business needs. There is a wide range of software that may be undertaken in a variety of environments appropriate to both the business and technical contexts in which they will be used, the software development environments used will be selected and specified during the design phase when the physical models are produced. In some organisations, may be undertaken as part of a holistic life cycle approach where one individual or team may complete all stages; whereas in other organisations, 4

6 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY Scope Overview each stage of development may be undertaken by individuals or teams or as part of projects and/or programmes. Competency Mapping Gaps in Indian PC1. check your understanding of the Business Requirements Specification (BRS)/User Requirements Specification (URS) with appropriate people PC2. check your understanding of the Software Requirements Specification (SRS) with appropriate people PC3. check your understanding of High Level Design (HLD) with appropriate people PC4. design basic programming structures to implement functionality in line with requirements defined in BRS/URS, SRS and HLD PC5. review your designs with appropriate people PC6. analyze inputs from appropriate people to identify, resolve and record design defects and inform future P2. Assist with the collation and use of information relating to IT architecture models together with business, data and HCI design deliverables in order to inform software development and testing P10. Use appropriate programming constructs to produce effective software 8. Functionally test that the processing and functional needs specified within logical and physical software design deliverables have been met 5

7 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY designs Gaps in Indian PC7. document your designs using standard templates and tools PC8. comply with any relevant organization s policies, procedures and guidelines when contributing to the design of software products and applications Knowledge & Understanding; Organisational Context KA29. organization s policies, procedures and guidelines for designing software products and applications and your role and responsibilities in relation to this P3. Assist in specifying precisely how the software that has been developed functions P4. Assist with the documentation of software P1. Follow organisational standards for the systems development lifecycle P6. Comply with any relevant legislation, regulation and external standards relating to software P9. Use naming conventions and standards in line with organisational standards Knowledge & Understanding K3. The fact that many developers may work together to develop differing elements of a total software solution and these individual software elements need to work coherently together K33. Operate with reference to: K33.1 organisational standards for K33.2 professional and ethical standards in software K33.3 integrity and confidentiality during software 6

8 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY K33.4 design requirements and operating environments Gaps in Indian KA30. your organization s knowledge base and how to access and update this KA31. the scope of work to be carried out and the importance of keeping within these boundaries KA32. who you may need to involve to provide feedback to your designs KA33. the importance of collating feedback on your designs K6. The importance of accurately translating design deliverables in software development work K24. The inputs to and required outputs from any piece of K30. The fact that software development deliverables must meet design requirements K4. The importance of verifying the accuracy, currency, completeness and relevance of information used during K3. The fact that many developers may work together to develop differing elements of a total software solution and these individual software elements need to work coherently together K3. The fact that many developers may work together to develop differing elements of a total software solution and these individual software elements need to work coherently together K4. The importance of verifying the accuracy, currency, completeness and relevance of information used during 7

9 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY Gaps in Indian KA34. how to analyze and use feedback to improve your designs KA35. who you may need to involve to provide feedback on your designs KA36. standard templates and tools available and how to use these to document your designs KA37. the approval process for designs of software products and applications K3. The fact that many developers may work together to develop differing elements of a total software solution and these individual softwareelements need to work coherently together K16. Document software development and testing accurately and clearly to allow further development, amendments and updates to be made to solutions Technical Knowledge KB9. how to interpret and follow different design specifications, including: Business Requirements Specification (BRS) User Requirements Specification (URS) Software Requirements Specification (SRS) High Level Design (HLD) Technical Knowledge K5. The relationship between physical software design, data and HCI design and software development K12. The importance of documenting software development and testing in a clear and understandable manner that will allow further development, amendments and updates to be made to solutions K14. Collate information from data and HCI design deliverables in order to inform and testing 8

10 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY Gaps in Indian KB10. how to design basic program structures KB11. how to design software products KB12. how to design software applications KB13. different sources of information for help to design software products and K31. Interpret physical and logical designs to Identify and select: K31.1 the processing and functional needs specified within logical and physical software design deliverables K31.2 the functional requirements for individual software components K31.3 what inputs need to be incorporated into software and what required outputs need to be produced from it K7. The importance of and value of being informed and directed by the deliverables from software design K17. The fact that software solutions must combine data and the commands to manipulate it in the most effective manner to meet the business informed and directed by the deliverables from software design K5. The relationship between physical software design, data and HCI design and K5. The relationship between physical software design, data and HCI design and K24. The inputs to and required outputs from any piece of 9

11 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY specifications Gaps in Indian KB14. the range of equipment used to design software products and applications KB15. common design defects and how to resolve these KB16. current practice in the infrastructure design of software products and applications KB17. the range of involved in designing different software products and applications KB18. how to test new products and applications are fit for purpose KB19. implications new products and applications may have on business processes and business infrastructure K1. The importance of the systems development lifecycle as it relates to software K2. What is meant by software development and the stages of activity that constitute it K15. Verify functional requirements for individual software components K31.4 information required to perform functional testing K31.5 functional and unit testing which will be required as an integral part of development work K10. The fact that new software may need to be developed or existing software enhanced or adapted to take account of changing business needs *General Note: s SSC/N9001 to SSC/N9005 and SSC/N0703 are related to employability skills. In UK, such generic competencies are covered through apprenticeship. 10

12 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY Section II continued:compares the competencies in Indian Develop Software code to Specification (SSC/N0502) with the UK Software Development (ESKITP5023). Mapping Descriptions Indian QP Title Software Developer UK Qualification Not Specified Indian QP Code SSC/Q0502 UK Qualification Code Not Specified Indian Title Develop Software Code to Specification UK Unit Title Software Development Indian Code SSC/N0502 UK Code ESKITP5023 Scope This unit/task covers the following: Appropriate people: Overview This is the entry level Software Developer role, suitable for those in the role for 0-2 years line manager peers subject matter experts Software Requirements Specification includes: functional requirements non-functional requirements High Level Design includes: technical solution selected and its rationale assumptions constraints dependencies interfaces This sub discipline covers the core competencies required to create software to address the needs of business problems and opportunities, resulting in a variety of software solutions, ranging from operating and control software to web based or specialist applications, such as accounting software and games software. Development produce software that translates the design deliverables from HCI design, data design and software design, into working software. These designs will include, at a detailed level, functions and processing, interfaces, 11

13 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY Scope Low Level Design includes: programming structures Overview data handling and storage needs and how the system will be used by and interact with people, as appropriate. coding standards checklists Requirements where: business impact is low technical complexity is low Development involves the translation of the designs into working software solutions that meet the business needs. There is a wide range of software that may be undertaken in a variety of environments appropriate to both the business and technical contexts in which they will be used, the software development environments used will be selected and specified during the design phase when the physical models are produced. In some organisations, may be undertaken as part of a holistic life cycle approach where one individual or team may complete all stages; whereas in other organisations, each stage of development may be undertaken by individuals or teams or as part of projects and/or programmes. 12

14 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY Competency Mapping: Gaps in Indian PC1. check your understanding of the Business Requirements Specification (BRS), Software Requirements Specification (SRS), High Level Design (HLD) and Low Level Design (LLD) with appropriate people PC2. access reusable components, code generation tools and unit testing tools from your organization s knowledge base PC3. convert technical specifications into code to meet the requirements, leveraging reusable components, where available PC4. create appropriate unit test cases (UTCs) PC5. review codes and UTCs with appropriate people PC6. execute UTCs and document results PC7. rework the code and UTCs to fix identified defects PC8. analyze inputs from appropriate people to inform P2. Assist with the collation and use of information relating to IT architecture models together with business, data and HCI design deliverables in order to inform and testing P7. Create software that incorporates the full range of design specifications, for example those relating to data and HCI, in order to produce effective software P5. Correctly use software development procedures, tools and techniques, as directed by superiors P10. Use appropriate programming constructs to produce effective software P11. Optimize the use of system resources in software P8. Functionally test that the processing and functional needs specified within logical and physical software design deliverables have been met 13

15 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY future designs PC9. record corrective actions for identified defects to inform future designs P4. Assist with the documentation of software Gaps in Indian PC10. submit tested code for approval by appropriate people PC11. update your organization s knowledge base with your experiences of the code developed PC12. comply with organization s standards, policies, procedures and guidelines when developing software code to specification Knowledge & Understanding: Organisational Context KA24. Organization s policies, procedures and guidelines for designing software products and applications and your role and responsibilities in relation to this P1. Follow organisational standards for the systems development lifecycle P1. Follow organisational standards for the systems development lifecycle P3. Assist in specifying precisely how the software that has been developed functions P1. Follow organisational standards for the systems development lifecycle P6. Comply with any relevant legislation, regulation and external standards relating to P9. Use naming conventions and standards in line with organisational standards Knowledge & Understanding K3. The fact that many developers may work together to develop differing elements of a total software solution and these individual software elements need to work coherently together K33. Operate with reference to: K33.1 organisational standards for K33.2 professional and ethical standards in software 14

16 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY Gaps in Indian KA25. the scope of work to be carried out and the importance of keeping within these boundaries KA26. your organization s knowledge base and how to K33.3 integrity and confidentiality during software K33.4 design requirements and operating environments K24. The inputs to and required outputs from any piece of K30. The fact that software development deliverables must meet design requirements K6. The importance of accurately translating design deliverables in software development work K24. The inputs to and required outputs from any piece of K30. The fact that software development deliverables must meet design requirements K31 Interpret physical and logical designs to Identify and select: K31.1 the processing and functional needs specified within logical and physical software design deliverables K31.2 the functional requirements for individual software components K31.3 what inputs need to be incorporated into software and what required outputs need to be produced from it K31.4 information required to perform functional testing K31.5 functional and unit testing which will be required as an integral part of development work K4. The importance of verifying the accuracy, currency, 15

17 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY Gaps in Indian access and update this KA27. the importance of collating feedback on your coding and UTCs KA28. how to analyze and use feedback to improve your coding and UTCs KA29. who you may need to involve to provide feedback on your coding and UTCs KA30. your organization s approval process for software code designs Technical Knowledge completeness and relevance of information used during K14. Collate information from data and HCI design deliverables in order to inform and testing K12. The importance of documenting software development and testing in a clear and understandable manner that will allow further development, amendments and updates to be made to solutions K32.5 the procedures, tools and techniques to undertake functional testing K2. What is meant by software development and the stages of activity that constitute it K13. Use and apply the systems development lifecycle as appropriate to software KB13. how to interpret and follow different design specifications K5. The relationship between physical software design, data and HCI design and software development K7. The importance of and value of being informed and directed by the deliverables from software design K17. The fact that software solutions must combine data and the commands to 16

18 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY manipulate it in the most effective manner to meet the business requirements K28. The importance of ensuring that any software development uses all relevant inputs to it K29. and provides all necessary outputs from it K31. Interpret physical and logical designs to Identify and select: K31.1 the processing and functional needs specified within logical and physical software design deliverables K31.2 the functional requirements for individual software components K31.3 what inputs need to be incorporated into software and what required outputs need to be produced from it K31.4 information required to perform functional testing K31.5 functional and unit testing which will be required as an integral part of development work K32. Use and apply: K32.1 specified software development procedures, tools and techniques K32.2 naming conventions and standards in line with organisational standards K32.3 appropriate programming constructs to produce effective software K32.4 information relating to data and HCI design deliverables in order to inform Gaps in Indian 17

19 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY Gaps in Indian KB14. the process for converting technical specifications into code KB15. current practice in the infrastructure design of software code KB16. how to write software code that is efficient, readable and maintainable K32.5 the procedures, tools and techniques to undertake functional testing K1. The importance of the systems development lifecycle as it relates to software K21. What is involved in translating physical designs into working software K22. Data types that can be used and how they can be represented and manipulated K25. The and tasks involved in software development K26. Why naming conventions and standards are used during work K32. Use and apply: K32.1 specified software development procedures, tools and techniques K32.2 naming conventions and standards in line with organisational standards K32.3 appropriate programming constructs to produce effective software K32.4 information relating to data and HCI design deliverables in order to inform K32.5 the procedures, tools and techniques to undertake functional testing K18. What is meant by the syntax (grammar) of a programming language K19. The relationship between programming languages and 18

20 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY development environments Gaps in Indian KB17. the range of code generation tools and unit testing tools used to develop software code KB18. how to use coding tools K20. The relationship between programming languages and file/database structures K23. Programming constructs available and the uses they can be put to K24. The inputs to and required outputs from any piece of K27. The importance of optimising the use of system resources in software development work K19 The relationship between programming languages and development environments K32 Use and apply: K32.1 specified software development procedures, tools and techniques K32.2 naming conventions and standards in line with organisational standards K32.3 appropriate programming constructs to produce effective software K32.4 information relating to data and HCI design deliverables in order to inform K32.5 the procedures, tools and techniques to undertake functional testing K19 The relationship between programming languages and development environments K32 Use and apply: K32.1 specified software development procedures, tools and techniques 19

21 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY Gaps in Indian KB19. how to create, review and execute UTCs KB20. how to determine whether components are suitable for re-use KB21. different types of problems and defects that may occur and how these may be K32.2 naming conventions and standards in line with organisational standards K32.3 appropriate programming constructs to produce effective software K32.4 information relating to data and HCI design deliverables in order to inform K32.5 the procedures, tools and techniques to undertake functional testing K15. Verify functional requirements for individual software components K32 Use and apply: K32.1 specified software development procedures, tools and techniques K32.2 naming conventions and standards in line with organisational standards K32.3 appropriate programming constructs to produce effective software K32.4 information relating to data and HCI design deliverables in order to inform K32.5 the procedures, tools and techniques to undertake functional testing K32.5 the procedures, tools and techniques to undertake functional testing 20

22 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY resolved Gaps in Indian KB22. how recording corrective actions for problems and defects can improve future designs KB23. how to test and debug new software code KB24. different sources of information for help to write software code KB25. how to protect software assets KB26. policy for 3rd party software and freeware K16. Document software development and testing accurately and clearly to allow further development, amendments and updates to be made to solutions K32.5 the procedures, tools and techniques to undertake functional testing K32 Use and apply: K32.1 specified software development procedures, tools and techniques K32.2 naming conventions and standards in line with organisational standards K32.3 appropriate programming constructs to produce effective software K32.4 information relating to data and HCI design deliverables in order to inform K32.5 the procedures, tools and techniques to undertake functional testing K8. the relationship between and other solution development and implementation K9. the value and role of in addressing business problems 21

23 TRANSTIOL SKILL STANDARDS FOR IT-ITeS INDUSTRY and opportunities Gaps in Indian K10. The fact that new software may need to be developed or existing software enhanced or adapted to take account of changing business needs K11. The fact that external providers of software development services exist K33. Operate with reference to: K33.1 organisational standards for K33.2 professional and ethical standards in software K33.3 integrity and confidentiality during software K33.4 design requirements and operating environments 22