rm040126.ppt application of the competence guidelines to software engineering dirc workshop on...
Post on 22-Dec-2015
218 views
TRANSCRIPT
rm040126.ppt
Application of the Competence Application of the Competence Guidelines to Software EngineeringGuidelines to Software Engineering
Application of the Competence Application of the Competence Guidelines to Software EngineeringGuidelines to Software Engineering
DIRC Workshop on Software Quality and the
Legal System13 February 2004
DIRC Workshop on Software Quality and the
Legal System13 February 2004
Rod MayTel: +44 (0)1427 667118email: [email protected]
Rod MayTel: +44 (0)1427 667118email: [email protected]
rm040126.ppt
Agenda
1. Standards for personnel competence
2. The Competency Guidelines
3. Application to Software Engineering
4. Benefits
Agenda
1. Standards for personnel competence
2. The Competency Guidelines
3. Application to Software Engineering
4. BenefitsRod May
Tel: +44 (0)1427 667118email: [email protected]
Rod MayTel: +44 (0)1427 667118email: [email protected]
Application of Application of the the
Competence Competence Guidelines to Guidelines to
Software Software EngineeringEngineering
Application of Application of the the
Competence Competence Guidelines to Guidelines to
Software Software EngineeringEngineering
DIRC Workshop on Software Quality and the
Legal System13 February 2004
DIRC Workshop on Software Quality and the
Legal System13 February 2004
rm040126.ppt
Strategy to obtain functional safety Strategy to obtain functional safety
Technical requiremen
ts Safety managem
ent
Personnel competen
cy
IEC 61508 requirements
rm040126.ppt
IEC61508 Requirements for Personal IEC61508 Requirements for Personal CompetenceCompetence
Management of functional safety - Part 1 Section 6
Requirement 6.2 ……. the following should be considered:
6.2.1 hthe 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
rm040126.ppt
IEC61508 Part 1 Annex B (informative)IEC61508 Part 1 Annex B (informative)
B.1 ObjectiveThis 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 ConsiderationsAll 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
rm040126.ppt
PrinciplesPhase 1 – Establish requirements for CMSA1 Identify activities and assess risksA2 Select standards
Phase 2 – Design CMSA3 Develop procedures and methodsA4 Decide how to meet the standardsA5 Establish requirements for training, development and assessmentA6 Maintain managers’ competencies
Phase 3 – Implement CMSA7 Select and recruit staffA8 Train, develop and assess staffA9 Control activities undertaken
Phase 4 – Maintain competenceA10 Monitor and reassess staffA11 Update the competence of individualsA12 Manage sub-standard performanceA13 Keep records
Phase 5 – Audit and review CMSA14 Verify and audit CMSA15 Review and feed back
Railway Safety Principles and Guidance
rm040126.ppt
CompetencCompetency modely model
CompetencCompetency modely model
Operation of schemeOperation of scheme
Guidance provided
Management systemPersonal assessmentSelf assessmentTeam competenciesProfessional developmentLicensing & accreditation
Guidance provided
Management systemPersonal assessmentSelf assessmentTeam competenciesProfessional developmentLicensing & accreditation
Standards of
competence
Standards of
competenceAll with respect to safety
Corporate managementProject assuranceHazard & risk analysisRequirements specificationArchitectural designHardware realisationSoftware realisationHuman factorsProcurementMaintenance/modificationIndependent assessment
All with respect to safety
Corporate managementProject assuranceHazard & risk analysisRequirements specificationArchitectural designHardware realisationSoftware realisationHuman factorsProcurementMaintenance/modificationIndependent assessment
IEE/BCS/HSE Guidelines
rm040126.ppt
Competency ModelCompetency ModelCompetency ModelCompetency 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 competenceFor each
individual competency
Competency Assessment
Assessment GuidanceSupervised Practitione
rExpert
Context
Summary
Job
LevelFunctionRole
Technical skillsKnowledgeBehavioural skillsUnderstanding
Individual competencies
Task-related Function-related
IEE/BCS/HSE Guidelines
rm040126.ppt
11 Select a Function against Select a Function against which an assessment of which an assessment of competency is to be madecompetency is to be madeSoftware EngineeringSoftware Engineering::
Requirements engineeringRequirements engineeringSystem designSystem designSoftware designSoftware designSoftware constructionSoftware constructionSoftware build, integrate and testSoftware build, integrate and testSoftware maintenanceSoftware maintenance
Application to software engineering
rm040126.ppt
For the Function selected
2 Enter context of assessment
Application to software engineering
a company’sWeb-based
rm040126.ppt
3 Select an individual competency to 3 Select an individual competency to assess for the Functionassess for the FunctionSoftware construction:Software construction:
Interpret software requirementsInterpret software requirementsSoftware high-level designSoftware high-level designModelling and prototypingModelling and prototypingDesigning for software integrityDesigning for software integrityAssess and manage riskAssess and manage riskCompliance with software design Compliance with software design
standardsstandardsSoftware design verification and Software design verification and
validationvalidationSoftware design documentationSoftware design documentationApplication, commercial and market Application, commercial and market
awarenessawarenessSoftware design issuesSoftware design issuesSoftware design strategiesSoftware design strategiesSoftware design techniques and toolsSoftware design techniques and toolsCreative/conceptualiseCreative/conceptualisePersuasivenessPersuasivenessEffective communicationsEffective communications
Application to software engineering
rm040126.ppt
Using the description and Using the description and guidance provided:guidance provided:4a4a Claim a level; andClaim a level; and4b4b Reference the Reference the evidenceevidenceRepeat for all Repeat for all competenciescompetencies
Application to software engineering
rm040126.ppt
Viewing the histogram of competencies assessment
5a Claim overall level5b Provide summary5c Plan actions
Application to software engineering
rm040126.ppt
Company benefits from adoption of Company benefits from adoption of Competency Management SystemCompetency Management System
Company benefits from adoption of Company benefits from adoption of Competency Management SystemCompetency 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 salesSummary
rm040126.ppt
Two quotationsTwo quotations 1 1Two quotationsTwo quotations 1 1
The only rule I have in management is to ensure The only rule I have in management is to ensure that I have good people - really good people - and that I have good people - really good people - and that I grow good people, and that I provide an that I grow good people, and that I provide an environment where good people can produce.environment where good people can produce.
Knowledge is the raw material of software Knowledge is the raw material of software development, and it is software engineers who development, and it is software engineers who transform knowledge into software products … transform knowledge into software products … Improving technology and process alone is not Improving technology and process alone is not enough in the most knowledge-intense industry in enough in the most knowledge-intense industry in history. Improving a software organisation requires history. Improving a software organisation requires continual improvement of its people and of the continual improvement of its people and of the conditions that empower their performance.conditions that empower their performance.
1 Source: Curtis, Hefley and Miller, People Capability Maturity Model, SEI Carnegie Mellon University, 1995
Summary