You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
There are no files selected for viewing