Home

ソフトウェアの評価技術 に関する標準化 成 果 報 告 書

Contents

1.
2.
3. JIS INSTAC
4. TS ISO IEC 9126 4 2004 Software engineering
5. 1991 7 1993 1 CMM MOD SQPA STD
6. Y Y7 TS ISO IEC TR 9126 3 2003 Software engineering
7. 3 2 1
8. He JIS X 0145 JIS X 0145 1 1 JIS X 0145 2 2 JIS X 01453 3 JIS X 01454 4 3 JIS X 01 45 4 0000 ISO IEC 15504 4 2004 4
9. COTS B JIS X 0152 1995 JIS X 0129 1994 JIS X 0129 1994 JIS X 0129 1 2003 SQUARE JIS X 25010 JIS X 0152 1995
10. UC DRE a rs COW OEE CC Yh LI
11. TS TS TS IEC TC 65 ISO IEC JTC1 SC27 1 TS
12. TS TS TS 6 TS X 0111 4 2009 ISO IEC 9126 4 2004 IEC TC6S ISO IEC JTCUSC27 2 3 TS
13. i lt 4 GE JIS X 0135 3 2010 3 Software measurement Functional size measurement Part 3 Determination of funtional domains for use with functional size measurement and Performance verification of functional size measurement methods 2003 1 ISO IEC TR 14143 3 Software measurement Functional size measurement Part 3 Verification of functional size measurement methods 2002 1 ISO IEC TR 14143
14. ISO IEC 15504 4 2004 Information technology Process assessment Part 4 Guidance on use for process improvement and process capability determination IDT DT X ISO IEC Guide 21 1 20 1 JIS X 0135 1 2010 ISO IEC 14143 1 2006 22 OO X 0135 1 2008 ISO IEC 14143 1 2006 H X cu A nn EEEE i000 0tii00t 2 2 io 2 3 ee 2 4 Eon dd ud da d dad 4 4 4 5 2 ibas 4 6 FSM ma 6 7 FSM meeeeeeeeeeeeeeeeoeeoeeeoossseseeeesesesseeseeeeeseeeeesesseseseesesseeesesessesessesessesssessesessesseessessesesesesses
15. BA JIS 5 DISO IEC 15504 1 2004 Information technology Process Assessment Part 1 Concepts and vocabulary ISO IEC 15504 2 2003 Information technology Process Assessment Part 2 Performing an assessment 10 ISO IEC 15504 3 2004 Information technology Process Assessment Part 3 Guidance on performing an assessment ISO IEC 15504 4 2004 Information technology Process Assessment Part 4 Guideline on use for process improvement and process capability determination BISO IEC 15504 5 2006 Information technology Process Assessment Part 5 An exemplar process assessment model 5 ISO IEC TR 15504 6 2008 Information technology Process Assessment Part 6 An exempl
16. a COTS b COTS c COTS COTS P COTS
17. Re 1979 IBM Allan J Albrecht Albrecht FSM
18. SQuaRE JIS X 0129 JIS X 0133 ISO IEC 25000 2005 Software engineering Software product Quality Requirements and Evaluation SQuaRE Guide to SQuaRE IDT DT ISO IEC Guide 21 2 SOuaRE SQuaRE 3 4
19. LC SQuaRE JIS X 0129 1994 X JIS X 0129 JIS X 0133 SQuaRE
20. JIS X 0145 2 a b CO d e f JIS X 0145 2 JIS X 0145 2 ISO IEC 15504 4 2004 Information technology Process assessment Part3 Guidance on 19 4 JIS X 0145 4 2010 ISO IEC 15504 4 2004 22 OO
21. s 25 NPO Mozilla Thunderbird SC7 WG2 8 4
22. 2 3 2 1 2009 04 17 4 2 2009 05 H 15 4 3 2009 06 19 4 4 n 2009 07 17 4 5 2009 09 18 4 6 2009 10 16 amp 7 2009 11 20 8 2009 4 12 H 18 4 9 2010 01 H 08 4 10 2010 02 19 2 3 3 Thunderbird Thunderbirrd
23. JIS SC7 WG6 212 SOuaRE 2501 n 2503 n 2500 n 2504 n 2502 n 25050 25099 1 SQuaRE SQuaRE 1 Division Extension
24. FPE 3 JIS X 25000 2010 ISO IEC 25000 2005 SQuaRE SQuaRE software engineering Software product Quality Requirements and Evaluation SQuaRE Guide to SQuaRE 2005 1 ISO IEC 25000
25. i lt 3 X 25051 2010 ISO IEC ISO IEC 25051 2006 JIS X 25051 0000 ISO IEC 25051 2006 SQuaRE COTS software engineering Software product Quality Requirements and Evaluation SQuaRE Requirements for quality of Commercial Off The Shelf COTS software product and instructions for testing 2006 1 ISO IEC 25051 COTS lt
26. JISX0129 JIS X 013338 8 HE X JISX0129 JIS X 0133 pear SOuaRB SQuaRE 2 X 25000 2010 ISO IEC 25000 2005 SQuaRE
27. JIS X 0145 JIS X 0145 1 1 JIS X 0145 2 2 JIS X 0145 3 3 JIS X 0145 4 4 4 JIS X 0145 8 2010 ISO IEC 15504 3 2004 3 Information Technology Process assessment part3 Guidance on Performing an assessment 2004 1 ISO IEC 15504 3 1 JIS X 0145 2
28. 1 2500n 2 SOuaRE e ISO IEC 25000 Software engineering Software product Quality Requirements and Evaluation SQuaRE Guide to SQuaRE IS 2005 8 e ISO IEC 25001 Software engineering Software product Quality Requirements and Evaluation SQuaRE Planning and management IS 2007 2 2 2501n 2 ISO IEC 25010 Software engineering Software product Quality Requirements and Evaluation SQua
29. loo YO ISO IEC 14143 1 2006 Information technology Software measurement Functional size measurement Part 1 Definition of concepts IDT IDT ISO IEC Guide 21 21 3 JIS X 0135 3 2010 ISO IEC 14143 3 4 5 2003 22 OO 2 X 0135 3 2010 ISO IEC 14143 3 4 5 2003 A d our ey Ee ee d gentes Mut unten dn eedem MI cS MM ree net eee oro E E 1 ME ue NN NN 1 2 pp o Re E ee Re ete 2 2 4 E M X ee 5 SS 5 E ED ce A E N 8 ON NES o EL 3 611 eRe sate at a ACORDES me I osteo etn etter A 8 612 eere mi tenete aho em 8 6 1 3 NO 8 9
30. TS ISO IEC TR 9126 2 2003 Software engineering Product quality Part 2 External metrics IDT IDT ISO IEC Guide 21 2 TS JIS X 0129 1 3 TS TS JIS X 0020 1992 ISO IEC 2382 20 1990 Information technology Vocabulary Part 20 System development MOD JIS X 0129 1 2003
31. COTS COTS COTS COTS COTS
32. 12 INSTAC ISO IECJTCI SC7 JTC1 SC7 INSTAC JTC1 SC7 JIS B
33. GUI e ISO IEC WD 26511 Software and systems engineering User documentation requirements for managers e ISO IEC CD 26512 Software and systems engineering Requirements for acquirers and suppliers of user documentation e ISO IEC FCD 26513 Systems and software engineering Requirements for testers and reviewers of user documentation e SO IEC CD 15289 Systems and software engineering Content of life cycle information products amp 335 Documentation 2 3 4
34. SQuaRE 4 1 acquirer VATA JIS X 0160 1996 4 2 analysis model 4 3 attribute JIS X 0141 2009 A NNN 14 SQUARE COTS JIS X 25051 2010 ISO IEC ISO IEC 25051 2006 X 25051 2010 ISO IEC ISO IEC 25051 2006 Sy EEE EEE i000 00 3 2 i i c EEOEE EEE EEE 3 3 FH pp EE 3 4 3 5 COTS eereeereereereereereereereereereereereereereereereereereeseereeseereeseereereereeseeseeseeseereeseeseeseereesee 6
35. SOQuaRE 2 SQuaRE d SQuaRB ISO IEC 2500n JIS Q9000 SQOuaRE ISOMEC 25020
36. SQuaRE JIS X 0129 JIS X 0133 SQuaRB 3 X 25000 2010 ISO IEC 25000 2005 1 ASE SQuaRE SQuaRE SQuaRE 2 JIS X 0129 JIS X 0133 SQuaRE JIS X 0129 JIS X 0133 SQuaREB
37. 3 1 ISOMEC 9126 1 KU ISO IEC 14598 1 20077 2 3 PR NE a sate ys Log cc JTC1 SC7 WG6 SCT WG6 6 ROME CHA ID SCIIWG6 SQuaRE Software product Quality Requirements and Evaluation 2
38. Fie AIO Ia Cees NWI SC7 WG2 OpenOffice org Writer Calc Draw Impress
39. SQuaRE INSTAC 115 ISQuaRE 65 JIS 2 SQuaRE JIS 22 WG2 SPA 221
40. FSM FSM JIS X 0135 JIS X 0135 1 2008 JIS X 0135 2 2004 ISO IEC TR 14143 3 2003 WSW MM DG s DARA AMET BUR LU 1 FSM FSM FSM
41. NIT NTT 144 WG3 OLD zt BS ESSA K HF Yet Ho Fri vum KE MA E F7 X 1 5 WG
42. TRIER ESI E ER iH S DRAB F tc yE H ase FEC HB BRR FE ER ER NTT R NALE APT AREA 4 3 WG2
43. JIS X 0141 JIS X 0129 JIS X 0133 SQuaRE JISX0141 SQuaREB ISO IEC 2500n ISO IEC 2501n ISO IEC 2502n ISO IEC 2503n ISO IEC 2504n ISO IEC 25050 ISO IEC 25099 SQuaRE SQuaRB BRE IV SQuaRE
44. JA BAI A uH RB FF fT HATA Cm DARA EE amp RAPES WR EPEA FFE SER ETAT PER A PE SEDAN ER Ban TH EC HS PAE EXE S Fr amp 44 dt ER XM XA OA OA OAR XE H um rn mr xu xu xu uw wy mu xu wm x uu xu xu Wu wu m PE ES a 4 EX Na XA XA OR XR OR OR OA OM A NA NA NA Na Ni rH As IX A Hf AER BY EVE
45. ISO IEC 15504 Automotve Spice IPA SEC 23 WG3 OLD 2 3 1
46. X 0134 4 2009 ISO IEC 15504 4 2004 X our EEE EEE 1 2 By FH FF EE 2 3 ee 2 7 S ITT TT TIT ITT TTITT TT TIT TT TT 2 41 2 4 2 2 43 3 44 3 45 ee 3 46 4 5 5 5 1 t OT ITT TIT TITIT TIT TT TTT TIT TTTTT TTTTTT 5 WD n E E aa SEE 5 5 3 E EEDE 5 S 4 E 7 55 DOA KAY KT 8 6 oo 10 6 1 rr 10 62 11 7 18 7 1 rr 18 72 P ee 20 7 3 ir 22 A 24 meh RARE RULES pin nie 29 HEC SX JECDXEP 0SB8 V ood ud i eie e HUI IH HUE 31 RE EEE 34 2 X 0134 4 2009 ISO IEC 15504 4 2004
47. IT TS TS JISX 0129 1 2003 1 TS X 0111 3 2008 3 JIS X 0129 1 TS X 0111 4 2008 4 JIS X 0129 1 1 TS JIS X 0129 1 JISX0129 1 TS a b c
48. TS TS JIS X 0129 1 2003 1 1 TS JIS X 0129 1 JISX0129 1 TS a b c TS
49. 1 ISO IEC 9126 1 2001 Software engineering Product quality Part 1 Quality model IDT JIS X 0133 1 1999 1 ISO IEC 14598 1 1999 Information technology Software product evaluation Part 1 General overview IDT JIS X 0133 2 2001 2 ISO IEC 14598 2 2000 Software engineering Product evaluation Part 2 Planning and management IDT TS X 0111 3 2009 ISO IEC TR 9126 3 2003 16 3 JIS X 0129 1 TS X 0111 3 20 ISO IEC 9126 3 2003 21 10 20 24 10 19 1 TS X0111 3 2009 ISO IEC TR 9126 3 2003 our 5 10 7 T seer 000000007000 0000 1 EEEE i0000t 1 2 i i EEE EEE 2 3 io 2 4
50. 1 3 OY SPE SPA OLD WG1 SPE WG SPA 1 A A WG3 OLD 14 1 4 1 ZA E Hom WI KE BK AU
51. JIS JIS X0142 TFPUG IFPUG4 1 I N 5 I N s odas Document Type Title Source Project Status References Action ID Due Date Start Date Distribution Medium No of Pages Note ISO IEC JTC1 SC7 Software and Systems Engineering INFORMATION TECHNOLOGY STANDARDS Secretariat CANADA SCC ISO IEC JTC1 SC7 N4S22 2010 01 04 FCD Ballot FCD 25010 Software engineering Software product Quality Requirements and Evaluation SQuaRE Quality mode WG6 25010 N4386 N4520 N4521 ACT 2010 05 04 2010 01 04 SC7 AG PDF 46 Please vote using the ISO Electronic Balloting Facilities Resolution 937 Address reply to ISO IEC JTC1 SC7 Secretariat Ecole de technologie sup rieure Departement of Software and IT Engineering 1100 Notre Dame Ouest Montr al Qu bec Canada H3C 1K3 secretariat jtcl sc7 org www jtcl sc7 org TITLE DATE SOURCE WORK ITEM STATUS DOCUMENT TYPE ACTION PROJECT EDITOR DOCUMENT EDITOR CO EDITOR CO EDITOR CO EDITOR CO EDITOR ISO IEC JTC1 SC7 WG6 Nxxx 30 Dec 09 ISO IEC FCD 25010 Systems and software engineering oystem and software product Quality Requirements and Evaluation
52. ooo 79 8 5 2 1 ooo 79 853 2 el Bd 01 Melo CSS 82 8 5 5 4 oo 84 8 5 6 5 er 86 8 5 7 6 io 88 8 6 EL EO EOC oo 90 87 EI o 1 7 E E 93 eod qe WX M E a 03 8 7 2 1 HITS MR EE 94 8 7 3 2 oo 97 8 7 4 3 EI EI oo 98 8 7 5 4 tre 101 8 7 6 5 FTR 103 8 7 7 6 neonneoneounsousoousouseoesoessoeseessoeseesseeseseeseesseeseesseeseesseessesseesseeseesseessesseesseeseesseeseesseessesseesseeseess 107 8 7 8 7 rr 109 8 79 8 EEC 1 110 3 X 0142 0000 ISO IEC 20926 2003 8 7 10 9 EI CO 2 111 87 11 EL FTR EU DET someone X0142 0000 EX c EU 8 7 12 EI OD HERE HB U
53. FSM 12 FSM 1 MEDE S FSM FSM 13 FSM FSM RUR RUR C D FSM
54. IFPUG 4 1 ISO IEC 20926 2003 Software engineering IFPUG 4 1 Unadjusted functional size measurement method Counting practices manual MOD MOD ISO IEC Guide 21 1 mcg 6 21 BE SE VERE SIEUT Fc Bal 38 Ze vo 22 3 T 100 0014 2 13 5 03 3592 1408 T 107 8440 4 1 24 03 3585 4558
55. TS TS TS X 0111 TS X 0111 2 2 JIS X 0129 1 TS X 0111 3 3 JIS X 0129 1 TS X 0111 4 4 JIS X 0129 1 3 TS TS X 0111 2 2009 ISO IEC TR 9126 2 2003 2 JIS X 0129 1 software engineering Product quality Part 2 External metrics 2003 1 ISO IEC TR 9126 2 2003
56. Information technology Process assessment Part 4 Guideline on use for process improvement and process capability determination 2004 1 ISO IEC 15504 4 1 JIS X 0160
57. g 1 AFL FAH 2 h COTS ISO IEC 25051 2006 Software engineering Software product Quality Requirements and Evaluation SQuaRE Requirements for quality of Commercial Off The Shelf COTS software product and instructions for testing IDT IDT ISO IEC Guide 21 1 des 8 TS X 0111 2 2009 ISO IEC TR 9126 2 2003 15 2 JIS X 0129 1 TS X 0111 2 20 ISO IEC 9126 2 2003 21 10 20 24 10 19
58. 145 899 7 EQ nennen 147 8 9 10 8 oo 149 8 9 11 EO FTR DET 151 8 9 12 EQ ooo 151 JA HER RE Sn 153 4 X 0142 0000 ISO IEC 20926 2003 tE 5
59. TS ld TS TS TS IEC TC6S ISO IEC JTC1 SC27 1 2 TS X 0111 2
60. 4 20 JIS X0135 1 1 21 JIS X 0135 3 3 TARBEBRUEKOO XE ROME FE JIS 22 IS X0142 TFPUG IFPUG4 1 ET IE 2 WG 21 WG1 SPE 2 1 1 ISO IEC 9126 Software engineering Product quality part1 7 4 IS X 0129 1 TS X 0111 2 3 4 XU ISO IEC 14598 Information technology Software product evaluation partl 6 JIS X 0133 PAYER EOF RAO 10
61. C JTCI SC7 JIS INSTAC JIS IS JIS BR JIS INSTAC FRO Hs JIS 0 JIS A MERR ELT JIS HA 1 2 3 4 5 6 7 8
62. 1 TS X 0111 2 2009 ISO IEC TR 9126 2 2003 our 1 EEEE i0000t 1 2 i i EEE EEE 2 3 io 2 4 re 3 S 3 6 ee 3 7 oo 5 8 FE SD FR REESE 5 Sd EBERELC BEES BS SE ee ee ee ee ee ee re E 5 RE CE Len Le AT De 060170007170000020 0767000070707 71771 14 8 3 AtB i RP eee 25 Sd MH HS sce MEE RE MEE EM EIE 41 8 5 oo 53 SC HMS S ae OOO OE E E EE 61 A ee 68 B 73 C eee 79 D 85 2 TS X 0111 2 2009 ISO IEC TR 9126 2 2003 3 TS
63. moe 28 8 5 4 moo 28 2 TS X 0111 3 2009 ISO IEC TR 9126 3 2003 Re nae MEN ee Se eB ates a E E N 28 GG 4 EAN a OO 34 8 61 9 e Ir Edd ESS FFB 22222222 4 LLL 34 8 62 EXE REL S BE SALE S iii anea r a a UIT UDIN DN CSI UNIS UM RSS 34 8 6 3 oo 34 86 4 E icd ET 2 ho LR d 34 ses he Ce ko RAR A 9000000700000 34 A 40 B oo 45 C ie 51 57 OMe EU Send P10 a eeeeeeeeeeeeeseeeseseeeeeseseeseseseseseesesseseeeseeeseeesessessesesssssssessssssseseseeseeesseeseseseseseseseeeeeeseeeee 59 3 TS X0111 3 2009 ISO IEC TR 9126 3 2003 3 TS
64. SPICE Automotive SPICE iNTACS International Assessor Certification Scheme RE IPA SEC RI GG C t Cle LL RSET VOM pH 2 2 2
65. ISOMEC 14598 2 2000 Software engineering Product evaluation Part 2 Planning and management IDT 17 4 JIS X 0129 1 TS X 0111 4 200 ISO IEC TR 9126 4 2004 21 10 20 24 10 19 TS X0111 4 2009 ISO IEC 9126 4 2004 Sy nn EEEE i0000t 1 2 i i EEE EEE 2 3 io 2 4 re 3 S 3 6 ee 3 7 oo 5 8 EEE eee EEE 5 8 0 rr 5 SL SR Fe ae ME Er on 7 8 2 eo 8 8 3 om 10 SA Lu a A GEN aT T A to 12 B 17 C lt eee 23 D 30 MESSE oe 32
66. a 1 COTS 2 JIS X 0151 3 4 SO IEC 17050 5 ISO IEC Guide 23 b SO IEC X 25051 2010 ISO IEC ISO IEC 25051 2006 Guide 28 c ISO IEC 17025 d e 1 2 COTS 3 D
67. FSM FSM C D RUR UR C D RUR FSM FSM 22 IFPUG IFPUG4 1 JIS X 0142 0000 ISO IEC 20926 2003 22 OO X 0142 0000 ISO IEC 20926 2003 By Nanaimo EEEE 1 EDAIN nnnn000n00000d000n00d000d0tt00d0000td0t0r0trt00 itso 1 3 IFPUG 4 1 ir 9 31 oo 9 R 10 4 12 EE LE pk od ELE SELL ere 13 4 2 ooo 13 4
68. X 0142 0000 ISO IEC 20926 2003 GE JIS X 01 42 0000 IFPUG IFPUG 4 1 Software engineering IFPUG 4 1 Unadjusted functional size measurement method Counting practices manual 2003 1 ISO IEC 20926 JIS JA 1 IFPUG 4 1
69. M ne 52 validatio em AL SR ne Rs en a aa aa 52 ValUe Le ee Ma 52 VOMIT CANON ee C tied 52 ISO IEC 2002 All rights reserved ISO IEC FCD 25040 2009 E EX 53 BIDlograp 54 VI ISO IEC 2002 All rights reserved ISO IEC FCD 25040 2009 E Foreword ISO the International Organization for Standardization and IEC the International Electrotechnical Commission form the specialized system for worldwide standardization National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity ISO and IEC technical committees collaborate in fields of mutual interest Other international organizations governmental and non governmental in liaison with ISO and IEC also take part in the work In the field of information technology ISO and IEC have established a joint technical committee ISO IEC JTC 1 International Standards are drafted in accordance with the rules given in the ISO IEC Directives Part 2 The main task of the joint technical committee is to prepare International Standards Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting Publication as an International Standard requires approval by at least 75 of the national bodies casting a vote Attenti
70. M G in nn es 47 Measure NOUN ne a 47 easure VerbD ee re En cca claret aie bui teet esto a te ete NN E ue ed et OS EE eM 47 Micron 47 Measurement TUMCTIOM scars cise RUN 47 measurement metlhod en 48 Measurement procedure a RR Nd Ge 48 Measurement DlOCESS sm 48 ODSeIVAUOME 48 Operator nre c ee ne een a a da ei Cl 48 DI OCCS S Meer 48 g allty imuse Measure mc 49 Quality measure elements ed 49 gquallly MOG Sl PRE ee A RE Re ee ER RES 49 atid een 49 Falinig level mn 49 FOQUIFEMOENLS om cie ne eds RRR 49 SCale RR 49 SOMWAFE PIOGUCU iier 50 software product evaluation sm 50 SOMWar CO quallty ea 50 software quality characlerisliC nn ete eit Rx en Ds ni 50 SOMWare UaIIEV GVIUAUO asasen 50 SOMWane guality mm UUSee 50 SOMWALS quality IS 51 stakeholdet eee E 51 ilelrlgeeec e LP M 51 SYSTEM et 51 target ol DIOCESS RRB 51 UNIL or measuremebb 225551 55552 3 50 605525 66v DE ERE caeso et esas aa PER CE ERE Ho aaraa Dee Ease asina Elo eo ie SEE sc ORO 51 PLE M
71. oo 48 7 6 10 ILF RET DET 52 2 7 6 11 ILF D4 a MU REESE 52 7 7 ELOS A 53 7 71 EIF a n E SOL E nvescscccccsccnccnccnccnccnccnccnccncencsncsncsnsencsncsncsncsncsncsnssnssncsnssscsnesnssnssncsncsnssnssncsnesnesncsnesnssnssnesnesnesnesee 53 7 7 2 1 eereererererererererererecererererceoeoeoeoeeeeeeeserererererercroeoeoeoeeecee 54 7 7 3 2 eo 5G 7 7 4 3 coressssssssssssscsesscnsssnsnsssessenssssssssssnsesesessssssssssssnsesessnssssssssssnsessssssssssessnsess 58 7 7 5 4 58 7 7 6 5 oo 61 7 7 7 6 62 7 7 8 7 ro 64 7 7 9 8 oo 66 7 7 10 EIF RET DET 67 7 7 11 EIF 67 8 2 7 APER 68 8 1 EI EO EO t E 68 82 EL EO EO ot 72 83 EL EO EO oo 76 84 EL EO EO ORB LOI E IRE 78 8 5 E ALTER 1102 2 TT 79 8 5 1
72. 3 JISX0129 1 2009 10 20 TSX 0111 4 ISO IEC TR 9126 4 JISX0129 1 2009 10 20 2 15 SQuaRE
73. 3 JIS X 0145 8 2010 ISO IEC 15504 3 2004 22 0 X 0145 3 2004 ISO IEC 15504 3 2004 A our D T 1 ME ue ee 1 PEE o RM ed ee Re ne te 2 S MERU E R EEE 2 4 iuc AU LA A FORE Mo 2 AT eui i e etta titia es bd tmt ittm id ibn tutes times su ec rf uM EE 2 40 TD A I 2 43 FOLA vir paola n TES 3 eNEASLIA lc ez V LU NE 3 dS NE pea a 3 4 AT FEAR TES KDE BEC eT RE NR eC ET niea A AS PASS DOI otio tbv EE eia loe at O and iro dd 4 AN FA ee KF FORDE X aue este edes vate ul pen Ro tabu E ea naa me eO 4 5 FERAS Se ie m IBOOSE BI onda 5 Si ee eo a E N 5 5 B3 aU Te O B fake escalates Rb os 9 SA FERAS FIJADO ER Me i A eT nn 10 SS 2 S bibat a 14 56 xEMESTI EyT AS D BZBOUAOJ DN eie etim eret ead eie ese ERO Pet edu asd 14 6 AE FR Be FI EO 42 E dede tin dm ion ta inda cites ion are 15 61 KEO Tr JACA cee EE EE 15 62 MEL MONTE Lane tons nn Renan aiment 16 63 KE RSR VE SEE Landerneau tiennent 17 6 4 KEF EN SN TOP Le a an bonne 20 65 4 ARK 22 6 6 KES amdEl CUV V EE Linda E dai eu be ta su E ele tuf esu eia 25 67 JACA TERT etn piden bees ve deest bled esee vacare elevated diste d eld nde 27 68 Min A ERE m mml T LL 1 EE 28 29 7 1 cAEDU BB ESLISOM ye She ar
74. JIS JIS X0142 IFPUG HPUG4 1 GREY ii 1 1 1 V
75. documentation incorporated into the user interface This International Standard is applicable to acquirers suppliers of user documentation including a variety of specialists e information designers and architects who plan the structure format and content requirements of documentation products in a documentation set ISO IEC 2009 All rights reserved ISO IEC CD 26512 e business analysts who identify the tasks that the intended users will perform with the software e experienced authors and editors who develop the written content for user documentation e graphic designers with expertise in electronic media e user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen The standard may also be consulted by those with other roles and interests in the documentation process e managers of the software development process or the documentation process e acquirers of documentation prepared by suppliers Usability testers documentation reviewers subject matter experts e developers of tools for creating on screen documentation e human factors experts who identify principles for making documentation more accessible and easily used This International Standard is intended for use in all types of organizations whether they have a dedicated documentation department or not This Standard may be used as a basis for local standards and procedures Headers are ass
76. 2 1 iip 2 BEE 2 2 3 E ee ye ae esac Em 1 LE et SR E 1 L2 eme sea eee eos ana 1 L FRSE ei aon EEE 1 l TERRA E 2 LS 6 ee eG ie sate 4 IEEE 4 NO Fall Dees S nent en ne i 5 2 Yo op Re eg A Noo ee sum EA Le o aL das du eee 5 5 21 2 SOuaRE 0 e n e eene 6 PA PS OE By My oes cence E tans at ae ee yacieieercetasnus ht caleusen ann asseweads 8 DLL nuc e A g PS SEO RE 9 MEC AP We CAP ID A d Mt a Lm 9 NAME i rm 9 Do STD RD oe vc ERI ee 10 DE Se ee NE SE 11 2 2 EE E EE EE EE 11 DOS TI Pl n 12 23 ceo eere re cotone eR RM UI D Idee 12 09 e nU 12 PEE rui lC 13 9 aN Ns P 13 DEP MEETS iR ier 14 Be eee E esac ade esta cst cence adit chic RP dd Ea 14 Miu ccce CU MI eee EUM DEM ee d ME ee E 15 1 ISO IEC FCD 25010 Software engineering Software product Quality Requirements and Evaluation SQuaRE Qu
77. 32 WG 2 WGI 11 WG2 9 WG3 10 1 6 RE 1 ISO IEC FCD 25010 Software engineering Software product Quality Requirements and Evaluation SQuaRE Quality model 2 ISO IEC CD 25021 Software engineering Software product Quality Requirements and Evaluation SQuaRE Quality measure elements 3 ISO IEC FCD 25040 Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation reference model and guide 4 ISO IEC FDIS 25045 Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation module for recoverability 5 ISO IEC DTR 25060 Software engineering Software product Quality Requirements and Evaluation SQuaRE General framework for usability related information 6 ISO IEC WD 15504 8 Information technology Process assessment Part 8 An exemplar assessment model for IT service management 7 ISO IEC WD 15504 9 Information techno
78. Information technology Software measurement Functional size measurement Part 1 Definition of concepts 2006 2 ISO IEC 14143 1 UT
79. TS TS TS X 0111 TSX0111 2 2 JISX0129 1 TS X 0111 3 3 JISX0129 1 TSX0111 4 4 JISX0129 1 4 TS TS X 0111 3 2009 ISO IEC TR 9126 3 2003 3 JIS X 0129 1 software engineering Product quality Part 3 Internal metrics 2003 1 ISO IEC TR 9126 3
80. PPA BT fEO SAM HEALTH CHECK ESPRITII BOOTSTRAP SDCAM TRILLIUM ISO 9000 The Malcolm Baldrige National Quality Award pesti eb TR IS uU ES M EA E E L
81. 4 ISO IEC FCD 25010 ISO IEC FCD 25040 ISO IEC CD 25045 ISO IEC FCD 25060 WD 1 ISO IEC WD 25021 4 ISO IEC 25022 ISO IEC 25023 ISO IEC 25024 ISO IEC 25041 3 F ISO IEC 25042 ISO IEC 25043 ISO IEC 25044 3 ISO IEC 25040 ISO IEC 25000 X ISO Free Availability eJIS JIS TS 1 JIS 1 JIS 3 TS JIS X 25000 ISO IEC 25000 SQuaRE SQuaRE 2010 2 22 JIS X 25051 ISO IEC 25051 SQuaRE COTS 2010 02 26 2010 1 JISC TSX 0111 2 ISO IEC TR 9126 2 2 JISX0129 1 2009 10 20 TS X 0111 3 ISO IEC TR 9126 3
82. 5 X 25051 2010 ISO IEC ISO IEC 25051 2006 COTS COTS JIS X 0152 1995 ISOMEC 25010 JIS X 0151 B 6 1 COTS COTS FAN ZEUS RR Le WHA
83. DOCUMENT EDITOR CO EDITOR ISO IEC JTC1 SC7 JWG1 N093 19 Jun 09 ISO IEC DTR 25060 Software engineering Software product Quality Requirements and Evaluation SQUARE Common Industry Format CIF for Usability General Framework for Usability related Information 19 Jun 09 JTC1 SC7JWG1 Project Version 3 Text for TR For comment Mary Theofanos maryt nist gov Thomas Geis Document type Technical Report Document subtype Document stage 20 Preparatory Document language E ISO IEC TC JTC1 SC SC7 N Date 2009 06 19 ISO ISO IEC JTC1 SC7 WG1 Secretariat SQ eral Framework for Usability relate Software engineering Software product Quality Requirements and Evaluation Common Industry Format CIF for Usability Ge Information uaRE ISO IEC PDTR 25060 Copyright notice This ISO document is a working draft or committee draft and is copyright protected by ISO While the reproduction of working drafts or committee drafts in any form for use by participants in the ISO standards development process is permitted without prior permission from ISO neither this document nor any extract from it may be reproduced stored or transmitted in any form for any other purpose without prior written permission from ISO Requests for permission to reproduce this document for the purpose of selling it should be addressed as shown below or to ISO s member bo
84. re 3 S 3 6 ee 3 7 oo 5 8 FE SD FR REESE 5 Ee ee eae Pcp ee ee ee ee ee ee re ere ey eyes 5 SLI SOMMES ZH EE Re ne nine eR 6 S12 JETEUEL BH 3 2 Raisin sass A A EE E 6 A EE REC Ez Ld rd i LAIT eee 6 8 14 6 8 1 5 PARE HE EE netti Bg FU creme 6 E ei Le bee D 7777 720270777 20277 2770077777717 77 720777020700077 70710 700000777770 70707077 27070 207070 0700 12 SDL CR ES ok gen SE SE ee E S E EE E 12 825 BESEREOSIE BH 2 SP Eines nn ne FERRUM CHORO ONU ERE OE s 12 8 2 3 mo 12 8 2 4 Es 12 8 3 oo 17 3 LEE de Ge a a E E 17 832 Se BN ANSE Annee tent tnt 17 8 3 3 mo 17 8 3 DE EL MP tee a A EE A E T 17 43 5 ae Fee ape E S REL CR d ON REGE nn Re 17 Sd S a WE Ss HE n BI SER UNION RN NUI M NN UI M 24 GAL FRIC ER A EE LS 24 X PEE LEVE A ae D ELLE 24 8 4 3 eeeeeeeeececerererererererererererereeeeoeeeoeeeeeeesereeerererererororoeoeoeeeeeeeeererererererereeoeeeoeceoee 24 8 5 oo 28 8 5 1 mo 28 S52 ARRES A e E a 28 8 5 3
85. This International Standard IS was developed to assist users of ISO IEC 15288 2008 ISO IEC 12207 2008 or ISO IEC 20000 2005 Parts 1 and 2 to manage information items as products of the system or software life cycle processes In many cases ISO IEC 12207 2008 may state that the result of a process must be documented or may imply the need for a document or information item ISO IEC 12207 2008 clauses often do not specify the contents of documents The information items identified in ISO IEC 15289 aid in planning producing and evaluating the results of the life cycle processes Information items are essential to preserving what transpired when using system life cycle processes and may be identified as deliverable documents This International Standard may be used as a conformance or a guidance document for projects and organizations claiming conformance to ISO IEC 15288 2008 and or ISO IEC 12207 2008 and or ISO IEC 20000 1 2005 The nomenclature in this International Standard for information items document titles and contents is informative viii ISO IEC 2009 All rights reserved COMMITTEE DRAFT ISO IEC CD 15289 2 Software and systems engineering Content of life cycle information products documentation 1 Scope This International Standard IS assumes an organization is implementing life cycle processes in conformance with ISO IEC 15288 2008 or ISO IEC 12207 2008 or practicing Service Management in conformance with ISO IEC
86. 9 10 1 12 13 14 15 16 17 18 19 20 21 22 ISO IEC FCD 25010 Software engineering Software product Quality Requirements and Evaluation SQuaRE Quality model ISO IEC CD 25021 Software engineering Software product Quality Requirements and Evaluation SQuaRE Quality measure elements ISO IEC FCD 25040 Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation reference model and guide ISO IEC FDIS 25045 Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation module for recoverability ISO IEC DTR 25060 Software engineering Software product Quality Requirements and Evaluation SQuaRE General framework for usability related information ISO IEC WD 15504 8 Information technology Process assessment Part 8 An exemplar assessment model for IT service management ISO IEC WD 15504 9 Information technology Process assessment Part 9 Target Process Profiles ISO IEC 15504 10 Information technology Process assessment Part 10 Safety extension ISO IEC CD 15289 Systems and software engineering Content of life cycle information products Documentation ISO IEC CD 26511 Software and systems engineering User documentatio
87. Part 8 An exemplar assessment model for IT service management 1 Scope This informative part of ISO IEC 15504 defines an exemplar Process Assessment Model that meets the requirements of ISO IEC 15504 2 and that supports the performance of an assessment by providing indicators for guidance on the interpretation of the process purposes and outcomes as defined in ISO IEC 20000 4 and the process attributes as defined in ISO IEC 15504 2 provides guidance by example on the definition selection and use of assessment indicators A process assessment model comprises a set of indicators of process performance and process capability The indicators are used as a basis for collecting the objective evidence that enables an assessor to assign ratings The set of indicators included in this part of ISO IEC 15504 is not intended to be an all inclusive set nor is it intended to be applicable in its entirety Subsets that are appropriate to the context and scope of the assessment should be selected and possibly augmented with additional indicators see Annex C The Process Assessment Model in this part of ISO IEC 15504 is directed at assessment sponsors and competent assessors who wish to select a model and associated documented process method for assessment for either capability determination or process improvement Additionally it may be of use to developers of assessment models in the construction of their own model by providing examples of
88. Product quality Part 3 Internal metrics IDT DTD ISO IEC Guide 21 2 TS JIS X 0129 1 3 TS TS 9 JIS X 0020 1992 ISO IEC 2382 20 1990 Information technology Vocabulary Part 20 System development MOD JIS X 0129 1 2003 1 ISO IEC 9126 1 2001 Software engineering Product quality Part 1 Quality model IDT JIS X 0133 1 1999 7 7 RU ST Rn Oo gl 95 1 ISO IEC 14598 1 1998 Information technology Software product evaluation Part 1 General overview IDT JIS X 0133 2 2001 2
89. Product quality Part4 Quality in use metrics DT DT ISO IEC Guide 21 TS JIS X 0129 1 TS TS JIS X 0020 1992 ISO IEC 2382 20 1990 Information technology Vocabulary Part 20 System development MOD JIS X 0129 1 2003 1 ISO IEC 9126 1 2001 Software engineering Product quality Part 1 Quality model IDT 19
90. SQuaRE System and software quality models 30 Dec 09 JTC1 SC7 WG6 Project Version 1 81 FCD For comment Prof Motoei AZUMA Department of Industrial and Management Systems Eng Waseda University 3 4 1 Okubo Shinjuku ku Tokyo 169 8555 Japan az mo mitd biglobe ne jp Nigel BEVAN nigel nigelbevan com Vipula Godamunne David Zubrow Yukio Tanitsu Markku Tukiainen Reference number of working document ISO JTC 1 SC 7 N Date 30 Dec 09 Reference number of document ISO IEC FCD 25010 Committee identification ISO JTC 1 SC 7 WG 6 Secretariat SC7 Systems and software engineering System and software product Quality Requirements and Evaluation SQuaRE System and software quality models Document type International standard Document subtype Document stage Document language E Content 1 GO 9 2 GONO MANGE ne nn I Tm 10 3 TermsandidelnmonS set 10 OMEN nto ee E ge EE P rA 10 2 10 ee 10 cr GIFOCT U i i TL es dd ic eee ETAT 10 3 5 external measure of software quality ss 10 3 6 internal measure of software quality ss 11 wpDeonrnaee Be teh atte ma ea da nd de lee min 11 39 Uri SI 11 3 9 software intensive computer system pp 11 310 sollwaregualy ee 11 Salle StAKCNOIGOR siuieeiieiwiwavheltvent cbs TN 11 DA UOO pe ee a RE SA RL et dame ee 11 4 Quality model framework ioi eee ie Dec eoe edo Linie Roco nee tte 12 dy Qualy models ERES TU UU TM 12 42 Qualy dm dse modele eei een uit etes t
91. 6 52 EEEa a eu EE H ie WA be lp dw ales cic Bets a fs o DE 13 MET m Ce A eek ves a r sondenstsondanstsonseeacsoeess 16 6 1 FE BA Zo BE KK BBB E 16 A ie A I M Rn T 6 3 ee se ee 19 VERTU TIS SZ BEGET AEMMMMMMMMMMERIREENMEEEEEEEEBHBPIIIE ERRMMM JE Locas MO DO a LLL LLL D 22 7 1 oneeeeeeeenneoouauoouuuoouussooassoosssoossseossseoosseoosssoosssesossseosssesesssssssssssssesssssesessssessssessssssssssessssessssessssssssesesseseeeseeeee 22 go oe ceo ee en eee 22 23 mg ES NEST LE SE 22 7 4 ee 23 Q5 RS SE cc DD D DM E EE IE A MM 23 7 6 ed Se E O E UE P E 24 A SE RBS Ay BC Dott A 26 B COTS BA E E OE A 7 29 C JIS X 25051 ee es 34 ee Te A A A A E A A 35 2 X 25051 2010 ISO IEC ISO IEC 25051 2006
92. 9 FRE COM OS M ERR TOR TIT OD E T T 36 9 1 Generabe ee TTE DE UD IUSTI 36 9 2 Specific Tecord Contellls xen sro iE deduc deut eh anne are ra ER ane Seres een Ies can OPE uvae Abr E ER Ca Spas 36 10 Specific information item document contents ee 40 10 1 Acceptance plah sss desee sedeebves vanae Even seas pex Evan Pac ev Errare tone vases tee i 40 10 2 Acceptance review and testing report ee 41 10 89 Acquisition DIG icio PE Rap ete A cue chis aU bcc dense P EU Dre vernis 41 10 4 Asset management plan RE 41 10 5 Audit acknowledgement report e leeeeeieeeeeeeeeeeeeeee esee nennen nnn nnn nnn nnn nnn nnn n nnn nnn 42 10 6 Adit DIG iei aie rca ra Diei aa TE erar rca FER Fra coa co cea SE Fu E Eu raga DEL ERE Fx ter E dou co os Feu Peg aa DU EUR dc uas 42 10 7 Audit DIOCeGUe uisi cde cv apes e Exe seen cec en EE CuY ea EE EX F ua Ev REY RE Le Rn EXE EE 42 10 0 JAHdI TODOEL ee 42 10 9 Capacity AUC a en 43 10 10 Change treguesi eam 43 10 11 Coriceptolt oOperalloOlS sa 43 10 12 Configuration management plan 44 10 13 Configuration management procedures eee ee nennen nnn nnne nnn nnn nnn nnne nnn 44 ISO IEC 2009 All rights reserved iii ISO IEC CD 15289 2 Configuration Status report sm 45 COoHlf actibus id nd M ID ME IM ME EMI Ce 45 Customer satisfaction survey et 45 Database design descriptlon e sic ne ee esse nat ee ner 46 pevelopiment lr TN TOTO eo a 46 DISDosal am 47 Documentauon planoren EIE 47 Domain engineering plan
93. further called Divisions The Divisions within SQuaRE model are ISO IEC 2500n Quality Management Division The standards that form this division define all common models terms and definitions referred further by all other standards from SQuaRE series Referring paths guidance through SQuaRE documents and high level practical suggestions in applying proper standards to specific application cases offer help to all types of users The division provides also requirements and guidance for a supporting function which is responsible for the management of software product requirements specification and evaluation ISO IEC 2501n Quality Model Division The standard that forms this division present detailed quality models for software quality in use and data Practical guidance on the use of the quality model is also provided ISO IEC 2502n Quality Measurement Division The standards that form this division include a software product quality measurement reference model mathematical definitions of quality measures and practical guidance for their application Presented measures apply to internal software quality external software quality and quality in use Measurement primitives forming foundations for the latter measures are defined and presented ISO IEC 2503n Quality Requirements Division The standard that forms this division helps specifying quality requirements These quality requirements can be used in the process of quality require
94. in liaison with ISO and IEC also take part in the work In the field of information technology ISO and IEC have established a joint technical committee ISO IEC JTC 1 International Standards are drafted in accordance with the rules given in the ISO IEC Directives Part 2 The main task of the joint technical committee is to prepare International Standards Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting Publication as an International Standard requires approval by at least 75 of the national bodies casting a vote Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights ISO and IEC shall not be held responsible for identifying any or all such patent rights ISO IEC 25045 was prepared by Joint Technical Committee ISO IEC JTC 1 Information technology Subcommittee SC 7 Software and systems engineering ISO IEC 25045 is one of the SQuaRE series of International Standards which consists of the following divisions under the general title Software product Quality Requirements and Evaluation SQuaRE e Quality Management Division ISO IEC 2500n e Quality Model Division ISO IEC 2501n e Quality Measurement Division ISO IEC 2502n e Quality Requirements Division ISO IEC 2503n e Quality Evaluation Division ISO IEC 2504n ISO IEC 2009 All rights reserved V ISO IEC FDIS 25045 2009 E Introduct
95. process attributes and process attribute rating to create a target process profile for a process in the specified categories for domain of application of the business requirement for the community of use i the expression of results i e a target process profile for each required process with data and notes that allow traceability and interpretation for assessment and improvement guidance purposes VI ISO IEC 2008 All rights reserved WORKING DRAFT ISO IEC PDTR 15504 9 2 Information Technology Process Assessment Part 9 Target Process Profiles 1 Scope This part of the International Standard documents guidelines for target process profiles for Capability Determination and Improvement purposes This Technical Report provides guidance for target process profiles for the following purposes by or on behalf of an organization with the objective of specifying a target process profile based upon specified needs by or on behalf of an organization with the objective of specifying a target process profile against which to assess the actual capability of the organization to meet that target by or on behalf of an organization with the objective of specifying a target process profile against which to assess the actual capability of another organization to meet that target by or on behalf of an organization with the objective of determining the need for improvement based upon any capability gap between the actua
96. 10 H CR 6 2009 10 15 H CR 7 2009 11 05 A 8 2010 01 14 CR 9 2010 02 18 A 2 2 4 ISO IEC 15504 6 ISO IEC 15504 7 2008 IS JIS IS X 0145 3 3 2010 02 20 11 OJS X 0145 4 4 2010 02 26 2010 1 JISC 2 2 5 5 ISO IEC 15504 S CMM
97. 20000 1 and 1 2005 ISO IEC 12207 2008 and ISO IEC 15288 2008 define a set of processes for managing and performing the stages of a systems life cycle They define an Information Management process but they do not detail documentation in terms of name format explicit content and recording media ISO IEC IEEE 15288 2008 clause 1 4 ISO IEC 12207 2008 establishes a common framework for software life cycle processes and in passing identifies or requires a number of documentation items The Process Reference Model does not represent a particular process implementation approach nor does it prescribe a system software life cycle model methodology or technique ISO 20000 1 2005 establishes general requirements for documents and records 3 2 The purpose of this International Standard is to guide users of ISO IEC 12207 2008 ISO IEC 15288 2008 and ISO IEC 20000 1 and 1 2005 in identifying and planning the specific information items to be produced during systems and software life cycles This International Standard specifies the purpose and content of all identified Systems and Software Life Cycle information items The information item contents are defined according to generic document types as presented in Clause 7 and the specific purpose of the document Clause 10 The generic document types which may be referred to as information item types are to be used to identify the information necessary to support the ISO IEC 15288 2008 agreement en
98. Define decision criteria for quality meaSUureS ee ieeee eene enne nennen nn nnn nnn nanus nhan nns 22 6 43 Establish decision criteria for evaluation eiie ut den ess ie Ce creux Ce eno ga ce cu Puno Sauna cn as YE VENE D gens 23 6 5 Design the CV AI AOI RR 23 6 51 PlanmevaluationactiVilieS svectenswenseietiwcs M 23 6 6 Execute IMG CV PI cure em 24 6 6 1 Make measuremieblS a a 25 6 6 2 Apply decision criteria for measures umn 25 6 6 3 Apply decision criteria for evaluation ee 25 6 7 Concl de the evaluation sd 26 671 REVIEW hneevalualion resul arisi E EE 26 6 22 Create the evaluation report ocena GT TE RE 26 6 7 3 Perform disposition of evaluation data nn 28 Annex A Informative Evaluation evVelS me 29 A 1 Selection Of VAIUATION evelS sen 29 A 2 Selecting evaluation techniques from evaluation levels es 31 Annex B informative Evaluation methods 1 oot ooie ecco suse E CIE wo cia sae cop Sv cHP eese ous states sente cuo HE wuo eus 33 ISO IEC 2002 All rights reserved ISO IEC FCD 25040 2009 E B 1 Review of user and technical product documentation including on line JOCUMENTATION SEE I ERE 33 B 2 Evaluation based on supplier courses and training ee 33 B 3 Assessment of software engineering process nnn 33 B 4 Review of operating history wit
99. E CSR 11 3 Normative referehneeS ee 11 4 Srms and detinitio nsdn SRE SaaS 12 4 1 OV Al IO hod NG alee ulate SRE PR EOE Na AA 12 4 2 eValualocovwerage we 12 4 3 evaluat on TeVe enu e RS EOE PCS 12 4 4 valuation recor S ww 12 4 5 SVAN ATION Tedqueslef sn a E E a E Ea 12 4 6 evala On TOO a SAR EE a 12 4 7 SV AIM ATION SUMOENOV am a aR aT 13 4 8 madependentievalualo to sssi aE a E EE E a aaa EE Saa a EE aai 13 4 9 Cn Lacer seine 13 5 Software Product Quality Evaluation Reference Model e ereeeeeee ee 13 5 1 RGIGTeGG INOGGI general sen nn A nee none annee scout 13 5 2 Referencemoguelevaluationibrocesses ee 15 5 3 ppl me n 17 5 4 Quality iie llle CY ele a ane EAE 17 5 5 SUPPONMLTON ING VAUS OMi ee t 18 6 Software product quality evaluation proOCeSS 18 6 1 Generalrequmement mam a 18 6 2 DOCUMENTATION se PR a a EGA GN 18 6 3 Establish the evaluation requirements ena 19 6 3 1 Establish the purpose of the evaluation Lunas 19 6 3 2 Obtain the software product quality requirements rr 20 6 3 3 Identify product parts to be included in the evaluation ss 20 6 3 4 Define the stringency of the evaluation e lees eeeee ee eeee ense nennen enne n nnnm nn nnn nhan nhan nnns 21 6 4 Spbecifvthe evaluatio Pase ct ma 21 6 4 1 Select quality measures evaluation modules nanan 22 6 4 2
100. Generic praclices 181 C 2 Adaptation of the exemplar Process Assessment Model 182 C 2 1 Adding to or removing processes from the process dimension 182 C 2 2 Identifying process performance indicators for a new prOCESS 183 Bibliography to be revised ee 184 IV ISO IEC 2009 All rights reserved N A Foreword ISO the International Organization for Standardization is a worldwide federation of national standards bodies ISO member bodies The work of preparing International Standards is normally carried out through ISO technical committees Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee International organizations governmental and non governmental in liaison with ISO also take part in the work ISO collaborates closely with the International Electrotechnical Commission IEC on all matters of electrotechnical standardization International Standards are drafted in accordance with the rules given in the ISO IEC Directives Part 2 The main task of technical committees is to prepare International Standards Draft International Standards adopted by the technical committees are circulated to the member bodies for voting Publication as an International Standard requires approval by at least 75 of th
101. IEC the International Electrotechnical Commission form the specialized system for worldwide standardization National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity ISO and IEC technical committees collaborate in fields of mutual interest Other international organizations governmental and non governmental in liaison with ISO and IEC also take part in the work In the field of information technology ISO and IEC have established a joint technical committee ISO IEC JTC 1 International Standards are drafted in accordance with the rules given in the ISO IEC Directives Part 2 The main task of the joint technical committee is to prepare International Standards Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting Publication as an International Standard requires approval by at least 75 of the national bodies casting a vote In exceptional circumstances the joint technical committee may propose the publication of a Technical Report of one of the following types type 1 when the required support cannot be obtained for the publication of an International Standard despite repeated efforts type 2 when the subject is still under technical development or where for any other reason there is the future bu
102. Pha eet o tone ae ate A 12 43 Product iet H M P 13 4 4 Relationships between the quality models pp 14 AS WSING a HAN Model MERE uU UT 14 4 6 Quality from different stakeholder perspectives pp 15 4 7 Relationship between the models pp 16 5 Quality in use characteristics nn dns NS ne cht tel ren tte 17 S I elis lc ECOUTER 18 GO 18 CGI 18 59 1 purpose accompliSPitie lt NN 18 DOLE BRU SU e RR NE EE 18 9 as 18 SOR MEME Ce Med oer pe mere ee o TTE ELT 18 D4 ec M 19 541 66OOImGLOdaIAGGISE KO 19 od 6alNIaNOISSIeIWVS KK 19 Bade ENvronmMmen arhan TS ee ve RN 19 5 5 Context comprehensiveness sise 19 5 54 GOIeXKGOIODIGIGIO6SS EKK KK 19 SRM eem 19 ISO IEC FCD 25010 6 Product quality cliaracterisli6S sm 20 Gl unellonalSultablli Vy me nd a 20 20 6 12 PUNCUONAl COMCCINESS me 21 O L 9 Tunctional 3DDIopITalerieSS SR MU I SEE 21 62 EGG GO 21 2 21 0 2 2 TESOUNCS BllSdllOD ziv e rented n et ED i ent 21 603 0 1 9 2 1410 gr ed ae eee ee eee 21 DS ICO CS NCCC re whee erent teat eames aud di antec de ee ae asd tant esate ie de 21 0 92 NeroDperaDlity nnn a de a a 21 GUSADI PR a 22 6 4 1 appropriateness recognisabillly LO REO 22 O42 earnaDility ee ne a a A a eaa 22 GAS Operabililyc MS dc toon dd verdad i ame ee RE 22 04 4 MS6EeIIONDNOIGGUO KK 22 645 Userinlera
103. SQuaRE series of International Standards is to assist those developing and acquiring software products with the specification and evaluation of quality requirements It establishes criteria for the specification of software product quality requirements their measurement and evaluation It includes a two part quality model for aligning customer definitions of quality with attributes of the development process In addition the series provides recommended measures of software product quality attributes that can be used by developers acquirers and evaluators SQuaRE provides e terms and definitions e reference models e a general guide e individual division guides and e International Standards for requirements specification planning and management measurement and evaluation purposes SQuaRE includes International Standards on quality model and measures as well as on quality requirements and evaluation SQuaRE replaces the current ISO IEC 9126 series and the ISO IEC 14598 series ISO IEC 25040 Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation reference model and guide will replace the following e apart of ISO IEC 14598 1 Information technology Software product evaluation Part 1 General overview e ISO IEC 14598 3 Software engineering Product evaluation Part 3 Process for developers e ISO IEC 14598 4 Software engineering Product evaluation Part 4 P
104. SR I D Ip DD I p MU SUD DIM DIM M CO PED CME S CDL DIO 14 6 2 6 Information architect 0 PECE Hms 14 O 2 7 Usability AdeSIQNEr a A 14 6 2 8 Graphic desidneF EE 14 6 2 9 Informati n designet sa neces ainia AD Eaa E esse Carinina rain aa Rai 14 6 2 10 Technical Writek na 15 6 2 11 Instructional designer sm 15 6212 LUE ESS 5 Le MEET TIDETUR IT 15 62 13 EGC SRE anc TTC CREE E 16 6 2 14 Quality Speclallst sm 16 6215 INGOX Gl em RC 16 O210 Tesora IIR 16 6 2 17 Localization coordinator 0 16 6218 Translalol se a caseceaactcaceenceancnenenseaceane 16 6 219 PIDISIB sa cure ouaeesoasconasnecezcere 17 6 220 Print GOOrGINalON ss enc secs ne sit e 17 7 Project management TECHNIQUES mm oana aandae aiana ania raia asar anarei raaa 17 7 1 Types f analy SIS PER RS PR RE PE AR 17 7 2 Performing the work breakdown structure oo 17 7 2 1 Progress analysis sn I 17 7 2 2 Work breakdown structure 0 18 7 2 3 Whole Ol project variante em 19 Ts2 4 alite R 19 26511 8 MeasUremente sm 19 8 1 RecCOtdS ER EP 19 8 2 The measurement and recording prOCeESS nn 20 8 2 1 Selection criteria for measurements 2 20 90 2 2 Measurement techniqdues i 21 98 2 3 Product measurements a 21 8 2 4 Process measurements 0 21 Annex A informative Sample documentation plan see 23 A 1 Contents 23 A 2 INFOQU
105. Standard Recipients of this document are invited to submit with their comments notification of any relevant patent rights of which they are aware and to provide supporting documentation Copyright notice This ISO document is a working draft or committee draft and is copyright protected by ISO While the reproduction of working drafts or committee drafts in any form for use by participants in the ISO standards development process is permitted without prior permission from ISO neither this document nor any extract from it may be reproduced stored or transmitted in any form for any other purpose without prior written permission from ISO Requests for permission to reproduce this document for the purpose of selling it should be addressed as shown below or to ISO s member body in the country of the requester Indicate the full address telephone number fax number telex number and electronic mail address as appropriate of the Copyright Manger of the ISO member body responsible for the secretariat of the TC or SC within the framework of which the working document has been prepared Reproduction for sales purposes may be subject to royalty payments or a licensing agreement Violators may be prosecuted li ISO IEC 2002 All rights reserved ISO IEC FCD 25040 2009 E Contents Page FO OW ORG sec E vii PT POGUGU OM et i Viii 1 SCOPE seas T 11 2 ConDtFormallee me
106. a particular context of use This system model is applicable to both computer systems in use and software products in use The characteristics of both models apply to all software products and software intensive computer systems The characteristics and subcharacteristics provide consistent terminology for specifying measuring and evaluating system and software product quality They also provide a set of quality characteristics against which stated quality requirements can be compared for completeness ISO IEC 25012 contains a model for data quality that is complementary to this model The scope of the models excludes purely functional properties see C 5 but it does include functional Suitability see 6 1 The scope of application of the quality models includes supporting specification and evaluation of software and software intensive computer systems from different perspectives by those associated with their acquisition requirements development use evaluation support maintenance quality assurance and audit The models can for example be used by developers acquirers quality assurance staff and independent evaluators particularly those responsible for specifying and evaluating software product quality Activities during product development that can benefit from the use of the quality models include e identifying software and system requirements e validating the comprehensiveness of a requirements definition e identifying softw
107. a joint technical committee ISO IEC JTC 1 International Standards are drafted in accordance with the rules given in the ISO IEC Directives Part 2 The main task of the joint technical committee is to prepare International Standards Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting Publication as an International Standard requires approval by at least 75 of the national bodies casting a vote In exceptional circumstances the joint technical committee may propose the publication of a TR of one of the following types type 1 when the required support cannot be obtained for the publication of an International Standard despite repeated efforts type 2 when the subject is still under technical development or where for any other reason there is the future but not immediate possibility of an agreement on an International Standard type 3 when the joint technical committee has collected data of a different kind from that which is normally published as an International Standard state of the art for example Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights ISO and IEC shall not be held responsible for identifying any or all such patent rights ISO IEC TR 25021 which is a Technical Report of type 2 was prepared by Joint Technical Committee ISO IEC JTC 1 Information technology Subcom
108. and DefinitionS 0 imi eot oiu este soc c cra OPER S Ce cuve c v cce EL OVE Een voca Cose CUP PE RD TUE P ICE ONE OE CLIE aise 1 4 OV lg e scsen din s cet cest essuie en S M S 2 4 1 INTEOGUGCTION See TEES EN I 2 4 2 Target process profiles SDONS OM si 2 4 3 Target process DOINGS eet 2 4 4 Deploying a documented prOCess si 3 5 Target process brofiles sm eo 4 5 1 erp me te eR ne eee ee eae eee ae 4 5 2 Defining a Target process profile nn 4 5 2 1 Definingitiie durposSe a 4 5 2 2 Selectihecommunily OF US 4 5 2 3 Define the business requirement ee 5 5 2 4 Define the domain of application mn 5 5 2 5 Define categorles 5 5 2 6 Define target process profile factors ss 6 5 2 7 Define criteria for data and information collection ee 7 5 2 8 Select PIOCESSES sm EN 7 5 2 9 Define target process profile OUTDUL Esiaaninss 8 5 2 10 Define target capability 25 5 0 6 5 25 sen RG a 9 6 Process for creating selecting and using Target Process Profiles 9 6 1 OVO RVICW se 9 6 2 Create the target process profiles 5 10 6 3 Using target process brofilesS So sen aa E Ea EA 11 631 UserG GuldancGe 11 5 9 2 Applicauon or gap analysis i 11 7 Quallticatloh of DEES OMS iui iei cs 13 8 leere mI te 13 ISO IEC 2008 All rights reserved iii ISO IEC PDTR 15504 9 2 Foreword ISO the International Organization for Standardization and
109. and accounting policies and procedures cost reports or payroll data e Information items showing only approval of an ISO IEC 12207 2008 subclause such as ISO IEC 12207 2008 6 1 2 3 4 5 e Any ISO IEC 15288 2008 or ISO IEC 12207 2008 subclause not explicitly or implicitly identifying the recording of information about an activity or task for example ISO IEC 12207 2008 6 4 4 NOTE ISO IEC 26514 2008 Systems and software engineering Requirements for designers and developers of user documentation provides guidance on formats for software user documentation 2 Applicability This International Standard is applicable for use by 2 ISO IEC 2009 All rights reserved ISO IEC JTC1 SC7 0 Software and Systems Engineering INFORMATION TECHNOLOGY STANDARDS Secretariat CANADA SCC Document Type Title Source Project Status References Action ID Due Date Start Date Distribution Medium No of Pages Note ISO IEC JTCI SC7 N4257 2009 02 19 Combined WD circulation CD registration ballot and CD ballot Combined WD circulation CD registration ballot and CD ballot WD 26511 Software and systems engineering User documentation requirements for managers W G2 26511 WD Resolution 1039 ACT 2009 05 21 2009 02 21 SC7 AG PDF 42 Please vote using the ISO Electronic Balloting Facilities Resolution 937 Address reply to ISO IEC JTC1 SC7 Secretariat Ecole de technologie
110. identifying information items and their contents 72 Annex B Informative Bibliography ee 73 ISO IEC 2009 All rights reserved ISO IEC CD 15289 2 List of Tables Table 1 Mapping of ISO IEC 15288 2008 Clauses to Information Items for Each System Life Cycle Process ee 18 Table 2 Mapping of ISO IEC 12207 2008 Clauses to Information Items for Each Software Life Cycle mise MU 24 Table 3 Mapping of ISO IEC 20000 1 2005 and ISO IEC 20000 2 2005 Clauses to Information Items for Each Service Management Proces 8 enn e a 33 Table 4 Record References and Contents sees nemen nme memem een remeerecaisesese esae serere anas 37 VI ISO IEC 2009 All rights reserved ISO IEC CD 15289 2 Foreword ISO the International Organization for Standardization and IEC the International Electrotechnical Commission form the specialized system for worldwide standardization National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity ISO and IEC technical committees collaborate in fields of mutual interest Other international organizations governmental and non governmental in liaison with ISO and IEC also take part in the work In the field of information technology ISO and IEC have established a joint technical committee ISO IEC JTC
111. of SQuaRE series of standards 25020 Measurement reference model and quide 25022 25023 25024 Measurement of Measurement af Measurement of quality internal quality external quality In use 25021 Quality measure elements Figure 2 Structure of the Quality Measurement Division 9126 4 Qualitv in use 23021 Quality Measures FT x elements OME 9176 3 Intemal measures a M 9176 2 External measures m fa ig x i 120 1 Quality mode l i i ra SQuaRE Quality Measures a Quality characteristics La Quality sub characteristics P d i F Quality measure 1 Quality measure 2 T Quality measure 3 xt momommmmmmmsmmmm Quality measures Quality measure n l f 2502n uA bu n Figure 3 The relationship of 25021 as a link between the 9126 series and the SQuaRE series of standards ISO IEC 9126 series is compose of 4 documents list and describe characteristics sub characteristics and quality measures that refer as the quality model The SQuaRE quality models categorise product quality into characteristics which are further subdivided into subcharacteristics and quality attributes ISO IEC 25010 For each quality measure within ISO IEC 9126 series there are at least two 2 quality measures elements QMEs The attributes of a product are linked to the quality measure elements ISO IEC 25020 using a measurement method The 2502n series design and describe
112. quality characteristics and subcharacteristics are given in clause 5 and clause 6 NOTE The essential definitions from ISO IEC 25000 are reproduced in Annex D 3 1 asset anything that has value to a person or organization NOTE 1 based on ISO IEC 13335 1 2004 NOTE2 In this International Standard assets are work products such as requirements documents source code modules measurement definitions etc 3 2 benchmark standard against which results can be measured or assessed ISO IEC 24765 3 3 component entity with discrete structure such as an assembly or software module within a system considered at a particular level of analysis ISO IEC 15026 1998 3 4 direct user person who interacts with the product NOTE 1 This includes primary and secondary users NOTE 2 This is the ISO 9241 1 1definition of user 3 9 external measure of software quality measure of the degree to which a software product enables the behaviour of a system to satisfy stated and implied needs when the system including the software is used under specified conditions NOTE 1 Attributes of the behaviour can be verified and or validated by executing the software product during testing and operation 10 2 ISO IEC JTC1 SC7 WG6 Date January 2010 ISO IEC 25021 TITLE Software Engineering Software product Quality Requirements and Evaluation SQuaRE Quality measure elements DATE January 2010 SOURCE JTC1 SC7 WG6
113. requirements objectives and constraints 9 5 1 General mee a a a 9 5 2 Documentation evaluation activities 0 10 5 3 Selection of an evaluation method sm aeuo sata aeu tea x pue Cu e erra ce eo ey eee anani eese 10 5 4 DOCUMENTATION TeVIGW mm cn eot aliu dua eoa a Na 10 5 5 DOCUMENTATION OSU oe eue 11 5 6 Project requirements affecting documentation evaluation sise 11 5 7 Resource requirements and planning ei eeee eee eeee eese nenne enean nnne nnne n nana nana 12 5 7 1 Impact of evaluation on project schedules e 1lceeeeee eie eeeee eee eeee eene nnne n nnn nnn 13 6 Documentation evaluation methods and procedUreS 1 ceeeeeeeee eere esee rennen 13 6 1 Documentation TeVIGW Eee uesenesne 14 6 1 1 Planning documentallon feVIBWE ceo sene ce eno Crpadu a cek Sacre ce osa n Ene nunne noi genen Mme enr en ss sm aaia 14 6 1 2 Documentation review procedures EK 16 6 1 3 Managing the results of documentation review rr 17 6 1 4 Problem resolution and the documentation review cycle eee ceeeeeeeeess 17 6 2 System test of documentations ana ennemies sua eeu tao su Ea eu te rende dia 17 6 2 1 Planning system test of documentation 1 1lleeee eei eeeee eei ieeeee enne nennen nhan nnn nnns 18 6 2 2 Performing and asses
114. rights ISO IEC 26511 was prepared by Technical Committee ISO IEC TC JTC 1 Information Technology Subcommittee SC 7 Software and Systems Engineering 26511 Introduction Anyone who uses application software needs accurate information about how the software will help the user accomplish a task The documentation can be the first tangible item that the user sees and so influences the user s first impressions of the product If the information is supplied in a convenient form and is easy to find and understand the users can quickly become proficient at using the product Hence well designed documentation not only assists the user and helps to reduce the cost of training and support but also enhances the reputation of the product its producer and its suppliers Although many software designers aim to have user interfaces that behave so intuitively that very little separate documentation is needed this is rarely possible User documentation is an essential component of usable software products Documentation is often regarded as something done after the software has been implemented However for quality software documentation its development should be regarded as an integral part of the software life cycle process If done properly documentation or information management is a big enough job to require process planning in its own right Effective management of the user documentation task is essential in order to ensure that documentatio
115. table of information e An initial set of QMEs In Annex Annex A Justification of the selection of the initial QMEs Annex B Procedure for the measurement function to be completed Annex C Cross reference table representing the Life cycle phases and the use of QMEs Annex D Cross reference tables for quality measures Annex E Measurement scale type Annex F Bibliography This document is intended for but not limited to developers acquirers and independent evaluators of software product particularly those responsible for defining software product quality requirements and for software product evaluation Document Type Title Source Project Status References Action ID Due Date Start Date Distribution Medium No of Pages Note ISO IEC JTC1 SC7 By 3 Software and Systems Engineering INFORMATION TECHNOLOGY STANDARDS Secretariat CANADA SCC ISO IEC JTC1 SC7 N4536 2010 01 20 FCD Ballot FCD 25040 2 Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation reference model and guide WG7 25040 N4346 N4434 N4435 ACT 2010 05 20 2010 01 20 SC7 AG PDF 55 Please vote using the ISO Electronic Balloting Facilities Resolution 937 Address reply to ISO IEC JTC1 SC7 Secretariat Ecole de technologie sup rieure Departement of Software and IT Engineering 1100 Notre Dame Ouest Montr al Qu bec Canada H3C 1K3 secretariat jtcl
116. the ISO member body responsible for the secretariat of the TC or SC within the framework of which the working document has been prepared Reproduction for sales purposes may be subject to royalty payments or a licensing agreement Violators may be prosecuted 26511 Contents Page FOLOWOT O tM E erm V nOdUCHO NERONE TRITT TTE RUE INIM E vi 1 S6ODB recede d eU en ED cud Mic tUe Ll eC HD ici later dro de 1 2 COnIOrniali e Bier eco tice E EE E E EA E E DA I C MC LL LLL DE REIR III SEI 2 2 1 Definition of conformance nn es 2 2 2 Contormarce situatio nS a c Dose ta vede A UE Tee ee R ta COMI eats 2 3 Normative references 0 3 4 DENION SN a a E 3 5 PIOCOSS NN NN a 5 5 1 Defining and documenting processes ee 5 m Audiencedetiton em Leer 7 5 1 2 ControLot documentation plan si 7 5 2 Personnels 7 5 3 zeige M 10 5 4 Responsibililles so M cet 10 5 5 COSLestmal6S uon led MED DM ca eu dace nr SE E 11 5 6 SC CCS aise Het UTER Ne 12 5 7 Implementng th proeess mm 12 6 Roles in the user documentation process eeeecieeee sisse nennen enn n n nnn nennen nnn n nnns 12 6 1 Roles shall b GETING 12 6 2 zb cls xgllcseee e RR Ra 13 572 Ole 13 6 2 2 USePOdOCUIeGIIONT6SE KEKKK EE 13 623 Non team FOIS iiie tare ice i i tetes ER e tac 1 13 6 24 Manager eee 13 62 5 OOA di SE CD Sn DD IE
117. which comprise the Agreement vii ISO IEC 2009 All rights reserved ISO IEC CD 26512 processes and of the Information Management and Documentation Management Processes Documentation This International Standard may be used as a conformance or a guidance document for documentation products projects and organizations claiming conformance to ISO IEC 15288 2008 Systems engineering System life cycle processes or to ISO IEC 12207 2008 viii ISO IEC 2009 All rights reserved FINAL COMMITTEE DRAFT ISO IEC CD 26512 Software and systems engineering Requirements for acquirers and suppliers of user documentation 1 Scope This clause presents the scope purpose organization and candidate uses of this International Standard This International Standard supports the interest of software users in having consistent complete accurate and usable documentation It addresses both available approaches to standardization a process standards which specify the way that documentation products are to be acquired and supplied and b documentation product standards which specify the characteristics and functional requirements of the documentation Clause 5 of this International Standard provides an overview of the software user documentation and information management processes which may require acquisition and supply of software user documentation products and services Clause 6 applies the Agreement processes acquisition an
118. 0 Tel 41 22 749 01 11 Fax 41 22 749 09 47 E mail copyright iso org Web www iso org Reproduction may be subject to royalty payments or a licensing agreement Violators may be prosecuted i ISO IEC 2009 All rights reserved ISO IEC FDIS 25045 2009 E In accordance with the provisions of Council Resolution 21 1986 this document is circulated in the English language only ISO IEC 2009 All rights reserved iii ISO IEC FDIS 25045 2009 E Contents Page PIO LOW OF gc ES ne tac recat AS den nn A Gen EA Nc AS V INEOGUGEIO KEKSaReaasiegidaiagiaiklieggae Vi 1 sme M P 1 1 1 ChArACI TIS CS rm a at 1 1 2 Level ON valuation ee Te a E E n 1 1 3 LechniqUuG ea a 1 1 4 Applicability edm D qe Sn 2 2 CONREIOFMaAaNCe i RR 2 3 NormativetelereneceS is ei Sd 2 4 Terms and delinillons had a nn nu ne 3 5 inputs ANG Measure S mm 3 5 1 Evaluation Methodology si 3 5 1 1 Practical considerations relating to the methodology 5 5 1 20 DISTUFDANCeS ERE DE ms 5 5 2 input TOF THE CV AU ALO MN a 8 521 TNE SUT GOSCH eem 8 2 22 TNE WOrklOad describ lo ha me ne a 9 5 23 AheTault load descripliOl i aaa N iaaea EN 10 5 3 Dalaelemenlo eee 11 5 4 1 Qutput from the baselliie PUN aa 11 539 2 OutDpubtrom Ihe Te SE TD 11 5 3 3 Completion of the Autonomic Maturity Questionnaire nn 12 5 4 Quality Measure S nn D dues due eso pp ein date duelli cau cua e
119. 00 ISO IEC 2002 All rights reserved ISO IEC FCD 25040 2009 E Introduction As the use of information technology grows the number of critical computer systems also grows Such systems include for example security critical life critical economically critical and safety critical systems The quality of software in these systems is particularly important because software faults maylead to serious consequences Evaluation is the systematic determination of the extent to which an entity meets its specified criteria The evaluation of software product quality is vital to both the acquisition and development of software The relative importance of the various characteristics of software quality depends on the intended usage or objectives of the system of which the software is a part software products need to be evaluated to decide whether relevant quality characteristics meet the requirements of the system This document is part of SQuaRE series of standards and contains general requirements for software product quality evaluation as well as clarifies the associated general concepts Specific issues related to the developers acquirers and independent evaluation are provided in annexes The general goal of creating the SQuaRE set of standards is to move to a logically organised enriched and unified series covering two main processes software quality requirements specification and software quality evaluation supported by a software quali
120. 08 All rights reserved ISO IEC PDTR 15504 9 2 Part 7 Assessment of organizational maturity Part 8 An exemplar assessment model for service management processes Part 9 Target process profiles This Part of ISO IEC 15504 is informative ISO IEC 2008 All rights reserved V ISO IEC PDTR 15504 9 2 Introduction ISO IEC 15504 provides a framework for process assessment and sets out the minimum requirements for performing an assessment in order to ensure consistency and repeatability of assessment ratings Process assessment is applicable in the following circumstances by or on behalf of an organization with the objective of understanding the state of its own processes for process improvement by or on behalf of an organization with the objective of determining the capability of another organization s processes for a particular contract or class of contracts or to determine the capability of its own processes for a particular requirement or class of requirements Process assessment has two dimensions a process dimension and a capability dimension ISO IEC 15504 2 specifies the measurement framework within the capability dimension The process dimension is provided by an external process reference model which describes a set of processes each characterized by defined process purpose and process outcomes ISO IEC 15504 4 2004 describes the need for a target capability using the capability dimension i
121. 1 International Standards are drafted in accordance with the rules given in the ISO IEC Directives Part 2 The main task of the joint technical committee is to prepare International Standards Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting Publication as an International Standard requires approval by at least 75 of the national bodies casting a vote Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights ISO and IEC shall not be held responsible for identifying any or all such patent rights ISO IEC 15289 was prepared by Joint Technical Committee ISO IEC JTC 1 Information technology Subcommittee SC 7 Software and systems engineering This International Standard is based on ISO IEC 12207 2008 ISO IEC 15288 2008 ISO IEC 20000 1 2005 and ISO IEC 20000 2 2005 The IEEE Computer Society participated as a liaison organization in the joint development of this International Standard IEEE contributed IEEE 12207 1 1997 Industry Implementation of International Standard ISO IEC 12207 1995 ISO IEC 12207 Standard for Information Technology Software life cycle processes Life cycle data as a source for this standard This second edition of ISO IEC 15289 cancels and replaces the first edition 2006 which has been technically revised ISO IEC 2009 All rights reserved Vii ISO IEC CD 15289 2 Introduction
122. 10 ITSM MAN 9 1 Documentation management for ITSM eeee e eeeeeeee enne 28 5 1 11 ITSM MAN 9 2 Control of documents for ITSM ee ceeeeeeeee eee eeLeeeee eene nena n nanus 31 5 1 12 ITSM MAN 9 3 Control of records forITSM eee Leeeeee rennen enne n anna anne nra 32 5 2 Planning and implementing new or changed services process group PLA 35 02 1 AMDIFOQOUCHOD S3 5 niii uei cue qute eme aaa orbes exu AE aaa EN 35 5 2 2 ITSM PLA 1 Planning and implementing new or changed services 35 5 3 Service delivery processes SDE me 37 Tr eii gore t elio p Pee 37 5 3 2 ITSM SDE 1 Service level management eee e Lieeeeeece ei ieee nennen nena anna anas nana ananas 37 539 JIISMESDE Z SErviGe TODOFIHQ ee ss Dk a evv aia uuti ka uic ue wa Gus ES 38 5 3 4 ITSM SDE 3 1 Service continuity management eee eri eeeeeeee rene e nennen nnne nnmnnn nnna 39 5 3 5 ITSM SDE 3 2 Service availability management ee eeeeeeeeee eec Lc eeeeee enne nnn n nnns 41 5 3 6 ITSM SDE 4 1 Budgeting for IT services leeeeee e eeieeee eee ieeeee enne nennen enhn nana nnns 43 5 3 7 ITSM SDE 4 2 Accounting for IT services process eeee ee eeeeee essen eene nnne n nn nnns 44 5 3 8 ITSM SDE 5 Capacity management for ITSM uaa 45 5 3 9 ITSM SDE 6 Inf
123. 13 SQuaRE SQuaRE JIS X 25000 2010 ISO IEC 25000 2005 1 X 25000 2010 ISO IEC 25000 2005 cu A EEE EEE i000 00 3 2 i i c EEOEE EEE EEE 3 3 FH pp EE 3 4 3 5 SQuaRE eo 11 5 1 SQuaRE oo 11 5 2 SOuaRE eo 12 5 3 SQuaRE i3 A SOuaRE eo 18 B BA JIS X 0133 JIS X 0129 ee 22 C JIS X 0129 JIS X 0133 SQuaRE FRE 7 HE ERU CS IE 36 D BA SQUARE ooo 39 TL Bea TEE CE 41 2 X 25000 2010 ISO IEC 25000 2005
124. 19 clause s subclause s table s figure s annex es of which has have been technically revised vi ISO IEC 2009 All rights reserved ISO IEC CD 26512 Introduction This International Standard was developed to assist users of ISO IEC 15288 2008 Systems engineering System life cycle processes or ISO IEC 12207 2008 Information technology Software life cycle processes to acquire or supply software user documentation as part of the software life cycle processes It defines the documentation process from the acquirer s standpoint and the supplier s standpoint Anyone who uses application software needs accurate information about how the software will help the user accomplish a task The documentation may be the first tangible item that the user sees and so influences the user s first impressions of the software product If the information is supplied in a convenient form and is easy to find and understand the user can quickly become proficient at using the product Hence well designed documentation not only assists the user and helps to reduce the cost of training and support but also enhances the reputation of the product its producer and its suppliers Although software developers aim to design user interfaces that behave so intuitively that very little separate documentation is needed this is rarely possible Today s software offers increasingly robust functionality not only within applications but also a
125. 2009 ISO IEC TR 9126 2 2003 TS Rit Y Y7
126. 3 15 16 s 17 51 DH VT VA DA A VY KB BA SHIAB Fill D FE Be T 17 Sy D D E E E A E E A E 17 6 18 GA NU E SO p ERO RR nn dde esae denas i 18 62 ZH HBIEBBEIRUTYZU 4 L3a3vIEKg amp I BE DRR VE 20 63 FBR ROT FY TH 3 VLBA AREA d 41 50 WX nennen nennen 21 As s D a YD 3 O F 21 TL ILE EU EIF OEM N E GS 22 7 2 ILF EIE 23 7 3 ILF EIE 25 7 4 REE 26 7 5 ILF EIE eo 27 7 6 ILE 30 Tei ICE HAS VIAE 30 7 6 2 ERNEUT D ANNO ILE oeeerecerccercceccerccecceccceccecececcccccccoccocecccecoecocecoccccccoececcesoeccocceccccecccesoceseececeseeeo 30 7163 Bal OD S S LLL 34 7 6 4 3 io 40 D EA Ae ee ee LEE CE 40 266 SAS Sh Et oe Mena chandeliers 42 7 67 6 44 TeS EI T MERI SEA Som TRIER CREDIDI GRAMINA IRR NNI OI Iis 44 2 X 0142 0000 ISO IEC 20926 2003 7 6 9 8
127. 37 40 5 47 0 OPperatOores se da 56 0 62 99 Memory el Zo 67 BAO Data ltlenm 71 OL BEHOPCOBGOI ITOD o oe dera doe epe RA pu Pp Eu ET 75 01 2 System far eS erp 80 6 13 SoftWare aunes a rid Ea 84 6 15 Requirements tanli sn a bita esr Mim a cM ieu pas 93 Annex A Justification of the selection of the initial QME Lees esee creen e eene eren eee nuee 95 Annexe B Procedure for the measurement function informative 100 Annex C Cross reference table representing the Life cycle phases and the use of OMES 102 Annex D Tables forquality measures eot o o EE 104 Annex E Informative Measurement scale type sense 107 Annex EF BIDHO tabD ly SNE ES 109 Foreword ISO the International Organisation for Standardization and IEC the International Electrotechnical Commission form the specialized system for worldwide standardization National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organisation to deal with particular fields of technical activity ISO and IEC technical committees collaborate in fields of mutual interest Other international organisations governmental and non governmental in liaison with ISO and IEC also take part in the work In the field of information technology ISO and IEC have established
128. 4 JIS X 0129 1 Software engineering Product quality Part4 Quality in use metrics 2004 1 ISO IEC 9126 4 TS TS SER NER A a o TS KO 2 2 2 MAD Fa a hia TS X 0111 4 2008 gt en prune KAWE 1 TS JIS X 0129 1 CUT JIS X 0129 1 TS a b cj CLA ie TS
129. 4 6 23 Contract agreement ici perii tbe a MINI cease EDS E IM ML I URINE DEI 14 6 2 4 Contract management and monitoring Laan 14 6 2 5 ACQUIT FACC DIANCE a 15 6 2 6 AcqulisilioniclosUre c 15 6 3 User documentation supply process ua 15 6 3 1 P rposSeof the SUDDIV DIOC OSS EE 15 6 3 2 Qutcomes OL ING SUDDIY DIOCBSS oiii cota si a Ce eo eu Rc a E Aaa Sn nn ns 15 6 4 User documentation supply activities and tasks ee 15 6 4 4 Opportunity identification and evaluation ee 16 56 4 2 Proposal preparallOD sm 16 6 4 3 Contract agreement ocior ete eru cr ata o Ue Gain Eas aea sacs ces ds Une s Oa Ba cessus a casi S nes De ue Ca ooa a uS 16 6 4 4 Contract execullOnm ea a 16 6 4 5 Product service delivery and support uaa 18 6 46 CP oT ea a 18 7 Defining user documentation requirements and constraints eese 18 7 1 Scnedule constramto me cct 19 7 2 Usability FEGUIFGINGIAUS em 20 7 3 Product modification reqUifemiet EE 20 7 4 Localization and translation requirements e eese LLeeeee ee eeeee nenne enne n nnnm nnn nn nn 20 7 5 Legarreduremente sm a oue 21 7 6 Security REQUIF MENTS Es 21 7 7 Standards ang CONVEMUONS EE 21 7 8 Quality management requirements EE 22 8 User Documentation SHECITI CATON mn 22 9 User documentation Statement of Work ee eeieeee eei eeeeeeeieee enne n nennen nhan nnn hann 23 10 REQUEST for Proposal ect E 24 10 1 Project r ODI
130. 4 Software measurement Functional size measurement Part 4 Reference model 2004 1 ISO IEC TR 14143 5 Software measurement Functional size measurement Part 5 Determination of funtional domains for use with functional size measurement 5 JA 1 ISO IEC TR 14143 3 2003 Software measurement Functional size measurement Part 3 Verification of functional size measurement methods MOD ISO IEC TR 14143 4 2002 Software measurement Functional size measurement Part 4 Reference model MOD ISO IEC TR 14143 5 2004 Software measurement Functional size measurement Part 5 Determination of functional domains for use with functional size measurement MOD MOD ISO IEC Guide 21 11 FUR
131. 621 ITUR Z3 ie Ge RRO re ees o eo re pon ana a ee a 9 6 2 2 FSM oo 9 ME ui TN 9 9 72 200200040000000020000002000000900002000000eddpeaentoss 12 721 al LK Be FO Hike ae NILUS LUIS LL 12 TD De CT ale Pe LYM pacte 12 71 3 Ae EA JI O E coe 12 7 RI 12 732 ESM FEO EI Sere meee eee ER 12 7 5 9 Fal OAL Be 7 TS TES a 0 TE hy Sei ES EE 13 ET DER PLAIRE T DIM 13 7 3 5 I SIEG RT Ee ee 0600 0 080 Mio EE 13 DA in T LT 13 725 al ON 14 a EEE EEE 14 s1 SAAB Een RE sn RR A in 14 SL RE RE woe 14 MEUM e E de ne nt 15 82 SN 16 SL S ST ds nes ee ds kk ns de 16 S22 SR FSM Fl assesses EE es 16 Hae A CRE ARERR ESOS ttm 17 X 0135 3 2010 ISO IEC 14143 3 4 5 2003 B 20 C Ras 23 D Is ey RUR ec ee ne re rc lo 32 JA JIS 36 3 4 X 0135 3 2010 ISO IEC 14143 3 4 5 2003
132. CIION 2 E E Do LS Sd Nr nee 23 A 3 ela sr 24 A 4 SOIUL ON ERE TN TR 24 A 5 Yigg 25 BIbliodrabhV 36 26511 Foreword ISO the International Organization for Standardization is a worldwide federation of national standards bodies ISO member bodies The work of preparing International Standards is normally carried out through ISO technical committees Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee International organizations governmental and non governmental in liaison with ISO also take part in the work ISO collaborates closely with the International Electrotechnical Commission IEC on all matters of electrotechnical standardization International Standards are drafted in accordance with the rules given in the ISO IEC Directives Part 2 The main task of technical committees is to prepare International Standards Draft International Standards adopted by the technical committees are circulated to the member bodies for voting Publication as an International Standard requires approval by at least 75 of the member bodies casting a vote Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights ISO shall not be held responsible for identifying any or all such patent
133. F oe 37 2 TS X0111 4 2009 ISO IEC 9126 4 2004 3 TS TS TS TS X 0111 TS X 0111 2 2 JISX0129 1 TSX 0111 3 3 JISX0129 1 TS X 0111 4 4 JISX0129 1 3 5 TS X0111 4 2009 ISO IEC 9126 4 2004 SABE TS TS X 0111 4 2009 ISO IEC 9126 4 2004
134. ISO IEC PDTR 25060 Software engineering Software product Quality Requirements and Evaluation SQuaRE Common Industry Format CIF for Usability General Framework for Usability related Information 1 Scope This technical report describes a potential family of standards named the Common Industry Formats CIF that document the specification and evaluation of the usability of interactive systems The purpose of this document is to provide a general overview of the CIF Framework and contents definitions and the relationship of the framework elements The intended users of the framework are identified as well as the situations in which the framework may be applied The assumptions and constraints of the framework are also enumerated The framework content includes Consistent terminology and classification of specification evaluation and reporting A definition of the type and scope of formats and the high level structure to be used for documenting required information and the results of evaluation The framework is applicable to software and hardware products used for predefined tasks The information items are intended to be used as part of system level documentation resulting from development processes such as those in ISO 9241 210 previously ISO 13407 and ISO IEC JTC1 SC7 process standards The CIF framework focuses on documenting those elements needed for design and development of usable systems rather than prescr
135. N By 114 SS OO Eh 115 39 a E e E 10070000010900077 177070000700 0101700 1500770007 1071007070771007107717 71777000770 777 115 882 oo iis 8 8 3 1 2 116 8 8 4 2 1 118 8 8 5 3 O DP e a a A r Ay e Sses6ceiesrisisaiisiiritisiiiiiiisisiieiaiiii 120 8 8 6 4 122 A E ERE SIRE RP UU m 123 8 88 6 EO MMMHeSrneMMMe 125 8 8 9 7 00 2 1 224 4 5454 5 127 8 8 10 8 EO 129 8 8 11 EO FTR DET 131 8 8 12 EO eee 131 8 9 EO oo 132 891 ceo 35 8 9 2 an E SOI E 133 8 93 1 133 8 9 4 2 C eo 135 89 5 3 138 8 9 6 4 ED 1 oo 140 8 9 7 5 C JPN 143 8 9 8 6
136. O IEC 12207 2008 processes b Specify information in an agreement process as described in ISO IEC 15288 2008 or a two party situation as described in ISO IEC 12207 2008 The two party situation may range from an informal agreement within an organization or to a legally binding contract between organizations c Develop information items that provide evidence for process assessment performed with respect to ISO IEC 15504 Process Assessment and to guide process improvement activities d Guide a single party in self imposed tasks Not included in the scope of this International Standard are the following e The format or content of recommended input data or input information items except for the content of those input items that are also output information items e Instructions on combining or subdividing information items and information item contents of a similar nature e Guidance on selecting an appropriate presentation format delivery media and maintenance technology for system and software life cycle data records information items or documentation such as electronic publishing systems content management systems or data repositories e Detailed content for information items related to general business organizational and financial management that is not specific to systems and software engineering and service management such as business strategies human resources and investment policies personnel selection criteria budgeting
137. On ee eee as E vill 1 OO 1 2 ADIDIIGGDIIUVW cH RR NM 2 3 ConformalitG s EE co uode ER 3 3 1 D tinition of Conformance sm 3 3 2 Conformance SituatloneS se 4 3 3 TYp of Conformance oe 4 4 Normative feferences uoo oe ee Ri 4 5 Terms and delnitlols 5 oes degere va Debet e HE NN ecu costal eocanvewssueakee 5 6 Life cycle data and information items nn 7 6 1 Life cycle data characteristics ee 7 6 2 Records compared to other information items documents pp 8 6 3 Management of life cycle data records ee 8 6 4 Management of information items documents 4 8 6 4 1 Developing the documentation plan ee 9 6 4 2 Managing and controlling information items ee 9 7 Generic information types and information items es 9 T 1 Genera e 9 7 2 Record generc content ee 10 7 3 Description generic content nennen nnmnnn nnn nnn nn 10 7 4 Plan generic content 11 7 5 Procedure eINGFIG GOE6OEEEEKEK EE 13 7 6 Report generic content 14 7 7 request generic content nn ER 15 7 8 Specification generic content ee 16 8 Mapping of information items to the life cycle prOoCe SSeS 16 8 1 Mapping of information items to the system life cycle es 17 8 2 Mapping of information items to the software life cycle ps 22 8 3 Mapping of information items to the service management processes 32
138. QMEs and quality measures for the quality model 1 Scope This document provides a procedure to apply the measurement method as recommend in ISO IEC 15939 The measurement method generates from an attribute of a product a Quality Measure Element QME The document also provides a set of QMEs already designed and a list of QMEs that should be defined in the future Finally an informative annex B suggest a procedure for applying the measurement function to obtain quality measures The intent is to assist users of the ISO IEC 9126 series ISO IEC TR 9126 2 ISO IEC TR 9126 3 ISO IEC TR 9126 4 and users of SQuaRE series of quality measurement standards ISO IEC 25020 ISO IEC 25022 ISO IEC 25023 and ISO IEC 25024 This informative annex will be helpful when selecting and using different quality measures to evaluate the quality of the software product within the software product life cycle Every quality measure for internal quality measure external quality measure and quality in use measure described in the SQuaRE series of standards is from measures that are selected from a set of quality measure elements in the ISO IEC TR 9126 series Annex A This document contains e Conformance and normative references e Terms and definitions necessary for this document e Symbols and abbreviation terms e Quality measure elements concepts in SPQM RM Process different steps to design a Quality Measure Elements QME and the measurement method
139. RE Quality model FCD e ISO IEC 25012 Software engineering Software product Quality Requirements and Evaluation SQuaRE Data quality model IS 2008 12 3 2502n 5 e ISO IEC 25020 Software engineering Software product Quality Requirements and Evaluation SQuaRE Measurement reference model and guide IS 2007 5 ISO IEC TR 25021 Software engineering Software product Quality Requirements and Evaluation SQuaRE Quality Measure Elements TR 2007 10 revision ISO IEC 25021 Software engineering Software product Quality Requirements and Evaluation SQuaRE Quality measure elements CD e ISO IEC 25022 Software engineering Software product Quality Requirements and Evaluation SQuaRE Measurement of internal quality ISO IEC 25021 e ISO IEC 25023 Software engineering Software product Quality Requirements and Evalua
140. S uosis a 75 6 4 1 PA 4 1 Process measurement attribute nn 75 61 2 PAX2Process control attribute iioii ua aue code u en Uo desc sene ces nens ane s nues ER 77 6 5 evel Dc ODUMIZINO DOCS ee ee 79 6 5 1 PAS PFOCESS INNOVATION allriDUl6 ae 79 6 5 2 PA 5 2 Process optimization attribute 0 81 6 6 Related Processes for Process AttributeS 83 Annex A informative Conformity of the exemplar Process Assessment Model 85 A 1 MOU e o Piece 85 A 2 Requirements for Process Assessment Models from ISO IEC 15504 2 85 A TE UC UO teresa D DEL o oo 85 A 2 2 Process Assessment Model scoOpPE ee Leeee eei eeee eee e eee nennen enean nnn n nhan anna nnn nnns 85 A 2 3 Process Assessment Model elements and indicators 86 A 2 4 Mapping Process Assessment Models to Process Reference Models 86 A 2 5 Expression of assessment resultS 89 Annex B informative Work product characteristics ee 90 B 1 Generi Work products 0m 91 Generic Work Products Contributed by Tom McBride ee 93 B 2 Generic and specific work products Specific Work Products Contributed by Tom McBride ee 169 Annex C informative Adaptation of the assessment model c eceeeeeeee ess 180 C 1 Assessment indicators identification 0 180 SE Base ACU COS ER I a ae de i 180 C12
141. SCUVES Sn TETUER 24 10 2 Requirements for supporting prOCeSSeES 24 10 3 Supplier capabilities and experience ec cessere eee Lesser nennen nnne nennen nnn nnns 24 iV ISO IEC 2009 All rights reserved ISO IEC CD 26512 10 4 Instructions Toribidders 2 nt nn ne ae a m 24 10 5 List of deliverable user documentation products or services ee 25 106 Tennisand Conditons A E EA aE EU a AENA EEEa 25 10 7 Proposalievalualion criterlas re 26 11 DOCUMENTATION Proposal em a nnt 26 11 1 Documentation proposal contents EEE 26 11 2 Understanding of requirementS nn 26 THES SCOPE OLINE roel a a a E A E eE 27 DE PHOCCSSOS mom 27 11 5 Experience capabilities and available resources 1eecceee eee eeeee ee eeee enne nnn 27 11 60 Schedule em M 28 11 7 DeliVerables ee 28 MiG Price proposal ee a these tale dessinent a RE trees 28 Fig 1 The Information Management ProOCeSS nn 10 Annex A Informative Requirements clauses and checklist for acquirers 29 Annex B informative Requirements clauses and checklist for suppliers 33 Annex C informative BibliographyV es dk e esu aa Ecc nn De sy ue save cs cuoc xe oe rates een E Cun s 36 V ISO IEC 2009 All rights reserved ISO IEC CD 26512 Forew
142. SO IEC FCD 26512 Software and systems engineering Requirements for acquirers and suppliers of user documentation ISO IEC 26513 Systems and software engineering Requirements for testers and reviewers of user documentation JIS X 25000 SQuaRE SQuaRE JIS X 25051 SQuaRE COTS JIS TS X 0111 2 2 JISX0129 1 TS X 0111 3 3 JISX0129 1 TSX0111 4 4 JISX0129 1 TE JIS X 0145 3 3 JIS JIS X 0145 4 4 JIS X 0135 1 1 JIS X0135 3 3
143. SO and IEC shall not be held responsible for identifying any or all such patent rights ISO IEC 26513 was prepared by Joint Technical Committee ISO IEC JTC 1 nformation technology Subcommittee SC 7 Software and systems engineering IV ISO IEC 2009 All rights reserved ISO IEC 26513 2009 E Introduction Anyone who uses application software needs accurate information about how the software will help the users accomplish a task The documentation might be the first tangible item that the users see and so influences the first impressions the users have of the product If the information is supplied in a convenient form and is easy to find and understand the users can quickly become proficient at using the product Therefore well designed documentation not only assists the users and helps to reduce the cost of training and support but also enhances the reputation of the product its producer and its suppliers This International Standard addresses the evaluation and testing of user documentation It applies to both initial development and subsequent releases of the software and user documentation This International Standard is independent of the software tools that might be used to produce documentation and applies to both printed documentation and on screen documentation Much of its guidance is applicable to user documentation for systems including hardware as well as to software user documentation This International Standard con
144. WORK ITEM Project STATUS Version 2 2 DOCUMENT TYPE WD Revision of TR 25021 PROJECT EDITOR Dr Jean Marc Desharnais Canada CO EDITORS Dr Keum Suk Lee Korea Dr Jiri Vanicek Czech Republic Mr Atsushi Yamada Japan Contents Page Table des mati res ME DU c HM 8 2 On e RR m 9 3 Normative POLO Te CES aiio GEI oe cesses PEE DUE DERE ERR EHE en REIR REESE ee EP OP S EGRE ERE 9 4 Terms and detrittobiSuieseenseceeieniseereserset res edu cd ecussactyesasnticeudeaesoesssbsvssecesseeseicsi di ee NN danse sde 10 KNEE CREE RTT e 10 212 WSS meds e nou osuere b catismscsuwedonecarenscesenansane Nod ETA UIDI AS VEG CE AN NAR EPIS DRP de 10 CMM emvwedineaonre TERT m 11 dn 11 AS Extermal SOLEW ale gual te scenuedessadsesanddicess 11 AG Tadica CONTRE mm 11 A7 VPA 4 1 0 EU 11 25 Interiial SOtiwWare Quality a EN a iis 11 Ne T E A E E ci 12 LIO OIE ena EE E A TO 12 411 Derved MEASUNE dns de UU EE nie eo 12 2 IVICA odo cei ruso ec mt a nana D NII 12 4 13 Measure noun see 12 TII Measure verb dense ee nena Ne vit vua Din vas ele toc ti das Eos eS edi e nb deniers es 12 BUD DE LOL DNS A CO oraga ce i A i 12 4 16 Measurement functioOn esee sens cata 229 Fo EORR VA Cs Qao donnes XE vU SA CE VIN Su OI URN CLE U EATEN FARE RYE VD Ris 12 4 17 Measurement method 0 13 4 18 Measurement procedure look the difference and pu
145. a 48 UE 48 implementat on Proc dure S se 48 Improvement pla a EE L UE 48 Information management plan ee 49 INTORMAUON SECUFILY la 49 nstallatonm loan ea EM 50 LE 50 Integration and teStrF DOr nine ns Rs EE EE 50 Integration Ia 51 nterface deseriptlon se ee DO TIE 51 Jomttreview mmmules a Cauca laut oe Sig 51 Lie Cycle procedures ese a RN 51 Maintenance bah a 52 Maintenance Drocedures Se a 52 Measurement plan RBS 52 Migration DIAM ea ER RR EE 53 Monitoring and control report smi 53 Operational test procedures nn 53 Problem management procedUure eise sies esee nennen nnne nnn nnn nnn nnne nnn nnn nnn 54 Problem TeDOL t RS 54 Process assessment procedUre inar ve via era Pax Ru rau Ci Reo rra ba Ew xke SER EORR ERR ES E s GER SK ERA E ERE KNEE REESE FLA EEE E EE 55 Process improvement analysis report ee 55 Product need assessment nn 55 Progress FG eleg c SRR EE 56 Project management plan ee 56 PODOS ee oe T 57 Qualification test procedure ee 57 Qualification test report ivo mex nero inr eal once oec oon s a ado DEB re 58 Quality management plan oen rta ce RI ede ioo totom v t ox neo A eed Lb SL 58 Quality management DFOCeQdUfe me a a 58 Redquest tor proposal REP ii daa a na 59 Resource Tequest nm M P DRE 59 ERS UES Ola 60 Risk acion redues RS TEE tmm 60 Risk management Ol Aries sec anes EI d 60 Service availability and continuity plan ee 60 Ser
146. ality Evaluation Division es ISO IEC 25050 25099 SQUARE Extension Division ISO IEC FCD 25010 Introduction Software products and software intensive computer systems are increasingly used to perform a wide variety of business and personal functions Realization of goals and objectives for personal satisfaction business success and or human safety relies on high quality software and systems High quality software products and software intensive computer systems are essential to provide value and avoid potential negative consequences for the stakeholders Software products and software intensive computer systems have many stakeholders including those who develop acquire use or who are customers of businesses using software intensive computer systems Comprehensive specification and evaluation of the quality of software and software intensive computer systems is a key factor in ensuring value to stakeholders This can be achieved by defining the necessary and desired quality characteristics associated with the stakeholders goals and objectives for the system This includes quality characteristics related to the software system and data as well as the impact the system has on its stakeholders It is important that the quality characteristics are specified measured and evaluated whenever possible using validated or widely accepted measures and measurement methods The quality models in this International Standard can be used to identify rel
147. ality model 2 ISO IEC CD 25021 Software engineering Software product Quality Requirements and Evaluation SQuaRE Quality measure elements ISO IEC FCD 25040 Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation reference model and guide 4 ISO IEC FDIS 25045 Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation module for recoverability ISO IEC DTR 25060 Software engineering Software product Quality Requirements and Evaluation 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 SQuaRE General framework for usability related information ISO IEC WD 15504 8 Information technology Process assessment Part 8 Capability target profile ISO IEC WD 15504 9 Information technology Process assessment Part 9 Target Process Profiles ISO IEC 15504 10 Information technology Process assessment Part 10 ISO IEC CD 15289 Systems and software engineering Content of life cycle information products Documentation ISO IEC CD 26511 Software and systems engineering User documentation requirements for managers I
148. and internal measure of software quality as well as can be applied to evaluate the quality of pre developed software or custom software during its development process The software product quality evaluation can be conducted for instance by an acquirer a developer organisation or an independent evaluator These three different approaches are presented as annexes that complement the main evaluation process providing issues to be followed according to each evaluation perspective e ISO IEC 25041 Evaluation modules defines the structure and content of the documentation to be used to describe an Evaluation Module These Evaluation Modules contain the specification of the quality model i e characteristics SuDcharacteristics and corresponding internal external or quality in use measures the associated data and information about the planned application of the model and the information about its actual application Appropriate evaluation modules are selected for each evaluation In some cases it may be necessary to develop new evaluation modules Guidance for developing new evaluation modules is found in ISO IEC 25041 This International Standard can also be used by organisations producing new evaluation modules e ISO IEC 25045 Evaluation module for recoverability provides the specification to evaluate the subcharacteristic of recoverability defined under the characteristic of reliability of the quality model It determines the external measures o
149. ar system life cycle process assessment model DISO IEC TR 15504 7 2008 Information technology Process Assessment Part 7 Assessment of organizational maturity SISO IEC TR 15504 8 Information technology Process Assessment Part 8 An exemplar process assessment model for IT service management WD ISO IEC TR 15504 9 Information technology Process Assessment Part 9 Capability target profiles DTR QOISO IEC TR 15504 10 Information technology Process Assessment Safety extensions WD 1 5 SC7 Sudy Group CO ISO IEC 33000 1 JIS 2 2 3 1 2009 04 09 A 2 2009 05 H 14 H CI 3 2009 06 11 E A 4 2009 07 09 H CR 5 2009 09
150. are and system design objectives e identifying software and system testing objectives e identifying quality control criteria as part of quality assurance e identifying acceptance criteria for a software product and software intensive computer system e establishing measures of quality characteristics in support of these activities The quality models can be used in conjunction with ISO IEC 12207 and ISO IEC 15288 particularly the processes associated with requirements definition verification and validation with a specific focus on the specification and evaluation of quality requirements ISO IEC 25030 describes how the quality 9 ISO IEC FCD 25010 models can be used for software quality requirements and ISO IEC 25040 describes how the quality models can be used for the software quality evaluation process 2 Conformance Any software intensive computer system or software product quality requirement specification or evaluation that conforms to this International Standard shall either make use of the characteristics and subcharacteristics from clauses 5 and 6 giving the reasons for any exclusions or describe its own categorisation of quality attributes and provide a mapping to the characteristics and subcharacteristics in clauses 5 and 6 3 Terms and definitions For the purposes of all parts of this International Standard the terms and the definitions contained in ISO IEC 25000 apply except where indicated below Definitions of
151. ative Intended users and uses of the usability related information items 19 Annex B informative Bibliography mii 27 IV ISO IEC 2008 All rights reserved ISO IEC PDTR 25060 Foreword ISO the International Organization for Standardization is a worldwide federation of national standards bodies ISO member bodies The work of preparing International Standards is normally carried out through ISO technical committees Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee International organizations governmental and non governmental in liaison with ISO also take part in the work ISO collaborates closely with the International Electrotechnical Commission IEC on all matters of electrotechnical standardization International Standards are drafted in accordance with the rules given in the ISO IEC Directives Part 2 The main task of technical committees is to prepare International Standards Draft International Standards adopted by the technical committees are circulated to the member bodies for voting Publication as an International Standard requires approval by at least 75 of the member bodies casting a vote In exceptional circumstances when a technical committee has collected data of a different kind from that which is normally published as an International Standard state of the art for example it may decide by a sim
152. ce AS INElICS em una Puede T avt eun nement etre 22 6 46 ACCESSID MERERETUR TU LN 23 6897 GII 23 G5 DII ET c LT MES 23 6052 WAV II RE ES 23 6339 aulliolerance dido a etu ands Re AR Gy satu ia a iV an Dm VEU 23 6 54 fecoveraDil ss sen na Ce a nn i tan 23 DG 24 Gol DO 24 PP 24 56 9 MON TODUOIAION se ee Le A ee AN RR RN Sac NE NR 24 FC COI SR 24 6059 Ulhenuely mo a a a a a ea a 24 6 7 INCURIA n Ter ES 24 o 75 1 mnodulariby cdnn lecum GN a eee wet Uv dd d sait 25 GT MEE 1 010 i ERR CE 25 6073 Analys DIN se et 25 e Mb eene SE ee NS c S 25 SN lel a 25 68 DOHaDIIIDV EE 25 sme 26 Sa 26 616 3 Telacea We 26 Annex A Comparison with the quality model in ISO IEC 9126 1 27 ISO IEC FCD 25010 Annex B Example of mapping to dependability 0 30 Annex C Using the quality model for measurement nn 32 Annex D Terms and definitions nn 39 BIbDIIoOgraph je 43 ISO IEC FCD 25010 Foreword ISO the International Organization for Standardization and IEC the International Electrotechnical Commission form the specialized system for worldwide standardization National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity ISO and IEC technical commi
153. cess performance indicators for each process The Process Assessment Model also defines a second set of indicators of process performance by associating work products with each process Clause 5 is also linked directly to Annex B which defines the work product characteristics VI ISO IEC 2009 All rights reserved N A clause 6 addresses the capability dimension It duplicates the definitions of the capability levels and process attributes from ISO IEC 15504 2 and expands each of the nine attributes through the inclusion of a set of generic practices These generic practices belong to a set of indicators of process capability in association with generic resource indicators and generic work product indicators Annex B is also linked directly to Clause 6 as it defines the work product characteristics Annex A provides a statement of conformance of the Process Assessment Model to the requirements defined in ISO IEC 15504 2 Annex B provides selected characteristics for typical work products to assist the assessor in evaluating the capability level of processes Annex C contains style guides for defining base practices work products and generic practices for adjusting the Process Assessment Model and guidance explaining how to expand or adapt the model and the Bibliography contains a list of informative references ISO IEC 2009 All rights reserved Vii N A Information technology Process assessment
154. cial Off The Shelf software and Common Industry Formats for usability reports Vii ISO IEC FCD 25010 This International Standard can also be used in conjunction with ISO IEC 15504 which is concerned with the software process assessment to provide e a framework for software product quality definition in the customer supplier process e support for review verification and validation and a framework for quantitative quality evaluation in the support process e support for setting organisational quality goals in the management process This International Standard can be used in conjunction with ISO 9001 which is concerned with quality assurance processes to provide e support for setting quality goals e support for design review verification and validation viii ISO ISO IEC FCD 25010 Systems and software engineering Systems and software product Quality Requirements and Evaluation SQuaRE Quality models 1 Scope This International Standard defines a A product quality model composed of eight characteristics which are further subdivided into subcharacteristics that relate to static properties of software and dynamic properties of the computer system The model is applicable to both computer systems and software products b A quality in use model composed of five characteristics some of which are further subdivided into subcharacteristics that relate to the outcome of interaction when a product is used in
155. cross applications which intelligently exchange information with one another Further most software include underlying rules and calculations or algorithms that affect the results a user can obtain when using the software Such underlying programming mechanics are discernable by users but only through laborious testing For these reasons and more user documentation remains an essential component of usable software products Documentation is often regarded as something done after the software has been implemented However for high quality software documentation its development should be regarded as an integral part of the software life cycle process If done properly documentation or information management is important enough to require process planning in its own right The accurate description of the requirements for user documentation is essential in order to ensure that the documentation meets the needs of its users This International Standard addresses the identification of key components that ensures all user documentation requirements are identified and clearly defined as part of the acquisition and supply processes This International Standard covers the requirements for information items used in the acquisition of user documentation products the Acquisition Plan Document Specification Statement of Work Request for Proposals and the proposal It also discusses the use of a Documentation Management Plan and a Document Plan as they aris
156. d supply to software user documentation Clause 7 addresses the preparation of requirements for software user documentation These requirements are central to the user documentation specification and Statement of Work discussed in clauses 8 and 9 Clauses 10 and 11 address requirements for primary document outputs of the acquisition and supply process the Request for Proposal and the Proposal for user documentation products and services NOTE Software systems documentation prepared by software developers is rarely suitable for end user documentation as it describes how the software functions rather than providing instructions for user tasks This International Standard is intended neither to encourage nor discourage the use of either printed or electronic on screen media for documentation or of particular documentation development or management tools or methodologies This International Standard may be helpful for acquiring supplying the following types of documentation although it does not cover all aspects of them e documentation of products other than software e multimedia systems using animation video and sound computer based training CBT packages and specialized course materials intended primarily for use in formal training programs e documentation produced for installers computer operators or system administrators who are not end users e maintenance documentation describing the internal operation of systems software
157. de Deut QE 12 5 4 1 Summary of the Quality Measures and Quality Measure Elements QME 12 5 42 Quality Measure Resilient viscera RE a Gua qst eae a la edi cu du os caen ecrans nette 12 5 4 3 Quality Measure AUTONOMIC Recovery Index ee 13 5 4 4 Quality Measure Element QME Number of transactions under disturbance 15 5 4 5 Quality Measure Element QME Number of transactions under no disturbance 16 5 4 6 Quality Measure Element QME Autonomic Maturity Score ee 16 6 interpretation Of FOS UNS sn 17 6 1 Mapping OF measuUreS eee i 17 6 2 Reporntno ARE PP EQ 17 6 3 APPIICATION d goloi ie j nm 17 Annex A informative Sample Report diit roa stetur hdi canne safe n ba decori qae 18 BIDIIOOPADNV dome ecce P M 37 IV ISO IEC 2009 All rights reserved ISO IEC FDIS 25045 2009 E Foreword ISO the International Organization for Standardization and IEC the International Electrotechnical Commission form the specialized system for worldwide standardization National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity ISO and IEC technical committees collaborate in fields of mutual interest Other international organizations governmental and non governmental
158. design and testing throughout the lifecycle In order to enable a human centred approach to be adopted it is important that all the relevant usability information items are identified and documented This identification and documentation enables the usability of a system to be designed and tested This framework forms the basis for a family of standards that will provide a Common Industry Format CIF for specific information items to be used as part of a human centred approach to design of interactive systems ISO IEC 25062 The Common Industry Format CIF for Usability Test Reports which standardizes the types of information that are documented when providing a detailed report of the results of measuring effectiveness efficiency and satisfaction is the first specific standard in this family The Common Industry Format CIF for Usability family is part of the SQuaRE series ISO IEC 25000 ISO IEC 25099 of standards on software product quality requirements and evaluation The scope of the CIF family covers systems rather than just software so is broader in scope than the current SQuaRE series The CIF family of standards uses definitions reproduced in clause 2 that are consistent with the ISO 9241 series of standards Ergonomics of human system interaction as this is the terminology that is normally used for this subject matter In some cases these definitions differ from those in ISO IEC 25000 vi ISO IEC 2008 All rights reserved
159. documentation because their work affects the content display or presentation of documentation for the user for example developers of tools for creating on screen documentation graphic designers producing material displayed as part of the documentation and human factors experts who identify principles for making documentation more accessible and easily used also user interface designers and ergonomics experts working together to design the presentation of the documentation on screen In some organizations these roles may have different titles or an individual may perform more than one of these roles There are other roles that need to understand the test processes for the documentation for example authors should understand the test processed for the documentation that they have produced and acquirers of documentation prepared by another department or organization might want to know what testing has been performed and the processes followed for the documentation that they are acquiring from a supplier This International Standard is intended for use in all types of organizations whether or not a dedicated documentation department is present In all cases it may be used as a basis for local standards and procedures Readers are assumed to have experience or general Knowledge of testing or reviewing processes This International Standard deals with the evaluation of documentation only and not with the evaluation of the software it supports Documen
160. dology involving two types of evaluation for recoverability One part of the method makes use of the disturbance injection methodology and a list of disturbances based on common categories of operational faults and events to evaluate the quality measure of resiliency The second quality measure is based on a set of questions that is defined for each disturbance to evaluate the quality measure of autonomic recovery index by assessing how well the system detects analyses and resolves the disturbance without human intervention This International Standard is applicable to information systems executing transactions in a system supporting single or multiple concurrent users where speedy recovery and ease of managing recovery is important to the acquirer owner operator and the developer 1 1 Characteristics This evaluation module measures the quality measures defined under the following characteristic and sub characteristics of the quality model as defined in ISO IEC 9126 1 2001 NOTE The reference to ISO IEC 9126 1 will be replaced by a reference to ISO IEC 25010 when published Characteristic Reliability Sub characteristic Recoverability Quality measure Resiliency Quality measure Autonomic recovery index 1 2 Level of evaluation Level D as defined in ISO IEC 14598 5 This evaluation is intended for a system with executable products NOTE The reference to ISO IEC 14598 5 will be replaced by a reference to ISO IEC 25040 when publis
161. dy in the country of the requester Indicate the full address telephone number fax number telex number and electronic mail address as appropriate of the Copyright Manger of the ISO member body responsible for the secretariat of the TC or SC within the framework of which the working document has been prepared Reproduction for sales purposes may be subject to royalty payments or a licensing agreement Violators may be prosecuted ISO IEC 2008 All rights reserved iii ISO IEC PDTR 25060 Contents Page 1 DC OPC as 1 2 Ternms andDelinnone Ge T 2 3 A general framework for usability related information ee 5 3 1 Intended users and uses of usability related information items 5 3 2 Union Representatives and staff councilsSituations in which the information items apply 6 3 3 Process mdependence eet 7 3 4 Relationship to Human centred design HCD as described in ISO 9241 210 7 3 5 Iteration and support for exploration ee 8 4 Usability related information items ee Lees liess eeee en eee eene enne nnn n nnn nnne nnn nnn nnn nnn 8 4 1 Introducllom ee 8 4 2 ContexkEofsesidescrI pH 8 4 3 Userineeds reporb i 9 4 4 Userirequirements specification aa 9 4 5 User interaction specificatio histidine 10 4 6 Userinterface specillcallonN me lk 11 4 7 VAIUATION mL 11 4 8 PICIG Gala FEDOM Pe 12 Annex A inform
162. e BOOM na aca can liii esp mnt aida nt 29 12 PUG Re Wey IBN IL OLI ILLI 0 8 SRE atin Ek 23 1 iii 33 2 X 0145 3 2004 ISO IEC 15504 3 2004 82 od RR 36 9 PRRI J VD ee OE asian 39 10 c gE Fo ee 41 IOL 41 102 D MUR a ET 41 11 MS D aU VO FS eire nn 42 ill Z2EEXSBRBTIJONSSULOIsxE e ect eet E E tuu v ae ems 42 112 et 43 113 JZEEZATEAIJ YV FORSE we 44 A 45 HERAB EOTF oe 50 2 52 3 X 0145 3 2004 ISO IEC 15504 3 2004
163. e in the acquisition and supply processes Earlier standards tended to view the results of the documentation process as a single book or multi volume set a one time deliverable Increasingly documentation acquirers suppliers recognize that most user documentation is now produced from managed re use of previously developed information single source documentation adapted for new software versions or presentation in various on screen and printed media While this standard does not describe how to set up a content management system it is applicable for documentation organizations practicing single source documentation The standard is independent of the software tools that may be used to produce documentation and applies to both printed documentation and on screen documentation Much of its guidance is applicable to user documentation for systems including hardware as well as software The primary reference for this new standard is ISO IEC 26514 2008 Software and systems engineering Requirements for designers and developers of user documentation Other standards in the ISO IEC 265NN series are in preparation or planned to address the documentation and information management processes from the viewpoints of managers designers and developers and testers and reviewers This International Standard conforms to ISO IEC 12207 2008 Information technology Software life cycle processes as an implementation of the Acquisition and Supply processes
164. e member bodies casting a vote In exceptional circumstances when a technical committee has collected data of a different kind from that which is normally published as an International Standard state of the art for example it may decide by a simple majority vote of its participating members to publish a Technical Report A Technical Report is entirely informative in nature and does not have to be reviewed until the data it provides are considered to be no longer valid or useful ISO IEC TR 15504 8 was prepared by Technical Committee ISO IEC TC JTC1 Information Technology Subcommittee SC 7 Software and Systems Engineering ISO IEC TR 15504 consists of the following parts under the general title nformation technology Process assessment Part 1 Concepts and Vocabulary Part 2 Performing an Assessment Part 3 Guidance on performing an assessment Part 4 Guidance on use for process improvement and process capability determination Part 5 An exemplar Process Assessment Model Part 6 An exemplar system life cycle process assessment model Part 7 Assessment of organizational maturity Part 8 An exemplar assessment model for service management processes This Part of ISO IEC 15504 is informative ISO IEC 2009 All rights reserved V N A Introduction This part of ISO IEC 15504 provides an example of a Service Management Process Assessment Model for use in performing a confor
165. ecoverability of a software product conforms to this International Standard if it complies with Clause 5 3 Normative references The following referenced documents are indispensable for the application of this document For dated references only the edition cited applies For undated references the latest edition of the referenced document including any amendments applies ISO IEC 25000 2005 Software Engineering Software product Quality Requirements and Evaluation SQuaRE Guide to SQuaRE 2 ISO IEC 2009 All rights reserved 5 Ts Ti EC ISO IEC JTC1 SC7 SO JTC 1 Software and Systems Engineering INFORMATION TECHNOLOGY STANDARDS Secretariat CANADA SCC ISO IEC JTC1 SC7 N4420 2009 07 20 Document Type DTR Title DTR 25060 Software product Quality Requirements and Evaluation SQuaRE Common Industry Format CIF for Usability General Framework for Usability related Information Source JWG Project 25060 Status Final Reference N4233 N4418 N4419 Action ID FYI or ACT Distribution AG No of Pages 28 Note Sent to JTC 1 for DTR processing Address reply to ISO IEC JTC1 SC7 Secretariat Ecole de technologie sup rieure Department of Software and IT Engineering 1100 Notre Dame Ouest Montr al Qu bec Canada H3C 1K3 secretariat jtcl sc7 org www jtcl sc7 org ISO IEC 2008 All rights reserved TITLE DATE SOURCE WORK ITEM STATUS DOCUMENT TYPE ACTION
166. ental and non governmental in liaison with ISO also take part in the work ISO collaborates closely with the International Electrotechnical Commission IEC on all matters of electrotechnical standardization International Standards are drafted in accordance with the rules given in the ISO IEC Directives Part 2 The main task of technical committees is to prepare International Standards Draft International Standards adopted by the technical committees are circulated to the member bodies for voting Publication as an International Standard requires approval by at least 75 of the member bodies casting a vote In exceptional circumstances when a technical committee has collected data of a different kind from that which is normally published as an International Standard state of the art for example it may decide by a simple majority vote of its participating members to publish a Technical Report A Technical Report is entirely informative in nature and does not have to be reviewed until the data it provides are considered to be no longer valid or useful Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights ISO shall not be held responsible for identifying any or all such patent rights ISO IEC TR 15504 10 was prepared by Technical Committee ISO IEC TC JTC1 Information technology Subcommittee SC 7 Software and systems engineering ISO IEC TR 15504 consists of the followin
167. eople or organizations The works listed in the Bibliography provide guidance on the processes of managing preparing and testing user documentation 2 Conformance This International Standard may be used as a conformance document or as a guidance document for projects and organizations claiming conformance to ISO IEC 15288 2008 Systems engineering System life cycle processes or ISO IEC 12207 2008 Information technology Software life cycle processes It may also be used as a conformance standard for organizations who do not wish to implement the above International Standards applied either to the organization as a whole or to a single project team within the organization 2 1 Definition of conformance Whether the organization or project has tailored the selected software life cycle processes or adopted them in full the organization or project may claim conformance to this International Standard for its documentation process for the documentation or for both This standard is meant to be tailored so that only necessary and cost effective requirements are applied to documentation Tailoring may take the form of specifying approaches to conform to its mandatory requirements or altering its non mandatory recommendations and approaches to reflect the particular software and documentation product more explicitly Tailoring decisions made by the acquirer should be specified in the contract Throughout this International Standard
168. ernational Standard It is distributed for review and comment It is subject to change without notice and may not be referred to as an International Standard Recipients of this draft are invited to submit with their comments notification of any relevant patent rights of which they are aware and to provide supporting documentation Document type Technical Report Document subtype Document stage 20 Preparatory Document language E C Documents and Settings s13037 My Documents Standards lso Sc7 WG10 Safety Extension WG10N620 WD ISO IEC TR 15504 10 E 02 doc STD Version 2 1 ISO IEC PDTR 15504 10 Contents Page 1 CODe PR r NS SENS 1 2 NOrmaliVe reterence Ss nn a CINE On ni ne ne a a 1 3 TERMS and OGfINIONS se E 1 4 Theprocess GIMENSION Es 1 4 1 Safety Management DlOCGSS uum 1 4 2 Safety Engineering proceSS uum 4 4 3 Tool Qualification DIOCESS cn nn nn ne onu a mn oi et La RO ent 6 5 GOCVGI6 GUuldanGe a a One Dane LM nn tiens ue een EE UNE 8 ISO IEC 2009 All rights reserved iii ISO IEC PDTR 15504 10 Foreword ISO the International Organization for Standardization is a worldwide federation of national standards bodies ISO member bodies The work of preparing International Standards is normally carried out through ISO technical committees Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee International organizations governm
169. evant patent rights of which they are aware and to provide supporting documentation Document type International Standard Document subtype Document stage 30 Committee Document language E C adr WG2 15289 CD 15289 E doc STD Version 2 1 ISO IEC CD 15289 2 Copyright notice This ISO document is a working draft or committee draft and is copyright protected by ISO While the reproduction of working drafts or committee drafts in any form for use by participants in the ISO standards development process is permitted without prior permission from ISO neither this document nor any extract from it may be reproduced stored or transmitted in any form for any other purpose without prior written permission from ISO Requests for permission to reproduce this document for the purpose of selling it should be addressed as shown below or to ISO s member body in the country of the requester Indicate the full address telephone number fax number telex number and electronic mail address as appropriate of the Copyright Manger of the ISO member body responsible for the secretariat of the TC or SC within the framework of which the working document has been prepared Reproduction for sales purposes may be subject to royalty payments or a licensing agreement Violators may be prosecuted Il ISO IEC 2009 All rights reserved ISO IEC CD 15289 2 Contents Page FOreW ON 0 RP X vii mtrodu Ct
170. evant quality characteristics that can be further used to establish requirements their criteria for satisfaction and the corresponding measures This International Standard is derived from ISO IEC 9126 1991 Software product evaluation Quality characteristics and guidelines for their use which was developed to support these needs It defined six quality characteristics and described a software product evaluation process model ISO IEC 9126 1991 was replaced in 2001 by two related multipart standards ISO IEC 9126 Software product quality and ISO IEC 14598 Software product evaluation This International Standard revises ISO IEC 9126 1 2001 and incorporates the same software quality characteristics with some amendments e The scope of the quality models has been extended to include computer systems and quality in use from a system perspective e Context of use has been added as a quality characteristic with subcharacteristics context completeness and flexibility e Security has been added as a characteristic rather than a subcharacteristic of functionality e Compatibility including interoperability and co existence has been added as a characteristic e he following subcharacteristics have been added functional completeness availability accessibility modularity and reusability e he compliance subcharacteristics have been removed as compliance with laws and regulations is part of overall system requirements rather tha
171. exemplar Process Assessment Model sn 3 421 ProceSsseSsm 4 4 2 2 Process GIMENSION ue ed eocea dco lecstavacenteb aaa aaa a NA 7 4 2 3 Gapability dimmehSIOD a 7 4 3 Assessment INAICAIOrS 38 9 43 Process Capability MdIiCAtOrS RR 10 4 3 2 Process Performance INGICALOFS si 11 4 4 Measuring process capability sem 12 5 The process dimension and process performance indicators level 1 13 5 1 Management process group MAN eroi ee enne nennen nennen nnnm nnn nnn nnn nnn n n nnn nnns 15 Set ADMFOQUCHODB zione anoo a 15 5 1 2 ITSM MAN 1 SMS establishment and maintenance for ITSM 15 5 1 3 ITSM MAN 2 Process establishment for ITSM e eeeeeee ee Leeee eere e nennen nennt 17 5 1 4 ITSM MAN 3 Process assessment for ITSM 1 eee e eieeeee eee iieeee enne nenne nnn nana nnn nnns 18 5 1 5 ITSM MAN 4 MeasurementforlITSM lesse Lees ee ileeecuiiee enne nean nena nhan sana aa anas a nma saa 19 5 1 6 ITSM MAN 5 Audit Tor IT SM vis e ci assise dense uva cu euo nest aiai nes aaa cas o a au oz RR vade 21 5 1 7 IESM MAN 6 Improvement for ITSM Lun 23 5 1 8 ITSM MAN 7 Human resource management for ITSM ii 25 5 1 9 ITSM MAN 8 Risk management for ITSM 1 1lleeee ee eeeeeeee eiie nennen nnn n unen nhan nnn anna 27 5 1
172. extended to the autonomic ability of the software product and thereby a system to be self managed with minimal involvement by human operators There are interests in the user domain and industry on how well a software product and thereby a system handles such disturbances in the way it detects analyses adjusts or recovers This International Standard determines the quality measures of resiliency and autonomic recovery index when the information system composed of one or more software products execution transactions is subjected to a series of disturbances A disturbance could be an operational fault e g an abrupt shutdown of an operating system process that brings down a system or an event e g a significant increase of users to the system To be published Under preparation ISO IEC 2009 All rights reserved FINAL DRAFT INTERNATIONAL STANDARD ISO IEC FDIS 25045 2009 E Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation module for recoverability 1 Scope This International Standard is one of the SQuaRE series of International Standards which contains general requirements for specification and evaluation of software quality and clarifies the associated general concepts SQuaRE provides a framework for evaluating the quality of software products and states the requirements for methods of software product measurement and evaluation This International Standard uses a metho
173. f software quality of resiliency and autonomic recovery index when the information system composed of one or more software products execution transactions is subjected to a series of disturbances A disturbance could be an operational fault e g an abrupt shutdown of an OS process that brings down a system or an event e g a significant increase of users to the system ISO IEC 25040 Evaluation reference model and guide is a revised version and replaces the current ISO IEC 14598 1 Software product evaluation General overview X ISO IEC 2002 All rights reserved COMMITTEE DRAFT Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation reference model and guide 1 Scope This International Standard contains requirements and recommendations for the evaluation of software product quality and clarifies the general concepts This document provides a process description for evaluating software product quality and states the requirements for the application of this process The evaluation process can be used for different purposes and approaches The process can be used for the evaluation of the quality of pre developed software commercial off the shelf software or custom software and can be used during or after the development process This International Standard establishes the relationship of the evaluation reference model to the SQuaRE documents as well as shows how each SQuaRE docume
174. forms with ISO IEC 26514 2008 Systems and software engineering Requirements for designers and developers of user documentation SO IEC 15288 2008 Systems and software engineering System life cycle processes and ISO IEC 12207 2008 Systems and software engineering Software life cycle processes This International Standard was developed to assist those who test and review software user documentation as part of the software life cycle process This International Standard defines the Documentation Management and Validation processes of ISO IEC 12207 2008 from the tester s standpoint This International Standard may be used as a conformance or a guidance document for products projects and organizations claiming conformance to ISO IEC 15288 2008 or ISO IEC 12207 2008 ISO IEC 2009 All rights reserved V INTERNATIONAL STANDARD ISO IEC 26513 2009 E Systems and software engineering Requirements for testers and reviewers of user documentation 1 Scope This International Standard supports the interest of software users in receiving consistent complete accurate and usable documentation This International Standard defines the process in which user documentation products are tested This International Standard is intended neither to encourage nor discourage the use of either printed or electronic on screen media for documentation or of any particular documentation testing or management tools or methodologies This Inte
175. g parts under the general title Information technology Process assessment Part 10 Safety extension Part n Part n 1 IV ISO IEC 2009 All rights reserved ISO IEC PDTR 15504 10 Introduction The published ISO IEC 15504 process assessment models for systems and software do not currently provide a sufficient basis for performing a process capability assessment of processes with respect to the development of complex safety critical systems The ISO IEC 15504 standard does provide a general framework in which assessments can take place however additional guidance and processes are needed to support the use of the existing process assessment models for systems and software when applied to safety related systems development in order to make consistent judgement regarding process capability or improvement priorities Developing safety critical systems requires specialised processes techniques skills and experience Process amplifications are needed in the area of safety management safety engineering and the selection and qualification of software tools and libraries together with additional informative components concerning additional lifecycle verification activities related to the methods and techniques selected relevant to safety integrity levels adopted and tailoring guidance for users intending to use the Safety Extension as part of a process assessment The Safety Extension as a standalone document can be
176. good service management practices Any process assessment model meeting the requirements defined in ISO IEC 15504 2 concerning models for process assessment may be used for assessment Different models and methods may be needed to address differing business needs The assessment model in this part of ISO IEC 15504 is provided as an exemplar of a model meeting all the requirements expressed in ISO IEC 15504 2 The scope of this Part of ISO IEC 15504 is consistent with the scope of Part 5 and 6 of ISO IEC 15504 in order to assist situations where assessment is being made of both service management and system software life cycle processes NOTE Copyright release for the Exemplar Process Assessment Model Users of this part of ISO IEC 15504 may freely reproduce the detailed descriptions contained in the exemplar assessment model as part of any tool or other material to support the performance of process assessments so that it can be used for its intended purpose 2 Normative references The following normative documents contain provisions which through reference in this text constitute provisions of this part of ISO IEC 15504 For dated references subsequent amendments to or revisions of any of these publications do not apply However parties to agreements based on this part of ISO IEC 15504 are encouraged to investigate the possibility of applying the most recent editions of the normative documents indicated below For undated references the la
177. h the supplier Lee sees Leser ee rere rn ee rennen nnne nnns 34 B 4 1 Operating history requirements ooo dice doo aid deii tuve resi i tenant dou uae icu cU onu need 34 B 42 Operating history FeVIOW curet ioo eeu dpa tuve cuu da awd deat cu uud Sense ne te anne dal awww bague cU o uu adus 34 B 5 Review of operating history with customers nn 35 B 6 Review of supplier capability support and quality system eee sse 35 B 7 Prototyping and other evaluation methodS e eeeeee e Lire eee ieeecliiee nennen nnnm uana aaa sana ananas 36 BL PEOIOIWVDIN E TEE TOEIC Ime 36 B72 Other evaluauon mielliOdS icis eed cose ne ne RE toe oa oe oa ooo oa Ecos PP eo Nes Saone Saber sud 37 Annex C informative Example of Cost Effectiveness Ranking of Evaluation Methods 38 Annex D informative Relationships between software product quality evaluation process reference model and software and system life cycle processes eese 39 Annex E informative Evaluation report template eese lesse ee eeeee eee ee eene nennen nnn nnn nnn 41 E 1 Section dsldentificationS 0 Oo EN 41 E 2 Section 2 Evaluation requiremehls EK 42 E 3 Section 3 Evaluation specilicatlionN oe 42 E 4 Section 4 Evaluation methods 0 42 E 5 Section 5 Evaluation Hesul
178. he form of specifying approaches to comply with its mandatory requirements or altering its non mandatory recommendations and approaches to reflect the particular software and documentation product more explicitly The acquirer may involve other parties including potential suppliers or any necessary third parties such as regulators before contract award in determining the acquirer s requirements for tailoring of this International Standard for the project Annex A normative of ISO IEC 2 ISO IEC 2009 All rights reserved 12 INTERNATIONAL ISO IEC STANDARD 26513 First edition 2009 10 15 Systems and software engineering Requirements for testers and reviewers of user documentation Ing nierie des systemes et du logiciel Exigences pour testeurs et v rificateurs de documentation utilisateur Heference number ISO IEC 26513 2009 E ISO IEC 2009 ZS ES ISO IEC 26513 2009 E PDF disclaimer This PDF file may contain embedded typefaces In accordance with Adobe s licensing policy this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing In downloading this file parties accept therein the responsibility of not infringing Adobe s licensing policy The ISO Central Secretariat accepts no liability in this area Adobe is a trademark of Adobe Systems Incorporated Details of the software p
179. hed 1 3 Technique A disturbance injection methodology is a test methodology where disturbances are injected against the application and other components of the system while it is running a workload of interest to the acquirer A disturbance injection methodology and a list of disturbances based on common categories of operational faults and events are used to evaluate the quality measure of Resiliency For each disturbance the Resiliency of the system is calculated based on the ratio between the number of transactions that complete successfully om ISO IEC 2009 All rights reserved ISO IEC FDIS 25045 2009 E while the system is under disturbance and the number of transactions that complete successfully in a system that does not encounter the disturbance A set of disturbances is defined under the following categories e Unexpected shutdown e g abrupt operating system OS shutdown process shutdown network shutdown e Resource contention e g CPU memory IO hogs memory leak database management system DBMS runaway query DBMS deadlock DBMS and queuing server storage exhaustion e Loss of data e g DBMS loss of data DBMS loss of file DBMS and queuing server loss of disk e Load resolution e g a moderate or significant increase of users or workload e Restart failures e g restart failure on OS and middleware server process Other disturbance categories may be identified if appropriate A set of quest
180. ibing a specific process and is intended to be used in conjunction with existing standards including ISO 9241 210 ISO 9241 ISO 20282 ISO 9126 and the ISO IEC 25000 SquaRE series This framework does not prescribe any kind of method lifecycle or process To ensure that these information items can be used within the broadest range of process models and can be used in combination with other information items the descriptions are given in the format defined in ISO IEC 15289 and ISO IEC 15504 6 The information items for documenting usability related information can be integrated in any process models For the purpose of establishing process models ISO IEC 24774 and ISO IEC 15504 2 specify the format and conformance requirements for process models respectively In addition ISO IEC 15289 defines the types and content of information items developed and used in process models for system and software lifecycle management ISO IEC 15504 5 and 6 define work products including information items for the purpose of process capability assessment Process models and associated information items for human centred design of interactive systems are contained in ISO 9241 210 and ISO PAS 18152 respectively ISO IEC 2008 All rights reserved 1 ISO IEC 2009 All rights reserved DAT j 41 0 ISO IEC TC JTC1 SC 7 WG10N 608008 Date 2009 04 26 ISO IEC WD 2 15504 8 ISO IEC TC JTC1 SC 7 WG 10 Secretariat ANSI Information technology Process a
181. ing Software product Quality Requirements and Evaluation SQuaRE Evaluation modules RAF e ISO IEC 25042 Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation process for developers 25040 e ISO IEC 25043 Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation process for acquirers 25040 e ISO IEC 25044 Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation process for evaluators 25040 e ISO IEC 25045 Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation module for recoverability FDIS 6 25051 25099 SQuaRE 3 e ISO IEC 25051 Software engineering Software product Quality Requirements and Evaluation SQuaRE Requirements for quality of Commercial Off The Shelf COTS software product and instructions for testing IS 2006 4 e ISO IEC 25060 Software engineering Software product Quality Requirements and Evaluation SQuaRE General framework for usability related information DIS e ISO IEC 25062 Software engineering Software product Quality Requireme
182. ion The evaluation of software product quality is vital to both the acquisition and development of software that meets quality requirements The relative importance of the various characteristics of software quality depends on the mission or objectives of the system of which it is a part software products need to be evaluated to decide whether relevant quality characteristics meet the requirements of the system The essential parts of software quality evaluation are a quality model the method of evaluation software measurement and supporting tools To develop good software quality requirements should be specified the software quality assurance process should be planned implemented and controlled and both intermediate products and end products should be evaluated This International Standard is part of the SQuaRE series of International Standards It contains general requirements for specification and evaluation of software quality and clarifies the associated general concepts It provides a framework for evaluating the quality of software products and states the requirements for methods of software product measurement and evaluation The general goal of creating the SQuaRE series of International Standards is to move to a logically organized enriched and unified series covering two main processes software quality requirements specification and software quality evaluation supported by a software quality measurement process The purpose of the
183. ions to assess how well the system detects analyses and resolves the disturbance is defined for each disturbance to evaluate the quality measure of autonomic recovery index A score is calculated for each disturbance based on the answers to those questions The overall Resiliency and autonomic recovery index are calculated respectively as an average of those individual scores The detailed evaluation methodology involved is given in 5 1 1 4 Applicability This evaluation module is applicable to an information system that involves a software product and other software components The information system must have a workload that has a consistently reproducible performance result to properly assess the impact of disturbance and recovery The evaluation module can be used in the following situations a evaluation as part of the system verification testing b evaluation against the test environment of a production system to gauge recoverability and identify weakness C evaluation of the recoverability of different solutions proposed by vendors using a common workload The evaluation result is only applicable to the specific release and configuration of the software and hardware components on which they were evaluated Two results are comparable if they use the same workload and workload parameter set defined in 5 2 2 2 and fault load and fault load parameter set defined in 5 2 3 2 for the evaluation 2 Conformance An evaluation of the r
184. ist esee eese e eee eere eene nennen nnn nnns 37 PID IO ON NY Poem c rc 53 ISO IEC 2009 All rights reserved iii ISO IEC 26513 2009 E Foreword ISO the International Organization for Standardization and IEC the International Electrotechnical Commission form the specialized system for worldwide standardization National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity ISO and IEC technical committees collaborate in fields of mutual interest Other international organizations governmental and non governmental in liaison with ISO and IEC also take part in the work In the field of information technology ISO and IEC have established a joint technical committee ISO IEC JTC 1 International Standards are drafted in accordance with the rules given in the ISO IEC Directives Part 2 The main task of the joint technical committee is to prepare International Standards Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting Publication as an International Standard requires approval by at least 75 of the national bodies casting a vote Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights I
185. l capability and the target process profile 2 Normative references The following referenced documents are indispensable for the application of this document For dated references only the edition cited applies For undated references the latest edition of the referenced document including any amendment applies ISO IEC 15504 1 2004 Information Technology Process Assessment Part 1 Concepts and Vocabulary ISO IEC 15504 2 2003 Information Technology Process Assessment Part 2 Performing an Assessment 3 Terms and Definitions For the purposes of this part of ISO IEC 15504 the terms and definitions given in ISO IEC 15504 1 and the following apply 3 1 target process profile A target process profile specifies which process attributes are required and the rating necessary for each process attribute or the capability level and rating for a required process 3 2 target capability The set of target process profiles subject to an acceptable process related risk which meet the specified requirement for process capability determination or the business goals for process improvement ISO IEC 2008 All rights reserved 1 ISO IEC 2009 All rights reserved DAT j 41 8 ISO IEC TC JTC1 SC 7 N 620 Date 2009 10 10 ISO IEC PDTR 15504 10 ISO IEC TC JTC1 SC 7 WG 10 Secretariat ANSI Information technology Process assessment Part 10 Safety extension Warning This document is not an ISO Int
186. lementation of the user documentation part of 6 1 Documentation This International Standard may be used as a conformance or a guidance document for products projects and organizations claiming conformance to ISO IEC 15288 2008 and or ISO IEC 12207 2008 and Amendments Vi 26511 Software and systems engineering User documentation requirements for managers 1 Scope This clause presents the scope purpose organization and candidate uses of this standard This standard supports the interest of software users in consistent complete accurate and usable documentation This standard includes the process standard approach to standardization which specifies the way in which user documentation projects are managed This standard is intended neither to encourage nor discourage the use of either printed or electronic online media for documentation or of any particular documentation testing or management tools or methodologies The requirements are media independent as far as possible This International Standard may be helpful for managing the following types of documentation although it does not cover all aspects of them e documentation of products other than software e multimedia systems using animation video and sound e computer based training CBT packages and specialized course materials intended primarily for use in formal training programs documentation produced for installers computer operators or system admi
187. logy Process assessment Part 9 Target Process Profiles 8 ISO IEC 15504 10 Information technology Process assessment Part 10 Safety extension 9 ISO IEC CD 15289 Systems and software engineering Content of life cycle information products Documentation 10 ISO IEC CD 26511 Software and systems engineering User documentation requirements for managers 11 ISO IEC FCD 26512 Software and systems engineering Requirements for acquirers and suppliers of user documentation 12 ISO IEC 26513 Systems and software engineering Requirements for testers and reviewers of user documentation 13 JIS X 25000 SQuaRE SQuaRE 14 JISX 25051 SQuaRE COTS JIS 15 TSX0111 2 2 JSX0129 1 16 TSXOIII 3 3 JISX0129 1 17 TSX01114 4 JSX0129 1 18 JIS X 0145 3 3 JIS 19 JIS X 0145 4
188. logy or tools The Process Reference Model defined in ISO IEC 20000 4 has been used as the basis for the Process Assessment Model in this part of ISO IEC 15504 As an exemplar this Process Assessment Model embodies the core characteristics that could be expected of any Process Assessment Model consistent with ISO IEC 15504 2 Nevertheless use of this Process Assessment Model is not required to meet the requirements of ISO IEC 15504 any other process assessment models meeting the requirements of ISO IEC 15504 2 may be used in a conformant assessment This Part of ISO IEC 15504 has a similar structure to Parts 5 and 6 It may be used in conjunction with these other parts for joint assessment of service management processes and system software life cycle processes Within this part of ISO IEC 15504 clause 4 provides a detailed description of the structure and key components of a process assessment model which includes two dimensions a process dimension and a capability dimension Assessment indicators are introduced in this clause clause 5 addresses the process dimension It uses process definitions from ISO IEC 20000 4 to designate the Process Reference Model The processes of the Process Reference Model are described in the Process Assessment Model in terms of purpose and outcomes and are grouped in seven process categories The Process Assessment Model expands the Process Reference Model process definitions by including a set of pro
189. ls test mno terete 2 2 a ee tee eee re ne 42 Annex F Normative Common terms and definitions II 43 F 1 Le 0 UT LE Soe 43 F 2 analysis MOE l a a a a 43 F 3 TRUE 43 F 4 aitribute Tor quality measUule eonim tawewaseniecuwes RRR RN 43 F 5 Dase miedslle a 43 F 6 commercial off the shelf software product ee 44 F 7 CONIEXLOLUSO c he mans Le neue D tune et a i tante 44 F 8 CUSIOIN SOMWANG so De 44 F 9 dala RRE EEA E A EEE A TA De cn dti li Ne D t 44 F210 decision cerea Re 44 F 11 derived measure a a Sk es cece chet eee cee ee Se i ne 44 1 ME Ie Em 44 FIs divisionot standardS EEK EE 45 F14 cend use 45 Be sa 45 F 16 evaluauon method sn ik SNS 1 hihi 45 Ft evaluationmodule a De kil1111l lt 4 45 TS 45 F19 11 ee 45 F200 Ta 45 F21 iunctionalrequiremente Es 46 F 22 amplied TIGedSs csiouscc s verte S vL oc sese peius delete devo D Ungu ne a 46 F 23 CAO Os 46 IV ISO IEC 2002 All rights reserved F 24 F 25 F 26 F 27 F 28 F 29 F 30 F 31 F 32 F 33 F 34 F 35 F 36 F 37 F 38 F 39 F 40 F 41 F 42 F 43 F 44 F 45 F 46 F 47 F 48 F 49 F 50 F 51 F 52 F 53 F 54 F 55 F 56 F 57 F 58 F 59 F 60 F 61 F 62 ISO IEC FCD 25040 2009 E Iiniormaliomn need se 46 iniormation prodUCt nm a RG 46 Informationisystem need Ss ma NR 46 Intermediale SOMWare DOOEGNEE 47 intermediate software product needs uum 47 mamlamer mm Dc
190. mant assessment in accordance with the requirements of ISO IEC 15504 2 An integral part of conducting an assessment is to use a process assessment model that is constructed for that purpose is related to a process reference model and is conformant with ISO IEC 15504 2 which sets out the minimum requirements for performing an assessment in order to ensure consistency and repeatability of the ratings A process reference model cannot be used alone as the basis for conducting consistent and reliable assessments of process capability because it requires greater detail to indicate process performance and capability Therefore the descriptions of process purpose and process outcomes provided by a process reference model need to be supported with a comprehensive set of indicators of process performance and the capability levels and process attributes defined in ISO IEC 15504 2 and its associated rating scale need to be supported with a set of indicators of process capability This additional detail describes a process reference model in terms of a process assessment model that can enable the assessment of consistent and repeatable ratings of process capability This Process Assessment Model contains a set of indicators to be considered when interpreting the intent of its Process Reference Model These indicators may also be used when implementing a process improvement program or to help evaluate and select an assessment model method methodo
191. ments elicitation for a software product to be developed or as inputs for an evaluation process The requirements definition process is mapped to technical processes defined in ISO IEC 15288 Information Technology Life Cycle Management System Life Cycle Processes ISO IEC 2504n Quality Evaluation Division The standards that form this division provide requirements recommendations and guidelines for software product evaluation whether performed by independent evaluators acquirers or developers The support for documenting a measure as an Evaluation Module is also presented ISO IEC 25050 to ISO IEC 25099 are reserved to be used for SQuaRE extension International Standards and or Technical Reports ISO IEC 2002 All rights reserved ISO IEC FCD 25040 2009 E This International Standard is part of the 2504n Quality Evaluation Division that currently consists of the following International Standards e ISO IEC 25040 Evaluation reference model and guide contains general requirements for specification and evaluation of software quality and clarifies the general concepts Provides a process description for evaluating quality of software product and states the requirements for the application of this process The evaluation process is the basis for software product quality evaluation for different purposes and approaches Therefore the process can be used for the evaluation of quality in use external measure of software quality
192. mittee SC 7 Software and System Engineering This document is a revision of the TR 25021 and a propose approach to prepare an IS SQUARE series of standards consists of the following divisions under the general title Software product Quality Requirements and Evaluation Quality Management Division Quality Model Division Quality Measurement Division Quality Requirements Division and Quality Evaluation Division Introduction The purpose of this document is to define and or design an initial set of Quality Measure Elements QME to be used throughout the software product life cycle for the purpose of software Product Quality Requirement and Evaluation SQuaRE The document also gives a set of rules to design a QME or verify the design of an existing QME call a measurement method ISO IEC 15939 The content of this document constitutes the link between the ISO IEC 9126 series of standards and the subsequent SQuaRE series of standards The necessary QMEs for quality measures that quantify some of the characteristic and sub characteristic represent an initial list which is to be used during the construction of the quality measures as referenced in ISO IEC TR 9126 2 ISO IEC TR 9126 3 and ISO IEC TR 9126 4 Quality measures presented in the SQuaRE series Figure 1 2 were extracted from ISO IEC TR 9126 series When evaluating selected quality measures the user should first understand the definition of each attribute related to a quality meas
193. n ISO IEC 15504 2 for each process in a process reference model appropriate to the specified requirements This informative part of ISO IEC 15504 provides guidance on how to create and utilize target process profiles to meet the need for this target capability This part of ISO IEC 15504 is being developed as a Technical Report Type 2 to enable experience in the use of the approach to setting Target Process Profiles to be gained In future revisions of the Standard it is likely that the content of this part will be integrated with part 4 of the standard The Technical Report provides guidelines for creating and using a target process profile These guidelines cover the following aspects a the defined purpose of the target process profile such as a process improvement initiative or process capability determination b the community of use such as automotive aerospace c the business requirement d the domain of application such as systems software IT services management e the categorization scheme for the domain of application such as safety critical systems f applicable processes or process reference models for the domain of application g the data and information to be collected to ensure the profile is relevant to the community of use business requirements domain of application and categorization scheme h the factors that when analysed transform the collected data or information into processes and process capability
194. n embedded typefaces In accordance with Adobe s licensing policy this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing In downloading this file parties accept therein the responsibility of not infringing Adobe s licensing policy The ISO Central Secretariat accepts no liability in this area Adobe is a trademark of Adobe Systems Incorporated Details of the software products used to create this PDF file can be found in the General Info relative to the file the PDF creation parameters were optimized for printing Every care has been taken to ensure that the file is suitable for use by ISO member bodies In the unlikely event that a problem relating to it is found please inform the Central Secretariat at the address given below Copyright notice This ISO document is a Draft International Standard and is copyright protected by ISO Except as permitted under the applicable laws of the user s country neither this ISO draft nor any extract from it may be reproduced stored in a retrieval system or transmitted in any form or by any means electronic photocopying recording or otherwise without prior written permission being secured Requests for permission to reproduce should be addressed to either ISO at the address below or ISO s member body in the country of the requester ISO copyright office Case postale 56 e CH 1211 Geneva 2
195. n is accurate fit for purpose and supports the users sufficiently in their use of software This standard addresses the management of user documentation development as it relates to both initial development and subsequent releases of the software and user documentation This International Standard was developed to assist users of ISO IEC 15288 2008 Systems engineering Systems life cycle process or ISO IEC 12207 2008 Information technology Software life cycle processes to manage software user documentation development as part of the software life cycle process It defines the documentation process from the manager s standpoint This standard was developed to assist those who provide input to perform and evaluate user documentation management NOTE Other International Standards in the ISO IEC 265NN series are in preparation or planned to address the documentation and information management processes from the viewpoint of documentation designers developers assessors and testers and acquirers and suppliers This International Standard is independent of the software tools that may be used to produce documentation and applies to both printed documentation and on screen documentation Much of its guidance is applicable to user documentation for systems including hardware as well as to software user documentation This International Standard conforms with ISO IEC 12207 2008 Information technology Software life cycle processes as an imp
196. n requirements for managers ISO IEC FCD 26512 Software and systems engineering Requirements for acquirers and suppliers of user documentation ISO IEC 26513 Systems and software engineering Requirements for testers and reviewers of user documentation JIS X 25000 SQuaRE SQuaRE JIS X 25051 SQuaRE COTS JIS TS X 0111 2 2 JSX0129 1 TS X 0111 3 3 JISX0129 1 TS X 0111 4 4 JISX0129 1 TR T JIS X 0145 3 3 JIS JIS X 0145 4 4 JIS X 0135 1 1 JIS X0135 3 3
197. n specifically part of quality e The internal and external quality models have been combined as the product quality model e When appropriate generic definitions have been adopted rather than using software specific definitions e Several characteristics and subcharacteristics have been given more accurate names Full details of the changes are in Annex A This International Standard is intended to be used in conjunction with the other parts of the SQuaRE series ISO IEC 25000 ISO IEC 25099 of standards and with ISO IEC 14598 until superseded by the ISO IEC 2504n series of standards Vi ISO IEC FCD 25010 Figure 1 adapted from ISO IEC 25000 illustrates the organisation of the SQuaRE series representing families of standards further called Divisions The Divisions within SQuaRE series are ISO IEC 2500n Quality Management Division The standards that form this division define all common models terms and definitions referred further by all other standards from SQuaRE series The division also provides requirements and guidance for a supporting function that is responsible for the management of software product quality requirements specification and evaluation Quality Model Division 2501n Quality Quality Management Quality Requirements Division Evaluation Division 2500n Division 2503n 2504n Quality Measurement Division 2502n Extension Division 25050 25099 Figure 1 Organization of SQuaRE series of In
198. nistrators who are not end users maintenance documentation describing the internal operation of systems software This International Standard is applicable for use by people who manage documentation designers and developers including persons performing the roles described in Clause 6 The standard may also be consulted by those with other roles and interests in the documentation process e managers of the software development process acquirers of documentation prepared by suppliers developers of tools for creating on screen documentation experienced authors and writers who develop the written content for user documentation human factors experts who identify principles for making documentation more accessible and easily used graphic designers with expertise in electronic media user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen This standard is intended for use in all types of organizations whether or not a dedicated documentation department is present In all cases it may be used as a basis for local standards and procedures Readers are assumed to have experience or general knowledge of testing or reviewing processes L 26511 lt applies to people or organizations producing suites of documentation and to those undertaking a single documentation project and documentation produced internally as well as to documentation contracted to outside p
199. nizational purposes as further defined in Clause 2 Applicability and Clause 3 Conformance NOTE ISO IEC 15504 5 Information technology Software process assessment Part 5 assessment model and indicator guidance provides guidance on the content of work products as well as information items Its guidance includes descriptions of a set of information items documents which an assessor may encounter The information items in its guidance may be produced by combinations and subdivisions of the required information items in this IS The life cycle processes result in many other work products and artifacts besides information items such as software and models These are outside the scope of this standard ISO IEC 2009 All rights reserved 1 ISO IEC CD 15289 2 Use of this International Standard is not limited by size complexity or criticality of the project It may be applied to a Any type of project and life cycle process b Any of the activities and tasks of a project and system or software product or service life cycle c All forms of information items information item content and document delivery media d Documentation in Commercial Off the Shelf COTS products when the COTS product is specified as a deliverable under a two party situation See ISO IEC 12207 2008 clause 1 2 This International Standard is intended for use to a Address the technical information needed by those involved in ISO IEC 15288 2008 and IS
200. not an ISO International Standard It is distributed for review and comment It is subject to change without notice and may not be referred to as an International Standard Recipients of this draft are invited to submit with their comments notification of any relevant patent rights of which they are aware and to provide supporting documentation Document type International Standard Document subtype Document stage 30 Committee Document language E Macintosh HD Users fcoallier Documents SC7 Secr tariat Documents mis par FC Serie N4501 07N4503 FCD ISO IEC 26512 1 doc STD Version 2 1 ISO IEC CD 26512 Copyright notice This ISO document is a working draft or committee draft and is copyright protected by ISO While the reproduction of working drafts or committee drafts in any form for use by participants in the ISO standards development process is permitted without prior permission from ISO neither this document nor any extract from it may be reproduced stored or transmitted in any form for any other purpose without prior written permission from ISO Requests for permission to reproduce this document for the purpose of selling it should be addressed as shown below or to ISO s member body in the country of the requester Indicate the full address telephone number fax number telex number and electronic mail address as appropriate of the Copyright Manger of the ISO member body responsible for the secretariat of the TC or SC wi
201. nt should be used during the activities of the evaluation process This International Standard is intended for those responsible for software product evaluation and is appropriate for developers acquirers and independent evaluators of software products These three different approaches are detailed in specific standards ISO IEC 14598 3 4 and 5 This International Standard is not intended for evaluation of other aspects of software products such as functional requirements process requirements business requirements etc 2 Conformance Evaluation of software product quality conforms to this International Standard if it complies with the requirements of clause 6 3 Normative references The following normative documents contain provisions which through reference in this text constitute provisions of ISO IEC 25040 For dated references subsequent amendments to or revisions of any of these publications do not apply However parties to agreements based on ISO IEC 25040 should investigate the possibility of applying the most recent editions of the normative documents indicated below For undated references the latest edition of the normative documents referred to applies Members of ISO and IEC maintain registers of currently valid International Standards References informative to this standard are listed in Bibliography ISO IEC 25000 Software engineering Software product Quality Requirements and Evaluation SQuaRE Guide to SQ
202. nts and Evaluation SQuaRE Common Industry Format CIF for usability test reports IS 2006 4 JIS SQuaRE 25001 25010 25021 25022 25023 25024 25030 25040 25045 C 2 1 3 1 2009 04 03 4 2 2009 05 08 45 3 2009 06 05 4 4 2009 07 31 amp 5 2009 09 04 4 6 2009 10 02 45 7 2009 10 30 45 8 2009 12 04 4 9 2010 01 08 10 20104202 H 158 A 11 2010 03 08 2 1 4 2 1 2 e IS TR 8 ISO IEC 25000 ISO IEC 25001 ISO IEC 25012 ISO IEC 25020 ISO IEC 25030 ISO IEC 25051 ISO IEC 25062 ISO IEC TR 25021 revision FCD CD
203. ocess is mapped to technical processes defined in ISO IEC 15288 Systems and software engineering System life cycle processes ISO IEC 2504n Quality Evaluation Division The International Standards that form this division provide requirements recommendations and guidelines for software product evaluation whether performed by evaluators acquirers or developers The support for documenting a measure as an Evaluation Module is also presented This International Standard is part of the Quality Evaluation Division ISO IEC 2504n which consists of the following International Standards see Figure 2 1 2 viii ISO IEC 25040 Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation reference model and guide contains general requirements for specification and evaluation of software quality and clarifies the general concepts It provides a process description for evaluating the quality of software products and states the requirements for the application of this process The evaluation process is the basis for software product quality evaluation for different purposes and approaches Therefore the process can be used for the evaluation of quality in use external software quality and internal software quality It can also be applied to evaluate the quality of pre developed software or custom software during its development process The software product quality evaluation can be conducted by an ac
204. on is drawn to the possibility that some of the elements of this document may be the subject of patent rights ISO and IEC shall not be held responsible for identifying any or all such patent rights ISO IEC 25040 makes a part of SQuaRE series of standards and was prepared by Joint Technical Committee ISO IEC JTC 1 information technology Subcommittee SC 7 Software and System Engineering SQuaRE series of standards consists of the following divisions under the general title Software product Quality Requirements and Evaluation e ISO IEC 2500n Quality Management Division e ISO IEC 2501n Quality Model Division e ISO IEC 2502n Quality Measurement Division e ISO IEC 2503n Quality Requirements Division and e ISO IEC 2504n Quality Evaluation Division Annex A provides an explanation on levels of evaluation aspects to be considered when defining evaluation levels and suggestions on evaluation techniques to be applied according to the rank of evaluation level Annex B provides examples of evaluation methods Annex C provides a table showing relationships between some evaluation methods possible costs rank and their effectiveness per software quality characteristics Annex D provides relationships between software product quality evaluation process reference model and software and system life cycle processes Annex E provides an example template for evaluation report Annex F provides common SQuaRE definitions from ISO IEC 250
205. ord ISO the International Organization for Standardization is a worldwide federation of national standards bodies ISO member bodies The work of preparing International Standards is normally carried out through ISO technical committees Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee International organizations governmental and non governmental in liaison with ISO also take part in the work ISO collaborates closely with the International Electrotechnical Commission IEC on all matters of electrotechnical standardization International Standards are drafted in accordance with the rules given in the ISO IEC Directives Part 2 The main task of technical committees is to prepare International Standards Draft International Standards adopted by the technical committees are circulated to the member bodies for voting Publication as an International Standard requires approval by at least 75 of the member bodies casting a vote Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights ISO shall not be held responsible for identifying any or all such patent rights ISO IEC 26512 was prepared by Technical Committee ISO IEC TC JTC1 Information technology Subcommittee SC 7 Software and system engineering This second third edition cancels and replaces the first second edition ISO 180
206. ormation security management for ITSM eee ceeeeee eren 47 5 4 Relationship processes REL sm 50 Bidet InitroductioN a 50 5 4 2 ITSM REL 1 Business relationship management for ITSM ee 50 5 4 3 ITSM REL 2 Supplier management for ITSMI ee 53 5 5 Resolution processes RES Sc nn ns cine 56 Bidet ioci leet 56 5 5 2 ITSM RES 1 Incident management for ITSM eee eieeeeen eese nennen nnne nnn nnns 56 ISO IEC 2009 All rights reserved iii N A 5 5 3 ITSM RES 2 Problem management for ITSM cccccssssceesseesseeeseeeesseeeseeeesseeeeeeeenseeeseoeeneessooenseees 57 5 6 Control processes CON aa aa ei nn 59 501 MER OCHO Disease SLT 59 5 6 2 ITSM CON 1 Configuration management for ITSM ee 59 5 6 3 ITSM CON 2 Change management for ITSM ccceeeeeseeesnseeeeeeeeeeeesneeeeeeeeeooeasseeeeeeeooeseneeeeees 60 5 7 FIGIEASE DIO66GSS RE 63 rs Ode TON PRE mmt 63 5 7 2 ITSM RLS 1 release management for ITSM ee 63 6 Process capability indicators level 1 to 5 ee 65 6 1 Level T Performed Drocess ne ele nee eon REN em nn Seem E ete eae ee eran ee ena ae eave mae 65 6 1 1 PA 1 1 Process performance attribute 0 65 6 2 Level 2 Managed DFOCOSS mm EN aaa aa 66 6 2 1 PA 2 1 Performance management attribute 0 66 6 2 2 PA 2 2 Work product management attribuyute 69 6 3 Level 3 Established DIOGBSS mm 71 6 3 1 PA 3 1 Process definition attribute Le 71 6 3 2 PA 3 2 Process deployment attribute 0 73 6 4 Levels Predictable DrOCES
207. ors or system administrators who are not end users e maintenance documentation describing the internal operation of systems software This International Standard is applicable to testers reviewers and other related roles including a variety of specialists e usability testers documentation reviewers and subject matter experts e information designers and architects who plan the structure and format of products in a documentation set ISO IEC 2009 All rights reserved ISO IEC 26513 2009 E e usability specialists and business analysts who identify the tasks the intended users will perform with the software The International Standard can also be consulted by those with other roles and interests in the documentation process Managers of the software development process or the documentation process should consider the testing of documentation as part of their planning and management activities Project managers in particular have an important role in planning the testing and reviewing of documentation Testing of the documentation is likely to highlight any defects or nonconformances in tools that are used to create or display on screen documentation Similarly usability testing of the documentation is likely to highlight defects or nonconformances with the presentation or layout of documentation and associated graphics and other media As a result there are a number of roles that should be involved in the testing of
208. ple majority vote of its participating members to publish a Technical Report A Technical Report is entirely informative in nature and does not have to be reviewed until the data it provides are considered to be no longer valid or useful Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights ISO shall not be held responsible for identifying any or all such patent rights ISO IEC TR 25060 was prepared by Technical Committee ISO TC JTC1 Information Technology Subcommittee SC SC7 Software and System Engineering in conjunction with ISO TC 159 Ergonomics SC 4 Human System Interaction ISO IEC 2008 All rights reserved V ISO IEC PDTR 25060 Introduction The purpose of this technical report is to define a framework and consistent terminology for the specification and evaluation of the usability of an interactive system Specifying and evaluating usability will assist those developing and acquiring interactive systems It describes a framework that defines a set of information items as part of a human centred approach to design of interactive system The framework is intended to assist in documenting and communicating usability related information through the system development life cycle The human centred design approach of ISO 9241 210 previously ISO 13407 is well established and focuses specifically on making systems usable Usability can be achieved by applying human centred
209. pplication cases offer help to all types of users The division also provides requirements and guidance for a supporting function which is responsible for the management of software product requirements specification and evaluation e ISO IEC 2501n Quality Model Division The International Standard that forms this division presents a detailed quality model including internal external and quality in use characteristics Furthermore the internal and external software quality characteristics are decomposed into sub characteristics Practical guidance on the use of the quality model is also provided e ISO IEC 2502n Quality Measurement Division The International Standards that form this division include a software product quality measurement reference model mathematical definitions of quality measures and practical guidance for their application Presented measures apply to internal software quality external software quality and quality in use Measurement primitives forming foundations for the latter measures are defined and presented e ISO IEC 2503n Quality Requirements Division The International Standard that forms this division helps in specifying quality requirements These quality requirements can be used in the process of quality requirements elicitation for a software product to be developed or as input for an evaluation process The ISO IEC 2009 All rights reserved Vii ISO IEC FDIS 25045 2009 E requirements definition pr
210. quirer a developer organization a supplier or an independent third party evaluator ISO IEC 250412 Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation modules defines the structure and content of the documentation to be used to describe an evaluation module These evaluation modules contain the specification of the quality model i e characteristics sub characteristics and corresponding internal external or quality in use measures the associated data and information about the planned application of the model and the information about its actual application Appropriate evaluation modules are selected for each evaluation In some cases it might be necessary to develop new evaluation modules Guidance for developing new evaluation modules is found in ISO IEC 25041 This International Standard can also be used by organizations producing new evaluation modules ISO IEC 25045 Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation module for recoverability provides the specification to evaluate the sub characteristic of recoverability defined under the characteristic of reliability of the quality model The ability of a software product and thereby a system to remain available or to recover within an acceptable timeframe from disturbance has always been important since a down time often has economic and other consequences The emphasis in recent years has
211. rnational Standard specifies processes for use in testing and reviewing of user documentation Clause 5 It is not limited to the test and review phase of the life cycle but includes activities throughout the Information Management and Documentation Management processes This International Standard provides the minimum requirements for the testing and reviewing of user documentation Clause 6 including both printed and on screen documents used in the work environment by the users of systems software It applies to printed user manuals online help tutorials and user reference documentation The order of clauses in this International Standard does not imply that the software user documentation should be tested in this order In each clause the requirements are media independent as far as possible The informative checklists found in Annexes A and B may be used at each phase of the documentation process to verify that the appropriate steps have been carried out and that the finished product has acceptable quality This International Standard can be helpful for testing and reviewing the following types of documentation e documentation of products other than software for example hardware or devices e multimedia systems using animation video and sound e computer based training CBT packages and specialized course materials intended primarily for use in formal training programs e documentation produced for installers computer operat
212. rocess for acquirers e ISO IEC 14598 5 Information technology Software product evaluation Part 5 Process for evaluators VI ISO IEC 2009 All rights reserved ISO IEC FDIS 25045 2009 E ISO IEC 25041 Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation modules will replace ISO IEC 14598 6 Software engineering Product evaluation Documentation of evaluation modules ISO IEC 25001 Software engineering Software product Quality Requirements and Evaluation SQuaRE Planning and management replaces ISO IEC 14598 2 Software engineering Product evaluation Part 2 Planning and management Quality Model Division 2501n Quality Quality Quality Requirements Management Division Evaluation Division Division 2500n 2503n 2504n Quality Measurement Division 2502n Figure 1 Organization of the SQuaRE series of International Standards Figure 1 illustrates the organization of the SQuaRE series representing families of standards also called divisions The divisions within SQuaRE model are e ISO IEC 2500n Quality Management Division The International Standards that form this division define all common models terms and definitions further referred to by all other International Standards from the SQuaRE series Referring paths guidance through SQuaRE documents and high level practical suggestions in applying proper standards to specific a
213. roducts used to create this PDF file can be found in the General Info relative to the file the PDF creation parameters were optimized for printing Every care has been taken to ensure that the file is suitable for use by ISO member bodies In the unlikely event that a problem relating to it is found please inform the Central Secretariat at the address given below COPYRIGHT PROTECTED DOCUMENT ISO IEC 2009 All rights reserved Unless otherwise specified no part of this publication may be reproduced or utilized in any form or by any means electronic or mechanical including photocopying and microfilm without permission in writing from either ISO at the address below or ISO s member body in the country of the requester ISO copyright office Case postale 56 e CH 1211 Geneva 20 Tel 41 22 749 01 11 Fax 41 22 749 09 47 E mail copyright iso org Web www iso org Published in Switzerland i ISO IEC 2009 All rights reserved ISO IEC 26513 2009 E Contents Page POLGWOELU eo tt occa ee Sac Ca dede tea aid teach verunt O ne ete et iv Introduction ee ws V 1 SCOPO BS 1 2 Coniormanee we 2 2 1 Definition OF CONOMANCR em 2 2 2 Conformance SITUATIONS nouo veto oda a eet en eu oct a dudes an nn opu se dt 3 3 Terms aNd delinillonDs a 3 4 User documentation process within the systems software life cycle 8 5 Documentation evaluation process
214. rved 1 Document Type Title Source Project Status References Action ID Due Date Start Date Distribution Medium No of Pages Note ISO IEC JTC1 SC7 44 9 Software and Systems Engineering INFORMATION TECHNOLOGY STANDARDS Secretariat CANADA SCC ISO IEC JTC1 SC7 N4513 2009 10 14 Combined CD Registration and CD Ballot Combined CD Registration and CD Ballot CD 15289 Systems and software engineering Content of life cycle information products Documentation WG2 15289 N4295 N4511 Resolution 1037 ACT 2010 03 17 2009 12 17 SC7 AG PDF 81 Please vote using the ISO Electronic Balloting Facilities Resolution 937 Address reply to ISO IEC JTC1 SC7 Secretariat cole de technologie sup rieure Departement of Software and IT Engineering 1100 Notre Dame Ouest Montr al Qu bec Canada H3C 1K3 secretariat a jtc 1 sc7 org www jtcl sc7 org ISO IEC 2009 All rights reserved ISO IEC JTC 1 SC 7 N Date 2009 10 30 ISO IEC CD 15289 2 ISO IEC JTC 1 SC 7 WNG 2 Secretariat ANSI Software and systems engineering Content of life cycle information products documentation Warning This document is not an ISO International Standard It is distributed for review and comment It is subject to change without notice and may not be referred to as an International Standard Recipients of this draft are invited to submit with their comments notification of any rel
215. sc7 org www jtcl sc7 org ISO IEC FCD 25040 2009 E ISO IEC JTC1 SC7 WG6 Nxxxx Date 18 January 2010 ISO IEC FCD 25040 TITLE Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation reference model and guide DATE 18 01 2010 SOURCE JTC1 SC7 WG6 WORK ITEM Project STATUS Version 4 DOCUMENT TYPE FCD ACTION Revision by Project editor before FDIS Ballot PROJECT Prof Motoei AZUMA EDITOR Department of Industrial Eng and Management Waseda University 3 4 1 Okubo Shinjuku ku Tokyo 169 8555 Japan azumam waseda jp DOCUMENT Danilo SCALET EDITOR CELEPAR Companhia de Informatica do Parana R Mateus Leme 1142 80530 010 Curitiba PR Brazil danilo pr gov br CO EDITOR Jorgen Bgegh Denmark joh terma com CO EDITOR Jean Marc Desharnais CA CO EDITOR Mary Theofanos USA CO EDITOR Nigel BEVAN UK nigel nigelbevan com CO EDITOR Kazuhiro Esaki Japan esaki kazuhiro ebara com ISO IEC 2002 All rights reserved ISO IEC FCD 25040 2009 E ISO IEC JTC 1 SC 7 Nxxx Date 2010 01 18 ISO IEC FCD 25040 ISO IEC JTC 1 SC 7 WG 6 Secretariat SCC Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation reference model and guide Warning This document is not an ISO International Standard It is distributed for review and comment It is subject to change without notice and may not be referred to as an International
216. shall is used to express a provision that is binding should to express a recommendation among other possibilities and may to indicate a course of action permissible within the limits of this International Standard When using this International Standard as a guide replace the term shall with should Use of the nomenclature of this standard for the parts of user documentation that is chapters topics pages screens windows is not required to claim conformance 2 2 Conformance situations Conformance of user documentation may be interpreted differently for various situations The relevant situation shall be identified in the claim of conformance e When conformance is claimed for an organization the organization shall make public a document declaring its tailoring of the life cycle process NOTE 1 One possible way for an organization to deal with clauses that cite the documentation plan is to specify that they shall be interpreted in the project plans for any particular documentation project e When conformance is claimed for a project the project plans or the contract shall document the tailoring of the documentation requirements NOTE 2 A projects claim of conformance is typically specified with respect to the organization s claim of conformance e When conformance is claimed for a multi supplier program it may be the case that no individual project may claim conformance because no single contract calls for all the req
217. sing results of system test of documentation 22 6 2 3 Problem resolution and the system test of documentation life cycle 22 6 3 Usability testing of documentation 1111 leeee eee ieeeeee ee ieeee eese nenne nnn nnn nnne nnn n nnns nnn 22 6 3 4 Objectives for usability testing of documentation 1 1eeeeee ec Leeeee eer eene nennen 23 6 3 2 Measures and metrics for documentation usability testing sss 23 6 3 3 Planning usability tests mm 24 6 3 4 Performing usability test of documentation ee eieeeee eec eeeeee reine eene nnne nnne n nnn 26 6 3 5 Problem resolution for documentation usability tests eee eeeeeee sss 27 6 4 Accessibility testing of documentation La 27 6 4 T Planning aceessibility TOSS 27 6 4 2 PEFOFMING ACCESSIDINITY LOSES EK 28 6 5 Localization and customization testing uaa 28 6 5 1 Planning for localization and customization testing 28 6 5 2 Performing localization and customization testing e eeeeee eee ceeeee erre nennen 28 6 6 Problem resoluti n process nn a a a a 29 Annex A informative Checklists for user documentation e ceres eee ceeeeee rennen 30 Annex B informative Test and review checkl
218. ssesseeesesesssesseesseeeseeee 6 2 X 0135 1 2008 ISO IEC 14143 1 2006 JIS X 0135 1 1999 ME JIS X 0135 JIS X 0135 1 1 JIS X 0135 2 2 JIS X 0135 1 1999 JIS X 0135 6 6 JISX013S 3 E JIS X 0135 1 2008 ISO IEC 14143 1 2006 rr zB
219. ssessment Part 8 An exemplar assessment model for IT service management Document type Technical Report Document subtype Document stage 20 Preparatory Document language E C Documents and Settingss1303 My Documents Standards lso Sc7 WG10 Part 8WG10N608_ISO IEC TR 15504 8 WD2 2009 04 27 doc STD Version 2 1 N A Copyright notice This ISO document is a Draft International Standard and is copyright protected by ISO Except as permitted under the applicable laws of the user s country neither this ISO draft nor any extract from it may be reproduced stored in a retrieval system or transmitted in any form or by any means electronic photocopying recording or otherwise without prior written permission being secured Requests for permission to reproduce should be addressed to either ISO at the address below or ISO s member body in the country of the requester ISO copyright office Case postale 56 e CH 1211 Geneva 20 Tel 41 22 749 01 11 Fax 41 22 749 09 47 E mail copyright iso org Web www iso org Reproduction may be subject to royalty payments or a licensing agreement Violators may be prosecuted II ISO IEC 2009 All rights reserved N A Contents Page xor V INtroducUuoOnN ee vi 1 CO 1 2 NonmallVerelerenmecess gi ee RN 1 3 Terms and d fmitloNS se ee doi ae nent nent net nest 2 4 Overview of the exemplar Process Assessment Model nr 2 4 1 INTFOCUCTION TO OVERVIEW wr da 2 4 2 Structure of the
220. sup rieure Departement of Software and IT Engineering 1100 Notre Dame Ouest M ontr al Qu bec Canada H 3C 1K 3 secretariat jtc1 sc7 org Www jtc1 sc7 org ISO IEC TC JTC1 SC SC7 N4257 Date 2007 01 12 26511 ISO IEC TC JTC1 SC SC7 WG 2 Secretariat Software and systems engineering User documentation requirements for managers l ment introductif l ment central l ment compl mentaire Document type International Standard Document subtype Document stage 20 Preparatory Document language E Macintosh HD Users fcoallier Documents SC7 Secr tariat Documents mis par FC S rie N4219 07N4257 26511 draft 20090116 doc STD Version 2 1 26511 Copyright notice This ISO document is a working draft or committee draft and is copyright protected by ISO While the reproduction of working drafts or committee drafts in any form for use by participants in the ISO standards development process is permitted without prior permission from ISO neither this document nor any extract from it may be reproduced stored or transmitted in any form for any other purpose without prior written permission from ISO Requests for permission to reproduce this document for the purpose of selling it should be addressed as shown below or to ISO s member body in the country of the requester Indicate the full address telephone number fax number telex number and electronic mail address as appropriate of the Copyright Manger of
221. t a reference 13 419 Meta Model mm 13 LEGCO T A A 13 E OME CS T A I CC 13 2122 Oray SE med EO eiae aE E E A CG 13 0 E TV li ee nase E A T E O E E EN E 13 424 Quality measure clement ae endum dnd in o a a a i es 13 4 25 Repeatability of results of measurement i 14 4 26 Reproductibility of results of measurement ss 14 Aar D E T i i i i 14 4 28 Unit of measur ment PERRO TOI EU TT em 14 5 Symbols and abbreviated termS 14 6 Quality measure elements concept in SPOM RM fr 14 7 Designing a Quality Measure Element QMBP 16 FM T troqductionm acaso baler Sate o De has bid Pario lea CANE 16 7 2 Identificabzon of the OM ES KK 17 7 3 Identification of the attribute used by the QME and definition of the attribute 18 7 4 Definition of the concepts related to the identified attribute eee 19 7 5 Construction of the meta model ex schema ertt eroe eR eod ees PEN Pa RERO Ree PEL HE eH pe Tes ree Eg Re 19 7 6 Assignment of the unit of measurement formula and scale type 21 7 7 Measurement method table of imformaton ee 21 8 Initial set of Quality Measure Elements OMES ttt 25 Od MISC CAS cC es 25 OMEN OnE TT e Un 25 OL Tes CaSe m lasse 30 8 9 Software tault mn 34 DE ITOL TNESSAG 6 om a
222. t not immediate possibility of an agreement on an International Standard type 3 when the joint technical committee has collected data of a different kind from that which is normally published as an International Standard state of the art for example Technical Reports of types 1 and 2 are subject to review within three years of publication to decide whether they can be transformed into International Standards Technical Reports of type 3 do not necessarily have to be reviewed until the data they provide are considered to be no longer valid or useful Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights ISO and IEC shall not be held responsible for identifying any or all such patent rights ISO IEC TR 15504 9 which is a Technical Report of type 2 was prepared by Joint Technical Committee ISO IEC JTC 1 Joint Technical Committee Information technology Subcommittee SC 7 Software and Systems Engineering ISO IEC 15504 consists of the following parts under the general title nformation Technology Process Assessment Part 1 Concepts and Vocabulary Part 2 Performing an Assessment Part 3 Guidance on performing an assessment Part 4 Guidance on use for process improvement and process capability determination Part 5 An exemplar Process Assessment Model Part 6 An exemplar system life cycle process assessment model IV ISO IEC 20
223. tation is also included in evaluation of the software product as in the ISO IEC 25000 series of standards In particular ISO IEC 25051 2006 Software engineering Software product Quality Requirements and Evaluation SQuaRE Requirements for quality of Commercial Off The Shelf COTS software product and instructions for testing The works listed in the Bibliography provide additional guidance on the processes of managing preparing and testing user documentation 2 Conformance This International Standard may be used as a conformance or a guidance document for projects and organizations claiming conformance to ISO IEC 15288 2008 Systems and software engineering System life cycle processes ISO IEC 12207 2008 Systems and software engineering Software life cycle processes or both 2 1 Definition of conformance When the selected software life cycle processes are tailored the organization or project may claim conformance to this International Standard for its documentation process Throughout this International Standard shall is used to express a provision that is binding should to express a recommendation among other possibilities and may to indicate a course of action permissible within the limits of this International Standard When using this International Standard as a guide replace the term shall with should 2 ISO IEC 2009 All rights reserved X 25000 2010 ISO IEC 25000 2005
224. ternational Standards ISO IEC 2501n Quality Model Division The standards that form this division present detailed quality models for computer systems and software product system quality in use and data Practical guidance on the use of the quality models is also provided ISO IEC 2502n Quality Measurement Division The standards that form this division include a software product quality measurement reference model mathematical definitions of quality measures and practical guidance for their application Examples are given of internal and external measures for software quality and measures for quality in use Quality Measure Elements QME forming foundations for these measures are defined and presented ISO IEC 2503n Quality Requirements Division The standards that form this division help specifying quality requirements using quality models and quality measures These quality requirements can be used in the process of quality requirements elicitation for a software product to be developed or as input for an evaluation process ISO IEC 2504n Quality Evaluation Division The standards that form this division provide requirements recommendations and guidelines for software product evaluation whether performed by evaluators acquirers or developers The support for documenting a measure as an Evaluation Module is also present ISO IEC 25050 25099 SQuaRE Extension Division These currently include Requirements for quality of Commer
225. terprise project and technical processes the ISO IEC 12207 2008 primary supporting and organizational life cycle processes or the ISO IEC 20000 1 2005 Service Management processes This International Standard identifies records and information items based on analysis of references in ISO IEC 15288 2008 ISO IEC 12207 2008 and ISO IEC 20000 1 2005 and 20000 2 2005 which in some cases provide partial or complete outlines for the content of specific documents However the requirements for the life cycle processes do not uniquely and unambiguously state the requirements for the information items contents or the information needed by a user of an information item Moreover the information from the life cycle processes may overlap or may be created and revised at different times In short the analyzed references do not result in a logically complete list of information items For each life cycle process it would be possible to prepare a plan procedures and reports as well as numerous records requests descriptions and specifications Such an elaboration of the documentation schema would be more rigorous than specified by ISO IEC 15288 2008 or ISO IEC 12207 2008 As ISO IEC 15288 2008 points out 1 4 This International Standard does not detail the life cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process Thus information items may be combined or subdivided as needed for project or orga
226. test edition of the normative document referred to applies Members of ISO and IEC maintain registers of currently valid International Standards ISO IEC 20000 4 yyyy Information technology Service management Part 4 Process Reference Model ISO IEC 2009 All rights reserved 1 ISO IEC JTC1 SC7 By Software and Systems Engineering INFORMATION TECHN OLOGY STANDARDS Secretariat CANADA SCC Document Type Title Source Project Status References Action ID Due Date Start Date Distribution Medium No of Pages Note ISO IEC J TC 1 SC7 N4170 2008 12 03 Combined WD circulation and PDTR registration ballot Combined WD circulation and PDTR Registration Ballot 15504 9 Information Technology Process Assessment Part 9 T arget Process Profiles WG10 15504 9 Final ACT 2009 03 05 2008 12 05 SC7 AG PDF 19 Please vote using the ISO Electronic Balloting Facilities Resolution 937 A ddress reply to ISO IEC JTC1 SC7 Secretariat cole de technologie sup rieure Departement of Software and IT Engineering 1100 Notre Dame Ouest M ontr al Qu bec Canada H 3C 1K 3 secretariat jtc1 sc7 org Www jtc1 sc7 org ISO IEC PDTR 15504 9 2 Contents Page gl po BET Iv INTFOGUGTIONT ee ee c NEUE vi 1 SCODG 1 2 NormativereferencCeS sm i 1 3 Terms
227. thin the framework of which the working document has been prepared Reproduction for sales purposes may be subject to royalty payments or a licensing agreement Violators may be prosecuted i ISO IEC 2009 All rights reserved ISO IEC CD 26512 iii ISO IEC 2009 All rights reserved ISO IEC CD 26512 Contents Page OFC WOM er nn fe eens vi TTOGUGC HON sect tm vi 1 SCODE ed a Li 1 2 ConformalicB cisini a aeaa ENN 2 2 1 DeTINITION OF CONIONMANC emt 2 2 2 Conformance SITUATIONS EE 3 3 Normalive Telerel COS iiio eee een nes sen nn EDI UR EOD E ede GEER eo state aV oM EEUU Pee Dea RUE RR tres 3 4 DETIMLIONS RE da M 3 5 User documentation within the systems software life cycle ss 9 5 1 Documentation Management Process Leeeee i eeeee esee eres eene n nnmnnn n nnnm n nnnm anna nnn nn 9 5 2 Information Management Process EE 10 6 User documentation agreement processes within the systems software life cycle 11 6 1 User Documentation Acquisition Process 1 ecce eieeeee eei eeeene seen e nnne n nnn nean nnn nnn nnne 11 6 1 1 Purpose or the Acquisition process aan 11 6 1 2 Outcomes of the Acquisition PrOCESS ne 11 6 2 User documentation Acquisition activities and tasks ee 12 621 Acdquisilion prepatalioN re RRRR 12 6 22 lt SUPDIIEF SCIECUON se a 1
228. tion SQuaRE Measurement of external quality ISOMEC 25021 e ISO IEC 25024 Software engineering Software product Quality Requirements and Evaluation SQuaRE Measurement of quality in use ISO IEC 25021 4 2503n 1 JIS X 0170 e ISO IEC 25030 Software engineering Software product Quality Requirements and Evaluation SQuaRE Quality requirements IS 2007 6 5 2504n 3 e ISO IEC 25040 Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation reference model and guide FCD e ISO IEC 25041 Software engineer
229. ttees collaborate in fields of mutual interest Other international organizations governmental and non governmental in liaison with ISO and IEC also take part in the work In the field of information technology ISO and IEC have established a joint technical committee ISO IEC JTC 1 International Standards are drafted in accordance with the rules given in the ISO IEC Directives Part 2 The main task of the joint technical committee is to prepare International Standards Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting Publication as an International Standard requires approval by at least 75 of the national bodies casting a vote Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights ISO and IEC shall not be held responsible for identifying any or all such patent rights ISO IEC 25010 is a part of the SQuaRE series of standards and was prepared by Joint Technical Committee ISO IEC JTC 1 information technology Subcommittee SC 7 Software and Systems Engineering The SQuaRE series of standards consists of the following divisions under the general title Software product Quality Requirements and Evaluation e ISO IEC 2500n Quality Management Division e ISO IEC 2501n Quality Model Division e ISO IEC 2502n Quality Measurement Division e ISO IEC 2503n Quality Requirements Division e ISO IEC 2504n Qu
230. ty measurement process The purpose of the SQuaRE set of standards is to assist those developing and acquiring software products with the specification and evaluation of quality requirements It establishes criteria for the specification of software product quality requirements their measurement and evaluation It includes a quality model for aligning customer definitions of quality with attributes of the development process In addition the series provides recommended measures of software product quality attributes that can be used by developers acquirers and evaluators SQuaRE provides e Terms and definitions e Reference models e General guide e Individual division guides and e Standards for requirements specification planning and management measurement and evaluation purposes SQuaRE includes international standards on quality model and measures as well as on quality requirements and evaluation SQUARE replaces the current ISO IEC 9126 series and the 14598 series This International Standard is intended to be used in conjunction with the other parts of the SQuaRE series of standards and with ISO IEC 14598 series and ISO IEC 9126 series until superseded by the ISO IEC 25000 series of standards Viii ISO IEC 2002 All rights reserved ISO IEC FCD 25040 2009 E Figure 1 Organisation of the SQuaRE series of standards Figure 1 illustrates the organisation of the SQuaRE series representing families of standards
231. uaRE ISO IEC 25001 Software engineering Software product Quality Requirements and Evaluation SQuaRE Planning and management ISO IEC 25010 Software engineering Software product Quality Requirements and Evaluation SQuaRE Quality model ISO IEC 2002 All rights reserved FINAL DRAFT ISO IEC JTC 1 Secretariat ANSI Voting begins on 2009 10 09 Voting terminates on 2009 12 09 RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT WITH THEIR COMMENTS NOTIFICATION OF ANY RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE AND TO PROVIDE SUPPORT ING DOCUMENTATION IN ADDITION TO THEIR EVALUATION AS BEING ACCEPTABLE FOR INDUSTRIAL TECHNO LOGICAL COMMERCIAL AND USER PURPOSES DRAFT INTERNATIONAL STANDARDS MAY ON OCCASION HAVE TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE MADE IN NATIONAL REGULATIONS 4 ISO IEC FDIS 25045 INTERNATIONAL STANDARD Software engineering Software product Quality Requirements and Evaluation SQuaRE Evaluation module for recoverability Ing nierie du logiciel Exigences de qualit et evaluation du logiciel SQuaRE Module d valuation pour la possibilit de r cup ration Please see the administrative notes on page iii Heference number ISO IEC FDIS 25045 2009 E LER ISO SSL ISO IEC 2009 ISO IEC FDIS 25045 2009 E PDF disclaimer This PDF file may contai
232. uent amendmenis to or revisions of any of these publications do not apply However parties to agreements based on this International Standard are encouraged to investigate the possibility of applying the most recent editions of the normative documents indicated below For undated references the latest edition of the normative document referred to applies Members of ISO and IEC maintain registers of currently valid International Standards lt 1BD gt 3 Terms and definitions For the purposes of the International Standard the definitions given in ISO IEC 15504 1 lt 33001 gt apply 4 The process dimension In this section the definitions of processes needed to support process assessments and to promote consistency with domain specific safety standards currently under development the Safety Extension is provided 4 1 Safety Management process ProcessID PP Safety Management Process The purpose of the Safety Management process is to ensure that the activities which are Purpose Necessary for the achievement of the required functional safety and safety policy objectives included those related to suppliers are planned their performance and results are monitored against the plan and possible deviations from plan are corrected Process 1 Safety principles and criteria are established to satisfy safety functions Outcomes 2 The scope of the safety activities for the project is defined ISO IEC 2009 All rights rese
233. uired activities Nevertheless the program as a whole may claim conformance if each of the required activities is produced by an identified party The program plans shall document the tailoring of the required tasks and their assignment to the various parties as well as the interpretation of clauses of the standard that reference the contract Document Type Title Source Project Status References Action ID Due Date Start Date Distribution Medium No of Pages Note ISO IEC JTC1 SC7 I I Software and Systems Engineering INFORMATION TECHNOLOGY STANDARDS Secretariat CANADA SCC ISO IEC JTC1 SC7 N4503 2009 10 14 FCD Ballot FCD 26512 Software and systems engineering Requirements for acquirers and suppliers of user documentation WG2 26512 N4221 N4501 N4502 ACT 2010 02 14 2009 10 14 SC7 AG PDF 44 Please vote using the ISO Electronic Balloting Facilities Resolution 937 Address reply to ISO IEC JTC1 SC7 Secretariat Ecole de technologie sup rieure Departement of Software and IT Engineering 1100 Notre Dame Ouest Montr al Qu bec Canada H3C 1K3 secretariat jtcl sc7 org www jtcl sc7 org ISO IEC 2009 All rights reserved TC JTC1 SC 7 N4503 Date 2009 06 15 ISO IEC CD 26512 ISO IEC TC JTC1 SC 7 WG 2 Secretariat Software and systems engineering Requirements for acquirers and suppliers of user documentation Warning This document is
234. umed to have experience or knowledge of general agreement processes for acquisition and supply of products and services The order of clauses in this International Standard does not imply that the acquisition activities should be performed in this order nor that documentation should be developed in this order or presented to the user in this order In each clause the requirements are media independent as far as possible The checklists in Annexes A and B may be used to track conformance with the requirements of this International Standard for acquirers and suppliers of documentation products The bibliography of works listed in Annex C provides guidance on the processes of acquiring and supplying user documentation 2 Conformance This International Standard may be used as a conformance or a guidance document for projects and organizations claiming conformance to ISO IEC 15288 2008 Systems engineering System life cycle processes or ISO IEC 12207 2008 Information technology Software life cycle processes 2 1 Definition of conformance Whether the organization or project has tailored the selected software life cycle processes or adopted them in full the organization or project may claim conformance to this International Standard for its acquisition or supply processes for user documentation This International Standard is meant to be tailored so that only necessary and cost effective requirements are applied Tailoring may take t
235. ure element used within the selected quality measures some important benefits from defining and using the quality measures elements in this document are e To provide guidance for different organisations to develop their own QMEs using a procedure different steps to implement the measurement method as defined in this document e To improve the consistency of measurement between different software within or across different organisations e To help identifying the set of quality measure elements that are uniquely required to derive all the quality measures for a given characteristics or a sub characteristics of a product The quality measure elements are the common components of a number of quality measures The intended usage of this document is that users will be able to select measures from valid quality measure elements to define internal external or quality in use quality measures Then these can be used for quality requirements definition software products evaluation and quality assessment but not necessary limited to those It is therefore recommended to use this document prior or together with the ISO IEC 2502n series of standards Note The justification of the selection of the initial set of QMEs is explained in annex A Quality Model Division 2501n Quality Requirements Evaluation Division E Division 2503n und 2504n I Quality Management Division Quality Measurement Division J502n Figure 1 Organisation
236. used in conjunction with the Part 5 and or Part 6 process assessment models by experienced assessors with minimal support from safety domain experts The Safety Extension is developed independent of any specific safety standards that define safety principles methods techniques and work products however elements of relevant safety standards are able to be mapped to the Safety Extensions and the Safety Extensions is intended to be extendable to include specific safety standards requirements Editors Notes are provided written in red and included between Editors notes indicate issues that the editors put in evidence and that should be discussed during the Working Group meetings ISO IEC 2009 All rights reserved V WORKING DRAFT ISO IEC PDTR 15504 10 Information technology Process assessment Part 10 Safety extension 1 Scope The scope of this part of the ISO IEC 15504 is to develop a Safety Extension that defines additional processes and guidance to support the use of the exemplar process assessment models for system and software ISO IEC 15504 Parts 5 and 6 when applied to the assessment of safety related systems developments in order to make consistent judgment regarding process capability and or improvement priorities 2 Normative references The following normative documents contain provisions which through reference in this text constitute provisions of this International Standard For dated references subseq
237. vice Cal al OO PNE en a i 61 Service level agreement SLA nn 61 Service Management plan si 61 Serkvice rebo ERES 62 Software architecture description ee 62 Software design description ne erii er ie eei Eo Lusia e eio sodas ase aves xeu Eon uva CR E ag apre DES x VEDO it ouse fe eecten es 63 Software requirements specification 11 e eese ieeeeeeeeee eese ee nnne nnne nnn nnns a nasa nua h nana 64 Software unit describtllo sn RE 65 Software unit test procedure ee 65 Software unit tesE FeDOTL sn RR 65 Supplier management procede ceu cause hae ous pde ione dent tt en co Eae tent eee 65 Supplier selection procedure ue cni ecco iia a manne REM ELE EUER pA Oct es ne ttes tee 66 System architecture description es 66 SYSTEM element descriIDUOFH a edu EE vsus RN 67 System requirements specification 2 5o ie esa Qoa ceo hawt hee a cob vpn io P cca qu cc epus eno gre lignes 67 FANNING documentatlion ee 67 ISO IEC 2009 All rights reserved ISO IEC CD 15289 2 107 TalmInmgi 68 10 75 User documentalon es 68 10 76 User notitiCatlON se EE 69 ANOLE allqation Dla TT E denses E eue cc uenn sen e cu anneau 69 VOLTS Valladtio n Te DOFLTt si ue NN NN 69 10 79 Validation test SDecifICatIoni odere ST NT a ERG 69 10 60 Veriicatlon io eme e etre some 69 10 61 VEFITMIC ATION Tepbo isis Hour ence bed esee LU qe Oe ue D couse cece am eo lh 71 Annex A informative Procedure for

Download Pdf Manuals

Related Search

Related Contents

Télécharger le manuel d`utilisation de ScienceDirect  DVD/CD-Player Lettore DVD/CD Lecteur de DVD/CD  DSL-G804V Wireless ADSL Router User's Guide  Aavara SW421 video mixer  Diptico Marauder 1600.FH11    Massive Wall light 17132/86/10  V4 user manual - the BGA Store  CDA FF181  PL - Novoferm  

Copyright © All rights reserved. Failed to retrieve file