Re: Software and Standards
When using the term software, I think I am talking about the product and the process producing that product. So I guess you mean these two's quality.
Software engineering is always based on analytical models to
1. Understand the nature of processes and products
2. Grasp the variations of them
3. Figure out how they connect together
4. Analyze and predict future changes and possible faults during operations in a long run
These four points indicates your assumption on the software standard is mistaken
[edit]I intend to add 3 more points to sum up to 7 but, well...enough :) ;)
Re: Software and Standards
seems to be a good starting point:
Carnegie Mellon Capability Maturity Model for Software - http://www.sei.cmu.edu/cmm/cmm.html
IBM Rational Unified Process: http://www-306.ibm.com/software/awdtools/rup/
Re: Software and Standards
I hope, this thread can be also useful.