Requirements Specification of the Vertical Industrial Use Case ... - IKS

More documents

Recommendations

Info

14 / 196Deliverable 2.3: Requirements Specification for the Vertical Industrial Use CaseIn the following sections, these challenges are described in more detailed and their relevancefor the vertical industrial use case of the domain “software engineering” is described.1.1.5.1 Clustering of ArtefactsThe clustering of content provides algorithms for the (semi-) automatic creation of contentclusters. Such clusters group cross-media items or artefacts which address the same topic,e.g.: “The interaction of the user with content”. Figure 2 gives a schematic overview aboutthe general approach to content clustering, bringing together content from different levels ofabstraction and in various notations.Figure 2: Clustering of content itemsAccording to the current capabilities of ALM tools, there are still desirable features and functionalitiesfor the clustering of software engineering artefacts and these are currently unsupported.It should be possible to automatically cluster content items from different activities ofthe software engineering process. This requires the capability to analyse different kinds ofcontent items and to define by which criteria these items should be clustered. In addition, appropriatelabels for the clusters should be defined, which identifies the common topic addressedby the clustered content items.© IKS Consortium2010
15 / 196Deliverable 2.3: Requirements Specification for the Vertical Industrial Use Case1.1.5.2 Traceability among Software Engineering ArtefactsThe traceability among content items is realized by the (semi-)automatic creation of links betweenthe different content items. As shown in Figure 3, different kinds of links represent therelations among the artefacts.Figure 3: Traceability among software engineering artefactsThe analysis of existing tools has shown that these still lack capabilities to (semi-) automaticallycreate links between content items to provide traceability. At first, it needs to be possibleto specify different kinds of relations that can be defined between content items andcorresponding rules for the creation of these relations. Furthermore, a CMS should be able toanalyse content items described in different notations, and relate them to each other accordinga given rule set. In other words, current software engineering tools are weak on basicCMS as well as semantic CMS functionality.1.1.5.3 Redundancy CheckThe redundancy check for software engineering artefacts should support the consolidation ofsoftware specifications. Therefore duplicates, especially in the requirements specificationshould be identified. The calculation of the similarity between different requirement descriptionscan also be used to aggregate content items.On the one hand, there is the need for reorganization and consolidation of requirements especiallyin large, complex software projects. On the other hand, is there not sufficient supportby current RE/RM and ALM tools as shown in section 2.1.4. Thus the calculation of similaritiesamong content items and the identification of duplicates are still open challenges for themanagement of software engineering artefacts.© IKS Consortium2010
Page 2 and 3: 2 / 196Deliverable 2.3: Requirement
Page 10 and 11: 10 / 196Deliverable 2.3: Requiremen
Page 64 and 65:
64 / 196Deliverable 2.3: Requiremen
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
100 / 196Deliverable 2.3: Requireme
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196:
show all

Requirements Specification of the Vertical Industrial Use Case ... - IKS

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?