1 / 27

Comprehensive System for Systematic Case-Driven Software Reuse

Comprehensive System for Systematic Case-Driven Software Reuse. M. Śmiałek , A. Kalnins, E. Kalnina, A. Ambroziewicz, T. Straszak, K. Wolter. Warsaw University of Technology , Poland IMCS University of Latvia, Latvia University of Hamburg, Germany. SOFSEM 2010 25 . 01 .20 10.

ferdinand-anderson
Download Presentation

Comprehensive System for Systematic Case-Driven Software Reuse

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Comprehensive System for Systematic Case-Driven Software Reuse M. Śmiałek, A. Kalnins, E. Kalnina, A. Ambroziewicz, T. Straszak, K. Wolter Warsaw University of Technology, Poland IMCS University of Latvia, Latvia University of Hamburg, Germany SOFSEM 2010 25.01.2010

  2. Outline – reuse schema Requirements driven Transformation driven Software Case 1 Software Case 1 Software Case 1 Software Case 1 Software Case 1 Design 1 Code 1 Requirements 1 Software case repositories δR2 Retrieval technologies Software Case 12 Requirements 2 Design 2 Code 2

  3. ReDSeeDS Engine 3

  4. Reuse schema – step 1 Software Case 1 Software Case 1 Software Case 1 Software Case 1 Software Case 1 Design 1 Code 1 Requirements 1 δR2 Software Case 12 Requirements 2 Design 2 Code 2

  5. RSL = scenarios + vocabulary

  6. RSL Editor

  7. Evolution schema – step 2 Software Case 1 Software Case 1 Software Case 1 Software Case 1 Software Case 1 Design 1 Code 1 Requirements 1 δR2 Software Case 12 Requirements 2 Design 2 Code 2

  8. R to D transformation rules Requirements Domain Notion Use Case Domain Statement Scenario step Scenario step Scenario step DS Logic Design AL_Interface al_operation DL_Interface dl_operation Application Behavior Domain Behavior

  9. D = t(R) - structure

  10. D = t(R) - dynamics

  11. Evolution schema – step 3 Software Case 1 Software Case 1 Software Case 1 Software Case 1 Software Case 1 Design 1 Code 1 Requirements 1 δR2 Software Case 12 Requirements 2 Design 2 Code 2

  12. Application logic code IShowExtendedCourseList classCShowExtendedCourseListimplementsIShowExtendedUserList { // (...) wantsToSeeCourseList(){ // // } } classCShowExtendedCourseListimplementsIShowExtendedUserList { // (...) wantsToSeeCourseList(){ ICourseList.builds(cl); UI.showsCourseList(cl); } } CourseManagement

  13. Domain logic code CoursesServices ICourseList class CCourseListimplements ICourseList { // (...) voidbuilds(CourseListDTOcld){ // // // // // } } class CCourseListimplements ICourseList { // (...) voidbuilds(CourseListDTOcld){ UserListDTOresList; for (i=1; i==user_list_length; i++) { resList.add(userList[i]); } cld=resList; } } R1

  14. R to D to C and reuse Requirements Technological Framework Functional Requirements Domain Definition Non-functional Requirements R to D Transformation Design Application Behaviour System Structure Domain Behaviour D to C Transformation Code

  15. Reuse schema – step 4 Software Case 1 Software Case 1 Software Case 1 Software Case 1 Software Case 1 Design 1 Code 1 Requirements 1 δR2 Software Case 12 Requirements 2 Design 2 Code 2

  16. Extending requirements

  17. Reuse schema – step 5 Software Case 1 Software Case 1 Software Case 1 Software Case 1 Software Case 1 Design 1 Code 1 Requirements 1 δR2 Software Case 12 Requirements 2 Design 2 Code 2

  18. R to D to C again

  19. New application logic code IShowExtendedCourseList classCShowExtendedCourseListimplementsIShowExtendedUserList { // (...) wantsToSeeCourseList(){ UI.showsCourseFilterForm(f); } } CourseManagement

  20. New domain logic code CoursesServices C1 ICourseFilter class CCourseListimplements ICourseList { // (...) voidbuilds(CourseFilterDTOfil, CourseListDTOcld){ UserListDTOresList; for (i=1; i==user_list_length; i++) { ifcompare(udto,userList[i]) resList.add(userList[i]); } cld=resList; } } R2

  21. Determine elements for reuse Software Case 1 Software Case 1 Software Case 1 Software Case 1 Software Case 1 Design 1 Code 1 Requirements 1 δR2 Software Case 12 Requirements 2 Design 2 Code 2

  22. Similarity measures • Similarity measures based on: • common terminology • description logic • structural approach (defResource c1::Client--NounPhrase (rdf:type owl:Class) (owl:intersectionOf TRRSL:NounPhrase (owl:Restriction (owl:onProperty TRRSL:nounLink) (owl:allValuesFrom TY::order2)) (owl:Restriction (owl:onProperty TRRSL:isPartOfDomainStatement_d1e3741) (owl:allValuesFrom c2::order--DomainStatement))))

  23. Showing similarity

  24. Showing elements for reuse

  25. Summary – evolution or revolution? support for reuse Software Case 15 Requirements 4 Design 4 Code 4 QR4 δR4 “instant refactor” Software Case 1 Software Case 1 Software Case 1 Software Case 1 Software Case 1 Design 1 Code 1 Requirements 1 δR2 “instant diff” Software Case 12 Requirements 2 Design 2 Code 2

  26. Thank you for your attention. www.redseeds.eu

  27. Consortium members, duration and budget Infovide S.A. Warsaw University of Technology HITeC e.V. University of Koblenz-Landau PRO DV Software AG Fraunhofer - Gesellschaft (Institute for Experimental Software Engineering) Latvia Institute of Mathematics and Computer Science - University of Latvia Algoritmu sistemos, UAB Vienna University of Technology C/S IT Ltd. - Cybersoft Heriot-Watt University Budget: 3.804.000,- € Community Contribution: 2.990.710,- € Duration: September 2006 – October 2009 27

More Related