Presentation is loading. Please wait.

Presentation is loading. Please wait.

Co-funded by the European Union Semantic CMS Community Requirements Engineering for Semantic CMS Copyright IKS Consortium 1 Lecturer Organization Date.

Similar presentations


Presentation on theme: "Co-funded by the European Union Semantic CMS Community Requirements Engineering for Semantic CMS Copyright IKS Consortium 1 Lecturer Organization Date."— Presentation transcript:

1 Co-funded by the European Union Semantic CMS Community Requirements Engineering for Semantic CMS Copyright IKS Consortium 1 Lecturer Organization Date of presentation

2 www.iks-project.eu Page: Copyright IKS Consortium Introduction of Content Management Foundations of Semantic Web Technologies Storing and Accessing Semantic Data Knowledge Interaction and Presentation Knowledge Representation and Reasoning Semantic Lifting Designing Interactive Ubiquitous IS Requirements Engineering for Semantic CMS Designing Semantic CMS Semantifying your CMS Part I: Foundations Part II: Semantic Content Management Part III: Methodologies (2) (1) (3) (4) (5) (6) (7) (8) (9) (10)

3 www.iks-project.eu Page: What is this Lecture about?  We have seen... ... existing technologies of the Semantic Web ... how these technologies can be used for semantic content management  What is missing?  Methodologies for the development of semantic CMS  First, requirements for semantic CMS need to be specified Copyright IKS Consortium 3 Designing Interactive Ubiquitous IS Requirements Engineering for Semantic CMS Designing Semantic CMS Semantifying your CMS Part III: Methodologies (7) (8) (9) (10)

4 www.iks-project.eu Page: Outline  What the course is about?  Methodology  Understand industry needs/expectations  Analysis of Traditional CMSs  Identify business scenarios  Identification of High Level Requirements (HLRs)  High Level Requirements  Use cases  Resulting requirements  Summary Copyright IKS Consortium 4

5 www.iks-project.eu Page: What the course is about?  This course aims to  Give the details of the domain-independent requirement elicitation process of semantic enhancement of any Content Management System Copyright IKS Consortium 5

6 www.iks-project.eu Page: Methodology  Bilateral meetings with CMS vendors  Workshops  Interviews  Brainstorming sessions  Gathered requirements  Categorization under major topics  High Level Requirements  Use cases  Validate the resulting use cases against the requirements of different CMS vendors Copyright IKS Consortium 6

7 www.iks-project.eu Page: Results  Requirements Engineering Process  Refine HLRs into specific software requirements using scenario and use case descriptors  Actors model  All requirements are based on use cases which use a common actor’s model for CMS.  Integration of semantic services to existing CMSs  Easy to use and technology independent mechanisms  RESTful HTTP services  All features are expressed in terms of services  Applicable to and can be accessed by “any” CMS  Mash-up to create new high-order services Copyright IKS Consortium 7

8 www.iks-project.eu Page: Analysis of Traditional CMSs  GOAL:  Identify common parts that all CMSs have  INPUT:  Product descriptions  Expectations from industry  Product web-sites  Running CMS itself Copyright IKS Consortium 8

9 www.iks-project.eu Page: Analysis of Traditional CMSs  Analysis of  Content Types  Content Workflow  Content Services  Architectural Styles Copyright IKS Consortium 9

10 www.iks-project.eu Page: CMS – Content Types  Documents  Web sites / web applications  Multi-media files (audio, image, video)  Postings + Comments ( blogs, forums)  Short messages (sms, twitter)  Topics (wiki)  Correspondence (e- mail, newsletter)  Feeds (rss)  Individuals (social networking) Copyright IKS Consortium 10

11 www.iks-project.eu Page: CMS – Content Workflow  Main innovations take place in the phases  Enrichment  Storage  Publishing Copyright IKS Consortium 11

12 www.iks-project.eu Page: CMS – Content Workflow Semantic Enrichment  Automatic classification and routing  Faceted classification  Use of predefined taxonomies  Automatic semantic tagging  Automatic ranking  Semi-automatic annotations  Annotation with Microformats  Ontology extraction  Concepts, people, places etc… extraction  Relationship extraction (isA, partOf)  Cross-Source Correlations  Document models from ontologies  Knowledge representation Copyright IKS Consortium 12

13 www.iks-project.eu Page: CMS – Content Workflow Persistence  Workflow states  Relations  Directories  Audit  User preferences  Converted content  Synchronization of Content Repository Semantics with Semantic Persistence Stores Copyright IKS Consortium 13

14 www.iks-project.eu Page: CMS – Content Workflow Publishing  Semantic workflows  Collaborative content management  Semantic & social techniques  Personalization of UI  Knowledge view  Administration Copyright IKS Consortium 14 Semantic Framework CMS Compone nt Content CMS Compone nt

15 www.iks-project.eu Page: CMS – Content Workflow Search  External semantic search  Pluggable  Ambiguity resolution  Similarity searches  Semantic based and multilingual  Relationship recognition  Keyword search  Natural language queries  Ranked search results  Faceted search Copyright IKS Consortium 15 http://affordableseo101.com/

16 www.iks-project.eu Page: CMS – Existing Content Services  Creation / Ingestion  Ingestion schedules  Transcoding  Indexing  Metadata extraction  Storing  Versioning  Audit / Archive  Workflow Management  Publishing  Notification  Search and Query  Rendering  User profiles  Security  Ad service Copyright IKS Consortium 16

17 www.iks-project.eu Page: Traditional CMS Architecture Copyright IKS Consortium 17

18 www.iks-project.eu Page: Semantic CMS Architecture Copyright IKS Consortium 18

19 www.iks-project.eu Page: Merge All Inputs  Workshops  Brainstorming sessions  Collected list of statements from CMS vendors  Representing their view on a semantic CMS  e.g. legacy data, how to semantify them?  e.g. tagging, different for each person, rules for personalized tagging  Examination of existing systems  Focus on industrial needs rather than theoretical thinking  Merge all input and come up with High Level Requirements Copyright IKS Consortium 19

20 www.iks-project.eu Page: High Level Requirements  HLR-1: Common Vocabulary  HLR-2: Architecture and integration  HLR-3: Semantic lifting & tagging  HLR-4: Semantic search & semantic query  HLR-5: Reasoning on content items  HLR-6: Links/relations among content items  HLR-7: Workflows  HLR-8: Change management, versions and audit  HLR-9: Multilingualism  HLR-10: Security Copyright IKS Consortium 20

21 www.iks-project.eu Page: The refinement process  Start with HLRs and ends with testable software requirements Copyright IKS Consortium 21

22 www.iks-project.eu Page: The refinement process Copyright IKS Consortium 22

23 www.iks-project.eu Page: HLR 1 Common Vocabulary  For a common understanding for users  Relating a content item with clear and precise vocabulary items  Services and engineering of  External ontologies, taxonomies, thesauri  4 scenarios upon the collected information  e.g. statements from CMS vendors  “Agree on a set of categories and relations, attributes as the default set”  “Help in finding good vocabularies” Copyright IKS Consortium 23 http://lsdis.cs.uga.edu

24 www.iks-project.eu Page: HLR 1 Common Vocabulary Use Cases Copyright IKS Consortium 24

25 www.iks-project.eu Page: HLR 1 Common Vocabulary Resulting Requirements  Functional requirements  The Vocabulary shall be navigable  …  Data requirements  Vocabulary shall be in one of standard format which  …  Integration requirements  Vocabulary shall be in an accepted standard format  …  Interface requirements: an interface shall be implemented for  Presenting list of Vocabularies  …  Non functional requirements  Vocabularies shall always be accessible  … Copyright IKS Consortium 25

26 www.iks-project.eu Page: HLR 2 Architecture and integration  Easy integration of services to be developed into different heterogeneous system environments  RESTful service interfaces  The implementation should be as technology independent as possible  Should also provide technology specific access to the services for best performance results Copyright IKS Consortium 26 http://xml.com

27 www.iks-project.eu Page: HLR 2 Architecture and integration  Everything should be accessed by an URI  Linked Data approach  The communication should be based on standardized text-based data formats  e.g. XML Copyright IKS Consortium 27 http://viralpatel.net/

28 www.iks-project.eu Page: HLR 3 Semantic lifting & tagging  Semantic tagging on content items  Ontological classes  RDF properties  Microformats Copyright IKS Consortium 28 http://microformats.org/  Extract semantics from structures and unstructured data automatically or semi-automatically  Make suggestions about annotations  Navigate on the content items in a semantic fashion

29 www.iks-project.eu Page: HLR 4 Semantic search & semantic query  Faceted search mechanisms in top of semantic query language support  Statements from the industry  Similarity search, similarity detection  User friendly RDF query  Support for disambiguation of search Copyright IKS Consortium 29

30 www.iks-project.eu Page: HLR 5 Reasoning on content items  Extracting implicit information from the explicit information residing in the content repositories  “Semantic consistency check in CMSs” Copyright IKS Consortium 30 http://www.kent.ac.uk/

31 www.iks-project.eu Page: HLR 6 Links/relations among content items  Along with the semantic annotations of the content items, semantic relations among them should also be considered  “Instance linking, linked data cloud, whenever we create something link it with something existing” Copyright IKS Consortium 31 http://ctmlogistics.co.uk/

32 www.iks-project.eu Page: HLR 7 Workflows  Control flow/lifecycle of the content  Workflows for semantic actions similar to workflows for content  “Intelligent content workflows, configured based on organization, hierarchy” Copyright IKS Consortium 32 http://coredotnet.blogspot.com

33 www.iks-project.eu Page: HLR 8 Change management, versions and audit  The system should also be aware of changing content and provide solutions to invalidate semantic data  Prior extracted semantic information might become invalid as the content changes  Content evolution  Semantic data evolution Copyright IKS Consortium 33 asdhttp://visiongss.com

34 www.iks-project.eu Page: HLR 9 Multilingualism  Services to be provided should be aware of content in different languages  Enabling a variety of users in different nationality  Language support independent of the CMS application domain Copyright IKS Consortium 34 http://ec.europa.eu/

35 www.iks-project.eu Page: HLR 10 Security  The system must consider existing access control restrictions in CMSs  New kinds of restrictions which reflect the semantic data access  e.g. for algorithms that reason on existing data  Integration of permission, role and group models Copyright IKS Consortium 35 http://www.oplin.org

36 www.iks-project.eu Page: Summary  The requirements evolved from a systematic requirements engineering approach  Started with the analysis of current CMS systems and their similarities  Collection of needs of CMS vendors in the field of semantic enhancements of their systems  Workshops  Brainstorming sessions  Interviews  From the High Level Requirements (HLRs)  Necessary Actors are defined  Scenarios are constructed Copyright IKS Consortium 36

37 www.iks-project.eu Page: Summary  From the scenarios for each HLR  Use cases are extracted  From the use cases resulting requirements are refined into the following types of requirements  Functional  Data  Integration  Interface  Non functional Copyright IKS Consortium 37


Download ppt "Co-funded by the European Union Semantic CMS Community Requirements Engineering for Semantic CMS Copyright IKS Consortium 1 Lecturer Organization Date."

Similar presentations


Ads by Google