Changes for page Overview

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,8 +1,8 @@
1		-Every paradigm, computational model, or language is based on some kind of driving abstract or high level metaphors, which are often are essential to define the main characteristics of the paradigm abstractions. simpA metaphors are taken from humans cooperative working environments, where "systems" are composed by individual autonomous entities (humans), encapsulating different kind of skills, which actively carry on some kind of task or goal oriented activities, both individually and cooperatively by interacting with other individuals and suitably exploiting resources and tools, artifacts to use a unique term, available in the environment.
	1	+Every paradigm, computational model, or language is based on some kind of driving abstract or high level metaphors, which are often are essential to define the main characteristics of the paradigm abstractions. {{simpa/}} metaphors are taken from humans cooperative working environments, where "systems" are composed by individual autonomous entities (humans), encapsulating different kind of skills, which actively carry on some kind of task or goal oriented activities, both individually and cooperatively by interacting with other individuals and suitably exploiting resources and tools, artifacts to use a unique term, available in the environment.
2	2
3		-simpA brings this metaphor down to computer programming, conceiving a software systems as one or multiple **workspaces** where ensemble of autonomous entities called **agents** execute their task-oriented activities and interact by co-constructing, sharing and using **artifacts**, analogously to the human case.
	3	+{{simpa/}} brings this metaphor down to computer programming, conceiving a software systems as one or multiple **workspaces** where ensemble of autonomous entities called **agents** execute their task-oriented activities and interact by co-constructing, sharing and using **artifacts**, analogously to the human case.
4	4
5		-So, while classes and objects are still used to represent basic data structures and abstract data types, in simpA agents and artifacts are used as basic high-level building blocks to decompose and structure complex systems, composed by ensemble of interacting and coordinating parts.
	5	+So, while classes and objects are still used to represent basic data structures and abstract data types, in {{simpa/}} agents and artifacts are used as basic high-level building blocks to decompose and structure complex systems, composed by ensemble of interacting and coordinating parts.
6	6
7	7	In particular:
8	8
...	...	@@ -16,6 +16,6 @@
16	16
17	17	//"The biggest sea change in software development since the OO revolution is knocking at the door, and its name is Concurrency ... The concurrency revolution is primarily a software revolution. The difficult problem is not building multicore hardware, but programming it in a way that lets mainstream applications benefit from the continued exponential growth in CPU performance ... Today concurrent programming languages and tools are at a level comparable to sequential programming at the beginning of the structured programming era. Semaphores and coroutines are the assembler of concurrency, and locks and threads are the slightly higher-level structured constructs of concurrency. What we need is OO for concurrency - higher-level abstractions that help build concurrent programs, just as object-oriented abstractions help build large componentized programs."//
18	18
19		-Following this perspective, in simpA agents and artifacts abstractions can be used as higher-level building blocks to design and build concurrent applications, not providing just mechanisms but a new (methodological) perspective to be exploit for developing software systems.
	19	+Following this perspective, in {{simpa/}} agents and artifacts abstractions can be used as higher-level building blocks to design and build concurrent applications, not providing just mechanisms but a new (methodological) perspective to be exploit for developing software systems.
20	20
21	21	{{include reference="Environment" excludeFirstHeading="true"/}}