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

More documents

Recommendations

Info

4 / 196Deliverable 2.3: Requirements Specification for the Vertical Industrial Use CaseIKS in a Nutshell“Interactive Knowledge Stack” (IKS) is an integrating project targeting small to medium ContentManagement Systems (CMS) providers in Europe providing technology platforms forcontent and knowledge management to thousands of end user organizations. Current CMStechnology platforms lack the capability for semantic web enabled, intelligent content, andtherefore lack the capacity for users to interact with the content at the user’s knowledge level.The objective of IKS therefore, is to bring semantic capabilities to current CMS frameworks.IKS puts forward the “Semantic CMS Technology Stack” which merges the advances in semanticweb infrastructure and services with CMS industry needs of coherent architecturesthat fit into existing technology landscapes. IKS will provide the specifications and at leastone Open Source Reference Implementation of the full IKS Stack. To validate the IKS Stackprototype solutions for industrial use cases ranging from ambient intelligence infotainment,project management and controlling to an online holiday booking system will be developed.Executive SummaryThe objective of this deliverable is to provide requirements for IKS by analysing industrialvertical use cases and their domain-specific needs. We decided to look at three different domainsin order to factor out common features and real, domain specific requirements. Thedomains “software engineering”, “news market for journalists’ teams” and “portal market fortravel agencies” were analyzed. Addressing the needs of the domain “software engineering”existing requirements management (RM) and application lifecycle management (ALM) toolswere analyzed with respect to their semantic capabilities. By identifying as yet, unsupportedfunctionalities, a set of high-level requirements for this domain was derived.The existing CMS of the industrial partners TXT and CIC/Pisano were analyzed addressingthe domains “news market for journalists’ teams” and “portal market for travel agencies”, respectively.Furthermore business goals and scenarios from these domains were captured toelicit their domain specific requirements. Using a formalised process for refining requirements,concrete lower-level requirements were derived from the high-level goals. As a result,requirements from three different domains with different business-driven goals were gatheredfor the specification of requirements for the IKS.Section 1 describes each of the three application domains and points at specific challengesthat the domain poses for content management. In section 2 the methodology for requirementsspecification and refinement are described. This includes a model of Actors to be usedfor describing the stakeholders of the various requirements. Section 3 contains the main outcomeof this work: a set of more than 120 concrete and testable requirements derived fromthe domain-specific high-level requirements.This deliverable should be seen in the context of other work in the first phase of IKS, all ofwhich led to specifications of requirements, from different perspectives: D 1.3 generated requirementsfrom analyses of surveys as well as from analyses of benchmarking exercisesconducted by industrial partners. D2.1. (Ambient Intelligence Case) and D2.4 (Project ControllingTool) generated detailed requirements for two larger scale usage scenarios which willlead to software demonstrators for IKS. D2.2 was the counterpart of this deliverable, lookingat hoizontal, i.e. generally valid requirements for semantics-enhanced CMS. A consolidatedset of requirements is expected once the results of WP3 (Requirements from the perspectiveof the layers of the IKS Stack) are finalised and merged with those of WP1 and WP2.© IKS Consortium2010
5 / 196Deliverable 2.3: Requirements Specification for the Vertical Industrial Use Case1 Vertical Industrial Use CasesThis section gives an overview about the different domains analyzed in the vertical industrialuse case. The investigation of domain specific applications will lead to a list of high-level requirementswhich provide the starting point for the requirements specification process finallybringing up concrete and testable requirements.One the one hand, the software engineering domain is analyzed from a more theoretical perspective.Therefore the specific needs for the management of the different kinds of contentitems created in the software engineering process are investigated. Furthermore an evaluationof the tool support by existing ALM tools is done to identify missing capabilities in thestate-of-the-art. Finally the remaining challenges for the management of software engineeringartefacts are described and the IKS high-level requirements from this domain are derived.On the other hand domains of CMS providers focussing on “news market for journalists’teams” and “portal market for travel agencies” are part of the investigation. Industrial partners(TXT and PISANO) working in these domains provide input for the specification of high-levelrequirements and corresponding scenarios driven by their business needs to the InteractiveKnowledge Stack. Furthermore the existing CMS are analyzed regarding their capabilitiesand desirable capabilities or enhancements are identified.1.1 Software EngineeringIn this section the software engineering domain is introduced as the first vertical industrialuse case of the analysis. In order to derive high level requirements for this domain, the softwareengineering domain and the central concepts behind it are investigated, focussing onthe artefacts and content items that have to be managed in the software engineering process.The discipline of software engineering aims at the development of software at a high level ofquality. The research done in this field led to different approaches, processes and methodologiessupporting the engineering of software in different phases through the whole lifecycle.In the first step, the actual needs and requirements which should be addressed by the softwarehave to be identified. Therefore the stakeholder requirements are elicited, documentedand consolidated. The requirements engineering process is a consequent refinement approachstarting from business related high-level requirements which are successively refinedinto concrete software requirements (comparable to the structure and approach of this deliverable).The software addressing these requirements can be designed by using architecturaldescription languages (ADLs) like UML. The design is done on different levels of abstraction.Identified layers and modules represent logical groups of reusable components. In a moreconcrete granularity the components itself, their subcomponents, interfaces and relations aredesigned. The designed software is implemented in an appropriate programming languageand tested against the requirements.Existing process models (e.g. waterfall, agile approaches) provide frames for managing themain activities: Analysis, Design, Implementation and Test. Nevertheless, in addition to theorganization of these activities a remaining challenge is the management of the contentwhich is created in the different activities.1.1.1 Content Items in the Software Engineering ProcessAs described in the previous section, different kinds of content items are created in the softwareengineering process. We will investigate the activities Analysis, Design, Implementation© IKS Consortium2010
Page 2 and 3: 2 / 196Deliverable 2.3: Requirement
Page 10 and 11: 10 / 196Deliverable 2.3: Requiremen
Page 54 and 55:
54 / 196Deliverable 2.3: Requiremen
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
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

Create successful ePaper yourself

Delete template?

Save as template?