Compiled by: Ali Azarkar (Padidpardaz Engineering Company)

SOFTWARE AND SYSTEMS ENGINEERING STANDARDS A COMPACT LIST Compiled by: Ali Azarkar (Padidpardaz Engineering Company) Release: 1.1, June 2009

We shall not cease from exploration, And the end of all our exploring, Will be to arrived where we started, And know the place for the first time. T. S. Eliot, Little Gidding, Four Quartets

Table of Content 1. Introduction...1 ISO/IEC Standards (JTC1/SC7)...4 2. ISO 5807:1985...5 3. ISO/IEC 9126-1:2001...6 4. ISO/IEC TR 9126-2:2003...7 5. ISO/IEC TR 9126-3:2003...9 6. ISO/IEC TR 9126-4:2004... 11 7. ISO/IEC TR 9294:2005... 12 8. ISO/IEC 25051:2006... 13 9. ISO/IEC 12207:2008... 14 10. ISO/IEC 14102:2008... 15 11. ISO/IEC 14143-1:2007... 17 12. ISO/IEC 14143-2:2002... 18 13. ISO/IEC TR 14143-3:2003... 19 14. ISO/IEC TR 14143-4:2002... 20 15. ISO/IEC TR 14143-5:2004... 21 16. ISO/IEC 14143-6:2006... 22 17. ISO/IEC TR 14471:2007... 23 18. ISO/IEC 14598-1:1999... 25 19. ISO/IEC 14598-2:2000... 26 20. ISO/IEC 14598-3:2000... 27 21. ISO/IEC 14598-4:1999... 28 22. ISO/IEC 14598-5:1998... 29 23. ISO/IEC 14598-6:2001... 30 24. ISO/IEC 14764:2006... 31 25. ISO/IEC TR 9294:2005... 33 26. ISO 9127:1988... 34 27. ISO/IEC TR 12182:1998... 35 28. ISO/IEC 12207:2008... 36 29. ISO/IEC 15026:1998... 37 30. ISO/IEC DTR 15026-1... 38 Page i Release: 1.1

31. ISO/IEC CD 15026-2... 39 32. ISO/IEC TR 15271:1998... 40 33. ISO/IEC 15288:2008... 41 34. ISO/IEC 15289:2006... 42 35. ISO/IEC 15504-1:2004... 43 36. ISO/IEC 15504-2:2003... 44 37. ISO/IEC 15504-3:2004... 46 38. ISO/IEC 15504-4:2004... 47 39. ISO/IEC 15504-5:2006... 48 40. ISO/IEC TR 15504-6:2008... 49 41. ISO/IEC TR 15504-7:2008... 51 42. ISO/IEC NP TR 15504-8... 53 43. ISO/IEC CD TR 15504-9... 54 44. ISO/IEC 15910:1999... 55 45. ISO/IEC 15939:2007... 56 46. ISO/IEC 15940:2006... 57 47. ISO/IEC 16085:2006... 58 48. ISO/IEC TR 16326:1999... 59 49. ISO/IEC TR FDIS 16326... 60 50. ISO/IEC DTR 18018.2... 61 51. ISO/IEC 19501:2005... 63 52. ISO/IEC TR 19759:2005... 64 53. ISO/IEC TR 19760:2003... 65 54. ISO/IEC 19770-1:2006... 66 55. ISO/IEC FCD 19770-2... 67 56. ISO/IEC NP 19770-3... 68 57. ISO/IEC DTR 24748... 69 58. ISO/IEC FDIS 24765... 70 59. ISO/IEC DTR 24766.2... 71 60. ISO/IEC 24773:2008... 72 61. ISO/IEC TR 24774:2007... 73 62. ISO/IEC CD TR 24774... 74 Page ii Release: 1.1

63. ISO/IEC 25000:2005... 75 64. ISO/IEC 25001:2007... 76 65. ISO/IEC CD 25010... 77 66. ISO/IEC 25012:2008... 78 67. ISO/IEC 25020:2007... 79 68. ISO/IEC TR 25021:2007... 80 69. ISO/IEC 25030:2007... 81 70. ISO/IEC CD 25040... 83 71. ISO/IEC FCD 25045... 84 72. ISO/IEC 25051:2006... 85 73. ISO/IEC CD 25060... 86 74. ISO/IEC 25062:2006... 87 75. ISO/IEC CD 26500... 88 76. ISO/IEC WD 26511... 89 77. ISO/IEC CD 26512... 90 78. ISO/IEC FCD 26513... 91 79. ISO/IEC 26514:2008... 92 80. ISO/IEC 26702:2007... 93 81. ISO/IEC CD 29118... 94 82. ISO/IEC AWI 29148... 95 83. ISO/IEC NP 29154... 96 84. ISO/IEC NP 29155... 97 85. ISO/IEC NP 29151... 98 86. ISO/IEC NP 29152... 99 87. ISO/IEC 42010:2007... 100 88. ISO/IEC CD 42010... 101 89. ISO/IEC NP 90003... 102 90. ISO/IEC 90003:2004... 103 91. ISO/IEC TR 90005:2008... 105 92. ISO/IEC NP 90006... 106 93. ISO/IEC 24744:2007... 107 IEEE Standards... 108 Page iii Release: 1.1

94. IEEE Std. 610-1990... 109 95. IEEE Std. 610.1... 110 96. IEEE std. 610.2-1987... 111 97. IEEE Std. 610.12-1990... 112 98. IEEE Std. 730-2002... 113 99. IEEE Std. P730... 114 100. IEEE Std. 828-2005... 115 101. IEEE Std. P828... 116 102. IEEE Std. 829-2008... 117 103. IEEE Std. 830-1998... 119 104. IEEE Std. 982.1-2005... 120 105. IEEE Std. 1008-1987... 121 106. IEEE Std. P1012... 122 107. IEEE Std. 1016-1998... 123 108. IEEE Std. 1028-2008... 124 109. IEEE Std. 1044-1993... 127 110. IEEE Std. 1058-1998... 128 111. IEEE Std.: 1058a-1998... 129 112. IEEE Std. 1061-1998... 130 113. IEEE Std. P1062... 131 114. IEEE Std. 1062a-1998... 133 115. IEEE Std. 1063-2001... 134 116. IEEE Std. 1074-2006... 135 117. IEEE Std. 1175.1-2002... 137 118. IEEE Std. 1175.2-2006... 138 119. IEEE Std. 1175.3-2004... 140 120. IEEE Std. 1175.4-2008... 141 121. IEEE Std. P1175.5... 143 122. IEEE Std. 1219-1998... 145 123. IEEE Std. 1220-2005... 146 124. IEEE Std. 1228-1994... 147 125. IEEE Std. 1233-1998... 148 Page iv Release: 1.1

126. IEEE Std. 1233a-1998... 150 127. IEEE Std. 1320.1-1998... 151 128. IEEE Std. 1320.2-1998... 152 129. IEEE Std. 1462-1998... 153 130. IEEE Std. 1465-1998... 154 131. IEEE Std. 1471-2000... 156 132. IEEE Std. 1517-1999... 159 133. IEEE Std. P1517... 161 134. IEEE Std. 1540-2001... 162 135. IEEE Std. P1648... 163 136. IEEE Std. P1723... 164 137. IEEE Std. 2001-2002... 165 138. IEEE Std. P2063... 166 139. IEEE Std. 12207-2008... 167 140. IEEE Std. 12207.1-1997... 169 141. IEEE Std. 12207.2-1997... 171 142. IEEE Std. 14143.1-2000... 172 143. IEEE Std. 14764-2006... 173 144. IEEE Std. P15026... 175 145. IEEE Std. 15288-2008... 176 146. IEEE Std. 15288-2007-2007... 178 147. IEEE Std. P15289... 179 148. IEEE Std. 15939-2008... 180 149. IEEE Std. 16085-2006... 182 150. IEEE Std. P20000.1... 183 151. IEEE Std. P20000.2... 184 152. IEEE Std. P24748... 185 153. IEEE Std. P24765... 187 154. IEEE Std. P25051... 188 155. IEEE Std. P42010... 190 156. IEEE Std. 90003-2008... 191 157. IEEE Std. ISO/IEC 23026:2006(E)-2006... 192 Page v Release: 1.1

158. IEEE Std. P1044... 194 159. IEEE Std. P16326... 196 160. IEEE Std. 1633-2008... 197 161. ISO/IEC 42010:2007(E)-2007... 198 Military Standards... 201 162. MIL-STD-498... 202 163. MIL-STD-961E... 205 164. MIL-STD-962D(1)... 206 165. DOD 4120.24-M... 207 166. MIL-STD-967... 208 167. DOD-STD-1679A... 209 168. DI-MCCR-80459... 210 169. DI-MCCR-80491A... 211 170. DI-MCCR-80700... 212 171. DI-MCCR-80902... 213 172. DI-IPSC-80942... 214 173. DI-NUOR-81412... 215 174. DI-IPSC-81427A... 216 175. DI-IPSC-81428A... 217 176. DI-IPSC-81429A... 218 177. DI-IPSC-81433A... 219 178. DI-IPSC-81435A... 220 179. DI-IPSC-81438A... 221 180. DI-IPSC-81439A... 222 181. DI-IPSC-81440A... 223 182. DI-IPSC-81441A... 224 183. DI-IPSC-81442A... 225 184. DI-IPSC-81443A... 226 185. DI-IPSC-81444A... 227 186. DI-IPSC-81445A... 228 187. DI-IPSC-81488... 229 188. DI-IPSC-81633... 230 Page vi Release: 1.1

189. DI-TMSS-81728... 231 190. DI-MGMT-81739... 232 191. DI-MGMT-81740... 233 192. DI-IPSC-81756... 234 193. MIL-HDBK-348(1) NOT 1... 235 194. MIL-HDBK-1467 NOT 1... 236 195. AQAP-150 ED.2... 237 196. AQAP-160 ED.1... 238 197. ITOP-1.1.056... 239 198. ITOP-1.1.057... 240 199. QAP-268 ED.1... 241 200. ISO15939... 242 British Standard Institute... 243 201. BS 4058:1987... 244 202. BS 5760-8:1998... 245 203. BS 7649:1993... 246 204. BS 7830:1996... 247 205. BS 7925-1:1998... 248 206. BS IEC 60300-3-6:1997... 249 207. BS IEC 61713:2000... 250 208. BS ISO/IEC 12207:2008... 251 209. BS ISO/IEC 14143-1:2007... 253 210. BS ISO/IEC 14143-2:2002... 254 211. BS ISO/IEC 14143-6:2006... 255 212. BS ISO/IEC 14598-1:1999... 256 213. BS ISO/IEC 14598-3:2000... 257 214. BS ISO/IEC 14598-4:1999... 258 215. BS ISO/IEC 14598-5:1998... 259 216. BS ISO/IEC 14598-6:2001... 260 217. BS ISO/IEC 14764:2006... 261 218. BS ISO/IEC 15026:1998... 262 219. BS ISO/IEC 15288:2002... 263 Page vii Release: 1.1

220. BS ISO/IEC 15289:2006... 264 221. BS ISO/IEC 15504-1:2004... 265 222. BS ISO/IEC 15504-2:2003... 266 223. BS ISO/IEC 15504-3:2004... 267 224. BS ISO/IEC 15504-4:2004... 268 225. BS ISO/IEC 15504-5:2006... 269 226. BS ISO/IEC 15910:1999... 270 227. BS ISO/IEC 15939:2007... 271 228. BS ISO/IEC 16085:2006... 272 229. BS ISO/IEC 16326:1999... 273 230. BS ISO/IEC 19770-1:2006... 274 231. BS ISO/IEC 24744:2007... 275 232. BS ISO/IEC 24773:2008... 276 233. BS ISO/IEC 25000:2005... 277 234. BS ISO/IEC 25001:2007... 278 235. BS ISO/IEC 25012:2008... 279 236. BS ISO/IEC 25020:2007... 280 237. BS ISO/IEC 25030:2007... 281 238. BS ISO/IEC 25051:2006... 282 239. BS ISO/IEC 25062:2006... 283 240. BS ISO/IEC 26514:2008... 284 241. BS ISO/IEC 26702:2007... 285 242. BS ISO/IEC 42010:2007... 286 243. BS ISO/IEC 90003:2004... 287 244. BS ISO/IEC 9126-1:2001... 288 245. BS ISO/IEC ISP 15287-2:2000... 289 246. BS ISO/IEC TR 12182:1998... 290 247. BS ISO/IEC TR 14143-4:2002... 291 248. BS ISO/IEC TR 14759:1999... 292 249. BS ISO/IEC TR 15271:1998... 293 250. BS ISO/IEC TR 15846:1998... 294 251. PD ISO/IEC TR 14143-3:2003... 295 Page viii Release: 1.1

252. PD ISO/IEC TR 14143-5:2004... 296 253. PD ISO/IEC TR 14471:2007... 297 254. PD ISO/IEC TR 15504-6:2008... 298 255. PD ISO/IEC TR 15504-7:2008... 299 256. PD ISO/IEC TR 19760:2003... 300 257. PD ISO/IEC TR 19760:2003... 301 258. PD ISO/IEC TR 24774:2007... 302 259. PD ISO/IEC TR 25021:2007... 303 260. PD ISO/IEC TR 90005:2008... 304 261. PD ISO/IEC TR 9126-2:2003... 305 262. PD ISO/IEC TR 9126-3:2003... 306 263. PD ISO/IEC TR 9126-4:2004... 307 264. PD ISO/IEC TR 9294:2005... 308 ANSI Standards... 309 British Computer Society... 310 ISIRI... 311 265. ISIRI - ISO 25001... 312 266. ISIRI-ISO 25030... 313 267. ISIRI 9965... 314 268. ISIRI 9966... 315 269. ISIRI 8168-1... 316 270. ISIRI 8168-2... 317 271. ISIRI 8168-3... 318 272. ISIRI 8168-4... 319 273. ISIRI 8168-5... 320 274. ISIRI 8168-6... 321 275. ISIRI 8168-7... 322 276. ISIRI 8168-8... 323 277. ISIRI 8173... 324 278. ISIRI 8174... 325 279. ISIRI 9147... 326 280. ISIRI 8085-1... 327 Page ix Release: 1.1

281. ISIRI 8085-2... 328 282. ISIRI 8085-3... 329 283. ISIRI 9796-1... 330 284. ISIRI 9796-2... 331 Page x Release: 1.1

1. Introduction This collection can be considered as a compact list of standards developed for software and system engineering. 1-1. Scope It covers most of important and relevant standards, developed and/or raised by major authorities in this context. To define its scope, some points should be cleared first: Major and more important standards (in order to be used and adopted somehow for domestic purposes) are listed. Information about standards are extracted from web sites of their corresponding formal authorities. With some exceptions, sithdrawn and superseded standards are not listed at all. More updated revisions are listed instead. This list is not complete; both in terms of covering all relevant standards and covering all types of standards (active, superseded, withdrawn, archive, and so on). More other resources, in addition to formal web sites, are given at the end of this Chapter. 1-2. Purpose The purpose of this document are: Providing a short list as well as introduction to important software and system engineering standards Enumerating relevant standards in the field 1-3. Document Structure The document is structured into Parts, Chapters and Sections. Each part lists standards proposed by a specific standardization body (e.g., ISO and IEEE). Each Chapter then Page 1 of 343 Release: 1.1

describes an individual standard. Sections gives more detailed information about each specific standard. 1-4. Document History Release 1.0: First draft of the document. (April 2009) Release 1.1: Document revised and updated. ISIRI standards added. References updated. Defense standards completed. (June 2009) 1-5. Copyright Notices This document is free to use and distribute. All comments regarding its enrichment and improvement are highly welcome and appreciated. 1-6. Resources & References [1] International Standard Organization: http://www.iso.ch [2] International Standard Organization Online Pages for Standards: http://www.iso.ch/iso/en/isoonline.openerpage [3] International Standard Organization SC7 (JTC1/SC7): http://www.jtc1-sc7.org [4] Institute of Electrical and Electronics Engineers (IEEE), Computer Society: http://www.computer.org/cspress/ [5] Institute of Electrical and Electronics Engineers (IEEE) Computer Society IEEE Computer Society/Software & Systems Engineering Standards Committee: http://standards.computer.org/sesc/index.htm [6] IEEEXplore Browsing Standards: http://ieeexplore.ieee.org/xpl/standards.jsp. The page allows finding a standard by its range (number), as well as its revision history. [7] Systems and Software Consortium: http://www.systemsandsoftware.org [8] International Electro-technical Commission (IEC): http://www.iec.ch. IEC is a notfor-profit, non-governmental international standards organization that prepares and publishes International Standards for all electrical, electronic and related technologies collectively known as "electro-technology". IEC standards cover a Page 2 of 343 Release: 1.1

vast range of technologies from power generation, transmission and distribution to home appliances and office equipment, semiconductors, fiber optics, batteries, solar energy, nanotechnology and marine energy as well as many others. The IEC also manages three global conformity assessment systems that certify whether equipment, system or components conform to its International Standards. [9] The International Council on Systems Engineering (INCOSE): http://www.incose.org. INCOSE is a not-for-profit membership organization founded in 1990. Its mission is to advance the state of the art and practice of systems engineering in industry, academia, and government by promoting interdisciplinary, scaleable approaches to produce technologically appropriate solutions that meet societal needs. [10] Defense Standardization Program (official US Department of Defense Repository): http://assistdocs.com. The site provides fast access to DoD standards for software engineering. [11] British Computer Society: http://www.bcs.org [12] British Standard Institute: http://www.bsi-global.com [13] Browsing British Standard Institute Standards (Software and Networking): http://www.standardsuk.com/shop/products_list.php?page=1 Page 3 of 343 Release: 1.1

ISO/IEC Standards (JTC1/SC7) Almost all standards regarding software and system engineering are developed by ISO JTC 1/SC 7 (Software and systems engineering) sub-committee. This part covers most important ISO/IEC standards regarding software and system engineering. Page 4 of 343 Release: 1.1

2. ISO 5807:1985 2-1. Title Information processing -- Documentation symbols and conventions for data, program and system flowcharts, program network charts and system resources charts 2-2. Abstract Defines symbols to be used in information processing documentation and gives guidance on conventions to their use in data flowcharts, program flowcharts, system flowcharts, program network charts, system resources charts. Applicable in conjunction with ISO 2382/1. 2-3. Status Published Standard Page 5 of 343 Release: 1.1

3. ISO/IEC 9126-1:2001 3-1. Title Software engineering -- Product quality -- Part 1: Quality model 3-2. Abstract 3-3. Status Revised. See ISO/IEC TR 9126-2:2003, ISO/IEC TR 9126-3:2003, and ISO/IEC TR 9126-4:2004 Page 6 of 343 Release: 1.1

4. ISO/IEC TR 9126-2:2003 4-1. Title Software engineering -- Product quality -- Part 2: External metrics 4-2. Abstract ISO/IEC TR 9126-2:2003 provides external metrics for measuring attributes of six external quality characteristics defined in ISO/IEC 9126-1. ISO/IEC TR 9126-2:2003 defines external metrics, ISO/IEC TR 9126-3 defines internal metrics and ISO/IEC 9126-4 defines quality in use metrics, for measurement of the characteristics or the subcharacteristics. Internal metrics measure the software itself, external metrics measure the behavior of the computer-based system that includes the software, and quality in use metrics measure the effects of using the software in a specific context of use. The metrics listed in ISO/IEC TR 9126-2:2003 are not intended to be an exhaustive set. Developers, evaluators, quality managers and acquirers may select metrics from ISO/IEC TR 9126-2:2003 for defining requirements, evaluating software products, measuring quality aspects and other purposes. Users of ISO/IEC TR 9126-2:2003 can select or modify and apply metrics and measures from ISO/IEC TR 9126-2:2003 or may define application-specific metrics for their individual application domain. ISO/IEC TR 9126-2:2003 is intended to be used together with ISO/IEC 9126-1. ISO/IEC TR 9126-2:2003 contains an explanation of how to apply software quality metrics, a basic set of metrics for each sub-characteristic and an example of how to apply metrics during the software product life cycle. ISO/IEC TR 9126-2:2003 does not assign ranges of values of these metrics to rated levels or to grades of compliance, because these values are defined for each software product or a part of the software product, by its nature, depending on such factors as category of the software, integrity level and users' needs. Some attributes may have a desirable range of values, which does not depend on specific user needs but depends on generic factors; for example, human cognitive factors. Page 7 of 343 Release: 1.1

4-3. Status Published Standard Page 8 of 343 Release: 1.1

5. ISO/IEC TR 9126-3:2003 5-1. Title Software engineering -- Product quality -- Part 3: Internal metrics 5-2. Abstract ISO/IEC TR 9126-3:2003 provides internal metrics for measuring attributes of six external quality characteristics defined in ISO/IEC 9126-1. ISO/IEC TR 9126-2 defines external metrics, ISO/IEC TR 9126-3:2003 defines internal metrics and ISO/IEC 9126-4 defines quality in use metrics, for measurement of the characteristics or the subcharacteristics. Internal metrics measure the software itself, external metrics measure the behavior of the computer-based system that includes the software, and quality in use metrics measure the effects of using the software in a specific context of use. The metrics listed in ISO/IEC TR 9126-3:2003 are not intended to be an exhaustive set. Developers, evaluators, quality managers, maintainers, suppliers, users and acquirers may select metrics from ISO/IEC TR 9126-3:2003 for defining requirements, evaluating software products, measuring quality aspects and other purposes. Users of ISO/IEC TR 9126-3:2003 can select or modify and apply metrics and measures from ISO/IEC TR 9126-3:2003 or may define application-specific metrics for their individual application domain. For internal metrics view, there are pure internal metrics proposed for reference purposes. ISO/IEC TR 9126-3:2003 is intended to be used together with ISO/IEC 9126-1. ISO/IEC TR 9126-3:2003 contains: an explanation of how to apply software quality metrics; a basic set of metrics for each sub-characteristic; an example of how to apply metrics during the software product life cycle. ISO/IEC TR 9126-3:2003 does not assign ranges of values of these metrics to rated levels or to grades of compliance, because these values are defined for each software product or a part of the software product, by its nature, depending on such factors as Page 9 of 343 Release: 1.1

category of the software, integrity level and users' needs. Some attributes may have a desirable range of values, which does not depend on specific user needs but depends on generic factors; for example, human cognitive factors. 5-3. Status Published Standard Page 10 of 343 Release: 1.1

6. ISO/IEC TR 9126-4:2004 6-1. Title Software engineering -- Product quality -- Part 4: Quality in use metrics 6-2. Abstract ISO/IEC TR 9126-4:2004 provides quality in use metrics for measuring the attributes defined in ISO/IEC 9126-1. ISO/IEC TR 9126-2 defines external metrics and ISO/IEC TR 9126-3 defines internal metrics for measurement of the sub-characteristics defined in ISO/IEC 9126-1. Internal metrics measure the software itself, external metrics measure the behavior of the computer-based system that includes the software, and quality in use metrics measure the effects of using the software in a specific context of use. The metrics listed in ISO/IEC TR 9126-4 are not intended to be an exhaustive set. Developers, evaluators, quality managers and acquirers may select metrics from ISO/IEC TR 9126-4 for defining requirements, evaluating software products, measuring quality aspects and other purposes. ISO/IEC TR 9126-2 is intended to be used together with ISO/IEC 9126-1. ISO/IEC TR 9126-4 contains: an explanation of how to apply software quality metrics; a basic set of metrics for each characteristic; and an example of how to apply metrics during the software product life cycle. It includes as informative annexes a quality in use evaluation process and a reporting format. 6-3. Status Published Standard Page 11 of 343 Release: 1.1

7. ISO/IEC TR 9294:2005 7-1. Title Information technology -- Guidelines for the management of software documentation 7-2. Abstract ISO/IEC TR 9294:2005 offers guidance on the management of software documentation to managers responsible for the production of software or software-based products. This guidance is intended to assist managers in ensuring that effective documentation is produced in their organizations. ISO/IEC TR 9294:2005 addresses the policies, standards, procedures, resources and plans with which managers must concern themselves in order to manage software documentation effectively. The guidance given is intended to be applicable to all types of software, from the simplest program to the most complex software suite or software system. All types of software documentation are covered, relating to all stages of the software life cycle. The principles of software documentation management are the same whatever the size of a project. For small projects, much of the detail given in ISO/IEC TR 9294:2005 may not apply, but the principles remain the same. Managers may tailor the recommendations to their particular needs. The guidance given is from the point of view of software documentation management. Detailed advice is not provided on, for example, the content and layout of software documents. 7-3. Status Published Standard Page 12 of 343 Release: 1.1

8. ISO/IEC 25051:2006 8-1. Title Software engineering -- Software product Quality Requirements and Evaluation (SQuaRE) -- Requirements for quality of Commercial Off-The-Shelf (COTS) software product and instructions for testing 8-2. Abstract ISO/IEC 25051:2005 defines quality requirements for COTS software products. A COTS software product includes the product description, the user documentation, and the software contained on a computer sensible media. The quality requirements, functionality, reliability, usability, efficiency, maintainability, portability, and quality in use are consistent with the definitions of SQuaRE. In addition to the quality requirements, ISO/IEC 25051:2005 also defines requirements for test documentation. The test documentation purpose is to demonstrate the conformity of the software with the requirements. The documentation contains a test plan, the description of the tests cases, and the tests results. ISO/IEC 25051:2005 can be used by suppliers, certification bodies, testing laboratories, accreditation bodies, regulatory authorities and acquirers. 8-3. Status Published Standard (Translated to Persian by ISIRI) Page 13 of 343 Release: 1.1

9. ISO/IEC 12207:2008 9-1. Title Systems and software engineering -- Software life cycle processes 9-2. Abstract ISO/IEC 12207:2008 establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware. ISO/IEC 12207:2008 applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. ISO/IEC 12207:2008 also provides a process that can be employed for defining, controlling, and improving software life cycle processes. The processes, activities and tasks of ISO/IEC 12207:2008 - either alone or in conjunction with ISO/IEC 15288 - may also be applied during the acquisition of a system that contains software. 9-3. Status Published Standard Page 14 of 343 Release: 1.1

10. ISO/IEC 14102:2008 10-1. Title Information technology -- Guideline for the evaluation and selection of CASE tools 10-2. Abstract Within systems and software engineering, Computer-Aided Software Engineering (CASE) tools represent a major part of the supporting technologies used to develop and maintain information technology systems. Their selection must be carried out with careful consideration of both the technical and management requirements. ISO/IEC 14102:2008 defines both a set of processes and a structured set of CASE tool characteristics for use in the technical evaluation and the ultimate selection of a CASE tool. It follows the software product evaluation model defined in ISO/IEC 14598-5:1998. ISO/IEC 14102:2008 adopts the general model of software product quality characteristics and sub-characteristics defined in ISO/IEC 9126-1:2001 and extends these when the software product is a CASE tool; it provides product characteristics unique to CASE tools. This larger set of characteristics is then organized into four groups: characteristics related to life cycle process functionality; characteristics related to CASE tool usage functionality; general quality characteristics; general characteristics not related to quality. This grouping provides a more manageable approach to the overall evaluation and selection process. The technical evaluation can indicate how well a CASE tool meets its user's stated requirements. It can also indicate how well the tool meets its claimed functionality. The objective of the technical evaluation process is to provide quantitative results on which the final selection can be based. Measurement assigns numbers (or other ratings) to attributes of entities; a major activity of evaluation is to obtain these Page 15 of 343 Release: 1.1

measurements for use in selection. The final selection results should aim to achieve objectivity, repeatability and impartiality. These objectives and the confidence in the outcomes will in part depend on the resources allocated to the overall evaluation and selection process. The user of ISO/IEC 14102:2008 is asked to deal with these issues at an early stage. To be widely acceptable, these CASE tool evaluation and selection processes must be of value to the users of CASE tools, and to the suppliers of CASE to the community at large. The information outlined in ISO/IEC 14102:2008 should lead to more cost effective selections of CASE tools and to a greater uniformity in how CASE tool functions and features are described. 10-3. Status Published Standard Page 16 of 343 Release: 1.1

11. ISO/IEC 14143-1:2007 11-1. Title Information technology -- Software measurement -- Functional size measurement -- Part 1: Definition of concepts 11-2. Abstract ISO/IEC 14143-1:2007 defines the concepts of FSM (Functional Size Measurement). The concepts of Functional Size Measurement (FSM) are designed to overcome the limitations of earlier methods of sizing software by shifting the focus away from measuring how the software is implemented to measuring size in terms of the functions required by the user. 11-3. Status Published Standard Page 17 of 343 Release: 1.1

12. ISO/IEC 14143-2:2002 12-1. Title Information technology -- Software measurement -- Functional size measurement -- Part 2: Conformity evaluation of software size measurement methods to ISO/IEC 14143-1:1998 12-2. Abstract 12-3. Status Revised. See: ISO/IEC 14143-2:2002 ISO/IEC 14143-1:2007 ISO/IEC TR 14143-3:2003 ISO/IEC TR 14143-4:2002 ISO/IEC TR 14143-5:2004 ISO/IEC 14143-6:2006 Page 18 of 343 Release: 1.1

13. ISO/IEC TR 14143-3:2003 13-1. Title Information technology -- Software measurement -- Functional size measurement -- Part 3: Verification of functional size measurement methods 13-2. Abstract ISO/IEC TR 14143-3:2003 establishes a framework for verifying the statements of an FSM Method and/or for conducting tests requested by the verification sponsor, relative to the following performance properties: repeatability and reproducibility; accuracy; convertibility; discrimination threshold; applicability to Functional Domains. NOTE Statements and test requests relative to other performance properties are outside the scope of ISO/IEC TR 14143-3:2003. ISO/IEC TR 14143-3:2003 aims to ensure that the output from the verification is objective, impartial, consistent and repeatable. The verification report, produced as a result of applying ISO/IEC TR 14143-3:2003, will enable the prospective user to select the FSM Method which best meets their needs. 13-3. Status Published Standard Page 19 of 343 Release: 1.1

14. ISO/IEC TR 14143-4:2002 14-1. Title Information technology -- Software measurement -- Functional size measurement -- Part 4: Reference model 14-2. Abstract 14-3. Status Published Standard Page 20 of 343 Release: 1.1

15. ISO/IEC TR 14143-5:2004 15-1. Title Information technology -- Software measurement -- Functional size measurement -- Part 5: Determination of functional domains for use with functional size measurement 15-2. Abstract ISO/IEC TR 14143-5:2004 describes the characteristics of Functional Domains and the procedures by which characteristics of Functional User Requirements (FUR) can be used to determine Functional Domains. Two example methods for implementing these principles are provided in the annexes. Either of the methods may be used directly, or by using Functional Domains defined locally by: FSM Method to determine if a particular FSM Method is applicable to the Functional Domain(s) represented by their specific FUR; Describing, for a given set of FUR, the Functional Domain to which the FUR belong; and FSM Method owners and designers describing the Functional Domain(s) to which the FSM Method can be applied as outlined in ISO/IEC 14143-1:1998. 15-3. Status Published Standard Page 21 of 343 Release: 1.1

16. ISO/IEC 14143-6:2006 16-1. Title Information technology -- Software measurement -- Functional size measurement -- Part 6: Guide for use of ISO/IEC 14143 series and related International Standards 16-2. Abstract ISO/IEC 14143-6:2006 provides a summary of the FSM (Functional Size Measurement) related International Standards and the relationship between; the ISO/IEC 14143 series FSM framework International Standards that provide the definitions and concepts of FSM and conformance and verification of FSMMs (Functional Size Measurement Methods), and the ISO/IEC standard FSMMs, i.e. ISO/IEC 19761, ISO/IEC 20926, ISO/IEC 20968 and ISO/IEC 24570. An FSMM is a software sizing method that conforms to the mandatory requirements of ISO/IEC 14143-1. ISO/IEC 14143-6 also provides a process to assist users to select an FSMM that meets their requirements. It also gives guidance on how to use Functional Size (FS). FSMMs include, but are not limited to, ISO/IEC 19761, ISO/IEC 20926, ISO/IEC 20968 and ISO/IEC 24570, as well. Recommending a specific FSMM is outside the scope of ISO/IEC 14143-6. 16-3. Status Published Standard Page 22 of 343 Release: 1.1

17. ISO/IEC TR 14471:2007 17-1. Title Information technology -- Software engineering -- Guidelines for the adoption of CASE tools 17-2. Abstract Since CASE (computer aided software engineering) adoption is a subject of the broader technology transition problem, ISO/IEC TR 14471:2007 addresses the adoption practices appropriate for a wide range of computing organizations. ISO/IEC TR 14471:2007 neither dictates nor advocates particular development standards, software processes, design methods, methodologies, techniques, programming languages, or life-cycle paradigms. ISO/IEC TR 14471:2007 will: identify critical success factors (CSF); propose a set of adoption processes; guide successful adoption in consideration of organizational and cultural environment. The following groups are targeted as potential audiences: CASE users; information systems managers; chief information officers (CIO); CASE suppliers; software engineering consultants; those involved in the acquisition of CASE tools and technology. Therefore ISO/IEC TR 14471:2007 addresses aspects of CASE tools adoption. It is best used in conjunction with ISO/IEC 14102 for CASE tool evaluation and selection. It is Page 23 of 343 Release: 1.1

complementary to related ISO/IEC documents which deal with the general aspects of these topics. The purpose of ISO/IEC TR 14471:2007 is to provide a recommended practice for CASE adoption. It provides guidance in establishing processes and activities that are to be applied for the successful adoption of CASE technology. The use of ISO/IEC TR 14471:2007 will help to maximize the return and minimize the risk of investing in CASE technology. However, ISO/IEC TR 14471:2007 does not establish compliance criteria. 17-3. Status Published Standard Page 24 of 343 Release: 1.1

18. ISO/IEC 14598-1:1999 18-1. Title Information technology -- Software product evaluation -- Part 1: General overview 18-2. Abstract 18-3. Status Published Standard Page 25 of 343 Release: 1.1

19. ISO/IEC 14598-2:2000 19-1. Title Software engineering -- Product evaluation -- Part 2: Planning and management 19-2. Abstract 19-3. Status Published Standard Page 26 of 343 Release: 1.1

20. ISO/IEC 14598-3:2000 20-1. Title Software engineering -- Product evaluation -- Part 3: Process for developers 20-2. Abstract 20-3. Status Published Standard Page 27 of 343 Release: 1.1

21. ISO/IEC 14598-4:1999 21-1. Title Software engineering -- Product evaluation -- Part 4: Process for acquirers 21-2. Abstract 21-3. Status Published Standard Page 28 of 343 Release: 1.1

22. ISO/IEC 14598-5:1998 22-1. Title Information technology -- Software product evaluation -- Part 5: Process for evaluators 22-2. Abstract 22-3. Status Published Standard Page 29 of 343 Release: 1.1

23. ISO/IEC 14598-6:2001 23-1. Title Software engineering -- Product evaluation -- Part 6: Documentation of evaluation modules 23-2. Abstract 23-3. Status Published Standard Page 30 of 343 Release: 1.1

24. ISO/IEC 14764:2006 24-1. Title Software Engineering -- Software Life Cycle Processes -- Maintenance 24-2. Abstract ISO/IEC 14764:2006 describes in greater detail management of the Maintenance Process described in ISO/IEC 12207, including Amendments. It also establishes definitions for the various types of maintenance. ISO/IEC 14764:2006 provides guidance that applies to planning, execution and control, review and evaluation, and closure of the Maintenance Process. The scope of ISO/IEC 14764:2006 includes maintenance for multiple software products with the same maintenance resources. "Maintenance" in ISO/IEC 14764:2006 means software maintenance unless otherwise stated. ISO/IEC 14764:2006 provides the framework within which generic and specific software maintenance plans may be executed, evaluated, and tailored to the maintenance scope and magnitude of given software products. It provides the framework, precise terminology and processes to allow the consistent application of technology (tools, techniques and methods) to software maintenance. ISO/IEC 14764:2006 provides guidance for the maintenance of software. The basis for the Maintenance Process and its activities comes from the definitions of ISO/IEC 12207. It defines the activities and tasks of software maintenance, and provides maintenance planning requirements. It does not address the operation of software and the operational functions, e.g. backup, recovery and system administration, which are normally performed by those who operate the software. ISO/IEC 14764:2006 is written primarily for maintainers of software and additionally for those responsible for development and quality assurance. It may also be used by acquirers and users of systems containing software who may provide inputs to the maintenance plan. Page 31 of 343 Release: 1.1

24-3. Status Published Standard Page 32 of 343 Release: 1.1

25. ISO/IEC TR 9294:2005 25-1. Title Information technology -- Guidelines for the management of software documentation 25-2. Abstract ISO/IEC TR 9294:2005 offers guidance on the management of software documentation to managers responsible for the production of software or software-based products. This guidance is intended to assist managers in ensuring that effective documentation is produced in their organizations. ISO/IEC TR 9294:2005 addresses the policies, standards, procedures, resources and plans with which managers must concern themselves in order to manage software documentation effectively. The guidance given is intended to be applicable to all types of software, from the simplest program to the most complex software suite or software system. All types of software documentation are covered, relating to all stages of the software life cycle. The principles of software documentation management are the same whatever the size of a project. For small projects, much of the detail given in ISO/IEC TR 9294:2005 may not apply, but the principles remain the same. Managers may tailor the recommendations to their particular needs. The guidance given is from the point of view of software documentation management. Detailed advice is not provided on, for example, the content and layout of software documents. 25-3. Status Published Standard Page 33 of 343 Release: 1.1

26. ISO 9127:1988 26-1. Title Information processing systems -- User documentation and cover information for consumer software packages 26-2. Abstract Describes user documentation and cover information supplied with software packages. Is applicable to software packages sold off-the-shelf to consumers for business, scientific, educational and home use. References: ISO 6592; ISO 7185. 26-3. Status Published Standard Page 34 of 343 Release: 1.1

27. ISO/IEC TR 12182:1998 27-1. Title Information technology -- Categorization of software 27-2. Abstract 27-3. Status Published Standard Page 35 of 343 Release: 1.1

28. ISO/IEC 12207:2008 28-1. Title Systems and software engineering -- Software life cycle processes 28-2. Abstract ISO/IEC 12207:2008 establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware. ISO/IEC 12207:2008 applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. ISO/IEC 12207:2008 also provides a process that can be employed for defining, controlling, and improving software life cycle processes. The processes, activities and tasks of ISO/IEC 12207:2008 - either alone or in conjunction with ISO/IEC 15288 - may also be applied during the acquisition of a system that contains software. 28-3. Status Published Standard Page 36 of 343 Release: 1.1

29. ISO/IEC 15026:1998 29-1. Title Information technology -- System and software integrity levels 29-2. Abstract 29-3. Status Published Standard Page 37 of 343 Release: 1.1

30. ISO/IEC DTR 15026-1 30-1. Title Systems and Software Engineering -- Systems and Software Assurance -- Part 1: Concepts and vocabulary 30-2. Abstract 30-3. Status Under-Development Standard Page 38 of 343 Release: 1.1

31. ISO/IEC CD 15026-2 31-1. Title Systems and Software Engineering -- Systems and Software Assurance -- Part 2: Assurance case 31-2. Abstract 31-3. Status Under-Development Standard Page 39 of 343 Release: 1.1

32. ISO/IEC TR 15271:1998 32-1. Title Information technology -- Guide for ISO/IEC 12207 (Software Life Cycle Processes) 32-2. Abstract 32-3. Status Published Standard Page 40 of 343 Release: 1.1

33. ISO/IEC 15288:2008 33-1. Title Systems and software engineering -- System life cycle processes 33-2. Abstract ISO/IEC 15288:2008 establishes a common framework for describing the life cycle of systems created by humans. It defines a set of processes and associated terminology. These processes can be applied at any level in the hierarchy of a system's structure. Selected sets of these processes can be applied throughout the life cycle for managing and performing the stages of a system's life cycle. This is accomplished through the involvement of all interested parties, with the ultimate goal of achieving customer satisfaction. ISO/IEC 15288:2008 also provides processes that support the definition, control and improvement of the life cycle processes used within an organization or a project. Organizations and projects can use these life cycle processes when acquiring and supplying systems. ISO/IEC 15288:2008 concerns those systems that are man-made and may be configured with one or more of the following: hardware, software, data, humans, processes (e.g., processes for providing service to users), procedures (e.g., operator instructions), facilities, materials and naturally occurring entities. When a system element is software, the software life cycle processes documented in ISO/IEC 12207:2008 may be used to implement that system element. ISO/IEC 15288:2008 and ISO/IEC 12207:2008 are harmonized for concurrent use on a single project or in a single organization. 33-3. Status Published Standard Page 41 of 343 Release: 1.1

34. ISO/IEC 15289:2006 34-1. Title Systems and software engineering -- Content of systems and software life cycle process information products (Documentation) 34-2. Abstract ISO/IEC 15289:2006 was developed to assist users of systems and software life cycle processes to manage information items (documents). It is based on the life cycle processes specified in ISO/IEC 15288 or ISO/IEC 12207:1995/AMD 1:2002/AMD 2. Information items are essential to preserving what transpired when using system life cycle processes, and may be identified as deliverable documents. ISO/IEC 15289:2006 identifies the purpose and content of all identified systems and software life cycle information items as required for the various life cycle processes. The information item contents are defined according to generic document types (which may be referred to as information item types) and the specific purpose of the document. ISO/IEC 15289:2006 may be applied to any of the activities and tasks of a project, system or software product, or service life cycle. It is not limited by the size, complexity or criticality of the project. It may be applied to all forms of information items, information item content, and document delivery media. Information items may be combined or subdivided as needed for project or organizational purposes. The nomenclature for information items, document titles and contents is informative. 34-3. Status Published Standard Page 42 of 343 Release: 1.1

35. ISO/IEC 15504-1:2004 35-1. Title Information technology -- Process assessment -- Part 1: Concepts and vocabulary 35-2. Abstract This part of ISO/IEC 15504:2004 provides overall information on the concepts of process assessment and its use in the two contexts of process improvement and process capability determination. It describes how the parts of the suite fit together, and provides guidance for their selection and use. It explains the requirements contained within ISO/IEC 15504, and their applicability to performing assessments. Readers of this guide should familiarize themselves with the terminology and structure of the document suite, and then reference the appropriate parts of the suite for the context in which they propose to conduct an assessment. A more detailed description of the use of ISO/IEC 15504 is given in clause 4. 35-3. Status Published Standard Page 43 of 343 Release: 1.1

36. ISO/IEC 15504-2:2003 36-1. Title Information technology -- Process assessment -- Part 2: Performing an assessment 36-2. Abstract ISO/IEC 15504-2:2003 defines the requirements for performing process assessment as a basis for use in process improvement and capability determination. Process assessment is based on a two dimensional model containing a process dimension and a capability dimension. The process dimension is provided by an external process reference model, which defines a set of processes characterized by statements of process purpose and process outcomes. The capability dimension consists of a measurement framework comprising six process capability levels and their associated process attributes. The assessment output consists of a set of process attribute ratings for each process assessed, termed the process profile, and may also include the capability level achieved by that process. ISO/IEC 15504-2:2003 identifies the measurement framework for process capability and the requirements for: performing an assessment; process reference models; process assessment models; verifying conformity of process assessment. The requirements for process assessment defined in ISO/IEC 15504-2:2003 form a structure which: facilitates self-assessment; provides a basis for use in process improvement and capability determination; takes into account the context in which the assessed process is implemented; Page 44 of 343 Release: 1.1

produces a process rating; addresses the ability of the process to achieve its purpose; is applicable across all application domains and sizes of organization; and may provide an objective benchmark between organizations. The minimum set of requirements defined in ISO/IEC 15504-2:2003 ensures that assessment results are objective, impartial, consistent, repeatable and representative of the assessed processes. Results of conformant process assessments may be compared when the scopes of the assessments are considered to be similar; for guidance on this matter, refer to ISO/IEC 15504-4. 36-3. Status Published Standard Page 45 of 343 Release: 1.1

37. ISO/IEC 15504-3:2004 37-1. Title Information technology -- Process assessment -- Part 3: Guidance on performing an assessment 37-2. Abstract ISO/IEC 15504 (all parts) provides a framework for the assessment of processes. This framework can be used by organizations involved in planning, managing, monitoring, controlling and improving the acquisition, supply, development, operation, evolution and support of products and services. ISO/IEC 15504-3:2004 provides guidance on meeting the minimum set of requirements for performing an assessment contained in ISO/IEC 15504-2. It provides an overview of process assessment and interprets the requirements through the provision of guidance on: performing an assessment; the measurement framework for process capability; process reference models and process assessment models; selecting and using assessment tools; competency of assessors; verification of conformity. ISO/IEC 15504-3:2004 also provides an exemplar documented assessment process that conforms to the requirements of 4.2 in ISO/IEC 15504-2. 37-3. Status Published Standard Page 46 of 343 Release: 1.1

38. ISO/IEC 15504-4:2004 38-1. Title Information technology -- Process assessment -- Part 4: Guidance on use for process improvement and process capability determination 38-2. Abstract ISO/IEC 15504 (all parts) provides a framework for the assessment of processes. This framework can be used by organizations involved in planning, managing, monitoring, controlling and improving the acquisition, supply, development, operation, evolution and support of products and services. ISO/IEC 15504-3:2004 provides guidance on meeting the minimum set of requirements for performing an assessment contained in ISO/IEC 15504-2. It provides an overview of process assessment and interprets the requirements through the provision of guidance on: performing an assessment; the measurement framework for process capability; process reference models and process assessment models; selecting and using assessment tools; competency of assessors; verification of conformity. ISO/IEC 15504-3:2004 also provides an exemplar documented assessment process that conforms to the requirements of 4.2 in ISO/IEC 15504-2. 38-3. Status Published Standard Page 47 of 343 Release: 1.1

39. ISO/IEC 15504-5:2006 39-1. Title Information technology -- Process Assessment -- Part 5: An exemplar Process Assessment Model 39-2. Abstract ISO/IEC 15504-5:2006 describes an exemplar Process Assessment Model (PAM), conformant with the ISO/IEC 15504-2 requirements for PAM. It provides guidance by way of example, on the nature and structure of PAMs, and on the variety and function of different indicators of process performance and capability. It also provides guidance, through example, on the requirements for conformance of PAMs, and on the approaches for demonstration of conformance. ISO/IEC 15504 provides a framework for the assessment of process capability. This framework can be used by organizations involved in planning, managing, monitoring, controlling and improving the acquisition, supply, development, operation, evolution and support of products and services. ISO/IEC 15504 provides a framework for the assessment of process capability. This framework can be used by organizations involved in planning, managing, monitoring, controlling and improving the acquisition, supply, development, operation, evolution and support of products and services. It is also intended for use by assessors in the performance of process assessment, and by organizations involved in the development of process reference models, process assessment models or process assessment processes. 39-3. Status Published Standard Page 48 of 343 Release: 1.1

40. ISO/IEC TR 15504-6:2008 40-1. Title Information technology -- Process assessment -- Part 6: An exemplar system life cycle process assessment model 40-2. Abstract ISO/IEC 15504 provides a framework for the assessment of process capability. This framework can be used by organizations involved in planning, managing, monitoring, controlling and improving the acquisition, supply, development, operation, evolution and support of products and services. ISO/IEC TR 15504-6:2008 describes an exemplar Process Assessment Model (PAM) for system life cycle processes, conformant with the ISO/IEC 15504-2 requirements for a PAM. The ISO/IEC TR 15504-6:2008 exemplar PAM is derived from the Process Reference Model (PRM) defined in ISO/IEC 15288, associated with the process attributes defined in ISO/IEC 15504-2. The resulting PAM is a two-dimensional PAM which provides indicators for guidance on the interpretation of the process purposes and outcomes as defined in ISO/IEC 15288, and the process attributes as defined in ISO/IEC 15504-2. It can be used to perform a process assessment conformant with ISO/IEC 15504-2, either in the context of a process improvement programme or for process capability determination. ISO/IEC TR 15504-6:2008 describes: the overall structure of the PAM with its process dimension (derived from ISO/IEC 15288) and capability dimension (derived from the measurement framework defined in ISO/IEC 15504-2); process performance indicators (base practices and work products) for 26 processes drawn from ISO/IEC 15288; process capability indicators (generic practices, generic resources and generic work products) which characterize, for any process attribute of the capability Page 49 of 343 Release: 1.1