SOFTWARE AND SYSTEMS ENGINEERING...

SSOOFFTTWWAARREE AANNDD SSYYSSTTEEMMSS

EENNGGIINNEEEERRIINNGG SSTTAANNDDAARRDDSS ––

AA CCOOMMPPAACCTT LLIISSTT

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

SOFTWARE AND SYSTEMS ENGINEERING STANDARDS – A COMPACT LIST

Page i Release: 1.1

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 ii 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 iii 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 iv 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 v 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 vi 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 vii 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 viii 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 ix 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 x Release: 1.1

281. ISIRI 8085-2 ................................................................................................................ 328

282. ISIRI 8085-3 ................................................................................................................ 329

283. ISIRI 9796-1 ................................................................................................................ 330

284. ISIRI 9796-2 ................................................................................................................ 331


Page 1 of 343 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



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 not-for-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



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



IISSOO//IIEECC SSttaannddaarrddss ((JJTTCC11//SSCC77)) 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.



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



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



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 sub-characteristics. 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.



4-3. Status

Published Standard



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 sub-characteristics. 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



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



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



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



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)



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



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



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



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



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



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



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



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



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



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



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



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



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



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



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



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



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



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.



24-3. Status

Published Standard



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



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



27. ISO/IEC TR 12182:1998

27-1. Title

Information technology -- Categorization of software

27-2. Abstract

27-3. Status

Published Standard



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



29. ISO/IEC 15026:1998

29-1. Title

Information technology -- System and software integrity levels

29-2. Abstract

29-3. Status

Published Standard



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



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




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



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



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



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



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;



• 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



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:


• 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



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:


• 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



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



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



dimension, what are the expected characteristics that demonstrate achievement of that process attribute.

ISO/IEC TR 15504-6:2008 also includes

• the demonstration of conformity of the PAM with the requirements of ISO/IEC 15504-2;

• the detailed characteristics of the work products and the generic work products;

• guidance for adapting the PAM and defining additional assessment indicators.

40-3. Status

Published Standard



41. ISO/IEC TR 15504-7:2008

41-1. Title

Information technology -- Process assessment -- Part 7: Assessment of organizational maturity

41-2. Abstract

ISO/IEC 15504 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 TR 15504-7:2008 defines the conditions for an assessment of organizational maturity; it defines a framework for determining organizational maturity, based upon profiles of process capability derived from process assessment, and defines the conditions under which such assessments are valid.

ISO/IEC TR 15504-7:2008, organizational maturity is an expression of the extent to which an organization consistently implements processes within a defined scope that contributes to the achievement of its business goals (current or projected). An Organizational Maturity Model is based upon one or more specified Process Assessment Model(s), and addresses the domains and contexts for use of the Process Reference Model(s) from which the Process Assessment Model(s) are derived.

The assessment of organizational maturity is undertaken through the performance of process assessment as specified in ISO/IEC 15504-2. Specific conditions are defined in ISO/IEC TR 15504-7:2008 relating to the process scope of the organizational maturity assessment, the organizational scope of the assessment (which has to be specified as representing the elements characterized by the organizational maturity rating), and the data collection strategy (which needs to ensure that the results of the assessment are representative of the organizational scope). On completion of the assessment, the set of process profiles established for the organization determine the rating of the level of



organizational maturity based on the framework defined in ISO/IEC 15504-7, as specified in the relevant Organizational Maturity Model.

ISO/IEC TR 15504-7:2008 also contains guidance on implementing the requirements for constructing an Organizational Maturity Model; on performing assessments of organizational maturity; and on the application of organizational maturity ratings for process improvement and capability determination.

41-3. Status

Withdrawn Standard



42. ISO/IEC NP TR 15504-8

42-1. Title

Information technology -- Software process assessment -- Part 8: An exemplar process assessment model for IT service management

42-2. Abstract

42-3. Status




43. ISO/IEC CD TR 15504-9

43-1. Title

Information technology -- Software process assessment -- Part 9: Capability Target Profiles

43-2. Abstract

43-3. Status




44. ISO/IEC 15910:1999

44-1. Title

Information technology -- Software user documentation process

44-2. Abstract

44-3. Status

Published Standard



45. ISO/IEC 15939:2007

45-1. Title

Systems and software engineering -- Measurement process

45-2. Abstract

ISO/IEC 15939:2007 defines a measurement process applicable to system and software engineering and management disciplines. The process is described through a model that defines the activities of the measurement process that are required to adequately specify what measurement information is required, how the measures and analysis results are to be applied, and how to determine if the analysis results are valid. The measurement process is flexible, tailorable, and adaptable to the needs of different users.

ISO/IEC 15939:2007 identifies a process that supports defining a suitable set of measures that address specific information needs. It identifies the activities and tasks that are necessary to successfully identify, define, select, apply and improve measurement within an overall project or organizational measurement structure. It also provides definitions for measurement terms commonly used within the system and software industries.

45-3. Status

Published Standard



46. ISO/IEC 15940:2006

46-1. Title

Information Technology -- Software Engineering Environment Services

46-2. Abstract

ISO/IEC 15940:2006 defines the software engineering environment (SEE) services conceptually in a reference model that can be adapted to any SEEs to automate one or more software engineering activities.

It describes services that support the process definitions as in ISO/IEC 12207 so that the set of SEE Services are compatible with ISO/IEC 12207.

ISO/IEC 15940:2006 can be used either as a general reference, or to define an automated software process.

46-3. Status

Published Standard



47. ISO/IEC 16085:2006

47-1. Title

Systems and software engineering -- Life cycle processes -- Risk management

47-2. Abstract

ISO/IEC 16085:2006 defines a process for the management of risk in the life cycle. It can be added to the existing set of system and software life cycle processes defined by ISO/IEC 15288 and ISO/IEC 12207, or it can be used independently.

ISO/IEC 16085:2006 can be applied equally to systems and software.

Risk management is a key discipline for making effective decisions and communicating the results within organizations. The purpose of risk management is to identify potential managerial and technical problems before they occur so that actions can be taken that reduce or eliminate the probability and/or impact of these problems should they occur. It is a critical tool for continuously determining the feasibility of project plans, for improving the search for and identification of potential problems that can affect life cycle activities and the quality and performance of products, and for improving the active management of projects.

47-3. Status

Published Standard



48. ISO/IEC TR 16326:1999

48-1. Title

Systems and software engineering -- Life cycle processes -- Project management

48-2. Abstract

48-3. Status

Revised. See ISO/IEC FDIS 16326



49. ISO/IEC TR FDIS 16326

49-1. Title

Software engineering -- Guide for the application of ISO/IEC 12207 to project management

49-2. Abstract

49-3. Status




50. ISO/IEC DTR 18018.2

50-1. Title

Information technology -- Configuration Management tool capabilities

50-2. Abstract

50-3. Status




50-4. ISO/IEC 18019:2004

50-5. Title

Software and system engineering -- Guidelines for the design and preparation of user documentation for application software

50-6. Abstract

ISO/IEC 18019:2004 provides guidelines for the design and preparation of user documentation for application software. It describes how to establish what information users need, how to determine the way in which that information should be presented to the users, and how then to prepare the information and make it available.

Application software includes consumer software packages, software for office applications, business software and specialist software for use by professionals.

ISO/IEC 18019:2004 is for use by people responsible for specifying, designing and preparing user documentation for application software and people who manage these activities, including developers of tools for creating hardcopy documentation, product designers, application developers, project managers, authors, programmers, translators and localization staff.

It is intended for use in all types of organizations, whether or not a dedicated documentation department is present. In all cases, it can be used as a basis for local standards and procedures. Readers are assumed to have experience or knowledge of software development or documentation development processes.

50-7. Status

Published Standard



51. ISO/IEC 19501:2005

51-1. Title

Information technology -- Open Distributed Processing -- Unified Modeling Language (UML) Version 1.4.2

51-2. Abstract

ISO/IEC 19501:2004 describes the Unified Modeling Language (UML), a graphical language for visualizing, specifying, constructing and documenting the artifacts of a software-intensive system. The UML offers a standard way to write a system's blueprints, including conceptual things such as business processes and system functions, as well as concrete things such as programming language statements, database schemas, and reusable software components.

51-3. Status

Published Standard



52. ISO/IEC TR 19759:2005

52-1. Title

Software Engineering -- Guide to the Software Engineering Body of Knowledge (SWEBOK)

52-2. Abstract

ISO/IEC 19759:2005, a guide to the software engineering body of knowledge (SWEBOK), identifies and describes that subset of the body of knowledge that is generally accepted, even though software engineers must be knowledgeable not only in software engineering, but also, of course, in other related disciplines. SWEBOK is an all-inclusive term that describes the sum of knowledge within the profession of software engineering.

52-3. Status

Published Standard



53. ISO/IEC TR 19760:2003

53-1. Title

Systems engineering -- A guide for the application of ISO/IEC 15288 (System life cycle processes)

53-2. Abstract

ISO/IEC TR 19760:2003 is a Technical Report that provides guidance for application of the International Standard ISO/IEC 15288 Systems Engineering - System life cycle processes in regard to systems and projects irrespective of size and type. ISO/IEC TR 19760:2003 can be used as a companion document to the International Standard by those who:

• apply the International Standard within their organization;

• use the International Standard in regard to a specific system;

• prepare organizational and domain specific standards based on the International Standard.

ISO/IEC TR 19760:2003 elaborates on factors that should be considered when applying the International Standard. It does this in the context of the various ways in which ISO/IEC 15288 may be applied. ISO/IEC TR 19760:2003 provides example application concerns lists for user consideration. However, ISO/IEC TR 19760:2003 is not intended to provide how-to guidance for each application area of the International Standard.

Guidance is provided for appropriate tailoring of the International Standard for application to specific systems or projects. ISO/IEC TR 19760:2003 also provides appropriate links to other ISO documents for supporting application of the International Standard and to aid in assessing the effectiveness of the application of the International Standard.

53-3. Status

Published Standard



54. ISO/IEC 19770-1:2006

54-1. Title

Information technology -- Software asset management -- Part 1: Processes

54-2. Abstract

ISO/IEC 19770-1:2006 has been developed to enable an organization to prove that it is performing software asset management (SAM) to a standard sufficient to satisfy corporate governance requirements and ensure effective support for IT service management overall. ISO/IEC 19770-1:2006 is intended to align closely to, and to support, ISO/IEC 20000. Good practice in SAM should result in several benefits, and certifiable good practice should allow management and other organizations to place reliance on the adequacy of these processes. The expected benefits should be achieved with a high degree of confidence:

SAM should facilitate the management of business risks, cost control and give competitive advantages.

54-3. Status

Published Standard



55. ISO/IEC FCD 19770-2

55-1. Title

Information technology -- Software asset management -- Part 2: Software identification tag

55-2. Abstract

55-3. Status




56. ISO/IEC NP 19770-3

56-1. Title

Information technology -- Software asset management -- Part 3: Software entitlement tag

56-2. Abstract

56-3. Status




57. ISO/IEC DTR 24748

57-1. Title

Systems and software engineering -- Guide for life cycle management

57-2. Abstract

57-3. Status




58. ISO/IEC FDIS 24765

58-1. Title

Systems and software engineering -- Vocabulary

58-2. Abstract

58-3. Status




59. ISO/IEC DTR 24766.2

59-1. Title

Information Technology - Requirement Engineering Tool Requirements

59-2. Abstract

59-3. Status




60. ISO/IEC 24773:2008

60-1. Title

Software engineering -- Certification of software engineering professionals -- Comparison framework

60-2. Abstract

ISO/IEC 24773:2008 establishes a framework for comparison of schemes for certifying software engineering professionals. A certification scheme is a set of certification requirements for software engineering professionals. ISO/IEC 24773:2008 specifies the items that a scheme is required to contain and indicates what should be defined for each item.

ISO/IEC 24773:2008 will facilitate the portability of software engineering professional certifications between different countries or organizations. At present, different countries and organizations have adopted different approaches on the topic that are implemented by means of regulations and bylaws. The intention of ISO/IEC 24773:2008 is to be open to these individual approaches by providing a framework for expressing them in a common scheme that can lead to understanding.

60-3. Status

Published Standard



61. ISO/IEC TR 24774:2007

61-1. Title

Software and systems engineering -- Life cycle management -- Guidelines for process description

61-2. Abstract

An increasing number of international, national and industry standards describe process models. These models are developed for a range of purposes including process implementation and assessment. The terms and descriptions used in such models vary in format, content and level of prescription. ISO/IEC TR 24774:2007 presents guidelines for the elements used most frequently in describing a process: the title, purpose statement, outcomes, activities and tasks. Whilst the primary purpose of ISO/IEC TR 24774:2007 is to encourage consistency in standard process reference models, the guidelines it provides may be applied to any process model developed for any purpose

61-3. Status

Published Standard



62. ISO/IEC CD TR 24774

62-1. Title

Software and systems engineering -- Life cycle management -- Guidelines for process description

62-2. Abstract

62-3. Status




63. ISO/IEC 25000:2005

63-1. Title

Software Engineering -- Software product Quality Requirements and Evaluation (SQuaRE) -- Guide to SQuaRE

63-2. Abstract

ISO/IEC 25000:2005 provides guidance for the use of the new series of International Standards named Software product Quality Requirements and Evaluation (SQuaRE). The purpose of this guide is to provide a general overview of SQuaRE contents, common reference models and definitions, as well as the relationship among the documents, allowing users of this guide a good understanding of those series of International Standards, according to their purpose of use. This document contains an explanation of the transition process between the old ISO/IEC 9126 and the 14598 series and SQuaRE, and also presents information on how to use the ISO/IEC 9126 and 14598 series in their previous form.

SQuaRE provides:

• Terms and definitions,

• Reference models,

• General guide,

• Individual division guides, and

• Standards for requirements specification, planning and management, measurement and evaluation purposes.

63-3. Status

Published Standard



64. ISO/IEC 25001:2007

64-1. Title

Software engineering -- Software product Quality Requirements and Evaluation (SQuaRE) -- Planning and management

64-2. Abstract

ISO/IEC 25001:2007 provides details about the planning and management requirements associated with software product quality requirements and evaluation.

While it is mainly concerned with product quality requirements and evaluation, wherever it is relevant the corresponding process requirements and evaluation activities are also discussed.

ISO/IEC 25001:2007 aims to clarify the requirements which should be identified by the organization in order to ensure the success of specifying quality requirements and executing the evaluation.

ISO/IEC 25001:2007 is intended to be used in conjunction with the other parts of the SQuaRE series (ISO/IEC 25000-ISO/IEC 25051) of International Standards, and with ISO/IEC 14598 and ISO/IEC 9126-1 until superseded by the ISO/IEC 25000 series of International Standards.

ISO/IEC 25001:2007 complies with the technical processes identified in ISO/IEC 15288 related to quality requirements definition and analysis.

64-3. Status

Standard is translated into Persian by ISIRI under standards ISIRI-ISO 25000.



65. ISO/IEC CD 25010

65-1. Title

Software engineering-Software product Quality Requirements and Evaluation (SQuaRE) Quality model

65-2. Abstract

65-3. Status




66. ISO/IEC 25012:2008

66-1. Title

Software engineering -- Software product Quality Requirements and Evaluation (SQuaRE) -- Data quality model

66-2. Abstract

ISO/IEC 25012:2008 defines a general data quality model for data retained in a structured format within a computer system.

ISO/IEC 25012:2008 can be used to establish data quality requirements, define data quality measures, or plan and perform data quality evaluations. It could be used, for example,

• to define and evaluate data quality requirements in data production, acquisition and integration processes,

• to identify data quality assurance criteria, also useful for re-engineering, assessment and improvement of data,

• to evaluate the compliance of data with legislation and/or requirements.

ISO/IEC 25012:2008 categorizes quality attributes into fifteen characteristics considered by two points of view: inherent and system dependent. Data quality characteristics will be of varying importance and priority to different stakeholders.

ISO/IEC 25012:2008 is intended to be used in conjunction with the other parts of the SQuaRE series of International Standards, and with ISO/IEC 9126-1 until superseded by ISO/IEC 25010.

66-3. Status

Published Standard



67. ISO/IEC 25020:2007

67-1. Title

Software engineering -- Software product Quality Requirements and Evaluation (SQuaRE) -- Measurement reference model and guide

67-2. Abstract

ISO/IEC 25020:2007 provides a measurement reference model and guide for measuring the quality characteristics defined in ISO/IEC 2501n, Quality Model Division. ISO/IEC 25020:2007 sets requirements for the selection and construction of quality measures. It also contains informative annexes addressing the following topics: criteria for selecting software quality measures and quality measure elements, demonstrating predictive validity and assessing measurement reliability, and an example format for documenting software quality measures.

The Quality Measurement Division, of which ISO/IEC 25020 is a member, also offers examples of quality measures that can be used across the product development life cycle. These measures are defined in the other documents in the division and correspond to the quality characteristics in a software product quality model such as that described in ISO/IEC 25010. ISO/IEC 25020:2007 and the quality measures are designed to be used, in particular, with other standards in the SQuaRE series that address quality requirements (ISO/IEC 25030) and product quality evaluation (ISO/IEC 25040).

67-3. Status

Published Standard



68. ISO/IEC TR 25021:2007

68-1. Title

Software engineering -- Software product Quality Requirements and Evaluation (SQuaRE) -- Quality measure elements

68-2. Abstract

ISO/IEC TR 25021:2007 defines the set of quality measure elements to be used throughout the software product life cycle for the purpose of Software Product Quality Requirement and Evaluation (SQuaRE). While some quality measure elements can be used as standalone quality measures, their main purpose is to be the building blocks for other SQuaRE measurements as described in ISO/IEC TR 9126-2, ISO/IEC TR 9126-3 and ISO/IEC TR 9126-4. ISO/IEC TR 25021:2007 constitutes the link between ISO/IEC 9126 and the subsequent SQuaRE series of standards.

ISO/IEC TR 25021:2007 contains informative annexes documenting the cross-reference relationship between the quality measure elements and quality measures, characteristics and subcharacteristics defined in ISO/IEC 9126.

The Quality Measurement Division, of which ISO/IEC TR 25021:2007 is a member, also offers examples of quality measures that can be used across the product development life-cycle. These measures are defined in the other documents in the division and correspond to the quality characteristics in a software product quality model such as that described in the future International Standard ISO/IEC 25010 (replacing ISO/IEC 9126-1). ISO/IEC TR 25021:2007 is designed to be used, in particular, with other standards in the SQuaRE series that address quality requirements (ISO/IEC 25030) and product quality evaluation (the future International Standard ISO/IEC 25040).

68-3. Status

Published Standard



69. ISO/IEC 25030:2007

69-1. Title

Software engineering -- Software product Quality Requirements and Evaluation (SQuaRE) -- Quality requirements

69-2. Abstract

ISO/IEC 25030:2007 provides requirements and recommendations for the specification of software quality requirements. It applies to both acquirers and suppliers. It focuses on software quality requirements, but takes a system perspective since software is normally developed and applied as part of a larger system.

Software product quality requirements are needed for:

• specification (including contractual agreement and call for tender);

• planning (including feasibility analysis);

• development (including early identification of potential quality problems during development); and

• evaluation (including objective assessment and certification of software product quality).

If software quality requirements are not stated clearly, they may be viewed, interpreted, implemented and evaluated differently by different people. This may result in: software which is inconsistent with user expectations and of poor quality; users, clients and developers who are unsatisfied; and time and cost overruns to rework software.

ISO/IEC 25030:2007 helps to improve the quality of software quality requirements. It does this by providing requirements and recommendations for quality requirements, and guidance for the processes used to define and analyse quality requirements. It applies the quality model defined in ISO/IEC 9126-1 [ISO/IEC 25010] and it complies with the requirement processes defined in ISO/IEC 15288.

ISO/IEC 25030 is part of the SQuaRE series of International Standards.



69-3. Status

Published Standard




70-1. Title

Software engineering - Software product Quality Requirements and Evaluation (SQuaRE) - Evaluation reference model and guide

70-2. Abstract

70-3. Status




71. ISO/IEC FCD 25045

71-1. Title

Software Engineering - Software product Quality Requirements and Evaluation (SQuaRE) - Evaluation Module for Recoverability

71-2. Abstract

71-3. Status




72. ISO/IEC 25051:2006

72-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

72-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.

72-3. Status

Standard translated into Persian by ISIRI, under standard number: ISIRI-ISO 25030.




73-1. Title

Software product Quality Requirements and Evaluation (SQuaRE) -- Common Industry Format (CIF) for Usability -- General Framework for Usability-related Information

73-2. Abstract

73-3. Status




74. ISO/IEC 25062:2006

74-1. Title

Software engineering -- Software product Quality Requirements and Evaluation (SQuaRE) -- Common Industry Format (CIF) for usability test reports

74-2. Abstract

ISO/IEC 25062:2006 provides a standard method for reporting usability test findings. The format is designed for reporting results of formal usability tests in which quantitative measurements were collected, and is particularly appropriate for summative/comparative testing. The CIF does not indicate how to perform a usability test but provides guidance on how to report the results of a usability test. The CIF targets two audiences: usability professionals and stakeholders in an organization. Stakeholders can use the usability data to help make informed decisions concerning the release of software products or the procurement of such products.

The format includes the following elements:

• the description of the product,

• the goals of the test,

• the test participants

• the tasks the users were asked to perform,

• the experimental design of the test,

• the method or process by which the test was conducted,

• the usability measures and data collection methods, and

• the numerical results.

74-3. Status

Published Standard




75-1. Title

Information technology -- Application management -- Requirements for application management

75-2. Abstract

75-3. Status




76. ISO/IEC WD 26511

76-1. Title

Software and systems engineering -- User documentation requirements for managers

76-2. Abstract

76-3. Status





77-1. Title

Software and Systems Engineering -- Requirements for acquirers and suppliers of user documentation

77-2. Abstract

77-3. Status




78. ISO/IEC FCD 26513

78-1. Title

Systems and software engineering - Requirements for testers and reviewers of user documentation

78-2. Abstract

78-3. Status




79. ISO/IEC 26514:2008

79-1. Title

Systems and software engineering -- Requirements for designers and developers of user documentation

79-2. Abstract

ISO/IEC 26514:2008 provides requirements for the design and development of software user documentation as part of the life cycle processes. It defines the documentation process from the viewpoint of the documentation developer. ISO/IEC 26514:2008 also covers the documentation product. It specifies the structure, content, and format for user documentation, and also provides informative guidance for user documentation style. It 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 ISO/IEC 26514:2008 is also applicable to user documentation for systems including hardware.

79-3. Status

Published Standard



80. ISO/IEC 26702:2007

80-1. Title

Systems engineering -- Application and management of the systems engineering process

80-2. Abstract

ISO/IEC 26702:2007 defines the interdisciplinary tasks which are required throughout a system's life cycle to transform customer needs, requirements and constraints into a system solution. In addition, it specifies the requirements for the systems engineering process and its application throughout the product life cycle. ISO/IEC 26702:2007 focuses on engineering activities necessary to guide product development, while ensuring that the product is properly designed to make it affordable to produce, own, operate, maintain and eventually dispose of without undue risk to health or the environment.

80-3. Status

Published Standard




81-1. Title

Information Technology - Tools and Methods of requirements engineering and management for product lines

81-2. Abstract

81-3. Status




82. ISO/IEC AWI 29148

82-1. Title

Software and systems engineering -- Life cycle processes -- Requirements engineering

82-2. Abstract

82-3. Status




83. ISO/IEC NP 29154

83-1. Title

Software Engineering -- Certification of Software Engineering Professionals -- Guidelines and Examples

83-2. Abstract

83-3. Status





84-1. Title

Software and systems engineering -- IT Performance Benchmarking Framework

84-2. Abstract

84-3. Status





85-1. Title

Software and System Engineering -- Corporate Governance of Information Technology

85-2. Abstract

85-3. Status





86-1. Title

Software and Systems Engineering -- Requirements for acquirers and suppliers of user documentation (proposed ISO/IEC 26512)

86-2. Abstract

86-3. Status




87. ISO/IEC 42010:2007

87-1. Title

Systems and software engineering -- Recommended practice for architectural description of software-intensive systems

87-2. Abstract

ISO/IEC 42010:2007 addresses the activities of the creation, analysis and sustainment of architectures of software-intensive systems, and the recording of such architectures in terms of architectural descriptions. ISO/IEC 42010:2007 establishes a conceptual framework for architectural description and defines the content of an architectural description. Annexes provide the rationale for key concepts and terminology, the relationships to other standards, and examples of usage.

87-3. Status

Published Standard




88-1. Title

Systems and software engineering -- Architectural description

88-2. Abstract

88-3. Status





89-1. Title

Software engineering -- Guidelines for the application of ISO 9001:2000 to computer software

89-2. Abstract

89-3. Status




90. ISO/IEC 90003:2004

90-1. Title

Software engineering -- Guidelines for the application of ISO 9001:2000 to computer software

90-2. Abstract

ISO/IEC 90003:2004 provides guidance for organizations in the application of ISO 9001:2000 to the acquisition, supply, development, operation and maintenance of computer software and related support services. ISO/IEC 90003:2004 does not add to or otherwise change the requirements of ISO 9001:2000.

The guidelines provided in ISO/IEC 90003:2004 are not intended to be used as assessment criteria in quality management system registration/certification.

The application of ISO/IEC 90003:2004 is appropriate to software that is

• part of a commercial contract with another organization,

• a product available for a market sector,

• used to support the processes of an organization,

• embedded in a hardware product, or

• related to software services.

Some organizations may be involved in all the above activities; others may specialize in one area. Whatever the situation, the organization's quality management system should cover all aspects (software related and non-software related) of the business.

ISO/IEC 90003:2004 identifies the issues which should be addressed and is independent of the technology, life cycle models, development processes, sequence of activities and organizational structure used by an organization. Additional guidance and frequent references to the ISO/IEC JTC 1/SC 7 software engineering standards are provided to assist in the application of ISO 9001:2000: in particular ISO/IEC 12207, ISO/IEC TR 9126, ISO/IEC 14598, ISO/IEC 15939 and ISO/IEC TR 15504.



90-3. Status

Published Standard



91. ISO/IEC TR 90005:2008

91-1. Title

Systems engineering -- Guidelines for the application of ISO 9001 to system life cycle processes

91-2. Abstract

ISO/IEC TR 90005:2008 provides guidance for organizations in the application of ISO 9001:2000 to the acquisition, supply, development, operation and maintenance of systems and related support services. It does not add to or otherwise change the requirements of ISO 9001:2000. The guidelines provided in ISO/IEC TR 90005:2008 are not intended to be used as assessment criteria in quality management system registration or certification.

ISO/IEC TR 90005:2008 adopts ISO/IEC 15288 systems life cycle processes as a starting point for system development, operation or maintenance and identifies those equivalent requirements in ISO 9001:2000 that have a bearing on the implementation of ISO/IEC 15288.

ISO/IEC TR 90005:2008 is appropriate to systems that are

• part of a commercial contract with another organization,

• a product available for a market sector,

• used to support the processes of an organization,

• embedded in a hardware product, or

• related to software services.

91-3. Status

Published Standard




92-1. Title

Information Technology -- Guidelines for the application of ISO 9001:2000 to IT service management.

92-2. Abstract

92-3. Status




93. ISO/IEC 24744:2007

93-1. Title

Software Engineering – Meta-model for Development Methodologies

93-2. Abstract

Development methodologies may be described in the context of an underpinning meta-model, but the precise mechanisms that permit them to be defined in terms of their meta-models are usually difficult to explain and do not cover all needs. For example, it is difficult to devise a practice that allows the definition of properties of the elements that compose the methodology and, at the same time, of the entities (such as work products) created when the methodology is applied. ISO/IEC 24744:2007 introduces the Software Engineering Meta-model for Development Methodologies (SEMDM), a comprehensive meta-model that makes use of a new approach to defining methodologies based on the concept of power type. The aim of SEMDM is to define methodologies in information-based domains, i.e. areas characterized by their intensive reliance on information management and processing, such as software, business or systems engineering. The SEMDM combines key advantages of other meta-modeling approaches with none of their known drawbacks, allowing the seamless integration of process, modeling and people aspects of methodologies. Examples are given where other meta-models are mapped to SEMDM and a brief synopsis of problems is provided.

Various methodologies are defined, used, or implied by a growing number of standards, and it is desirable that the concepts used by each methodology be harmonized. A vehicle for harmonization is the SEMDM. Conformance to this meta-model will ensure a consistent approach to defining each methodology with consistent concepts and terminology.

93-3. Status

Published Standard



IIEEEEEE SSttaannddaarrddss This part of document covers standards developed by IEEE Computer Society/Software & Systems Engineering Standards Committee, regarding software and system engineering.



94. IEEE Std. 610-1990

94-1. Title

IEEE Standard Computer Dictionary: Compilation of IEEE Standard Computer Glossaries

94-2. Status

Withdrawn Standard. Withdrawn Date: Apr 20, 2001. No longer endorsed by the IEEE. Available for purchase as archive document.

94-3. Abstract

This dictionary is a compilation of IEEE standard glossaries covering the fields of mathematics of computing, computer applications, modeling and simulation, image processing and pattern recognition, data management, and software engineering. Every effort has been made to include all terms within the designated subject areas. Terms were excluded if they were considered to be parochial to one group or organization; company-proprietary or trademarked; multiword terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.



95. IEEE Std. 610.1

95-1. Title

Standard for Glossary of Mathematics of Computing Terminology

95-2. Status

Withdrawn. Standards project no longer endorsed by the IEEE.

95-3. Abstract

To define terms which are in general use in mathematics of computing.



96. IEEE std. 610.2-1987

96-1. Title

IEEE Standard Glossary of Computer Applications Terminology

96-2. Status

Withdrawn Standard. Withdrawn Date: Apr 20, 2001. No longer endorsed by the IEEE. Available for purchase as archive document.

96-3. Abstract

Terms currently in use in the computer field are identified, and standard definitions are established for them. Topics covered include automated language processing, automatic indexing, business data processing, character recognition, computer-aided design and manufacturing, computer-assisted instruction, control systems, critical path method, library automation, medical applications, micrographics, office automation, operations research, personal computing, scientific and engineering applications, telecommunications applications, and word processing. The terms included in this glossary are intended for users of computer systems. Terms were excluded if they were considered to be parochial to one group or organization; company-proprietary or trademarked; multiword terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.



97. IEEE Std. 610.12-1990

97-1. Title

IEEE Standard Glossary of Software Engineering Terminology

97-2. Status

Approved Publication of IEEE

97-3. Abstract

This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types; libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools. Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning. This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.

This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.



98. IEEE Std. 730-2002

98-1. Title

Standard for Software Quality Assurance Plans

98-2. Status

Approved Publication of IEEE , Published Date: Sep 23, 2002

98-3. Abstract

The standard specifies the format and content of software quality assurance plans. It meets the IEEE/EIA 12207.1. This standard establishes a required minimum contents for Software Quality Assurance plans. It is directed toward the development and maintenance of software. The orientation is toward delineating all of the planned and systematic actions on a particular project that would provide adequate confidence that the software product conforms to established technical requirements. This standard has been harmonized with the requirements for software quality assurance plans as defined in 730 and the content of such plans as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes.

To perform the required five-year revision of Std 730. This standard also will be harmonized with the requirements for software quality assurance plans as specified in IEEE/EIA 12207.1. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207. To clarify inconsistencies in existing document and bring it into compatibility with IEEE Std 828 and maintain compatibility with IEEE/EIA 12207.0.



99. IEEE Std. P730

99-1. Title

Standard for Software Quality Assurance Planning

99-2. Status

Revision Project

99-3. Abstract

This standard establishes the requirements for planning Software Quality Assurance activities in support of a software project. It is directed toward the development and maintenance of software. The orientation is toward planning the systematic actions on a particular project that would provide adequate confidence that the software product conforms to established technical requirements. The standard also provides a means of satisfying the planning requirements of an organization's Quality Manual for a software project. It has been harmonized with the requirements of the Quality Assurance process of IEEE/EIA 12207.0 and the documentation content requirements of ISO/IEC 15289. The purpose of this standard is to provide uniform, minimum acceptable requirements for Software Quality Assurance activities in support of a software project. In considering adoption of this standard, regulatory bodies should be aware that specific application of this standard may already be covered by one or more IEEE or ANSI standards documents relating to quality assurance, definitions, or other matters. It is not the purpose of this document to supersede, revise, or amend existing standards directed to specific industries or applications.



100. IEEE Std. 828-2005

100-1. Title

IEEE Standard for Software Configuration Management Plans

100-2. Status

Approved Publication of IEEE , Published Date: Aug 12, 2005

100-3. Abstract

The minimum required contents of a Software Configuration Management (SCM) Plan are established via this standard. This standard applies to the entire life cycle of critical software (e.g., where failure would impact safety or cause large financial or social losses). It also applies to non-critical software and to software already developed. The application of this standard is not restricted to any form, class, or type of software.



101. IEEE Std. P828

101-1. Title

Standard for Software Configuration Management

101-2. Status

Revision Project

101-3. Abstract

This standard establishes the minimum required process considerations for the Software Configuration Management (SCM)function. The application of this standard is not restricted to any form, class, or type of software. This revision effort moves the existing standard for a plan to a standard for software engineering processes for the SCM function. The SCM standard defines what SCM activities are to be done, how they are to be done, who is responsible for doing specific activities, when they are to happen, and what resources are required. It can address SCM activities over any portion of a software product’s life cycle. This standard is consistent with the IEEE Software Engineering Body of Knowledge SWEBOK) project Stoneman release on the topic of configuration management and with IEEE/EIA Std 12207.0™.



102. IEEE Std. 829-2008

102-1. Title

IEEE Standard for Software and System Test Documentation

102-2. Status


102-3. Abstract

Test processes determine whether the development products of a given activity conform to the requirements of that activity and whether the system and/or software satisfies its intended use and user needs. Testing process tasks are specified for different integrity levels. These process tasks determine the appropriate breadth and depth of test documentation. The documentation elements for each type of test documentation can then be selected. The scope of testing encompasses software-based systems, computer software, hardware, and their interfaces. This standard applies to software-based systems being developed, maintained, or reused (legacy, commercial off-the-shelf, Non-Developmental Items). The term “software” also includes firmware, microcode, and documentation. Test processes can include inspection, analysis, demonstration, verification, and validation of software and software-based system products.

This standard applies to all software-based systems. It applies to systems and software being developed, acquired, operated, maintained, and/or reused [e.g., legacy, modified, Commercial-Off-the-Shelf (COTS), Government-Off-the-Shelf (GOTS), or Non-Developmental Items (NDIs)]. When conducting the test process, it is important to examine the software in its interactions with the other parts of the system. This standard identifies the system considerations that test processes and tasks address in determining system and software correctness and other attributes (e.g., completeness, accuracy, consistency, and testability), and the applicable resultant test documentation.

The purpose of this standard is to:



• Establish a common framework for test processes, activities, and tasks in support of all software life cycle processes, including acquisition, supply, development, operation, and maintenance processes

• Define the test tasks, required inputs, and required outputs

• Identify the recommended minimum test tasks corresponding to integrity levels for a four-level integrity scheme

• Define the use and contents of the Master Test Plan and the Level Test Plan(s) (e.g., for component, integration, system, and acceptance test)

• Define the use and contents of related test documentation (Test Design, Test Case, Test Procedure, Anomaly Report, Test Log, Level Test Report, Interim Test Report, and Master Test Report)



103. IEEE Std. 830-1998

103-1. Title

IEEE Recommended Practice for Software Requirements Specifications

103-2. Status

Approved Publication of IEEE , Published Date: Oct 20, 1998

103-3. Abstract

The general area of requirements for software systems as specified by either potential customers/users or designers/producers and constituting the substance of an agreement between them. To establish a correlation between the content of software requirements specifications as defined in 830 and the content of such documentation as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation. To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.

The content and qualities of a good software requirements specification (SRS) are de-scribed and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/EIA12207.1-1997 are also provided.



104. IEEE Std. 982.1-2005

104-1. Title

IEEE Standard Dictionary of Measures of the Software Aspects of Dependability

104-2. Status

Approved Publication of IEEE , Published Date: May 08, 2006

104-3. Abstract

This standard specifies and classifies measures of the software aspects of dependability. It is an expansion of the scope of the existing standard; the revision includes the following aspects of dependability: reliability, availability, and maintainability of software. The applicability of this standard is any software system; in particular, it applies to mission critical systems, where high reliability, availability, and maintainability are of utmost importance. These systems include, but are not limited to, systems for military combat, space missions, air traffic control, network operations, stock exchanges, automatic teller machines, and airline reservation systems.

This standard provides measures that are applicable for continual self-assessment and improvement of the software aspects of dependability. A Standard Dictionary of Measures of the Software Aspects of Dependability for assessing and predicting the reliability, maintainability, and availability of any software system; in particular, it applies to mission critical software systems.



105. IEEE Std. 1008-1987

105-1. Title

IEEE Standard for Software Unit Testing

105-2. Status


105-3. Abstract

An integrated approach to systematic and documented unit testing is defined. It uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing. The testing process described composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. The standard can be applied to the unit testing of any digital computer software or firmware and to the testing of both newly developed and modified units. The software engineering concepts and testing assumption on which this standard approach is based and guidance and resource information to assist with the implementation and usage of the standard unit testing approach are provided in appendixes.



106. IEEE Std. P1012

106-1. Title

Standard for System and Software Verification and Validation

106-2. Status

Revision Project

106-3. Abstract

This standard defines the verification and validation processes that are applied to system, software, and hardware development throughout the system life cycle including acquisition, supply, development, operations, maintenance, and retirement. This standard applies to system, software, and hardware being acquired, developed, maintained, or reused. Software includes firmware, microcode, and documentation.

The purpose of the standard is to:

• Establish a common framework of V&V processes, activities, and tasks in support of all system, software, and hardware life cycle processes

• Define the V&V tasks, required inputs, and required outputs in each life cycle process

• Identify the minimum V&V tasks corresponding to a four-level system/software integrity scheme

• Define the content of the System and Software Verification and Validation Plan



107. IEEE Std. 1016-1998

107-1. Title

IEEE recommended practice for software design descriptions

107-2. Status


107-3. Abstract



108. IEEE Std. 1028-2008

108-1. Title

IEEE Standard for Software Reviews and Audits

108-2. Status

Approved Publication of IEEE, Published Date: Aug 15, 2008.

108-3. Abstract

This standard provides minimum acceptable requirements for systematic software reviews, where “systematic” includes the following attributes:

• Team participation

• Documented results of the review

• Documented procedures for conducting the review

Reviews that do not meet the requirements of this standard are considered to be non- systematic reviews. The standard is not intended to discourage or prohibit the use of non-systematic reviews. The definitions, requirements, and procedures for the following five types of reviews are included within this standard:

• Management reviews

• Technical reviews

• Inspections

• Walkthroughs

• Audits

This standard does not establish the need to conduct specific reviews; that need is defined by other software engineering standards or by local procedures. This standard provides definitions, requirements, and procedures that are applicable to the reviews of software development products throughout the software life cycle. Users of this standard shall specify where and when this standard applies and any intended



deviations from this standard. This standard may be used with other software engineering standards that determine the products to be reviewed, the timing of reviews, and the necessity of reviews. This standard is closely aligned with IEEE Std 1012™-2004 [B6], but it can also be used with IEEE Std 1074™-2006 [B11], IEEE Std 730™-2002 [B2], IEEE Std 12207™-2008 [B15], and other standards. A useful model is to consider IEEE Std 1028-2008 as a subroutine to the other standards. Thus, if IEEE Std 1012-2004 were used to carry out the verification and validation process, the procedure in IEEE Std 1012-2004 could be followed until such time as instructions to carry out a specific review are encountered. At that point, IEEE Std 1028-2008 would be “called” to carry out the review, using the specific review type described herein. Once the review has been completed, IEEE Std 1012-2004 would be “returned to” for disposition of the results of the review and any additional action required by IEEE Std 1012-2004.

This standard may also be used as a stand-alone definition of software review and audit procedures. In this case, local management must determine the events that precede and follow the actual software reviews and audits. In this model, requirements and quality attributes for the software product are “parameter inputs” to the review and are imposed by the “caller.” When the review is finished, the review outputs are “returned” to the “caller” for action. Review outputs typically include anomaly lists and action item lists; the resolution of the anomalies and action items are the responsibility of the “caller.”

The purpose of this standard is to define systematic reviews and audits applicable to software acquisition, supply, development, operation, and maintenance. This standard describes how to carry out a review. Other standards or local management define the context within which a review is performed, and the use made of the results of the review. Software reviews can be used in support of the objectives of project management, system engineering (for example, functional allocation between hardware and software), verification and validation, configuration management, quality assurance and auditing. Different types of reviews reflect differences in the goals of each review type. Systematic reviews are described by their defined procedures, scope, and objectives.



This standard defines five types of software reviews and audits, together with procedures required for the execution of each type. This standard is concerned only with the reviews and audits; it does not define procedures for determining the necessity of a review or audit, nor does it specify the disposition of the results of the review or audit. Review types include management reviews, technical reviews, inspections, and walkthroughs.

This standard is meant to be used either in conjunction with other IEEE software engineering standards or as a stand-alone definition of software review and audit procedures. In the latter case, local management must determine the events that precede and follow the actual software reviews and audits. The need for reviews and audits is described in several other IEEE standards, as well as standards prepared by other standards- writing organizations. IEEE Std 1028-2008 is meant to support these other standards. In particular, reviews and audits required by the standards listed in Annex B can be executed using the procedures described herein. The use of IEEE Std 1044-1993 [B8]a is encouraged as part of the reporting procedures for this standard.



109. IEEE Std. 1044-1993

109-1. Title

IEEE Standard Classification for Software Anomalies

109-2. Status

Approved Publication of IEEE. Undergoing Revision.

109-3. Abstract

A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.



110. IEEE Std. 1058-1998

110-1. Title

IEEE Standard for Software Project Management Plans

110-2. Status

Approved Publication of IEEE , Published Date: Dec 22, 1998

110-3. Abstract

To prescribe the format and contents of software management plans. A software management plan is the controlling document for managing a software project; it provides the technical and managerial activities necessary to satisfy the requirements for the software project. Project Purpose: To provide a uniform scheme to prepare and present a software project management plan. Revision to reflect experience of the past 5 years of use.

" The format and contents of software project management plans, applicable to any type or size of software project, are described. The elements that should appear in all software project management plans are identified."



111. IEEE Std.: 1058a-1998

111-1. Title

IEEE Supplement to Standard for Software Project Management Plans

111-2. Status

Approved Publication of IEEE , Published Date: Dec 22, 1998. 1058a will be published as part of 1058-1998.

111-3. Abstract

Project Scope: To establish a correlation between the content of software project management plans as defined in 1058 and the content of such plans as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation. To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards.



112. IEEE Std. 1061-1998

112-1. Title

IEEE Standard for a Software Quality Metrics Methodology

112-2. Status


112-3. Project Scope

Methodology for establishing quality requirements and identifying, implementing, analyzing, and validating software quality metrics. To clarify the use of terminology in the document; incorporate lessons learned since publication from workshops, teaching classes based on the document, and field experience of users, and clarify relationships with related international standards.

"A methodology for establishing quality requirements and identifying, implementing, analyzing, and validating the process and product software quality metrics is defined. The methodology spans the entire software life cycle."




113-1. Title

Recommended Practice for Software Acquisition

113-2. Status

Revision Project

113-3. Abstract

This recommended practice describes a set of useful quality considerations that can be selected and applied during one or more steps in a software acquisition process. The recommended practices can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. The software supply chain may include integration of commercial-off-the-shelf (COTS), custom, or open source software. Each organization or individual using this recommended practice will need to identify the specific quality and activities that need to be included within their acquisition process. Security will be included as a quality attribute considered during the acquisition process.

This recommended practice is designed to help organizations and individuals incorporate quality, including security, considerations during the definition, evaluation, selection, and acceptance of supplier software for operational use. It will also help determine how supplier software should be evaluated, tested, and accepted for delivery to end users. This recommended practice is intended to satisfy the following objectives:

• Promote consistency within organizations in acquiring software from software suppliers.

• Provide useful practices on including quality (including security) considerations during acquisition planning.

• Provide useful practices on evaluating and qualifying supplier capabilities to meet user requirements.

• Provide useful practices on evaluating and qualifying supplier software.



• Assist individuals or organizations judging the quality of supplier software for referral to end users.



114. IEEE Std. 1062a-1998

114-1. Title

Recommended Practice for Software Acquisition

114-2. Status


114-3. Abstract

To establish a correlation between the content of software acquisition plans as defined in 1062 and the content of such plans as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation.

To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards.



115. IEEE Std. 1063-2001

115-1. Title:

IEEE Standard for Software User Documentation

115-2. Status

115-3. Approved Publication of IEEE, Published Date: Dec 20, 2001

115-4. Abstract

This standard provides minimum requirements for the structure, information content, and format of user documentation, to include both paper and electronic documentation used in the work environment by users of systems containing software. The standard is limited to the software documentation product and will not include the processes of developing or managing software user documentation. The standard includes printed user manuals, online help, and user reference documentation. It does not apply to specialized course materials intended primarily for use in formal training programs.

A timely revision of Std 1063 will update the existing standard, which addresses paper documentation only, to provide requirements for the structure, information content and format of electronic documentation as well. The revised standard will address the interests of software acquirers, producers, and users in standards for consistent, complete, accurate, and usable documentation.

"Minimum requirements for the structure, information content, and format of user documentation, including both printed and electronic documents used in the work environment by users of systems containing software, are provided in this standard."



116. IEEE Std. 1074-2006

116-1. Title

IEEE Standard for Developing a Software Project Life Cycle Process

116-2. Status

Approved Publication of IEEE , Published Date: Jul 28, 2006

116-3. Abstract

Project Scope: This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. It is the function of the process architect to develop the SPLCP. This methodology begins with the selection of an appropriate software project life cycle model (SPLCM)for use on the specific project. It continues through the definition of the software project life cycle (SPLC),using the selected SPLCM, the activities provided in Annex A, and the portion of the software life cycle that is relevant to the project. The methodology concludes with the augmentation of the software life cycle with organizational process assets (OPAs) to create the SPLCP. The activities that are provided in Annex A cover the entire life cycle of a software system, from concept exploration through the eventual retirement of the software system. This standard does not address non-software activities, such as contracting, purchasing, or hardware development. It also does not mandate the use of a specific SPLCM, nor does it provide a selection of, or a tutorial on, SPLCMs. This standard presumes that the process architect is already familiar with a variety of SPLCMs, with the criteria for choosing among them and with the criteria for determining the attributes and constraints of the desired end system and the development environment that affects this selection. Finally, this standard does not prescribe how to perform the software activities in Annex A.

This standard defines the process by which an SPLCP is developed. It is useful to any organization that is responsible for managing and performing software projects. It can be used where software is the total system or where software is part of a larger system.



This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project.



117. IEEE Std. 1175.1-2002

117-1. Title

IEEE Guide for CASE Tool Interconnections - Classification and Description

117-2. Status

Approved Publication of IEEE , Published Date: Feb 09, 2003

117-3. Abstract

Introduce and characterize the problem of interconnecting CASE tools with their environment. Distinguish four interrelated contexts for interconnection. Partition interconnection concerns into issues of protocol, syntax, and semantics. Establish an integrating framework for the

other parts of the standard; describe their scope of application and their interrelations. This is a significant expansion of Part 1 of 1175. The material collected into this standard spans many aspects of CASE tool interconnection and serves a variety of software engineering and administrative personnel in the software industry. This overview describes the requirements and problems of CASE tool interconnection and points the reader to the appropriate parts of the standard. The other parts of the standard provide assistance in specifying the protocol, syntax, and semantics issues to be addressed for effectively integrating CASE tools into an organization's processes.

This guide describes the scope of application and interrelationships for the members of the IEEE 1175 family of standards. It points the reader to the appropriate member standard that ad-dresses issues involved in effectively integrating computing system tools into a productive engineering environment.



118. IEEE Std. 1175.2-2006

118-1. Title

IEEE Recommended Practice for CASE Tool Interconnection - Characterization of Interconnections

118-2. Status

Approved Publication of IEEE, Published Date: Jan 15, 2007

118-3. Abstract

Identify a standard set of attributes that characterize the contexts in which a CASE tool operates. These contexts are organizations, users, platforms, and other tools. The attributes in each context summarize the major factors affecting interconnection of the tool with that context. These are multi-dimensional attributes whose "values" are project-specific, organization-specific, professional, military and/or international standards for these attributes are identified. This is an expansion of Section 2 of the original 1175-1995 standard.

The attributes of CASE tool context are needed by software developers and process support personnel. They are a checklist of interconnection concerns which must be addressed when selecting, adopting, and using CASE tools. Analysis of a particular tool for these attributes can identify potential discrepancies in its operational interconnections that reduce or eliminate the value of the tool's use in an organization's processes. By cataloguing and characterizing groups of tool implementation factors to be addressed, this recommended practice assists its user's in organizing and using a large number of other industry standards to facilitate the design and realization of large, integrated, multi-vendor software engineering environments.

Interconnections that need to be understood and evaluated when buying, building, testing, or using Computer-Aided Software Engineering (CASE) tools are described in this recommended practice. This recommended practice is intended to help people interconnect tools by identifying and characterizing various contexts for tool interconnection. Each context serves to define a group of interconnections pertinent to



various functional perspectives. Each group contains interconnections that have a common kind of endpoint in the environment. This recommended practice considers four contexts: an organizational context for a tool, the individual user context for a tool, the platform context for a tool, and a peer context for a tool. Within a context, subsets of interconnections are characterized by a collection of common features applicable to a given functional perspective. The purpose of this recommended practice is to establish sets of interconnection features with which each perspective on a CASE tool’s interconnections can be characterized.



119. IEEE Std. 1175.3-2004

119-1. Title

IEEE Standard for CASE Tool Interconnections - Reference Model for Specifying Software Behavior

119-2. Status

Approved Publication of IEEE , Published Date: Sep 08, 2004

119-3. Abstract

Identify a common set of modeling concepts found in commercial CASE tools for describing the operational behavior of software product. Establish a uniform, integrated model and a textual syntax for expressing the common properties (attributes and relationships) of those concepts as they have been used to model software behavior.

This is a minor revision of Part 3 of the original standard. It is still useful within its defined scope. This minor revision of Part 3 of standard 1175 is being included in the revised standard for backward compatibility. The new 1175.4 has a much larger domain of applicability and a more rigorous basis for interpretation. Nevertheless, the previous meta-model is still appropriate for interconnecting CASE tools that have modeling concepts limited to conventional tool models of simple software behavior.



120. IEEE Std. 1175.4-2008

120-1. Title

IEEE Standard for CASE Tool Interconnections--Reference Model for Specifying System Behavior

120-2. Status

Approved Publication of IEEE, Published Date: Apr 17, 2009

120-3. Abstract

Most inter-tool data transfer standards deal with protocol and syntax of the transfer, with a shared semantic basis assumed. This standard provides an explicitly defined meta-model (and meta-metamodel) for specifying system and software behavior. It defines a semantic basis of observables that allows each tool, whatever its own internal ontology, to communicate facts about the behavior of a subject system as precisely as the tool’s meta-model allows. Conventional tool model elements are reduced into simpler, directly observable fact statements about system behavior.

This meta-model is much expanded over the original meta-model for software behavior in Part 3 of IEEE Std 1175™-1991. This reference model provides a common interpretation basis by which tools may express and communicate the observable features of system/software behavior to users and to other tools. Tools incorporating this meta-model in their import/export facilities enable engineers to interconnect best-in-class analysis and specification tools for integrated problem solving. Another feature of this meta-model is that it provides a specification that is directly testable. Finally, the provision of an explicit meta-metamodel enables tool builders to extend the reference meta-model for particular purposes.

A reference model that provides a common interpretation basis by which tools can express and communicate the observable features of system/software behavior to users and to other tools is presented. This standard specifies a Conceptual Meta-model for understanding and describing the causal behavior for a system. The purpose of this Conceptual Meta-model is to express causal behavior and compositions of causal



behavior in a model that integrates all observable operational features of a system into one behavior specification. This Conceptual Meta-model is useful for analyzing systems, for constructing particular system behavior models, and for using those models in the specification, design, and evaluation of engineered systems. It provides the necessary semantic elements for describing general hardware/software systems, including hardware-only, software-only, or mixed system components, and it allows these different types of components to be treated in a consistent manner, providing a basis for representing a wide variety of systems.



121. IEEE Std. P1175.5

121-1. Title

Standard for Computer-Aided Software Engineering (CASE) Tool Interconnections — Reference Data Meta-model for System Behavior Specifications

121-2. Status

New Standard Project

121-3. Abstract

This standard defines a data meta-model for system behavior specifications. The data meta-model provides explicit definitions of typed data elements, information representations, and relationships with which behavior models for subject systems can be instantiated. These elements, representations, and relations serve to reify the conceptual meta-model for system behavior specification described in IEEE Std 1175.4.

While the conceptual meta-model in IEEE Std 1175.4 provides a basis for thinking and talking about the behavior of a system in terms of black-box observables and relationships, the data meta-model provides a basis for capturing, storing, and transferring such descriptions in a data model representation.

The data meta-model standardizes the forms of terms and expressions to be used in recording the observable characteristics of a system’s behavior. It also standardizes the relationships by which those terms and expressions are combined to record facts about a system’s behavior. Populating the terms, expressions, and relations of the data meta-model with fact instances for a particular system creates a behavior model for that system. Such a behavior model can be manipulated and analyzed in various ways. It can be checked for completeness and self-consistency. It can be used to infer expected system responses in specified circumstances. It can also be used to determine valid scenarios of system usage. The data meta-model definition can also be used for designing behavior specification repositories, designing transfer interfaces between repositories, designing transfer interfaces between a repository and a system and



software engineering tool, and designing user interfaces based on behavior specification repositories.



122. IEEE Std. 1219-1998

122-1. Title

IEEE standard for software maintenance Status

122-2. Status

Archived

122-3. Abstract



123. IEEE Std. 1220-2005

123-1. Title

IEEE Standard for Application and Management of the Systems Engineering Process

123-2. Status

Approved Publication of IEEE, Published Date: Sep 09, 2005

123-3. Abstract

(First paragraph of existing 1.1, Scope): "This standard define the interdisciplinary tasks that are required throughout a system's life cycle to transform customer needs, requirements, and constraints into a system solution. This document is intended to guide the development of systems (which include humans, computers, and software) for commercial, government, military, and space applications. The information applies to an enterprise within an enterprise that is responsible for developing a product design and establishing the life cycle infrastructure needed to provide for life cycle sustainment."

(Existing 1.2, Purpose): "The purpose of this document is to provide a standard for managing a system from initial concept through development, operations, and disposal. The inclusion of computers and associated software in today's products has made the need to engineer each of those products as a total system more acute. The human, physical, and software components should all be addressed to optimize overall system performance." The purpose of the revision project is to harmonize the standard with the new ISO/IEC 15288, System Life Cycle Processes.

The interdisciplinary tasks that are required throughout a system’s life cycle to transform stakeholder needs, requirements, and constraints into a system solution are defined. This standard is intended to guide the development of systems for commercial, government, military, and space applications. The information applies to a project within an enterprise that is responsible for developing a product design and establishing the life cycle infrastructure needed to provide for life cycle sustainment.



124. IEEE Std. 1228-1994

124-1. Title

IEEE Standard for Software Safety Plans

124-2. Status


124-3. Abstract

The minimum acceptable requirements for the content of a software safety plan are established. This standard applies to the software safety plan used for the development, procurement, maintenance, and retirement of safety-critical software. This standard requires that the plan be prepared within the context of the system safety program. Only the safety aspects of the software are included. This standard does not contain special provisions required for software used in distributed systems or in parallel processors.



125. IEEE Std. 1233-1998

125-1. Title

IEEE Guide for Developing System Requirements Specifications

125-2. Status


125-3. Abstract

This guide will be used for developing a system requirements specification. A System is a set of interconnected elements constituted to achieve defined objectives by performing specified functions. Development includes the thought process involved in the collection, analysis, and organization of the requirements. This guide addresses conditions for incorporating co-operational concepts and configuration design requirements into the system specifications. It will also describe the necessary content and qualities of a good system specification and present several prototype outlines.

This document will serve as a guide for defining functional, performance and interface requirements for a system. This guide will recommend methods for specifying the requirements and capabilities for systems. System specifications developed using this guide will:

• Facilitate a contracting agent to specify requirements for a system to potential designers/developers.

• Provide templates for writing/auditing system specifications, and

• Provide a general overview of a system which may be required by trainers, support personnel, or other users.

Once completed, this guide will provide a foundation on which an IEEE tutorial on Developing System Specification can be built. Guidance for the development of the set of requirements, System Requirements Specification (SyRS), that will satisfy an expressed need is provided. Developing a SyRS includes the identification, organization, presentation, and modification of the requirements. Also addressed are



the conditions for incorporating operational concepts, design constraints, and design configuration requirements into the specification. This guide also covers the necessary characteristics and qualities of individual requirements and the set of all requirements.



126. IEEE Std. 1233a-1998

126-1. Title

IEEE Guide for Developing System Requirements Specifications

126-2. Status


126-3. Abstract

To establish a correlation between the content of systems requirements specification as defined in 1233 and the content of such plans as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation. To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards.



127. IEEE Std. 1320.1-1998

127-1. Title

IEEE Standard for Functional Modeling Language - Syntax and Semantics for IDEF0

127-2. Status

127-3. Approved Publication of IEEE

127-4. Abstract

This project will define the standard syntax and semantics of IDEFO language and usage conventions. The IDEFO language deals with constructs, semantics and syntax of the language. It is used to produce a function model which is a structured representation of the functions of a system or environment, and the information and objects which interrelate those functions. The US Air Force ICAآ program, and commercial development of similar techniques, yielded the first versions of IDEFO in the 1980s. This standard will facilitate model interchange and improve the consistency of all IDEFO models.

"IDEF0 function modeling is designed to represent the decisions, actions, and activities of an existing or prospective organization or system. IDEF0 graphics and accompanying texts are presented in an organized and systematic way to gain understanding, support analysis, provide logic for potential changes, specify requirements, and support system-level design and integration activities. IDEF0 may be used to model a wide variety of systems, composed of people, machines, materials, computers, and information of all varieties and structured by the relationships among them, both automated and non-automated. For new systems, IDEF0 may be used first to define requirements and to specify functions to be carried out by the future system. As the basis of this architecture, IDEF0 may then be used to design an implementation that meets these requirements and performs these functions. For existing systems, IDEF0 can be used to analyze the functions that the system performs and to record the means by which these are done."



128. IEEE Std. 1320.2-1998

128-1. Title

IEEE Standard for Conceptual Modeling Language - Syntax and Semantics for IDEF1X97 (IDEF object)

128-2. Status


128-3. Abstract

This project will define the standard syntax and semantics of IDEF1X97. IDEF1X97 will consist of two modeling languages, a key-style data modeling language which is downward compatible with the IS Government's standard for data modeling (FIPS PUB 184), and an identity-style language suitable for object-oriented modeling. Key-style models are data models providing a structured representation of the data, the relationships among the data, and the business rules. Identity-style models are object models providing a structured representation of the objects, the static and dynamic relationships among them, and the business rules.

The US Air Force ICAM program and commercial development of similar techniques, yielded the first versions of IDEF 1X in the 1980s. A US Government Standard (FIPS PUB 184) published in 1993 formally defined the language. Continued evolution of the language and techniques will enable their use in significant information system development efforts, and ensure a common definition among all users, government and commercial.

"IEEE Std 1320.1-1998, IEEE Standard for Conceptual Modeling Language Syntax and Semantics for IDEF1X97 (IDEF object)"



129. IEEE Std. 1462-1998

129-1. Title

IEEE Adoption of ISO/IEC 14102:1995 Information Technology – Guideline for the Evaluation and Selection of CASE Tools

129-2. Status


129-3. Abstract

This standard defines a process for evaluating and selecting a Computer Aided Software Engineering 9CASE) tool for a software development or maintenance activity. The standard addresses the evaluation and selection of tools supporting software engineering processes including: project management processes, development processes, and integral processes.

The primary users of ISO/IEC 14402 are organizations that intend to adopt CASE tools to support their software life cycle processes. CASE tool suppliers may also use 14402 to describe the characteristics of their CASE tools. IEEE Std 1462-1998 is an adoption of International Standard ISO/IEC 14102:1995), Information technology Guidelines for the evaluation and selection of CASE tools.



130. IEEE Std. 1465-1998

130-1. Title

IEEE Standard - Adoption of International Standard ISO/IEC 12119:1994(E)- Information Technology - Software Packages - Quality Requirements and Testing

130-2. Status


130-3. Abstract

IEEE Std 1465-1998 is an adoption of ISO/IEC 12119: 1994(E). IEEE Std 1465-1998 may be employed to

• Specify quality requirements for software, and provide instructions on how to test against these requirements.

• Manage and improve the organizationصs quality processes and personnel.

• Establish management and engineering environments based on the quality requirements and methods in ISO/IEC 12119: 1994(E).

• Foster improved understanding between customers and vendors, and among other parties involved in the software product life cycle.

• Facilitate world trade in software.

The intended users of ISO/IEC 12119 are Suppliers of software packages; certification bodies which may wish to establish a third-party certification scheme; testing laboratories which will have to follow the instructions for testing when testing for a certificate or mark of conformity; accreditation bodies for accrediting certification bodies and testing laboratories; auditors of testing laboratories; buyers software packages; users who may profit from better products.

Quality requirements for software packages and instructions on how to test a software package against these requirements are established. The requirements apply to



software packages as they are offered and delivered, not to the production process including activities and intermediate products, such as specifications).



131. IEEE Std. 1471-2000

131-1. Title

IEEE Recommended Practice for Architectural Description for Software-Intensive Systems

131-2. Status

Approved Publication of IEEE, Published Date: Oct 09, 2000

131-3. Abstract

The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the "architectural level" of system development. The phrases "architectural level" and "architecture" are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision- making found in the civil architecture profession. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments, architectural frameworks, models and patterns, and techniques for architectural analysis, evaluation and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the "architectural level of



systems development," and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies.

However, there has not yet emerged any reliable consensus on a precise definition of a system's "architecture," how it should be described, what uses such descriptions may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices and other practices, and between architectural technology and other technology, are not yet widely recognized. In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this standard is intended to reflect generally accepted trends in practices for architectural description and to provide a technical framework for further evolution in this area. Furthermore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This standard codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.

An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.

"This recommended practice addresses the activities of the creation, analysis, and sustainment of architectures of software-intensive systems, and the recording of such architectures in terms of architectural descriptions. A conceptual framework for architectural description is established. The content of an architectural description is



defined. Annexes provide the rationale for key concepts and terminology, the relationships to other standards, and examples of usage."



132. IEEE Std. 1517-1999

132-1. Title

IEEE Standard for Information Technology - Software Life Cycle Processes - Reuse Processes

132-2. Status

Approved Publication of IEEE (Formerly known as 1420.4)

132-3. Abstract

The project would develop material referencing IEEE/EIA 12207 to describe software reuse processes and how they would relate to traditional software life cycle processes described in Part 0 of 12207. The document will define processes and specify requirements for the processes, but will not specify particular techniques. The scope of the specified processes will be broader than that of 12207.0 because reuse activities transcend the life cycle of any particular system. The specified processes would be suitable on an organization wide basis.

Most software reuse processes are not distinct from the normal life cycle but instead must be integrated into other life cycle processes. Some acquirers are requiring software reuse because it has the potential to achieve faster time to market, improved quality and cost avoidance. These considerations argue for a process standard that explains how software reuse processes may be incorporated into the life cycle. The purpose of the proposed effort is to develop referencing IEEE/EIA 12207 specifying software reuse processes and how they would be incorporated into the life cycle process framework already provided by 12207. The primary purpose of the document would be to facilitate communication between acquirer and supplier (who may be either internal or external to the organization), particularly regarding questions on the scope of the contract and questions regarding who bears the expense and gains the benefits of reuse efforts. The document would be useful within organizations to describe how reuse processes related to traditional life cycle processes, activities, and tasks.



"A common framework for extending the software life cycle processes of IEEE/EIA Std12207.0-1996 to include the systematic practice of software reuse is provided. This standard specifies the processes, activities, and tasks to be applied during each phase of the software life cycle to enable a software product to be constructed from reusable assets. It also specifies the processes, activities, and tasks to enable the identification, construction, maintenance, and management of assets supplied. "




133-1. Title

Standard for Information Technology - System and Software Life Cycle Processes - Reuse Processes

133-2. Status

Revision Project

133-3. Abstract

The project will develop material referencing IEEE/EIA 12207 to describe system and software reuse processes. It will describe the relationship of reuse processes to system life cycle processes described in Part 6 of 12207 and software life cycle processes described in Part 7 of 12207. The document will define processes and specify requirements for the processes but will not specify particular techniques. The scope of the specified processes will be broader than that of 12207 because reuse activities transcend the life cycle of any particular system. The specified processes will be suitable on an organization-wide basis.

Most reuse processes are not distinct from the normal life cycle but instead must be integrated into other life cycle processes. Some acquirers require reuse because it has the potential to achieve faster time-to-market, improved quality, and cost avoidance. These considerations compel a process standard that explains how reuse processes may be incorporated into the life cycle. The primary purpose of the document is to facilitate communication between acquirer and supplier (who may be either internal or external to the organization) of reusable resources.



134. IEEE Std. 1540-2001

134-1. Title

IEEE Standard for Software Life Cycle Processes - Risk Management

134-2. Status

Archived

134-3. Abstract




135-1. Title

Recommended Practice for Establishing and Managing Software Development Efforts Using Agile Methods

135-2. Status


135-3. Abstract

This Recommended Practice describes a process that a software development client should adopt and use in contracting with and working with an Agile software developer. It is intended that both the technical and project management personnel should apply these recommendations to be aware of and control the three aspects of software development: development status of specific features, progress through the development cycle, and expenditure of contract funds.

The purpose of this Recommended Practice is to provide software acquirers with a process that is suitable for establishing and managing an Agile-style software development. This Recommended Practice focuses on the definition and control of feature development and does not address aspects of software development independent of the Agile development methodology.




136-1. Title

Standard for SOA (Service-Oriented Architecture) Solution Reference Architecture

136-2. Status


136-3. Abstract

This document provides a standard protocol for creating service-oriented solution architecture. This protocol is independent of the underlying implementation and products used to realize the service-oriented architecture (SOA) based solutions. This protocol is usable in all classes of solution scenarios. This standard is limited to design and modeling of service-oriented solution architecture and does not include design or modeling of service-oriented implementation and supporting infrastructures.

There is currently no defined, independent standard for designing and modeling service-oriented solutions based on service-oriented architecture (SOA). Each vendor builds some design and architectures into the underlying programming language or business process flows. Without an independent, openly defined protocol, applications and other solutions cannot automatically determine the type of solution being communicated and integrated. This protocol provides a minimum implementation subset that allows automatic identification and configuration of service-oriented solutions and vendor extensibility, which will provide for growth and product differentiation.



137. IEEE Std. 2001-2002

137-1. Title

Recommended Practice for the Internet - Web Site Engineering, Web Site Management and Web Site Life Cycle

137-2. Status

Approved Publication of IEEE, Published Date: Mar 03, 2003 (Supersedes 2001-1999).

137-3. Abstract

Define recommended practices for World Wide Web page engineering for Intranet and Extranet environments, based on World Wide Web Consortium (W3C) and related industry guidelines. (Expanded from previous PAR which specifically mentioned HTML and XML). To address items identified in Annex A (future work) of the approved standard, and identified during balloting which can be well defined. Respond to emerging technology and changes in practice that may result in new material or changes to approved recommendations.

This is intended to provide guidance to web page developers in Intranet (organizational internal), and Extranet (amongst a limited domain of organizational participants) web environments on recommended practices for web page engineering. The objective is to improve the productivity of Intra/Extranet web operations in terms of locating relevant information, and efficient development and maintenance practices.

"Recommended practices for World Wide Web page engineering for Intranet and Extra-net environments, based on World Wide Web Consortium (W3C ®) and related industry guidelines, are defined in this recommended practice. This recommended practice does not address stylistic considerations or human-factors considerations in web page design beyond limitations that reflect good engineering practice."




138-1. Title

Standard for System and Software Life Cycle Processes—Requirements Engineering

138-2. Status

Revision Project

138-3. Abstract

The scope of this project is requirements engineering for systems and software, encompassing the activities associated with requirements definition, analysis, and management. The product descriptions that form the basis of IEEE 830-1998, Recommended Practice for Software Requirements Specifications and IEEE 1233-1998, IEEE Guide for Developing System Requirements Specifications, will be retained, with appropriate updating to reflect current practice, in informative annexes. This standard will be consistent with IEEE/EIA 12207.0-1996, Software Life Cycle Processes and IEEE 15288-2005, System Life Cycle Processes.

The purpose of this project is to replace two existing product standards, IEEE 830-1998, Recommended Practice for Software Requirements Specifications and IEEE 1233-1998, IEEE Guide for Developing System Requirements Specifications, with a new process-based standard that elaborates the process objectives and expected outcomes for the engineering of systems and software requirements, as specified in the life cycle framework standards, IEEE/EIA 12207.0-1996, Software Life Cycle Processes and IEEE 15288-2005, System Life Cycle Processes. It is expected that this standard will be used in support of process definition under 12207 and 15288.



139. IEEE Std. 12207-2008

139-1. Title

Systems and software engineering — Software life cycle processes

139-2. Status

Approved Publication of IEEE , Published Date: Jan 31, 2008 (Revision of IEEE/EIA 12207.0-1996)

139-3. Abstract

This International Standard 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. This International Standard 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. This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.

The processes, activities and tasks of this International Standard—either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.

The purpose of this International Standard is to provide a defined set of processes to facilitate communication among acquirers, suppliers and other stakeholders in the life cycle of a software product. This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products. This International Standard is intended for use in a two-party situation and may be



equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf software. This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products. This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf software.

This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It 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. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.



140. IEEE Std. 12207.1-1997

140-1. Title

Guide for Information Technology - Software Life Cycle Processes – Life Cycle Data

140-2. Status

Approved Publication of IEEE , Published Date: Apr 27, 1998 (This project was formerly known as P1448.1.)

140-3. Abstract

The base document ISO/IEC 12207, establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains activities, and tasks that are to be applied during the acquisition of a system that contains software, a stand-alone software product, and software service and during the supply, development, operation, and maintenance of software products.

Software includes software portion of firmware. The standard will provide an integrated set of data descriptions for recording or capturing the results of the software life cycle processes of ISO 12207. The proposed standard will relate the needs of the developer who produces the life cycle data to the presentation needs of the various parties who use the data. It will provide direction to which IEEE standards provide guidance on presentation and organization of the life cycle data.

The base document provides a consistent framework and related methods for the supplier and acquirer of software to establish, understand, and communicate between the acquirer and the supplier their respective responsibilities and the requirements for the software. The proposed standard will increase harmonization between IEEE standards and ISO 12207. Improve usability of ISO/IEC 12207 in the industrial environment. Provide an integrated content view of data produced by life cycle processes.

"ISO/IEC 12207 provides a common framework for developing and managing software. IEEE/EIA12207.0 consists of the clarifications, additions, and changes accepted by the



Institute of Electrical and Electronics Engineers (IEEE) and the Electronic Industries Association (EIA) as formulated by a joint project of the two organizations. IEEE/EIA 12207.1 provides guidance for recording life cycle data resulting from the lifecycle processes of IEEE/EIA 12207.0."



141. IEEE Std. 12207.2-1997

141-1. Title

Guide for Information Technology - Software Life Cycle Processes - Implementation Considerations

141-2. Status

Approved Publication of IEEE , Published Date: Apr 27, 1998 (This project was formerly known as P1448.2)

141-3. Abstract

The base document ISO/IEC 12207, establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains activities, and tasks that are to be applied during the acquisition of a system that contains software, a stand-alone software product, and software service and during the supply, development, operation, and maintenance of software products.

Software includes software portion of firmware. The proposed standard will provide guidance for software reuse, software process management indicators, categories for problem reporting, guidance on software/system architecture, development strategies, tailoring and build planning, and software product evaluations, alternate means of compliance for joint reviews, configuration management and acquirer-supplier interaction.

The base document provides a consistent framework and related methods for the supplier and acquirer of software to establish, understand, and communicate between the acquirer and the supplier their respective responsibilities and the requirements for the software. The proposed standard will increase harmonization between IEEE standards and ISO 12207. Improve usability of ISO/IEC 12207 in the industrial environment by providing more options as to its use. Improve the implementation of ISO 12207.



142. IEEE Std. 14143.1-2000

142-1. Title

IEEE Adoption of ISO/IEC 14143-1:1998 Information Technology – Software Measurement - Functional Size Measurement - Part 1: Definition of Concepts

142-2. Status

Approved Publication of IEEE, Published Date: Apr 05, 2000

142-3. Abstract

This part of ISO/IEC 14143 defines the fundamental concepts of Functional Size Measurement (FSM) and describes the general principles for applying an FSM method. This part of ISO/IEC 14143 does not provide detailed rules on how to

• Measure Functional Size of software using a particular method,

• Use the results obtained from a particular method,

• Select a particular method.

The definition of FSM in this part of ISO/IEC 14143 is applicable when determining if a method for sizing software is a Functional Size Measurement Method. It does not prevent the development of various methods, but rather provides a basis for assessing whether a particular method conforms to FSM. This part of ISO/IEC 14143 is intended for use by those persons associated with the acquisition, development, use, support, maintenance and audit of software.

The purpose of the adoption is to harmonize IEEE practices for functional size measurement with relevant international standards. The purpose of the standard is to provide criteria for conforming functional measurement methods.

Implementation notes that relate to the IEEE interpretation of ISO/IEC 14143-1:1998 are described.



143. IEEE Std. 14764-2006

143-1. Title

Standard for Software Engineering - Software Life Cycle Processes - Maintenance

143-2. Status

Approved Publication of IEEE, Published Date: Sep 01, 2006

143-3. Abstract

This standard describes an iterative process for managing and executing software maintenance activities. Use of this standard is not restricted by size, complexity, criticality, or application of the software product. This standard uses a process model to discuss and depict each phase of software maintenance. The criteria established apply to both the planning of maintenance for software while under development, as well as the planning and execution of software maintenance activities for existing software products. Ideally, maintenance planning should begin during the stage of planning for software development. This International Standard 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. This International Standard provides the framework, precise terminology, and processes to allow the consistent application of technology (tools, techniques, and methods) to software maintenance. This International Standard 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, system administration, which are normally performed by those who operate the software. This International Standard 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.



This International Standard provides guidance on the management of (or how to perform) the Maintenance Process. It identifies how the Maintenance Process can be invoked during acquisition and operation. This international Standard also emphasizes the following in the Maintenance Process: the maintainability of software products; the need for maintenance service models; and the need for a maintenance strategy and plan. The process for managing and executing software maintenance activities is described.



144. IEEE Std. P15026

144-1. Title

Standard for Systems and Software Engineering - Systems and Software Assurance

144-2. Status

Modified New Project

144-3. Abstract

This International Standard provides requirements for the life cycle including development, operation, maintenance, and disposal of systems and software products that are critically required to exhibit and be shown to possess properties related to safety, security, dependability, or other characteristics. It defines an assurance case as the central artifact for planning, monitoring, achieving and showing the achievement and sustainment of the properties and for related support of other decision making. The interaction of the requirements for the assurance case with life cycle processes implies a normative interpretation of the processes from ISO/IEC 15288 ISO/IEC 12207. Finally, the standard provides requirements, in addition to those of ISO/IEC 15289, for information artifacts that result from those processes.

The purpose of this International Standard is to assist users who wish to apply the provisions of ISO/IEC 15288 and ISO/IEC 12207 to systems required to possess critical properties. It is intended to give relevant requirements and guidance in addition to those of the two life cycle standards.



145. IEEE Std. 15288-2008

145-1. Title

Systems and software engineering System life cycle processes

145-2. Status

Approved Publication of IEEE , Published Date: Jan 31, 2008 (Revision of IEEE Std 15288-2004)

145-3. Abstract

This International Standard 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. This International Standard 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. This International Standard 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. The two standards are harmonized for concurrent use on a single project or in a single organization. When the system element is hardware, refer to other International Standards outside the scope of SC7.

The purpose of this International Standard is to provide a defined set of processes to facilitate communication among acquirers, suppliers and other stakeholders in the life



cycle of a system. This International Standard applies to organizations in their roles as both acquirers and suppliers. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations and the situation can range from an informal agreement to a formal contract. The processes in this International Standard can be used as a basis for establishing business environments, e.g., methods, procedures, techniques, tools and trained personnel. Annex A provides normative direction regarding the tailoring of these system life cycle processes.

This International Standard establishes a common process framework for describing the life cycle of man-made systems. It defines a set of processes and associated terminology for the full life cycle, including conception, development, production, utilization, support and retirement. This standard also supports the definition, control, assessment, and improvement of these processes. These processes can be applied concurrently, iteratively, and recursively to a system and its elements throughout the life cycle of a system.



146. IEEE Std. 15288-2007-2007

146-1. Title

Systems and Software Engineering -- System Life Cycle Processes

146-2. Status


146-3. Abstract



147. IEEE Std. P15289

147-1. Title

Standard for Systems and Software Engineering — Content of systems and software life cycle process information products (Documentation)

147-2. Status

Revision Project

147-3. Abstract

This standard identifies 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, and the specific purpose of the document. 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 agreement, enterprise, project, and technical processes; and the ISO/IEC 12207 primary, supporting, and organizational life cycle processes. The purpose of this International Standard is to guide users of ISO/IEC 12207 Information technology -- Software life cycle processes, and ISO/IEC 15288 Systems engineering — System life cycle processes, in identifying and planning the specific information items to be produced during systems and software life cycles.



148. IEEE Std. 15939-2008

148-1. Title

IEEE Standard Adoption of ISO/IEC 15939:2007--Systems and Software Engineering--Measurement Process

148-2. Status

Approved Publication of IEEE , Published Date: Jan 30, 2009 (Adoption of ISO/IEC 15939:2007)

148-3. Abstract

This International Standard identifies the activities and tasks that are necessary to successfully identify, define, select, apply and improve measurement within an overall project or organizational measurement structure. It also provides definitions for measurement terms commonly used within the system and software industries. This International Standard does not catalogue measures, nor does it provide a recommended set of measures to apply on projects. It does identify a process that supports defining a suitable set of measures that address specific information needs.

A measurement process applicable to system and software engineering and management disciplines is defined by this International Standard. The process is described through a model that defines the activities of the measurement process that are required to adequately specify what measurement information is required, how the measures and analysis results are to be applied, and how to determine if the analysis results are valid. The measurement process is flexible, tailorable, and adaptable to the needs of different users. This International Standard identifies a process that supports defining a suitable set of measures that address specific information needs. It identifies the activities and tasks that are necessary to successfully identify, define, select, apply, and improve measurement within an overall project or organizational measurement structure. It also provides definitions for commonly used measurement terms. This International Standard provides an elaboration of the measurement process from



ISO/IEC 15288:2008 and IEEE Std 15288-2008, as well as ISO/IEC 12207:2008 and IEEE Std 12207-2008.



149. IEEE Std. 16085-2006

149-1. Title

Standard for Systems and Software Engineering-Life Cycle Processes-Risk Management

149-2. Status

Approved Publication of IEEE , Published Date: Dec 15, 2006

149-3. Abstract

This project is being performed jointly with ISO/IEC JTC 1/SC 7. As a result of balloting in ISO, the statement of scope was modified as follows: "This standard describes a process for the management of risk during systems or software acquisition, supply, development, operations, and maintenance."

As a result of balloting in ISO, the statement of purpose was modified as follows: "The purpose of this standard is to provide suppliers, acquirers, developers, and managers with a single set of process requirements suitable for the management of a broad variety of risks. This standard does not provide detailed risk management techniques, but instead focuses on defining a process for risk management in which any of several techniques may be applied."

A process for the management of risk in the life cycle is defined. It can be added to the existing set of software life cycle processes defined by the ISO/IEC 12207 or ISO/IEC 15288 series of standards, or it can be used independently.



150. IEEE Std. P20000.1

150-1. Title

Standard for ISO/IEC 20000-1:2005, Information Technology — Service Management — Part 1: Specification

150-2. Status

150-3. New Standard Project

150-4. Abstract

This is an IEEE adoption of ISO/IEC 20000-1. The scope of ISO/IEC 20000-1 is: This part of ISO/IEC 20000 defines the requirements for a service provider to deliver managed services of an acceptable quality for its customers.

This standard provides the high level specification of requirements for delivery of managed services. It supports managed service acquisition, proposal, consistency, benchmarking or appraisal, and process improvement.



151. IEEE Std. P20000.2

151-1. Title

Standard for ISO/IEC 20000-2:2005, Information Technology — Service Management — Part 2: Code of Practice

151-2. Status


151-3. Abstract

This is an adoption of ISO/IEC 20000-2. The scope of ISO/IEC 20000-2 is: This part of ISO/IEC 20000 represents an industry consensus on quality standards for IT service management processes. These service management processes deliver the best possible service to meet a customer’s business needs within agreed resource levels, i.e. service that is professional, cost-effective and with risks which are understood and managed.

This part of ISO/IEC 20000 describes the best practices for service management processes in the form of guidance and recommendations that should be used in conjunction with ISO/IEC 20000-1, Information Technology — Service Management — Part 1: Specification. ISO/IEC 20000-1 defines the requirements for a service provider to deliver managed services of an acceptable quality for its customers.



152. IEEE Std. P24748

152-1. Title

Systems and software engineering — Guide for life cycle management

152-2. Status

Modified New Project

Abstract

This Technical Report is a guide for the life cycle management of systems and software based on ISO/IEC 15288 and ISO/IEC 12207. This guide:

• Addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains

• Establishes a common framework for describing life cycles, including their individual stages, for the management of projects to provide or acquire either products or services

• Defines the concept and terminology of a life cycle

• Supports the use of the life cycle processes within an organization or a project. Organizations and projects can use these life cycle concepts when acquiring and supplying either products or services

• Provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle

• Describes the relationship between life cycles and their use in ISO/IEC 15288 (systems aspects) and ISO/IEC 12207 (software aspects)

• Shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects



• Describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management and risk management

• complements domain-specific application guidance in Technical Reports ISO/IEC TR 15271 (Information technology—Guide for ISO/IEC 12207) and ISO/IEC TR 19760 (Systems engineering—Guide for the application of ISO/IEC 15288).



153. IEEE Std. P24765

153-1. Title

Standard for Systems and Software Engineering - Vocabulary

153-2. Status

Revision Project

153-3. Abstract

Consistent with ISO vocabulary standards, each technical committee is responsible for standard terminology in its area of specialization. ISO/IEC 24765 provides a common vocabulary applicable to all systems and software engineering work falling within the scope of ISO JTC1/SC7.

The purpose of this vocabulary is to serve as a useful reference for those in the Information Technology field, and to encourage the use of systems and software engineering standards prepared by ISO/IEC and liaison organizations IEEE and PMI (Project Management Institute). The goal is to provide definitions that are rigorous, uncomplicated, and which can be understood by all concerned.



154. IEEE Std. P25051

154-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

154-2. Status

Revision Project

154-3. Abstract

The Scope clause of the international standard to be adopted is long. The portion that corresponds to an IEEE scope is as follows:

This International Standard establishes:

• Quality requirements for COTS software products;

• Requirements for test documentation for the testing of COTS software products, including test requirements, test cases, and test reporting;

• Instructions for conformity evaluation of COTS software products.

NOTE: The collection of documents for test is called “test documentation”.

It includes also recommendations for safety or business critical COTS software products.

The international standard being adopted has no distinct purpose clause. The portion of its Scope clause that best matches an IEEE purpose is as follows:

The intended users of this International Standard include:

• Suppliers when: 1) specifying requirements for a COTS software product; 2) advertising performance claims for their product (ISO 9127); 3) assessing their own software products against the claimed performance; 4) issuing declarations of conformity (ISO/IEC 17050); 5) applying for certificates or marks of conformity (ISO/IEC Guide 23);



• Certification bodies that may wish to establish a third-party certification scheme (international, regional or national) (ISO/IEC Guide 28);

• Testing laboratories which will have to follow the instructions for testing when testing for a certificate or a mark of conformity (ISO/IEC 17025);

• Accreditation bodies for accrediting registration or certification bodies and testing laboratories;

• Potential acquirers who may: 1) compare the requirements for the intended work task with the information in product descriptions of existing software products; 2) look for certified COTS software product; 3) check if the requirements are otherwise met;

• End users who may profit from better software products;

• Organizations:1) establishing management and engineering environments based on the quality requirements and methods of this international standard; and 2) managing and improving their quality processes and personnel;

• Regulatory authorities who may require or recommend the requirements of this International Standard for COTS software products used in safety or business-critical applications.



155. IEEE Std. P42010

155-1. Title

Standard for Systems and Software Engineering --- Architectural Description

155-2. Status

Revision Project

155-3. Abstract

The scope of this standard encompasses those products of system and software development that capture architectural information, referred to as architectural descriptions". This includes architectural descriptions that are used for the following:

• Expression of the system or software and its evolution

• Communication among the stakeholders

• Evaluation and comparison of architectures in a consistent manner

• Planning, managing, and executing the activities of development

• Expression of the persistent characteristics and supporting principles of a system or software to guide acceptable change

• Verification of an implementation's compliance with an architectural description

• Recording contributions to the body of knowledge of systems and software architecture

The purpose of this standard is to facilitate the expression, communication and review of architectures and thereby lay a foundation for quality and cost gains through standardization of elements of and practices for architectural description.



156. IEEE Std. 90003-2008

156-1. Title

IEEE Guide--Adoption of ISO/IEC 90003:2004 Software Engineering-- Guidelines for the Application of ISO 9001:2000 to Computer Software

156-2. Status

Approved Publication of IEEE, Published Date: Nov 14, 2008 (This is an adoption of ISO/IEC 90003:2004)

156-3. Abstract

This International Standard provides guidance for organizations in the application of ISO 9001:2000 to the acquisition, supply, development, operation and maintenance of computer software and related support services. It does not add to or otherwise change the requirements of ISO 9001:2000. Annex A (informative) provides a table pointing to additional guidance in the implementation of ISO 9001:2000 available in ISO/IEC JTC 1/SC 7 and ISO/TC 176 standards.

The guidelines provided in this International Standard are not intended to be used as assessment criteria in quality management system registration/certification.

This standard provides guidance to users of IEEE standards as to how to meet the quality management expectations of ISO 9001:2000 clauses and sub-clauses in a software development context by adopting ISO/IEC 90003 (the software development guidance document for ISO 9001) and adding an informative annex to cross-reference IEEE S2ESC standards to relevant ISO 9001 material.

This standard is identical to ISO/IEC 90003 but contains an additional informative annex, Annex C, cross-referencing material in ISO 9001 with material in S2ESC standards that could be helpful in meeting the intent of ISO 9001, as well as a second additional annex, Annex D, which is a bibliography of the specific IEEE standards referenced.



157. IEEE Std. ISO/IEC 23026:2006(E)-2006

157-1. Title

Software Engineering---Recommended Practice for the Internet---Web Site Engineering, Web Site Management, and Web Site Life Cycle

157-2. Status

Approved Publication of IEEE , Published Date: Jun 01, 2006. This standard is an adoption of IEEE Std 2001-2002. ISO/IEC 23026:2006(E) will replace (be sold instead of) IEEE Std 2001-2002. ISO/IEC 23026:2006(E) does not supersede IEEE Std 2001-2002. IEEE Std 2001-2002 is archived in SOL.

157-3. Abstract

This document defines recommended practices for World Wide Web page engineering for Intranet and Extranet environments, based on World Wide Web Consortium (W3C®) and related industry guidelines. This recommended practice does not address stylistic considerations or human-factors considerations in Web page design beyond limitations that reflect good engineering practice. Annex B contains topics which are not sufficiently mature or where there are not specific recommendations for inclusion in the current issue of this recommended practice.

This recommended practice is intended to provide guidance to Web page developers in Intranet (organizational internal), and Extranet (amongst a limited domain of organizational participants) Web environments on recommended practices for Web page engineering. The objective is to improve the productivity of Intranet/Extranet Web operations in terms of locating relevant information, and efficient development and maintenance practices. The 2002 revision of this recommended practice addresses items identified in Annex A of IEEE Std 2001-1999 [B14] which can be well-defined and to respond to emerging technology and changes in practice that have resulted in new material or changes to approved recommendations. Conformance to this recommended practice in developing and publishing a Web site provides a basis for a well-engineered Web site.



Recommended practices for World Wide Web page engineering for Intranet and Extranet environments, based on World Wide Web Consortium (W3C )and related industry guidelines, are defined in this recommended practice. This recommended practice does not address stylistic considerations or human-factors considerations in web page design beyond limitations that reflect good engineering practice.




158-1. Title

Standard Classification for Software Anomalies

158-2. Status

Modified Revision Project

158-3. Abstract

This standard provides for the core set of attributes for classification of failures and defects. It is recognized that there are other attributes of failures or defects that are of unique value to specific applications or business requirements. This standard is applicable to any software (including operating systems, database management systems, applications, test-ware, firmware, and embedded software) and to any phase of the project, product, or system lifecycle by which the software is developed, operated, and sustained. Classification attributes are unaffected by the choice of lifecycle model, and that choice is outside the scope of this standard. Some tailoring of classification attribute values based on the chosen lifecycle is expected and consistent with the intent of this standard.

Problems may be precursors to failure recognition. These are the conditions by which a user recognizes the software performing in an undesirable manner. Similarly, actions taken in response to a failure and fault may be documented as a change request. Classification of problems and change requests is outside of the scope of this standard. Understanding the scope of this standard depends upon understanding the definitions in section 3, so it is advisable to read them before proceeding. Scope understanding is also dependent upon understanding the relationship between several conceptual entities. Although Software Change Request (SCR) and Software Release are not addressed within this standard, they are included in the diagrams to help clarify scope. As examples, these could have been shown in a number of different configurations. The one used here is the relatively simple case in which a Defect may be associated with a



single Corrective SCR and each SCR may be associated with, at the most, a single Release.

The purpose of this standard is to define a common vocabulary with which different people and organizations can communicate effectively about software anomalies and to establish a common set of attributes that support industry techniques for analyzing software defect and failure data.



159. IEEE Std. P16326

159-1. Title

Systems and software engineering — Life cycle processes — Project management

159-2. Status

Modified Revision Project

159-3. Abstract

There is no separate Scope statement in the final draft International Standard. This International Standard is intended to aid project managers in managing to successful conclusion those projects concerned with software-intensive systems and software products.

This International Standard specifies the required content of the project management plan (PMP). This International Standard also quotes the extracted purpose and outcome statements from the project processes of ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std. 15288-2008), and adds detailed guidance for managing projects that use these processes for software products and software-intensive systems.



160. IEEE Std. 1633-2008

160-1. Title

IEEE Recommended Practice on Software Reliability

160-2. Status

Approved Publication of IEEE , Published Date: Jun 27, 2008 (New Standard)

160-3. Abstract

Software reliability (SR) models have been evaluated and ranked for their applicability to various situations. Many improvements have been made in SR modeling and prediction since 1992. This revised recommended practice reflects those advances in SR since 1992, including modeling and prediction for distributed and network systems. Situation specific usage guidance was refined and updated. The methodologies and tools included in this recommended practice are extended over the software life cycle (SLC). The recommended practice promotes a systems approach to SR prediction. Although there are some distinctive characteristics of aerospace software, the principles of reliability are generic, and the results can be beneficial to practitioners in any industry.

The methods for assessing and predicting the reliability of software, based on a lifecycle approach to software reliability engineering, are prescribed in this recommended practice. It provides information necessary for the application of software reliability (SR) measurement to a project, lays a foundation for building consistent methods, and establishes the basic principle for collecting the data needed to assess and predict the reliability of software. The recommended practice prescribes how any user can participate in SR assessments and predictions.



161. ISO/IEC 42010:2007(E)-2007

161-1. Title

Systems and software engineering - Recommended practice for architectural description of software-intensive systems

161-2. Status

Approved Publication of IEEE , Published Date: Jul 15, 2007

161-3. Abstract

This recommended practice addresses the architectural description of software-intensive systems. A software-intensive system is any system where software contributes essential influences to the design, construction, deployment, and evolution of the system as a whole.

The scope of this recommended practice encompasses those products of system development that capture architectural information. This includes architectural descriptions that are used for the following:

• Expression of the system and its evolution

• Communication among the system stakeholders

• Evaluation and comparison of architectures in a consistent manner

• Planning, managing, and executing the activities of system development

• Expression of the persistent characteristics and supporting principles of a system to guide acceptable change

• Verification of a system implementation’s compliance with an architectural description

• Recording contributions to the body of knowledge of software-intensive systems architecture

The purpose of this recommended practice is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains



through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment, and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the architectural level of system development. The phrases architectural level and architecture are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision-making found in the development of civil architecture projects. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments; architectural frameworks, models, and patterns; and techniques for architectural analysis, evaluation, and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the architectural level of systems development, and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies. However, there has not yet emerged any reliable consensus on a precise definition of a system’s architecture, i.e., how it should be described, what uses such a description may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices, and other practices; and between architectural technology and other technology, are not yet widely recognized.

In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this recommended practice is intended to reflect generally accepted trends in practices for



architectural description and to provide a technical framework for further evolution in this area. Furthermore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This recommended practice codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.

This recommended practice addresses the activities of the creation, analysis, and sustainment of architectures of software-intensive systems, and the recording of such architectures in terms of architectural descriptions. A conceptual framework for architectural description is established. The content of an architectural description is defined. Annexes provide the rationale for key concepts and terminology, the relationships to other standards, and examples of usage.



MMiilliittaarryy SSttaannddaarrddss US Department of Defense (DoD) developed a set of standards for software development purposed. These standards are commonly used by all DoD agencies as well as contractors. Moreover, DoD uses other well-known standards such as IEEE 12207 and ISO/IEC 61508. This part provides a short list of the standards developed by DoD.

It should be noted the DoD also developed various standards for other applications such as telecommunication, logistic support, airborne computers, microcircuits, and electronic parts, which are outside of the scope of this document.



162. MIL-STD-498

162-1. Title

Software Development and Documentation

162-2. Status

Withdrawn in June 1998, after official release of IEEE/EIA 12207.

162-3. Abstract

The standard was published in December of 1994 as a replacement for DOD-STD-2167A and another software development standard, DOD-STD-7395. MIL-STD-498 was only approved as an interim standard, with an expected life of two years, and only because there was no similar commercial standard available at the time. The standard was canceled in June 1998 following official release of IEEE/EIA 12207.

MIL-STD-498 was intended to satisfy a large number of distinct goals:

• Improve compatibility with Incremental and Evolutionary development models.

• Decrease dependence on formal reviews and audits.

• Decrease emphasis on preparing documentation.

• Improve compatibility with computer-aided software engineering (CASE) tools.

• Improve links to systems engineering.

• Include the use of software management indicators.

• Improve coverage of modification, reuse, and reengineering.

• Increase emphasis on software supportability.

• Provide a clearer distinction between requirements and design.

• Improve compatibility with non-hierarchical design methods.

• Improve coverage of database development.

• Improve the criteria used for software product evaluation.



• Eliminate confusion between software quality assurance and software product evaluation.

• Extend configuration management concepts to in-process work products.

• Clarify relationships to other standards.

• Provide a means to order software via the Contract Data Requirements List (CDRL).

• Eliminate inconsistencies and holes in the Data Item Descriptions (DIDs).

The MIL-STD-498 package consists of the standard and 22 Data Item Descriptions (DIDs):

• Software Development Plan (SDP)

• Software Test Plan (STP)

• Software Installation Plan (SIP)

• Software Transition Plan (STrP)

• Operational Concept Description (OCD)

• System/Subsystem Specification (SSS)

• Software Requirements Specification (SRS)

• Interface Requirements Specification (IRS)

• System/Subsystem Design Description (SSDD)

• Software Design Description (SDD)

• Interface Design Description (IDD)

• Database Design Description (DBDD)

• Software Test Description (STD)

• Software Test Report (STR)

• Software Product Specification (SPS)

• Software Version Description (SVD)

• Software User Manual (SUM)



• Software Input/Output Manual (SIOM)

• Software Center Operator Manual (SCOM)

• Computer Operation Manual (COM)

• Computer Programming Manual (CPM)

• Firmware Support Manual (FSM)



163. MIL-STD-961E

163-1. Title

Unique Specifications Format and Content

163-2. Status

Released 2 April 2008, superseding MIL-STD-961E (1 August 2003).

163-3. Abstract

This standard covers the format and content requirements for developing defense specifications, which are used on multiple programs or applications, and program-unique specifications, which are used for a single program or system with little or no potential for use with other programs or systems. The policies governing such procedural matters as authorization for document development, coordination, comment resolution, indexing and distribution, application, and document maintenance can be found in DoD 4120.24-M, “Defense Standardization Program Policies and Procedures.”



164. MIL-STD-962D(1)

164-1. Title

Defense Standards Format and Content

164-2. Status

Released 2 April 2008

164-3. Abstract

This standard covers the format and content requirements for DoD standards, which include interface standards, standard practices, design criteria standards, test method standards, and manufacturing process standards. The previous revision to MIL-STD-962 also covered the requirements for DoD handbooks. These have been removed from this standard and are now covered by MIL-STD-967.



165. DOD 4120.24-M

165-1. Title

Defense Standardization Program (DSP) Policies and Procedures

165-2. Status

N/A

165-3. Abstract

N/A



166. MIL-STD-967

166-1. Title

……………

166-2. Status

……………..

166-3. Abstract

………………………



167. DOD-STD-1679A

167-1. Title

Software Development

167-2. Status

N/A

167-3. Abstract

N/A



168. DI-MCCR-80459

168-1. Title

Software Developmental Status Report (SDSR)

168-2. Status

N/A

168-3. Abstract

N/A



169. DI-MCCR-80491A

169-1. Title

Computer Software Flowchart

169-2. Status

N/A

169-3. Abstract

N/A



170. DI-MCCR-80700

170-1. Title

Computer Software Product End Items

170-2. Status

N/A

170-3. Abstract

N/A



171. DI-MCCR-80902

171-1. Title

Software Development Summary Report

171-2. Status

N/A

171-3. Abstract

N/A



172. DI-IPSC-80942

172-1. Title

Computer Software System Document

172-2. Status

N/A

172-3. Abstract

N/A



173. DI-NUOR-81412

173-1. Title

Software Certification Plan (SCP)

173-2. Status

N/A

173-3. Abstract

N/A



174. DI-IPSC-81427A

174-1. Title

Software Development Plan (SDP)

174-2. Status

N/A

174-3. Abstract

N/A



175. DI-IPSC-81428A

175-1. Title

Software Installation Plan (SIP)

175-2. Status

N/A

175-3. Abstract

N/A



176. DI-IPSC-81429A

176-1. Title

Software Transition Plan (STRP)

176-2. Status

N/A

176-3. Abstract

N/A



177. DI-IPSC-81433A

177-1. Title

Software Requirements Specification (SRS)

177-2. Status

N/A

177-3. Abstract

N/A



178. DI-IPSC-81435A

178-1. Title

Software Design Description (SDD)

178-2. Status

N/A

178-3. Abstract

N/A



179. DI-IPSC-81438A

179-1. Title

Software Test Plan (STP)

179-2. Status

N/A

179-3. Abstract

N/A



180. DI-IPSC-81439A

180-1. Title

Software Test Description (STD)

180-2. Status

N/A

180-3. Abstract

N/A



181. DI-IPSC-81440A

181-1. Title

Software Test Report (STR)

181-2. Status

N/A

181-3. Abstract

N/A



182. DI-IPSC-81441A

182-1. Title

Software Product Specification (SPS)

182-2. Status

N/A

182-3. Abstract

N/A



183. DI-IPSC-81442A

183-1. Title

Software Version Description (SVD)

183-2. Status

N/A

183-3. Abstract

N/A



184. DI-IPSC-81443A

184-1. Title

Software User Manual (SUM)

184-2. Status

N/A

184-3. Abstract

N/A



185. DI-IPSC-81444A

185-1. Title

Software Center Operator Manual (SCOM)

185-2. Status

N/A

185-3. Abstract

N/A



186. DI-IPSC-81445A

186-1. Title

Software Input/Output Manual (SIOM)

186-2. Status

N/A

186-3. Abstract

N/A



187. DI-IPSC-81488

187-1. Title

Computer Software Product

187-2. Status

N/A

187-3. Abstract

N/A



188. DI-IPSC-81633

188-1. Title

Software Programmer's Guide

188-2. Status

N/A

188-3. Abstract

N/A



189. DI-TMSS-81728

189-1. Title

Software Manual for Cryptographic Key Production Equipment

189-2. Status

N/A

189-3. Abstract

N/A



190. DI-MGMT-81739

190-1. Title

Software Resources Data Reporting: Initial Developer Report and Data Dictionary

190-2. Status

N/A

190-3. Abstract

N/A



191. DI-MGMT-81740

191-1. Title

Software Resources Data Reporting: Final Developer Report and Data Dictionary

191-2. Status

N/A

191-3. Abstract

N/A



192. DI-IPSC-81756

192-1. Title

Software Documentation

192-2. Status

N/A

192-3. Abstract

N/A



193. MIL-HDBK-348(1) NOT 1

193-1. Title

Satellite Control Network Hardware and Software Operational Acceptance Process

193-2. Status

N/A

193-3. Abstract

N/A



194. MIL-HDBK-1467 NOT 1

194-1. Title

Acquisition of Software Environments And Support Software

194-2. Status

N/A

194-3. Abstract

N/A



195. AQAP-150 ED.2

195-1. Title

NATO Quality Assurance Requirements For Software Development AQAP-150

195-2. Status

N/A

195-3. Abstract

N/A



196. AQAP-160 ED.1

196-1. Title

NATO Integrated Quality Requirements for Software Throughout The Life Cycle

196-2. Status

N/A

196-3. Abstract

N/A



197. ITOP-1.1.056

Software Performance Testing and Analysis

197-1. Status

N/A

197-2. Abstract

N/A



198. ITOP-1.1.057

198-1. Title

FR/GE/UK/US International Test Operations Procedure (ITOP) 1-1-057 Safety Critical Software Analysis and Testing

198-2. Status

N/A

198-3. Abstract

N/A



199. QAP-268 ED.1

199-1. Title

Guidance on the Use of Safety Critical Software Standards

199-2. Status

N/A

199-3. Abstract

N/A



200. ISO15939

Software Engineering - Software Measurement Process

200-1. Status

N/A

200-2. Abstract

N/A



BBrriittiisshh SSttaannddaarrdd IInnssttiittuuttee Standards are provided by BSI are generally corresponding to other global standards, such as ISO/IEC and IEEE.



201. BS 4058:1987

201-1. Title

Specification for data processing flow chart symbols, rules and conventions

201-2. Status

Published 29th May 1987

201-3. Abstract



202. BS 5760-8:1998

202-1. Title

Reliability of systems, equipment and components. Guide to assessment of reliability of systems containing software

202-2. Status

Published 15th Oct 1998

202-3. Abstract



203. BS 7649:1993

203-1. Title

Guide to the design and preparation of documentation for users of application software

203-2. Status


203-3. Abstract



204. BS 7830:1996

204-1. Title

Guide to the design and preparation of on-screen documentation for users of application software

204-2. Status


204-3. Abstract



205. BS 7925-1:1998

205-1. Title

Software testing. Vocabulary

205-2. Status

Published 15th Aug 1998

205-3. Abstract



206. BS IEC 60300-3-6:1997

206-1. Title

Dependability management. Application guide. Software aspects of dependability

206-2. Status

Published 15th Jan 1998

206-3. Abstract



207. BS IEC 61713:2000

207-1. Title

Software dependability through the software life-cycle processes. Application guide

207-2. Status


207-3. Abstract



208. BS ISO/IEC 12207:2008

208-1. Title

Systems and software engineering. Software life cycle processes

208-2. Status

Publication Date 28 February 2009. Replaces BS ISO/IEC 12207:1995.

208-3. Abstract

BS ISO/IEC 12207 is the first international standard to provide a comprehensive set of life cycle processes, activities, and tasks for software that is part of a larger system, and for stand alone software products and services. BS ISO/IEC 12207 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 to apply 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: BS ISO/IEC 12207 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. BS ISO/IEC 12207 also provides a process that can be employed for defining, controlling, and improving software life cycle processes. The processes, activities, and tasks of this standard (either alone or in conjunction with ISO/IEC 15288 )- may also be applied during the acquisition of a system that contains software. BS ISO/IEC 12207 can be used in one or more of the following modes:

• By an organization - to help establish an environment of desired processes. These processes can be supported by an infrastructure of methods, procedures, techniques, tools and trained personnel. The organization may then employ this environment to perform and manage its projects and progress



systems through their life cycle stages. In this mode this standard is used to assess conformance of a declared, established set of life cycle processes to its provisions.

• By a project - to help select, structure and employ the elements of an established set of life cycle processes to provide products and services. In this mode BS ISO/IEC 12207 is used in the assessment of conformance of the project to the declared and established environment.

• By an acquirer and a supplier -, to help develop an agreement concerning processes and activities. Via the agreement, the processes and activities in BS ISO/IEC 12207 are selected, negotiated, agreed to and performed. In this mode this standard is used for guidance in developing the agreement.

• By organizations and assessors - to perform assessments that may be used to support organizational process improvement.



209. BS ISO/IEC 14143-1:2007

209-1. Title

Information technology. Software measurement. Functional size measurement. Definition of concepts

209-2. Status

Published 30th Jun 2008

209-3. Abstract



210. BS ISO/IEC 14143-2:2002

210-1. Title

Information technology. Software measurement. Functional size measurement. Conformity evaluation of software size measurement methods to ISO/IEC 14143-1:1998

210-2. Status

Published 13th Dec 2002

210-3. Abstract



211. BS ISO/IEC 14143-6:2006

211-1. Title

Information technology. Software measurement. Functional size measurement. Guide for use of ISO/IEC 14143 series and related international standards

211-2. Status

Published 30th Jun 2006

211-3. Abstract



212. BS ISO/IEC 14598-1:1999

212-1. Title

Information technology. Software production evaluation. General overview

212-2. Status

Published15th Jul 1999

212-3. Abstract



213. BS ISO/IEC 14598-3:2000

213-1. Title

Information technology. Software production evaluation. Process for developers

213-2. Status

Published 15th Jan 2001

213-3. Abstract



214. BS ISO/IEC 14598-4:1999

214-1. Title

Information technology. Software production evaluation. Process for acquirers

214-2. Status


214-3. Abstract



215. BS ISO/IEC 14598-5:1998

215-1. Title

Information technology. Software production evaluation. Process for evaluators

215-2. Status


215-3. Abstract



216. BS ISO/IEC 14598-6:2001

216-1. Title

Information technology. Software production evaluation. Documentation of evaluation modules

216-2. Status

Published 20th Sep 2001

216-3. Abstract



217. BS ISO/IEC 14764:2006

217-1. Title

Software engineering. Software life cycle processes. Maintenance

217-2. Status

Published 31st Oct 2006

217-3. Abstract



218. BS ISO/IEC 15026:1998

218-1. Title

Information technology. System and software integrity levels

218-2. Status

Published 15th Feb 1999

218-3. Abstract



219. BS ISO/IEC 15288:2002

219-1. Title

Systems engineering. System life cycle processes

219-2. Status

Published 28th Nov 2002

219-3. Abstract



220. BS ISO/IEC 15289:2006

220-1. Title

Systems and software engineering. Content of systems and software life cycle process information products (documentation)

220-2. Status

Published 31st May 2006

220-3. Abstract



221. BS ISO/IEC 15504-1:2004

221-1. Title

Information technology. Process assessment. Concepts and vocabulary

221-2. Status


221-3. Abstract



222. BS ISO/IEC 15504-2:2003

222-1. Title

Software engineering. Process assessment. Performing an assessment

222-2. Status


222-3. Abstract



223. BS ISO/IEC 15504-3:2004

223-1. Title

Information technology. Process assessment. Guidance on performing an assessment

223-2. Status

Published 21st Jan 2004

223-3. Abstract



224. BS ISO/IEC 15504-4:2004

224-1. Title

Information technology. Process assessment. Guidance on use for process improvement and process capability determination

224-2. Status

Published 14th Jul 2004

224-3. Abstract



225. BS ISO/IEC 15504-5:2006

225-1. Title

Information technology. Process assessment. An exemplar process assessment model

225-2. Status

Published 28th Apr 2006

225-3. Abstract



226. BS ISO/IEC 15910:1999

226-1. Title

Information technology. Software user documentation process

226-2. Status


226-3. Abstract



227. BS ISO/IEC 15939:2007

227-1. Title

Systems and software engineering. Measurement process

227-2. Status


227-3. Abstract



228. BS ISO/IEC 16085:2006

228-1. Title

Systems and software engineering. Life cycle processes. Risk management

228-2. Status


228-3. Abstract



229. BS ISO/IEC 16326:1999

229-1. Title

Software engineering. Guide for the application of ISO/IEC 12207 to project management

229-2. Status


229-3. Abstract



230. BS ISO/IEC 19770-1:2006

230-1. Title

Software asset management. Processes

230-2. Status

Published 31st May 2006

230-3. Abstract



231. BS ISO/IEC 24744:2007

231-1. Title

Software engineering. Meta-model for development methodologies

231-2. Status

Published 30th Mar 2007

231-3. Abstract



232. BS ISO/IEC 24773:2008

232-1. Title

Software engineering. Certification of software engineering professionals. Comparison framework

232-2. Status

Published 31st Mar 2009

232-3. Abstract



233. BS ISO/IEC 25000:2005

233-1. Title

Software engineering. Software product quality requirements and evaluation (SQuaRE). Guide to SQuaRE

233-2. Status


233-3. Abstract



234. BS ISO/IEC 25001:2007

234-1. Title

Software engineering. Software product quality requirements and evaluation (SQuaRE). Planning and management

234-2. Status


234-3. Abstract



235. BS ISO/IEC 25012:2008

235-1. Title

Software engineering. Software product quality requirements and evaluation (SQuaRE). Data quality model

235-2. Status


235-3. Abstract



236. BS ISO/IEC 25020:2007

236-1. Title

Software engineering. Software product quality requirements and evaluation (SQuaRE). Measurement reference model and guide

236-2. Status

Published 31st Jul 2007

236-3. Abstract



237. BS ISO/IEC 25030:2007

237-1. Title

Software engineering. Software product quality requirements and evaluation (SQuaRE). Quality requirements

237-2. Status


237-3. Abstract



238. BS ISO/IEC 25051:2006

238-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

238-2. Status


238-3. Abstract

……………………………………..



239. BS ISO/IEC 25062:2006

239-1. Title

Software engineering. Software product. Quality requirements and evaluation (SQuaRE). Common industry format (CIF) for usability test reports

239-2. Status


239-3. Abstract



240. BS ISO/IEC 26514:2008

240-1. Title

Software and systems engineering. Requirements for designers and developers of user documentation

240-2. Status


240-3. Abstract



241. BS ISO/IEC 26702:2007

241-1. Title

Systems engineering. Application and management of the systems engineering process

241-2. Status

Published 31st Aug 2007

241-3. Abstract



242. BS ISO/IEC 42010:2007

242-1. Title

Systems and software engineering. Recommended practice for architectural description of software-intensive systems

242-2. Status


242-3. Abstract



243. BS ISO/IEC 90003:2004

243-1. Title

Software engineering. Guidelines for the application of ISO 9001:2000 to computer software

243-2. Status


243-3. Abstract



244. BS ISO/IEC 9126-1:2001

244-1. Title

Information technology. Software product quality. Quality model

244-2. Status

Published 15th Jul 2001

244-3. Abstract



245. BS ISO/IEC ISP 15287-2:2000

245-1. Title

Information technology. Standardized application environment profile. Posix Realtime Application Support (AEP)

245-2. Status


245-3. Abstract



246. BS ISO/IEC TR 12182:1998

246-1. Title

Information technology. Categorization of software

246-2. Status


246-3. Abstract



247. BS ISO/IEC TR 14143-4:2002

247-1. Title

Information technology. Software measurement. Functional size measurement. Reference model

247-2. Status


247-3. Abstract



248. BS ISO/IEC TR 14759:1999

248-1. Title

Software engineering. Mock up and prototype. A categorization of software mock up and prototype models and their use

248-2. Status


248-3. Abstract



249. BS ISO/IEC TR 15271:1998

249-1. Title

Information technology. Guide for ISO/IEC 12207. (Software life cycle processes)

249-2. Status


249-3. Abstract



250. BS ISO/IEC TR 15846:1998

250-1. Title

Information technology. Software life cycle processes. Configuration management

250-2. Status


250-3. Abstract



251. PD ISO/IEC TR 14143-3:2003

251-1. Title

Information technology. Software measurement. Functional size measurement. Verification of functional size measurement methods

251-2. Status


251-3. Abstract



252. PD ISO/IEC TR 14143-5:2004

252-1. Title

Information technology. Software measurement. Functional size measurement. Determination of functional domains for use with functional size measurement

252-2. Status

Published 1st Apr 2004

252-3. Abstract



253. PD ISO/IEC TR 14471:2007

253-1. Title

Information technology. Software engineering. Guidelines for the adoption of CASE tools

253-2. Status

Published

253-3. Abstract



254. PD ISO/IEC TR 15504-6:2008

254-1. Title

Information technology. Process assessment. An exemplar system life cycle process assessment model

254-2. Status


254-3. Abstract



255. PD ISO/IEC TR 15504-7:2008

255-1. Title

Information technology. Process assessment. Assessment of organizational maturity

255-2. Status


255-3. Abstract



256. PD ISO/IEC TR 19760:2003

256-1. Title

Systems engineering. A guide for the application of ISO/IEC 15288 (System life cycle processes)

256-2. Status

Published 23rd Feb 2004

256-3. Abstract



257. PD ISO/IEC TR 19760:2003

257-1. Title

Systems engineering. A guide for the application of ISO/IEC 15288 (System life cycle processes)

257-2. Status


257-3. Abstract



258. PD ISO/IEC TR 24774:2007

258-1. Title

Software and systems engineering. Life cycle management. Guidelines for process description

258-2. Status


258-3. Abstract



259. PD ISO/IEC TR 25021:2007

259-1. Title

Software engineering. Software product quality requirements and evaluation (SQuaRE). Quality measure elements

259-2. Status

Published 31st Dec 2007

259-3. Abstract



260. PD ISO/IEC TR 90005:2008

260-1. Title

Systems engineering. Guidelines for the application of ISO 9001 to system life cycle processes

260-2. Status


260-3. Abstract



261. PD ISO/IEC TR 9126-2:2003

261-1. Title

Software engineering. Product quality. External metrics

261-2. Status


261-3. Abstract



262. PD ISO/IEC TR 9126-3:2003

262-1. Title

Software engineering. Product quality. Internal metrics

262-2. Status


262-3. Abstract



263. PD ISO/IEC TR 9126-4:2004

263-1. Title

Software engineering. Product quality. Quality in use metrics

263-2. Status

Published 2nd Apr 2004

263-3. Abstract



264. PD ISO/IEC TR 9294:2005

264-1. Title

Information technology. Guidelines for the management of software documentation

264-2. Status


264-3. Abstract



AANNSSII SSttaannddaarrddss ANSI has no specific standard regarding Software and System engineering, but promoting and supporting other Standardization bodies, such as ISO/IEC, IEEE and BSI.



BBrriittiisshh CCoommppuutteerr SSoocciieettyy BCS supports standards announced and promoted by BSI, in the context of Software and System engineering.



IISSIIRRII Institute of Standards and Industrial Research of Iran (ISIRI for short), focuses on development as well as adoption of standards for domestic purposed. Some of the standards provided and supported by ISIRI are Persian translations for their correspond international standards, such as ISO/IEC 25000. There are also some specific standards regarding localization of data entry and data exchange in Persian language.



265. ISIRI - ISO 25001

265-1. Title

Software engineering - Software product quality requirements and evaluation - Planning and management

265-2. Status

Published 1386 (2007)

265-3. Corresponding International Standard

ISO/IEC 25001:2005



266. ISIRI-ISO 25030

266-1. Title

Software engineering -- Software product Quality Requirements and Evaluation (SQuaRE) -- Quality requirements

266-2. Status



ISO/IEC 25030:2005



267. ISIRI 9965

267-1. Title برگه طراحي فرمها و صفحه رسم

267-2. Status



ISO 3535



268. ISIRI 9966

268-1. Title هايي براي مستند سازي سيستمهاي آاربردي بر مبناي آامپيوتر راهنمايي

268-2. Status



ISO 6592



269. ISIRI 8168-1

269-1. Title اصول آلي حاآم بر چيدمان صف: ١ قسمت –هاي اداري و سامانه چيدمان صحفه آليد براي متن –آوري اطالعات فن

269-2. Status



ISO/IEC 9995-1



270. ISIRI 8168-2

270-1. Title عددي-بخش حرفي : ٢ قسمت –هاي اداري طرح بندي صفحه آليد براي متن و سامانه–آوري اطالعات فن

270-2. Status



ISO/IEC 9995-2



271. ISIRI 8168-3

271-1. Title چيدمان مكمل ناحيه حرفی: ٣ قسمت –هاي اداري طرح بندي صفحه آليد براي متن و سامانه–آوري اطالعات فن

271-2. Status



ISO/IEC 9995-3



272. ISIRI 8168-4

272-1. Title بخش عددي: ٤ قسمت –هاي اداري چيدمان صحفه آليد براي متن و سامانه-آوري اطالعات فن

272-2. Status



ISO/IEC 9995-4



273. ISIRI 8168-5

273-1. Title بخش ويرايش: ٥ قسمت –هاي اداري د براي متن و سامانه چيدمان صحفه آلي-آوري اطالعات فن

273-2. Status



ISO/IEC 9995-5



274. ISIRI 8168-6

274-1. Title بخش تابع: ٦ قسمت –هاي اداري چيدمان صحفه آليد براي متن و سامانه-آوري اطالعات فن

274-2. Status



ISO/IEC 9995-6



275. ISIRI 8168-7

275-1. Title نمادهاي به آار رفته براي بيان : ٧ قسمت –هاي اداري چيدمان صحفه آليد براي متن و سامانه-آوري اطالعات فن

275-2. Status



ISO/IEC 9995-7



276. ISIRI 8168-8

276-1. Title تخصيص حروف به آليدهاي مجموعه : ٨ قسمت –هاي اداري چيدمان صحفه آليد براي متن و سامانه-آوري اطالعات فن

276-2. Status



ISO/IEC 9995-8



277. ISIRI 8173

277-1. Title متن و –هاي آيفيت تصوير براي تصوير چاپي خروجي گيري خصيصه اندازه–يزات اداري تجه–آوري اطالعات فن

تصوير

277-2. Status



ISO/IEC 13660



278. ISIRI 8174

278-1. Title شدههاي صفحه آليد قطعه بندي جانمايي–آوري اطالعات فن-آوري اداري رايانه و فن

278-2. Status



ISO/IEC 15411



279. ISIRI 9147

279-1. Title چيدمان حروف و عاليم فارسي بر صفحه آليد رايانه–آوري اطالعات فن

279-2. Status



None.



280. ISIRI 8085-1

280-1. Title معرفي و اصول آلي : اي معماري اسناد باز و قالب مبادله–آوري اطالعات فن

280-2. Status



ISO/IEC 8613-1



281. ISIRI 8085-2

281-1. Title يير مدارك واسط مجرد براي اصالح و تغ: اي معماري مدرك باز و قالب مبادله–آوري اطالعات فن

281-2. Status



ISO/IEC 8613-3



282. ISIRI 8085-3

282-1. Title شماي مدرك: اي معماري مدرك باز و قالب مبادله–آوري اطالعات فن

282-2. Status



ISO/IEC 8613-4



283. ISIRI 9796-1

283-1. Title مشخصات: قسمت اول- مديريت خدمات-فناوري اطالعات

283-2. Status



ISO/IEC 20000-1



284. ISIRI 9796-2

284-1. Title قواعد آار: قسمت دوم- مديريت خدمات-فناوري اطالعات

284-2. Status



ISO/IEC 20000-2

<END OF DOCUMENT>

SOFTWARE AND SYSTEMS ENGINEERING...

Documents

Transcript of SOFTWARE AND SYSTEMS ENGINEERING...