ISO 9001 for software

Ok, I'll read your post about IAF, I'll inform myself better about that... However, the 3°rd party auditor who made ther certifiucation visit, never mentionated this standard

 

Ok, but in Italy we have Accredia for thi ISO certification, IAF is nothing more than another certifying body. Our certification is no longer valid, true, but we are a small company and have close ties to customers, to the point that we have been growing steadily since we opened in 2008. My directors choose another certifyng body, I suppose it's the same as IAF. This is my opinion, but I may be wrong... If so please point it out to me
Bye and thanks for the advice

 

IAF (International Accreditation Forum) is not a certifying body. The members of this organization are accreditation bodies, usually government agencies, that regulate the operation of certifying bodies. Certifying bodies are private organizations that provides certification services to organizations, like your organization, who wanted to get certification against international standards such as ISO 9001, ISO 14001, ISO 45001, etc.

 

But for now I'm interested 9001 only, IAF it's not necessary... We will upgraded 2008 into 2015, it has already expired for many years

 

I'll check asap

 

That's true!
These have been very intense years.
Jokes aside, I came to work here about a year ago just to accomplish this upgrade, I have no idea why they decided with all this delay to upgrade the ISO, but that's the way it is, I don't feel like asking for explanations, what was there before they hired me I try not to let them interest me or ask questions about it.

Thank you very much for your answers, you are kind, so is tony s, thank you for your kindness

Translated with www.DeepL.com/Translator (free version)

 

In my country IAF cover food healthy, nothing about software.
Rina offers itself as an accredited body to issue quality management sstem certifications in accordance with ISO 9001 for various commodity sectors and related certification schemes.
IAF here don't do that. This is my opinion, but I may be wrong... If so please point it out to me

We are not exactly software, we don't develop software but we build models that have to manage sometimes the energy released by hydrogen fuel cells, sometimes we deal with the road mobilization of hybrid cars, you have to manage how the power to the wheels is distributed, whether by endothermic engines i by electric motors.
Perhaps "software modeling" is a term that best describes what the company in which I serve deals with.


Bye from italy

 

thanks very much for your explanATION..
I will check yopur link asap
Bye

 

I


I'm talking about ISO9001 not ISO17021, that is for the labouratory of phisical/ chemistry, iso 9001 is more generic

 

youre right, excuse me but my lack of preparation, my inexperience.
Thanks a lot for the advice

 

I'm extremely new to ISO9001, but do have some thoughts on measuring the software development process. I thought I'd share ahead of me having to figure this out for my own company.

Your software will have some customer, that may be an internal or external one, and they will have requirements about what that software should do.

The performance of the software engineering team ought to be measured based on it's ability to translate requirements to software and to do that consistently.

Therefore I would be interested in measuring project overspend (in terms of effort or timescales) on delivering software - projects overspending is a symptom of something going wrong (bad estimate, poor performance, unmitigated risks) - and if projects overspend then you are not going to consistently be able to deliver on requirements.

You could measure defect rate (bugs reported) as some measure of quality - however if you measure project overspend by looking at estimated vs actual effort - then you implicitly factor defects into this. (And avoid gaming of the overspend KPI by finishing a project on time but with bugs).

I fear that anything that digs deeper into the process may be counter productive. And may tie you into a particular method of developing software (agile is increasingly popular).

 

Andrew
Bear in mind that many customers don't know what they want, or even what is possible, and at the same time many developers are unable to put themselves in the position of the end-user and so anticipate actual usage requirements. Bug rate / speed of fixing / customer satisfaction feedback / number of changes to requirements / even the number of repeat orders can help. Although I admit that customer/user expectations are lower than when I started - Microsoft has perhaps led the way...