Skip to content
Snippets Groups Projects
Commit 7cd281e4 authored by Sebastian Götz's avatar Sebastian Götz
Browse files

classified

parent 00c5ee35
No related branches found
No related tags found
No related merge requests found
.project 0 → 100644
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>bp-study</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
</buildSpec>
<natures>
</natures>
</projectDescription>
...@@ -156,7 +156,7 @@ ...@@ -156,7 +156,7 @@
doi = {10.1145/2480361.2371411}, doi = {10.1145/2480361.2371411},
abstract = {In the context of Component-based Programming, which addresses the implementation stage of a component-based software engineering development process, this paper describes a specification and an operational integration of an inheritance system into a self-contained new component-based programming language named Compo. Our proposal completes and extends related works by making it possible to apply inheritance to the full description of components, i.e. both to structural (description of provisions and requirements, of component architecture) and behavioral (full implementations of services) parts in component descriptions. Inheritance in Compo is designed to be used in conjunction with composition to maximize reuse capabilities and expressive power. Compo implementation proposes a clear operational solution for inheritance and for achieving and testing substitutions.}, abstract = {In the context of Component-based Programming, which addresses the implementation stage of a component-based software engineering development process, this paper describes a specification and an operational integration of an inheritance system into a self-contained new component-based programming language named Compo. Our proposal completes and extends related works by making it possible to apply inheritance to the full description of components, i.e. both to structural (description of provisions and requirements, of component architecture) and behavioral (full implementations of services) parts in component descriptions. Inheritance in Compo is designed to be used in conjunction with composition to maximize reuse capabilities and expressive power. Compo implementation proposes a clear operational solution for inheritance and for achieving and testing substitutions.},
journal = {SIGPLAN Not.}, journal = {SIGPLAN Not.},
month = {sep}, month = "sep",
pages = {60–69}, pages = {60–69},
numpages = {10}, numpages = {10},
keywords = {architectures, inheritance, programming, substitutability} keywords = {architectures, inheritance, programming, substitutability}
......
...@@ -13,7 +13,8 @@ ...@@ -13,7 +13,8 @@
numpages = {12}, numpages = {12},
keywords = {behavioral programming, browser, client-side, coroutines, googleblockly, html5, javascript, visualprogramming, web application}, keywords = {behavioral programming, browser, client-side, coroutines, googleblockly, html5, javascript, visualprogramming, web application},
location = {Tucson, Arizona, USA}, location = {Tucson, Arizona, USA},
series = {AGERE! 2012} series = {AGERE! 2012},
classes = {Venue Type {Conference}, Type of Contribution{Approach}}
} }
@inproceedings{10.1145/2095050.2095079, @inproceedings{10.1145/2095050.2095079,
...@@ -31,7 +32,8 @@ ...@@ -31,7 +32,8 @@
numpages = {12}, numpages = {12},
keywords = {behavioral programming, bpj, decentralized control, erlang, java, lsc, multiple times scales}, keywords = {behavioral programming, bpj, decentralized control, erlang, java, lsc, multiple times scales},
location = {Portland, Oregon, USA}, location = {Portland, Oregon, USA},
series = {SPLASH '11 Workshops} series = {SPLASH '11 Workshops},
classes = {Venue Type {Workshop}, Type of Contribution{Approach}}
} }
@inproceedings{10.1145/3270112.3270126, @inproceedings{10.1145/3270112.3270126,
...@@ -67,24 +69,6 @@ ...@@ -67,24 +69,6 @@
series = {ECOOP'10} series = {ECOOP'10}
} }
@inproceedings{10.1145/2414639.2414650,
author = {Ricci, Alessandro and Santi, Andrea},
title = {Programming abstractions for integrating autonomous and reactive behaviors: an agent-oriented approach},
year = {2012},
isbn = {9781450316309},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/2414639.2414650},
doi = {10.1145/2414639.2414650},
abstract = {The integration of autonomous and reactive behavior is a relevant problem in the context of concurrent programming, related to the integration of thread-based and event-driven programming. From a programming paradigm perspective, the problem can not be easily solved by approaches based on object-oriented concurrent programming or by the actor model, being them natively based on the reactivity principle only. In this paper we tackle the problem with agent-oriented programming, using an agent-oriented programming language called simpAL.},
booktitle = {Proceedings of the 2nd Edition on Programming Systems, Languages and Applications Based on Actors, Agents, and Decentralized Control Abstractions},
pages = {83–94},
numpages = {12},
keywords = {ageactors, agent-oriented programming, autonomy, event-driven programming, reactivity},
location = {Tucson, Arizona, USA},
series = {AGERE! 2012}
}
@inproceedings{10.1145/2038642.2038686, @inproceedings{10.1145/2038642.2038686,
author = {Harel, David and Lampert, Robby and Marron, Assaf and Weiss, Gera}, author = {Harel, David and Lampert, Robby and Marron, Assaf and Weiss, Gera},
title = {Model-checking behavioral programs}, title = {Model-checking behavioral programs},
...@@ -100,7 +84,8 @@ ...@@ -100,7 +84,8 @@
numpages = {10}, numpages = {10},
keywords = {behavioral programming, java}, keywords = {behavioral programming, java},
location = {Taipei, Taiwan}, location = {Taipei, Taiwan},
series = {EMSOFT '11} series = {EMSOFT '11},
classes = {Venue Type {Conference}, Type of Contribution{Approach}}
} }
@inproceedings{10.1145/2687357.2687359, @inproceedings{10.1145/2687357.2687359,
...@@ -134,5 +119,6 @@ ...@@ -134,5 +119,6 @@
pages = {243–251}, pages = {243–251},
numpages = {9}, numpages = {9},
location = {Munich, Germany}, location = {Munich, Germany},
series = {MODELS '19} series = {MODELS '19},
classes = {Venue Type {Conference}, Type of Contribution{Lessons Learned}}
} }
\ No newline at end of file
Venue, Venue Type { Conference , Workshop , Journal } , Type of Contribution { Approach , Survey , Lessons Learned }
Venue Type , \ No newline at end of file
Type of Contribution
\ No newline at end of file
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment