1. rm040126.ppt Application of the Competence Guidelines to Software Engineering DIRC Workshop on Software Quality and the Legal System 13 February 2004 DIRC Workshop on Software Quality and the Legal System 13 February 2004 Rod May Tel: +44 (0)1427 667118 email: rodmay@iee.org Rod May Tel: +44 (0)1427 667118 email: rodmay@iee.org

2. rm040126.ppt Agenda 1. 1. Standards for personnel competence 2. 2. The Competency Guidelines 3. 3. Application to Software Engineering 4. 4. Benefits Agenda 1. 1. Standards for personnel competence 2. 2. The Competency Guidelines 3. 3. Application to Software Engineering 4. 4. Benefits Rod May Tel: +44 (0)1427 667118 email: rodmay@iee.org Rod May Tel: +44 (0)1427 667118 email: rodmay@iee.org Application of the Competence Guidelines to Software Engineering DIRC Workshop on Software Quality and the Legal System 13 February 2004 DIRC Workshop on Software Quality and the Legal System 13 February 2004

3. rm040126.ppt Strategy to obtain functional safety Technical requirements Safety management Personnel competency IEC 61508 requirements

4. rm040126.ppt IEC61508 Requirements for Personal Competence Management of functional safety - Part 1 Section 6 Requirement 6.2 ……. the following should be considered: 6.2.1 h the procedures for ensuring that applicable parties involved in any of the overall, E/E/PES or software safety lifecycle activities are competent to carry out the activities for which they are accountable Note 1 - Annex B provides guidelines on the competence requirements of those involved in any overall, E/E/PES or software safety lifecycle activity IEC 61508 requirements

5. rm040126.ppt IEC61508 Part 1 Annex B (informative) B.1 Objective This annex outlines considerations for ensuring that persons who have responsibilities for any overall, E/E/PES or software lifecycle activity are competent to discharge those responsibilities. B.2 General Considerations All persons involved in any overall, E/E/PES or software safety lifecycle activity, including management activities, should have the appropriate training, technical knowledge, experience and qualifications relevant to the specific duties they have to perform. The training, experience and qualifications of all persons involved in any overall, E/E/PES or software safety lifecycle activity, including management activities, should be assessed in relation to the particular application. IEC 61508 requirements

6. rm040126.ppt IEC61508 Part 1 Annex B (continued)  Factors to be considered when assessing competence  engineering knowledge appropriate to the application technology  safety engineering knowledge appropriate to the technology  knowledge of the legal and safety regulatory framework  increased competence and assessment for consequence SIL novelty of design  greater competence requires more related experience  qualifications must be relevant  Training, experience and qualifications should be documented IEC 61508 requirements

7. rm040126.ppt Principles Phase 1 – Establish requirements for CMS A1Identify activities and assess risks A2Select standards Phase 2 – Design CMS A3Develop procedures and methods A4Decide how to meet the standards A5Establish requirements for training, development and assessment A6Maintain managers’ competencies Phase 3 – Implement CMS A7Select and recruit staff A8Train, develop and assess staff A9Control activities undertaken Phase 4 – Maintain competence A10Monitor and reassess staff A11Update the competence of individuals A12Manage sub-standard performance A13Keep records Phase 5 – Audit and review CMS A14Verify and audit CMS A15Review and feed back Railway Safety Principles and Guidance

8. rm040126.ppt Competency model Operation of scheme Guidance provided Management system Personal assessment Self assessment Team competencies Professional development Licensing & accreditation Guidance provided Management system Personal assessment Self assessment Team competencies Professional development Licensing & accreditation Standards of competence All with respect to safety Corporate management Project assurance Hazard & risk analysis Requirements specification Architectural design Hardware realisation Software realisation Human factors Procurement Maintenance/modification Independent assessment All with respect to safety Corporate management Project assurance Hazard & risk analysis Requirements specification Architectural design Hardware realisation Software realisation Human factors Procurement Maintenance/modification Independent assessment IEE/BCS/HSE Guidelines

9. rm040126.ppt Competency Model Identify actions to improve competence Select an overall level and provide a summary For the function as a whole Provide the context of the assessment Standard of best practice Provide evidence to support the claim Make a claim for a level of competence For each individual competency Competency Assessment Assessment Guidance Supervised Practitioner Expert Context Summary Job LevelFunction Role Technical skills Knowledge Behavioural skills Understanding Individual competencies Task-related Function-related IEE/BCS/HSE Guidelines

10. rm040126.ppt 1Select a Function against which an assessment of competency is to be made Software Engineering: Requirements engineering System design Software design Software construction Software build, integrate and test Software maintenance Application to software engineering

11. rm040126.ppt For the Function selected 2 Enter context of assessment Application to software engineering a company’s Web-based

12. rm040126.ppt 3 Select an individual competency to assess for the Function Software construction: Interpret software requirements Software high-level design Modelling and prototyping Designing for software integrity Assess and manage risk Compliance with software design standards Software design verification and validation Software design documentation Application, commercial and market awareness Software design issues Software design strategies Software design techniques and tools Creative/conceptualisePersuasiveness Effective communications Application to software engineering

13. rm040126.ppt Using the description and guidance provided: 4aClaim a level; and 4bReference the evidence Repeat for all competencies Application to software engineering

14. rm040126.ppt Viewing the histogram of competencies assessment 5aClaim overall level 5bProvide summary 5cPlan actions Application to software engineering

15. rm040126.ppt Company benefits from adoption of Competency Management System  Improved staff competence  Improved staff deployment  Reduced staff turnover  More effective staff recruitment  More effective use of staff development budget  Compliance with professional development requirements  Improved staff competence  Improved staff deployment  Reduced staff turnover  More effective staff recruitment  More effective use of staff development budget  Compliance with professional development requirements  Improved and reduced maintenance of job descriptions  More effective annual appraisals  Compliance with ISO9001:2000  Provision of evidence of competence  Lower insurance premiums  Increased sales  Improved and reduced maintenance of job descriptions  More effective annual appraisals  Compliance with ISO9001:2000  Provision of evidence of competence  Lower insurance premiums  Increased sales Summary

16. rm040126.ppt Two quotations 1 The only rule I have in management is to ensure that I have good people - really good people - and that I grow good people, and that I provide an environment where good people can produce. Knowledge is the raw material of software development, and it is software engineers who transform knowledge into software products … Improving technology and process alone is not enough in the most knowledge-intense industry in history. Improving a software organisation requires continual improvement of its people and of the conditions that empower their performance. 1 Source: Curtis, Hefley and Miller, People Capability Maturity Model, SEI Carnegie Mellon University, 1995 Summary