#15 METL - Improvements to address needs of Software Engineering : change request accepted
Some changes in emphasis and wording across the Skill description and skill level descriptions to ensure Software Engineering is addressed.
Areas to review:
- How to reflect importance of automation throughout full life cycle of development and support and skills for roles like Tool Architect, DevOps Engineers
- The skill descriptors are too short / not sufficient competency indicators to be used consistently.
- Clarity on SFIA's interpretation of "methods" and of "tools" and how those fits with some related skills such as Quality Management
- Are Methods and Tools skills best described as "stand alone skills" or are they better embedded in particular skills which are heavily reliant on Methods and Tools
This change request is one of a number which are proposing revisions to SFIA to ensure it fully supports Software Engineering while retaining overall industry wide applicability and integrity.
The updates will support:
- The Software Engineering & Technology industry, it's employers and professionals to close skill gaps, attract and retain talent and improve the performance and productivity of engineers
- Alignment of Software Engineering training / accreditation
- Professional development through the IEEE-CS and other professional bodies representing software engineers
- Universities, technical institutes, and other higher education organisations to support professional education and accreditation and enhance the employability of their students
Also need to consider the relationship (e.g. unique skills and overlapping skills) between Software Engineering and IT.
Attached to Methods and tools
What we decided
Make sure the skill description is agnostice / neutral to what the method or tool is.
Ensure clearer delineation between levels and that the skill level descriptions have sufficient indicators (SFIA6 version are very short).
What we changed
Updated overall skill description.
Updated levels 4,5 & 6.
Added level 3.