Skip to content

History

Showing with 61 additions and 96 deletions.
  1. +1 −1 Data-driven.mediawiki
  2. +57 −3 Hackathon.mediawiki
  3. +2 −7 Home.mediawiki
  4. +1 −1 LinkedData.mediawiki
  5. +0 −41 Re-engineering.mediawiki
  6. +0 −43 Reverse-Engineering.mediawiki
2 changes: 1 addition & 1 deletion Data-driven.mediawiki
Expand Up @@ -22,7 +22,7 @@ The '''data-driven technological spaces''' deal with spreadsheets, sequential an

* Jean Bézivin’s invited talk may mention data journalism.
* Jácome Cunha’s invited talk will deal with spreadsheets.
* The hackathon on [[reverse engineering]] may leverage data-driven technological spaces.
* The [[hackathon]] on reverse engineering may leverage data-driven technological spaces.
=== Coordination ===

Expand Down
60 changes: 57 additions & 3 deletions Hackathon.mediawiki
@@ -1,3 +1,57 @@
To be filled in, for now see:
* [[Reverse engineering]]
* [[Re-engineering]]
== SoTeSoLa hackathon on re(verse) engineering ==

=== Summary ===

The hackathon aims at exercising the methods and tools for software reverse engineering and re-engineering as they are of interest to the participants. Reverse engineering is meant here in a broad sense to include fact extraction, software visualization, vocabulary mining, analysis of language usage, architecture recovery, etc. Re-engineering is meant here in a broad sense to include, for example, program refactoring, wrapping, dead-code elimination, language migration, database re-engineering, and other forms of software evolution.

The participants apply the methods and tools to the software chrestomathy of the 101companies project. Diverse experiments are enabled by the many contributions of the chrestomathy with its coverage of many software languages and technologies. The chrestomathy is available as a repository of source code and through “data dumps” for extracted facts. The participants select those parts of the chrestomathy that are the most suited for efficiently demonstrating their reverse engineering methods and tools. The expectation is that the hackathon produces a corpus of reverse engineering samples, which may be useful, for example, in teaching re(verse) engineering, or as a benchmark or point of reference in re(verse) engineering research.

=== Prerequisite ===

Participants should have some basic understanding of re(verse) engineering and some level of expertise in some technology that can serve as an instrument for reverse engineering. Teamwork may be of help, of course. Bring your methods and tools to reverse-engineer and re-engineer the 101companies chrestomathy!

=== Deliverables ===

* Reverse engineering components for different purposes:
** Fact extraction
** Metrics computation
** Software visualization
** Vocabulary mining
** Analysis of language usage
** Analysis of API usage
** Architecture recovery
** Design pattern recovery
* Re-engineering components for different purposes:
** Program refactoring
** Wrapping for backwards compatibility or SOA
** Code injection for extra functionality or assertions
** Dead-code detection and elimination
** Language or API migration
** Database re-engineering
** Architectural modifications
** Modularization or component identification
** Coupled software transformations
=== Resources ===

* [http://en.wikipedia.org/wiki/Reverse_engineering Reverse engineering] @ Wikipedia
* [http://en.wikipedia.org/wiki/Reengineering_(software) Re-engineering (software)] @ Wikipedia
* [http://github.com/SoTeSoLa/SoTeSoLa/tree/master/hackathon Simple illustrative implementations] @ github.com/SoTeSoLa
* More illustrative implementations elsewhere:
** [http://github.com/rlaemmel/loc101demo loc101demo]
** [http://github.com/rlaemmel/api101demo api101demo]
** [http://github.com/rlaemmel/coupling101demo coupling101demo]
* 101companies: [http://101companies.org/ wiki], [http://github.com/101companies/101repo repository], [http://101companies.org/index.php/Category:Meta_101feature (meta) 101features], [http://101companies.org/index.php/101companies:Data data]
* Conferences @ DBLP:
** Reverse engineering: [http://www.informatik.uni-trier.de/~ley/db/conf/wcre/ WCRE], [http://www.informatik.uni-trier.de/~ley/db/conf/iwpc/ ICPC], [http://informatik.uni-trier.de/~ley/db/conf/msr/ MSR]
** Re-engineering: [http://www.informatik.uni-trier.de/~ley/db/conf/icsm/ ICSM], [http://www.informatik.uni-trier.de/~ley/db/conf/csmr/ CSMR]
=== Relationships ===

* The working group on [[LinkedData]] may analyze LinkedData-like facts about the 101repo.
=== Coordination ===

* [http://github.com/grammarware Vadim Zaytsev]
* [http://github.com/anyahelene Anya Helene Bagge]
* [http://www.udo-borkowski.de Udo Borkowski]
9 changes: 2 additions & 7 deletions Home.mediawiki
Expand Up @@ -11,14 +11,9 @@ This section is under development.

SoTeSoLa is a [[Research|Research 2.0]] event — the expectations bound to this positioning will be explained during the launch of the working groups.

=== Hackathons ===
=== Hackathon ===

Non-wiki material for the hackathons will be stored eventually in the GitHub repository.

* [[Reverse engineering]]
* [[Re-engineering]]
Refined, alternative, or additional hackathon proposals are appreciated.
Non-wiki material for the [[hackathon]] will be stored eventually in the GitHub repository.

=== Working groups ===

Expand Down
2 changes: 1 addition & 1 deletion LinkedData.mediawiki
Expand Up @@ -26,7 +26,7 @@ Linked Data is increasingly used in the extended Semantic Web context for provid

* The working group on [[Research|Research 2.0]] assumes Linked Data as an important concept.
* The working group on SoTeSoLa-related [[community resources]] may deal with Linked Data.
* The hackathon on [[reverse engineering]] may use Linked Data-like dumps of the 101repo.
* The [[hackathon]] on reverse engineering may use Linked Data-like dumps of the 101repo.
=== Coordination ===

Expand Down
41 changes: 0 additions & 41 deletions Re-engineering.mediawiki
@@ -1,41 +0,0 @@
== SoTeSoLa hackathon on re-engineering ==

=== Summary ===

The hackathon aims at exercising the methods and tools for software re-engineering as they are of interest to the participants. Re-engineering is meant here in a broad sense to include, for example, program refactoring, wrapping, dead-code elimination, language migration, database re-engineering, and other forms of software evolution. The participants apply the methods and tools to the software chrestomathy of the 101companies project. Diverse experiments are enabled by the many contributions of the chrestomathy with its coverage of many software languages and technologies. The chrestomathy is available as a repository of source code and through “data dumps” for extracted facts. The participants select those parts of the chrestomathy that are the most suited for efficiently demonstrating their re-engineering methods and tools. The expectation is that the hackathon produces a corpus of re-engineering samples, which may be useful, for example, in teaching re-engineering, or as a benchmark or point of reference in re-engineering research.

=== Prerequisite ===

Participants should have some basic understanding of re-engineering and some level of expertise in some technology that can serve as an instrument for re-engineering. Team work may be of help, of course. Bring your methods and tools to re-engineer the 101companies chrestomathy!

=== Deliverables ===

* Re-engineering components for different purposes:
** Program refactoring
** Wrapping for backwards compatibility or SOA
** Code injection for extra functionality or assertions
** Dead-code detection and elimination
** Language or API migration
** Database re-engineering
** Architectural modifications
** Modularization or component identification
** Coupled software transformations
=== Resources ===

* [http://en.wikipedia.org/wiki/Reengineering_(software) Re-engineering (software)] @ Wikipedia
* 101companies: [http://101companies.org/ wiki], [http://github.com/101companies/101repo repository], [http://101companies.org/index.php/Category:Meta_101feature (meta) 101features], [http://101companies.org/index.php/101companies:Data data]
* Illustrative implementations:
** [http://github.com/rlaemmel/coupling101demo coupling101demo]
* Conferences @ DBLP: [http://www.informatik.uni-trier.de/~ley/db/conf/icsm/ ICSM], [http://www.informatik.uni-trier.de/~ley/db/conf/csmr/ CSMR]
=== Relationships ===

* The hackathon on [[reverse engineering]] precedes this hackathon on re-engineering.
=== Coordination ===

* [http://github.com/grammarware Vadim Zaytsev]
* [http://github.com/anyahelene Anya Helene Bagge]
* [http://www.udo-borkowski.de Udo Borkowski]
43 changes: 0 additions & 43 deletions Reverse-Engineering.mediawiki
@@ -1,43 +0,0 @@
== SoTeSoLa hackathon on reverse engineering ==

=== Summary ===

The hackathon aims at exercising the methods and tools for software reverse engineering as they are of interest to the participants. Reverse engineering is meant here in a broad sense to include, for example, fact extraction, software visualization, vocabulary mining, analysis of language usage, and architecture recovery. The participants apply the methods and tools to the software chrestomathy of the 101companies project. Diverse experiments are enabled by the many contributions of the chrestomathy with its coverage of many software languages and technologies. The chrestomathy is available as a repository of source code and through “data dumps” for extracted facts. The participants select those parts of the chrestomathy that are the most suited for efficiently demonstrating their reverse engineering methods and tools. The expectation is that the hackathon produces a corpus of reverse engineering samples, which may be useful, for example, in teaching reverse engineering, or as a benchmark or point of reference in reverse engineering research.

=== Prerequisite ===

Participants should have some basic understanding of reverse engineering and some level of expertise in some technology that can serve as an instrument for reverse engineering. Team work may be of help, of course. Bring your methods and tools to reverse-engineer the 101companies chrestomathy!

=== Deliverables ===

* Reverse engineering components for different purposes:
** Fact extraction
** Metrics computation
** Software visualization
** Vocabulary mining
** Analysis of language usage
** Analysis of API usage
** Architecture recovery
** Design pattern recovery
** …
=== Resources ===

* [http://en.wikipedia.org/wiki/Reverse_engineering Reverse engineering] @ Wikipedia
* [http://github.com/SoTeSoLa/SoTeSoLa/tree/master/hackathon-reverse Illustrative implementations] @ github.com/SoTeSoLa
* More illustrative implementations elsewhere:
** [http://github.com/rlaemmel/loc101demo loc101demo]
** [http://github.com/rlaemmel/api101demo api101demo]
* 101companies: [http://101companies.org/ wiki], [http://github.com/101companies/101repo repository], [http://101companies.org/index.php/Category:Meta_101feature (meta) 101features], [http://101companies.org/index.php/101companies:Data data]
* Conferences @ DBLP: [http://www.informatik.uni-trier.de/~ley/db/conf/wcre/ WCRE], [http://www.informatik.uni-trier.de/~ley/db/conf/iwpc/ ICPC], [http://informatik.uni-trier.de/~ley/db/conf/msr/ MSR]
=== Relationships ===

* The hackathon on [[re-engineering]] complements the present hackathon on reverse engineering.
* The working group on [[LinkedData|LinkedData]] may analyze LinkedData-like facts about the 101repo.
=== Coordination ===

* [http://github.com/grammarware Vadim Zaytsev]
* [http://github.com/anyahelene Anya Helene Bagge]
* [http://www.udo-borkowski.de Udo Borkowski]