SEMI-AUTOMATED PROCESS FOR OPEN SOURCE CODE REUSE
•
0 likes•901 views
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.
Recommended
Recommended
More Related Content
Similar to SEMI-AUTOMATED PROCESS FOR OPEN SOURCE CODE REUSE
Similar to SEMI-AUTOMATED PROCESS FOR OPEN SOURCE CODE REUSE (20)
More from Apostolos Kritikos
More from Apostolos Kritikos (11)
Recently uploaded
Recently uploaded (20)
SEMI-AUTOMATED PROCESS FOR OPEN SOURCE CODE REUSE
- 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
- 2. Who is reusing code ?
- 4. hobbyists
- 5. freelancers
- 7. Why ?
- 8. To avoid reinventing the wheel
- 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 )
- 10. Free / Libre Open Source Software ( FLOSS )
- 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
- 12. WWW
- 13. WWW POOL OF REUSABLE CODE
- 14. How do i reuse ? Any known recipes ? Do they actually exist?
- 15. We need one anyway
- 16. A methodology or...
- 17. Maybe A process
- 18. But...
- 19. reusers
- 20. reusers WHAT DO THEY WANT ?
- 21. REUSE CODE ADAPTING THE RETRIEVED CODE TO THE SYSTEM UNDER DEVELOPMENT ADAPTING THE SYSTEM UNDER DEVELOPMENT TO THE RETRIEVED CODE
- 22. reusers
- 23. reusers WHO ARE THEY ?
- 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 -
- 25. REUSE PROCESS & SOFTWARE PRODUCT'S LIFECYCLE
- 26. SOFTWARE PRODUCT'S LIFECYCLE PHASES 1. CONCEPT 2. DEVELOPMENT 3. PRODUCTION 4. UTILIZATION 5. RETIREMENT ISO/IEC 15288, 2002
- 27. SOFTWARE PRODUCT'S LIFECYCLE PHASES 1. CONCEPT 2. DEVELOPMENT 3. PRODUCTION 4. UTILIZATION 5. RETIREMENT ISO/IEC 15288, 2002
- 28. Reuse & floss components Component decomposition based on the requirements Requirement / component tree Possible alternation of the tree
- 29. A process for Open source code reuse
- 31. Search types Search forges: e.g. sourceforge Search for trivial code: source code search engines (krugle) or classical search engines (google)
- 32. Do i have to reuse?
- 33. And if i do...
- 34. CONCLUSIONS
- 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
- 36. FUTURE WORK
- 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
- 38. THANK YOU! akritiko@csd.auth.gr
Editor's Notes
- 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)