AtGentive WP2 Design Principles AtGentive; 2 nd General Meeting; 21-22 May 2006, Oxford, UK. Thierry Nabeth, Yé Deng & Pradeep Kumar Mittal INSEAD CALT (Centre for Advanced Learning Technologies) http://www.calt.insead.edu/. Table of content:. The Wish list. Flexible architecture
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
AtGentiveWP2 Design PrinciplesAtGentive; 2nd General Meeting; 21-22 May 2006, Oxford, UK
Thierry Nabeth, Yé Deng & Pradeep Kumar Mittal
INSEAD CALT (Centre for AdvancedLearning Technologies)
The “Wish list”
The “have to” and “nice to have”
The flexible architecture
The Web 2.0 principles
Adopting web 2.0.
Rich user experience; User participation; trust the users (Wikipedia); radical decentralisation (blog); emergence; more people use them the it is useful; fun to use; attitude; culture (community, versus process oriented, corporate and bureaucratic); navigation & serendipity.
Small pieces loosely joined; Mashup (combination); perpetual beta; granular addressability of content; tagging (not taxonomy. Folksonomies are not planned in advance); ideas originates from the “leisure Internet”.
Presentation Web 2.0
The technicality of Web 2.0.
Components. Components are independent, simple, and have a very clear interface (web services, rich-client / server)
Open Application / platform. Net API, plugin mechanisms.
Open to external services. Instant messaging (Skype?, MSN), Tagging (Del.icio.us, Flickr), bloging, maps
eXtreme Programming principles. Bottom-up, user centred, continuous improvement
The issues related to Adopting Web 2.0.
Adoption / adaptation to AtGentive
What is web 2.0 for us?
How can we adopt web 2.0 principles
Open Application / platform. The different platforms (ICDT, Ontdeknet, others?) should be opened (API / web services, plugin mechanisms). Ideas introduced by Claudia. We have to find some way to easily combine/glue the components (mashup).Note: Probably some commonalities, but most probably this work will be platform specific.
External Components. External components will have to be selected and wrapped. Examples: Instant messaging (Skype?, MSN), Tagging (Del.icio.us, Flickr), blogging, etc..Work: Some rich client interfaces will have to be created.
Specific AtGentive Components. Difference specific AtGentive components will have to be created. Work: Creation of small server components (exposed via web services, or incorporable into plugins) + Rich client part.
How to proceed & conclusion
Identification of the components. Specification of the functional specification according to a user centred perspective (Not a detailled technical description !). Alignment of these components to the Conceptual framework.
Definition of the technical framework. Clarification of the different mechanisms and approaches to be used. Plugin, API, etc.Definition of a common API. (not too detailed, with the objective is to sketch the principles, and be ready for easy later additions)
Architectural definition of the AtGentive Components. Definition of the server part and of the Rich client part.