Requirements Specification of the Vertical Industrial Use Case ... - IKS
Requirements Specification of the Vertical Industrial Use Case ... - IKS
Requirements Specification of the Vertical Industrial Use Case ... - IKS
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
26 / 196Deliverable 2.3: <strong>Requirements</strong> <strong>Specification</strong> for <strong>the</strong> <strong>Vertical</strong> <strong>Industrial</strong> <strong>Use</strong> <strong>Case</strong>2 <strong>Requirements</strong> <strong>Specification</strong> MethodologyIn this section, <strong>the</strong> requirements specification process used for <strong>the</strong> elicitiation anddocumentation <strong>of</strong> <strong>the</strong> requirements in <strong>the</strong> vertical use case are described. At first, <strong>the</strong> highlevelrequirements dervied from <strong>the</strong> different domains are summarized. Afterwards <strong>the</strong>refinement process is defined. We use domain-specifc scenarios to describe <strong>the</strong> high-levelrequirements. Based on <strong>the</strong> scenarios, use cases are derived, which are <strong>the</strong>n refined intoconcrete s<strong>of</strong>tware requirements.2.1 High-level requirementsThe objective <strong>of</strong> <strong>the</strong> analysis <strong>of</strong> <strong>the</strong> different domains described in section 1 was <strong>the</strong>identification <strong>of</strong> domain-specific business and technological needs from which high-levelrequirements can be derived. The grouping <strong>of</strong> <strong>the</strong>se needs into high-level requirementsprovides a starting point for <strong>the</strong> following specification and refinement process. Although <strong>the</strong>domains have been analyzed separately, <strong>the</strong> aggregation to high-level requirements hasshown that even diverse needs from different domains can be summarized in <strong>the</strong> same highlevelrequirement (HLR-2305: Content Enrichment). HLR-2301: Content clustering (“S<strong>of</strong>tware engineering”)HLR-2302: Traceability among content items (“S<strong>of</strong>tware engineering”)HLR-2303: Calculation <strong>of</strong> correlation among content (“S<strong>of</strong>tware 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”)2.2 <strong>Requirements</strong> refinement processThe requirements specification in this deliverable is structured according to <strong>the</strong> IEEE-830standard for recommended practice for s<strong>of</strong>tware requirements specifications [IEEE1998].The requirements specification and elicitation is a successive refinement process. After defininghigh-level requirements, each is refined into use cases and concrete s<strong>of</strong>tware requirementsas shown in Figure 14.© <strong>IKS</strong> Consortium2010
Change language