The presentation of my publication "A semi-automated process for open source code reuse" presented at the Evaluation of Novel Approaches to Software Engineering (ENASE) 2010 conference.
Bajaj Allianz Life Insurance Company - Insurer Innovation Award 2024
Code Reuse Presentation @ ENASE 2010
1. A SEMI-AUTOMATED PROCESS
FOR OPEN SOURCE CODE
REUSE
APOSTOLOS KRITIKOS
GEORGE KAKARONTZAS
IOANNIS STAMELOS
PARTIALLY FUNDED BY THE EUROPEAN COMMISSION IN
THE CONTEXT OF THE OPEN-SME PROJECT
ARISTOTLE UNIVERSITY OF THESSALONIKI INFORMATICS DEPT. ENASE 2010 JULY 23rd, 2010
9. Most classic components
are out there (www)
( reuse of floss code )
code createD can be used as a base to
Future project requests
( reuse of legacy code )
11. Model of COLLABORATIVE DEVELOPMENT
( software )
made AVAILABLE ON-LINE and for FREE
Many lines of code
Let users Download this code
Use / alter / even commercialize
The derived work
24. CAN BE
Any DEVELOPER
- IF A SYSTEMATIC
REUSE PROCESS IS ABSENT -
AN ACTUAL ENGINEER ASIGNED WITH THE TASK
OF ADAPTING REUSABLE COMPONENTS
- IN MORE SYSTEMATIC REUSE APPROACHES -
35. A FIRST ATTEMPT TO PROVIDE A structured
way of implementing reuse engineering
Currently our model requires the
presence of an expert for
various decisions
37. A FULLY AUTOMATED PROCESS WHERE NO
EXPERT WILL BE NEEDED
TRY MEASURING THE “FITNESS” OF A
REUSABLE COMPONENT WITH THE REST OF
THE SYSTEM UNDER DEVELOPMENT
The process depicted into this flowchart is trying to present the actions of a reuse engineer, from the point that receives the requirements for a new project to the one that delivers the final product. While I'll be presenting it to you, it might look familiar and obvious. The goal behind the flowchart is to gather all this obvious information in one place and organize it in a series of steps. After that, we would be able to focus on the parts of the process model that seem complex and confusing and thus, good research goals (something that we gladly show happening, when we received the reviewers comments)
The process depicted into this flowchart is trying to present the actions of a reuse engineer, from the point that receives the requirements for a new project to the one that delivers the final product. While I'll be presenting it to you, it might look familiar and obvious. The goal behind the flowchart is to gather all this obvious information in one place and organize it in a series of steps. After that, we would be able to focus on the parts of the process model that seem complex and confusing and thus, good research goals (something that we gladly show happening, when we received the reviewers comments)
The process depicted into this flowchart is trying to present the actions of a reuse engineer, from the point that receives the requirements for a new project to the one that delivers the final product. While I'll be presenting it to you, it might look familiar and obvious. The goal behind the flowchart is to gather all this obvious information in one place and organize it in a series of steps. After that, we would be able to focus on the parts of the process model that seem complex and confusing and thus, good research goals (something that we gladly show happening, when we received the reviewers comments)