{"title":"A \"framework\" for object oriented frameworks design","authors":"D. Parsons, A. Rashid, A. Speck, A. Telea","doi":"10.1109/TOOLS.1999.779007","DOIUrl":null,"url":null,"abstract":"Object-oriented frameworks are established tools for domain-specific reuse. Many framework design patterns have been documented, e.g. reverse engineering framework architectures from conventionally built applications for a given domain. The framework development cycle generally evolves from an open framework to a closed application. We describe a more flexible component-based approach to framework design that stresses a common interface for 'plugging-in' new components at different lifecycle stages. An analysis of framework-related user roles shows that the classical developer/end-user boundary is too rigid. We see the framework's development as a continuum within which its 'actors' can customise its behavior. This both increases the system's flexibility and reduces its maintenance requirement. A case study of three frameworks for different application domains illustrates the presented principles.","PeriodicalId":434404,"journal":{"name":"Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275)","volume":"44 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1999-06-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"37","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/TOOLS.1999.779007","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 37
Abstract
Object-oriented frameworks are established tools for domain-specific reuse. Many framework design patterns have been documented, e.g. reverse engineering framework architectures from conventionally built applications for a given domain. The framework development cycle generally evolves from an open framework to a closed application. We describe a more flexible component-based approach to framework design that stresses a common interface for 'plugging-in' new components at different lifecycle stages. An analysis of framework-related user roles shows that the classical developer/end-user boundary is too rigid. We see the framework's development as a continuum within which its 'actors' can customise its behavior. This both increases the system's flexibility and reduces its maintenance requirement. A case study of three frameworks for different application domains illustrates the presented principles.