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

More documents

Recommendations

Info

30 / 196Deliverable 2.3: Requirements Specification for the Vertical Industrial Use CaseActor Short name DescriptioncreatorAdvancedcontentcreatorContentmanagerAdvancedcreatorManagerand advise. On the other hand the novice content creator creates mostcontent elements withouht beeing responsible for the content.The advanced creator is the power-backend-user of a CMS, who usesall functionalities of the CMS backend. This actor manages products,articles, news, and publishes the content.The content manager is the super user for content consumption andcreation. The manager knows the CMS in detail and is able toconfigure and manage the workflows within the CMS.Administrator AdminThe CMS administrator configures and maintains the CMS and theintegrated IKS services. The admin is the power user who configuresthe used IKS services inside the CMS.Developer Developer All use cases that handle development or integration tasks areassociacted with some developer actor.IKSDeveloperCMSDeveloperIKSCustomizerIKS servicecustomizerIKSDeveloperCMSDeveloperIKSCustomizerServiceCustomizerThe IKS developer is an architect, designer or programmer of IKS corefunctionalities.A CMS developer is an architect, designer or programmer of a CMS.CMS programmers can customize the IKS as they are specialized IKScustomizers and specialized service customizers.The IKS customizer is an architect, designer or programmer that is ableto customize the IKS, e.g. implement a new semantic service using theIKS infrastructure. The customizer does not implement or change thecore of the IKS.An IKS service customizer customizes existing IKS services, e.g. byusing defined extension points of an IKS service.© IKS Consortium2010
31 / 196Deliverable 2.3: Requirements Specification for the Vertical Industrial Use Case3 High Level RequirementsIn this section, the high-level requirements of the industrial vertical use case are described.According to the requirements specification methodology described in section 2 the highlevelrequirements are described by scenarios from the different domains and refined intouse cases and concrete IKS requirements.In the domains “Software engineering”, “Portal market for travel agencies” and “News marketfor journalists´ teams” the following high-level requirements have been identified:HLR-2301: Content clustering (“Software engineering”)HLR-2302: Traceability among content items (“Software engineering”)HLR-2303: Calculation of correlation among content (“Software engineering”)HLR-2304: Information Extraction (“News market for journalists´ teams”)HLR-2305: Content Enrichment (“Portal market for travel agencies”, “News market forjournalists´ teams”) HLR-2306: Personalized content search assistance (“Portal market for travel agencies”)3.1 HLR-2301: Content clusteringHLR IDNameDescriptionClassificationDomainsHLR-2301Content clusteringIn order to be able to handle different kinds of unstructured and structureddata, the IKS should provide the (semi-)automatic clustering ofcontent.VerticalSoftware engineering (Clustering & Annotation),Relatedrequirements3.1.1 ScenariosScenario 1 (Automatic flat clustering):The software architect in a large software project tries to get an overview about the complexityof the given requirements specification by structuring them in different categories. The requirementsspecification is stored in a CMS. In order to cluster and categorize the content oflarge requirements specification, a service should be available that allows the automatic clus-© IKS Consortium2010
Page 2 and 3: 2 / 196Deliverable 2.3: Requirement
Page 10 and 11: 10 / 196Deliverable 2.3: Requiremen
Page 80 and 81:
80 / 196Deliverable 2.3: Requiremen
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

Create successful ePaper yourself

Delete template?

Save as template?