240 likes | 404 Views
Distributed Component-Based Software Development: An Incremental Approach. Eduardo Santana de Almeida , Alexandre Alvaro, Daniel Lucrédio, Antonio Francisco do Prado, Luis Carlos Trevelin Federal University of Pernambuco, Federal University of São Carlos, Brazil. Introduction. Motivation
E N D
Distributed Component-Based Software Development: An Incremental Approach Eduardo Santana de Almeida, Alexandre Alvaro, Daniel Lucrédio, Antonio Francisco do Prado, Luis Carlos Trevelin Federal University of Pernambuco, Federal University of São Carlos, Brazil
Introduction • Motivation • Lack ofpatterns, approaches….processes • Development for reuse, Development with reuse • Non-functional requirements • Distribution • Persistence • A question: What is necessary? • Full support for CBD {specification, design, implementation….} • The Ingredients (soup of techniques…) • CBSE, frameworks, patterns, distribution • The Proposal • Incremental approach • Development for and with reuse • But, Is It useful? • Experimental Study
Catalysis • CBD Method • Middleware • Component{distribution, search} • Frameworks, Patterns • Reuse • NFR • Distribution • Persistence • MVCASE Tool
MVCASE Tool www.recope.dc.ufscar.br/mvcase
Design Components (NFR) • Distribution, Fault Tolerance, Caching • Persistence
Experimental Study • Steps • Definition • Planning • Instantiation • Execution • Analysis • Definition – Goal Question Metric Paradigm (GQM) Analysethe use of the incremental approach in the distributed component-based software development. for the purpose ofcharacterizing the viability of its use and the development continuity. with respect tothe gain and difficulties of its use. from the point of view ofthe researcher. in the contextofthe distributed component-based software development.
Planning • 2 months and 18 days • Three versions of experimental plan • Instantiation and Execution • Selection of the Subjects • BSc(2),MSc(6) • Software Development • Analysis Mechanisms • Mean • Execution • 1 month
Analysis of the Results • Quantitative Evaluation • Qualitative Evaluation • Approach:Useful • Instrumentation
Conclusions • Incremental Approach • Developmentwithandforreuse • Non-functional requirements • MVCASE Tool • Experimental Study • Future works • Robust framework for software reuse • Technical aspects{process: reuse, reengineering, adaptation, certification, software reuse environment, repository system} • Non-technical aspects • Academia andIndustry www.cin.ufpe.br/~rise