lecture’15 so,ware’quality’matt/csc302/lectures/15_quality_1.pdf ·...
Transcript of lecture’15 so,ware’quality’matt/csc302/lectures/15_quality_1.pdf ·...
lecture 15 so,ware quality
csc302s
winter 2014
recap from last 5me
• sta0c analysis • a lot is done “live” by the IDE while you are coding.
• beyond what is done in your IDE: – aAempts to find null dereference or null assignment
– array index out of bounds etc. – other run0me errors not caught by compiler – duplicate code
• many false posi0ves & nega0ves • your mileage may vary
ISO/IEC 25010:2011
ISO/IEC 25010:201 The fundamental objec0ve of the ISO/IEC 9126 standard is to address some of the well known human biases that can adversely affect the delivery and percep0on of a soRware development project. These biases include changing priori0es aRer the start of a project or not having any clear defini0ons of "success." By clarifying, then agreeing on the project priori0es and subsequently conver0ng abstract priori0es (compliance) to measurable values (output data can be validated against schema X with zero interven0on), ISO/IEC 9126 tries to develop a common understanding of the project's objec0ves and goals.
The standard is divided into four parts: • quality model • external metrics • internal metrics • quality in use metrics.
slide from lecture 2 – architecture
"Il semble que la perfection soit atteinte non quand il n'y a plus rien à ajouter, mais quand il n'y a plus rien à retrancher.” – Antoine de Saint Exupéry, Terre des Hommes, 1939 (my) translation: “perfection is finally attained not when there is no longer anything to add, but when there is no longer anything to take away"