5,705
edits
Changes
Jump to navigation
Jump to search
Line 3:
Line 3: − + + + − + − * The scope of provided [[#Resources|resources]] should cover the full complement of low level collaborative behaviors between Network participants; where ''low level'' means that [[#Resources|resources]] are shared for all types of collaborative [[#Contexts|contexts]];+ − − * The software architecture and interfaces are structured to stimulate a "doing" and "sharing" workflow. − The whole Sugar Network is pictured by the following graphics:+ − + − + − + − + − + + + Line 309:
Line 311: + + + + + + + + + + + + + + + + + + + +
no edit summary
== Overview ==
== Overview ==
The whole initiative is tailored by the following decisions:
The major goal of the Sugar Network is providing an infrastructure to let people sharing different kinds of content, e.g., Sugar Activities, artifacts created by Sugar Activities, books, etc. for friends, a class, parents, teachers, or Sugar Learners anywhere.
Functionality of Sugar Network is split into two parts:
* The Sugar Network should be useful in off-line environments;
* Core functionality that covers low level needs to work with content ([[#Summary|described below]]);
* Any amount of representation models that are based on core functionality and add high level scenarios to interact with the same content, e.g., gamification elements. Representation models are pluggable and optional.
* The scope of provided [[#Resources|resources]] should be designed so that the Sugar Network is equally useful operating on-line as off-line;
== Targeted audience ==
{| border="0"
{| border="0"
|- valign="top" align="let"
|- valign="top" align="let"
| [[File:Sugar-network.png]]
| [[File:Sugar-network-audience.png|350px]]
| Where,
| The audience of Sugar Network might be different:
* '''Server'''<br>is shared data and services, in general. It might be a server accessible from the Internet (on-line case) or various distributed servers located, e.g., in schools (off-line case). See [[Platform_Team/Sugar_Network|technical pages]] for more details.
* '''Conceptual level logic'''<br>The design logic and software code structures that reify the Sugar Network concepts. From a conceptual level, these designs and code standards represent a separate entity that operates inbetween the Clients and Servers. From the technical perspective, this level is represented by the Server [[Platform_Team/Sugar_Network/API|application programming interface (API)]] and [[Platform_Team/Sugar_Network/Objects_model|objects model]] in particular.
* Students, might be different ages, depending on particular representation model;
* '''Client'''<br>is the software that allows Network participants to interact with the Sugar Network. These software components let people get access to the Sugar Network, and define how the Sugar Network should appear to users according to their needs. The user experience provided by the client software will vary from need to need, starting from a couple of elements in the existing software [[Wikipedia:Graphical_user_interface|GUI]] (when people even don't suspect they are interacting with the Sugar Network), and extending to clients that represent advanced conceptual elements of the Sugar Network as closely as possible.
* Educators who need to populate content for students and review what students uploaded to the Network;
* Deployment supporters who need to provide technical and educational support;
* Software developers who will have a chance to get feedback directly from users.
|}
|}
:* Click Home button for the found entity;
:* Click Home button for the found entity;
:* ''TODO''
:* ''TODO''
== Infrastructure overview ==
The whole initiative is tailored by the following decisions:
* The Sugar Network should be useful in off-line environments;
* The scope of provided [[#Resources|resources]] should cover the full complement of low level collaborative behaviors between Network participants; where ''low level'' means that [[#Resources|resources]] are shared for all types of collaborative [[#Contexts|contexts]];
* The scope of provided [[#Resources|resources]] should be designed so that the Sugar Network is equally useful operating on-line as off-line;
* The software architecture and interfaces are structured to stimulate a "doing" and "sharing" workflow.
The whole Sugar Network is pictured by the following graphics:
{| border="0"
|- valign="top" align="let"
| [[File:Sugar-network.png]]
| Where,
* '''Server'''<br>is shared data and services, in general. It might be a server accessible from the Internet (on-line case) or various distributed servers located, e.g., in schools (off-line case). See [[Platform_Team/Sugar_Network|technical pages]] for more details.
* '''Conceptual level logic'''<br>The design logic and software code structures that reify the Sugar Network concepts. From a conceptual level, these designs and code standards represent a separate entity that operates inbetween the Clients and Servers. From the technical perspective, this level is represented by the Server [[Platform_Team/Sugar_Network/API|application programming interface (API)]] and [[Platform_Team/Sugar_Network/Objects_model|objects model]] in particular.
* '''Client'''<br>is the software that allows Network participants to interact with the Sugar Network. These software components let people get access to the Sugar Network, and define how the Sugar Network should appear to users according to their needs. The user experience provided by the client software will vary from need to need, starting from a couple of elements in the existing software [[Wikipedia:Graphical_user_interface|GUI]] (when people even don't suspect they are interacting with the Sugar Network), and extending to clients that represent advanced conceptual elements of the Sugar Network as closely as possible.
|}
== Todo ==
== Todo ==