You are here: Foswiki>Adesa Web>NextSteps>WpStructure>WorkPackage4 (23 Apr 2007, ChristianDoerner)Edit Attach

WorkPackage4: Domain-independent Designs for End User Service Assembly Environments ( UM)

Objectives:
  • Definition of integrated appropriation support mechanisms for DoDEs
  • Formalise appropriate problem-solving models and patterns
  • Develop conceptual models of design assistance
  • Specify assistive mechanisms and techniques
  • Discover commonalities in design patterns and models across the different user scenarios
  • Compare with Domain Theory findings to formulate core knowledge structures
  • Design the Reuseable Designs Catalogue
  • Design a Generic Visual Editor and integrate with Designer's Assistant blueprints
  • Design generic infrastructure designs for service procurement, composition and monitoring
  • Design generic collaborative infrastructure
  • Provide methodological guidance about how to customise the generic design blueprints into domain-specific environments

T4.1. Define appropriation support mechanisms for service composions ( US)

Start date: M12

Objectives:
  • Definition of integrated appropriation support mechanisms for DoDEs

Description of work The proposed development of a DoDE that enables end users to develop service assemblies must also provide a stronger support for managing this flexibility. Keeping the tool interaction simple and providing good manuals is one strategy, but the adaptation and appropriation of tools is often more a social activity than a problem of individual learning and use. Knowledge sharing and delegation structures often develop over time. End User Development methods can address the social aspects of computing by treating users as a ‘(virtual) community of tool/technology users’, and by providing support for different appropriation activities that users can engage in to make use of a technology. Therefore we will define appropriation support mechanisms, supporting the development of service assemblies within the DoDE. Suitable mechanisms that cover these activities are:
  • Articulation Support: Support for technology-related articulations (real and online)
  • Historicity Support: Visualize appropriation as a process of emerging technologies and usages, e.g. by documenting earlier configuration decisions, providing retrievable storage of configuration and usage descriptions.
  • Delegation Support: Support delegation patterns within configuration activities; provide remote configuration facilities.
  • (Re-) Design support: feedback to designers on the appropriation processes.

The aim of the task is to define how the above described appropriation support activities should be integrated into the DoDE.

Deliverables:
  • D4.1.1: Design of appropriation support mechanisms, to be integrated in the prototype
  • D4.1.2: Collaborative Design Process Repository and Model - US please consider and introduce in text

T4.2. Assistive mechanisms for user-driven design of service assemblies ( UM, CMU, US, PF, PM)

Start date: ???

Objectives:
  • Formalise appropriate problem-solving models and patterns
  • Develop conceptual models of design assistance
  • Specify assistive mechanisms and techniques

Description of work ???

Deliverables:
  • D4..2 Blueprint for Designer's Assistant module and its integration with the Visual Editor and Formal Verification Input

T4.3. Knowledge structures reuse ( UM)

Start date: ???

Objectives:
  • Discover commonalities in design patterns and models across the different user scenarios
  • Compare with Domain Theory findings to formulate core knowledge structures
  • Design the Reuseable Designs Catalogue

Description of work ???

Deliverables:
  • Reuseble Designs Catalogue

T4.4. Generic Infrastructure Design ( UM)

Start date: ???

Objectives:
  • Design a Generic Visual Editor and integrate with Designer's Assistant blueprints
  • Design generic infrastructure designs for service procurement, composition and monitoring
  • Design generic collaborative infrastructure

Description of work ???

Deliverables:
  • D4.4. Infrastructure Design

T4.5. Develop Environment Customisation Method ( UM)

Start date: ???

Objectives:
  • Provide methodological guidance about how to customise the generic design blueprints into domain-specific environments

Description of work ???

Deliverables:
  • D4.5. DoDE customisation method

-- NikolayMehandjiev - 19 Apr 2007
Topic revision: r3 - 23 Apr 2007, ChristianDoerner
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback