Software engineering...standards and practices
Software engineering...standards and practices
(OP)
Hello,
Can someone throw some light on what are the codes/ specifications which are the most typical and authoritative in the field of software engineering?
I realize this is a vast subject/discussion and I would like to tentatively narrow it down. So what I have in mind is try to identify a set of standards which forms a baseline of requirement upon which any software can be engineered in a structured way and to quality. For instance, I suspect that to validate/ test a software - like any industrial product, and qualify that software for exploitation, you would need to set some acceptance criteria (a criteria that relates to the "use" - just to be clear here).
While doing some internet review, I came across this (as starting point):
ISO/IEC 9126-1 Software Product Quality Model
ISO 9241 - in particular part 11 which covers the "usability"
The above seems to apply irrespective of the size, type of the software, etc. Instead this seems to address the quality of the user experience.
What do you suggest? would the standard listed above be seen as something "over the top"?
Can you share some information based on your experience?
Thanks in advance
Can someone throw some light on what are the codes/ specifications which are the most typical and authoritative in the field of software engineering?
I realize this is a vast subject/discussion and I would like to tentatively narrow it down. So what I have in mind is try to identify a set of standards which forms a baseline of requirement upon which any software can be engineered in a structured way and to quality. For instance, I suspect that to validate/ test a software - like any industrial product, and qualify that software for exploitation, you would need to set some acceptance criteria (a criteria that relates to the "use" - just to be clear here).
While doing some internet review, I came across this (as starting point):
ISO/IEC 9126-1 Software Product Quality Model
ISO 9241 - in particular part 11 which covers the "usability"
The above seems to apply irrespective of the size, type of the software, etc. Instead this seems to address the quality of the user experience.
What do you suggest? would the standard listed above be seen as something "over the top"?
Can you share some information based on your experience?
Thanks in advance





RE: Software engineering...standards and practices
Dan - Owner
http://www.Hi-TecDesigns.com
RE: Software engineering...standards and practices
Cheers
Greg Locock
New here? Try reading these, they might help FAQ731-376: Eng-Tips.com Forum Policies http://eng-tips.com/market.cfm?
RE: Software engineering...standards and practices
http://standards.ieee.org/findstds/standard/12207-...
http://standards.ieee.org/develop/wg/WG_LCP.html
TTFN (ta ta for now)
I can do absolutely anything. I'm an expert! https://www.youtube.com/watch?v=BKorP55Aqvg
FAQ731-376: Eng-Tips.com Forum Policies forum1529: Translation Assistance for Engineers Entire Forum list http://www.eng-tips.com/forumlist.cfm
RE: Software engineering...standards and practices
Thanks very much for the references.
By the way, what do you mean by "supposed" industry standard, can I infer that this is on the paper - in the field, implementation is another story?
RE: Software engineering...standards and practices
TTFN (ta ta for now)
I can do absolutely anything. I'm an expert! https://www.youtube.com/watch?v=BKorP55Aqvg
FAQ731-376: Eng-Tips.com Forum Policies forum1529: Translation Assistance for Engineers Entire Forum list http://www.eng-tips.com/forumlist.cfm
RE: Software engineering...standards and practices
Software development is much more difficult to validate. While a sky scraper can be analyzed by seeing that each floor can support those above it, software could allow a loose toilet handle in the penthouse to destroy the foundation and bring it all down.
The most promising techniques are white-board walk-throughs and fuzzing, where random inputs are applied to functions to see how or if they fail.
From SEI:
Work Areas
Acquisition Support
Cyber-Physical Systems
Measurement & Analysis
Performance & Dependability
Pervasive Mobile Computing
Process & Performance Improvement
Risk Management
Security & Survivability
Smart Grid
Software Architecture
Software Product Lines
System of Systems
Ultra-Large-Scale Systems
RE: Software engineering...standards and practices
Maybe should stay away from the whole concept of "standard" ; probably something like "guidelines" or even "rules of thumb" would be more appropriate.
RE: Software engineering...standards and practices
Dan - Owner
http://www.Hi-TecDesigns.com