Presentation on theme: "Methodologies for Web Information System Design"— Presentation transcript:
1 Methodologies for Web Information System Design Peter Barna
2 Outline Traditional IS and WIS Phases of the design cycle for WIS Navigation and AdaptationMethodologiesConclusionQuestions
3 Traditional IS and WIS Traditional IS WIS Work typically with well defined and closed data repositoryServe to well known and specific audienceUse dedicated SW and HW platformsWork typically with heterogeneous, dynamic and distributed dataServe to diverse and large audienceUse web navigation with all its specifics
5 NavigationGood navigation structure of an application helps user to find relevant information fast and avoids him to be “lost” in hyperspaceNavigation model:Abstracts from concrete platform (OS, hypertext protocol) as much as possibleDepends on CM, but is separated (multiple NM possible for one CM)
6 Adaptation Makes WIS more suitable for individual users Based on different aspects:User’s platform; since it does not change during browsing the adaptation is static (adaptability)User’s preferences; since this also usually does not change during the adaptation is staticUser’s behaviour; since it includes also browsing, the adaptation is dynamic (adaptivity)
7 Methodologies: Example Conceptual model of the example in RDFS notationExample application has 3 views:TechniquePaintingPainterbased on particular concepts
8 RMM: Relationship Management Methodology Defines process of building of NM onlyCM is by default E-R diagramSlices as navigation objectsMeaningful collections of attributes from different CM conceptsNested and referenced from each otherNo adaptation modelling
9 OOHDM: Object-Oriented Hypermedia Design Methodology O-O approach based on OMT notationNM consists of:Navigation Class SchemaNavigation Context SchemaAdaptation can be modelled, but is not directly supported
10 UWE: UML Based Web Engineering Methodology O-O approach based on UML notationNM consists of:Navigation Space ModelNavigation Structure ModelAdaptation model is described in Munich Reference Model (AHAM-like UWE extension)
11 WebML: Web Modeling Language Oriented towards design patterns re-useSpecifies:Structure modelDerivation modelHypertext modelComposition modelNavigation modelAdaptation modelling can use User and Group entities pre-defined in structure model
12 Hera Model-driven methodology defines: Process of model specification (integration, navigation, adaptation, and presentation) using terms from predefined ontologiesFramework of WIS generating presentations on user request and process of data transformation (using designed models)
13 Hera Navigation specification is RMM-like, it uses the slice concept Adaptation in Hera:Static (adaptability): based on platform profile and user’s preferences. The appearance of slices is decided during presentation generationDynamic (adaptivity): based on overview of concepts/slices visited by user during browsing. Hera uses the AHAM reference model.
14 ConclusionO-O methodologies facilitate specification of WIS with possible rich functionality, but the functionality specification is usually vague (the implementation of methods is left to programmers).Many methodologies allow adaptation modeling in some ways, but just few really support it sufficiently.Hera: allows automated presentation generation, supports adaptation modeling.Future Hera research: extend it with techniques that would facilitate generation of presentations with functionality richer than only links following.