Bill Frakes in his website asked to Ted Biggerstaff one of the pioneers in software reuse and specialist in the software generators area, how big should be a reusable component.What do you thing about it?
Subscribe to:
Post Comments (Atom)
skip to main |
skip to sidebar
This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.
What language is better for software reuse?
Join The Community
Contributors
- Alexandre Alvaro
- Alexandre Martins
- Aline Timóteo
- Allan Araujo
- Cassio Melo
- Daniel Lucrédio
- Danuza Neiva
- Dietmar Stoll
- Ednaldo Dilorenzo
- Eduardo Almeida
- Eduardo Cruz
- Flavio Medeiros
- Fred Durao
- Heberth Braga
- Helaine Lins
- Hernan
- Iuri Santos
- Ivan Machado
- Jonatas Bastos
- Jose Jorge Dias
- Leandro Marques do Nascimento
- Leandro Souza
- Lica Barachisio
- Marcela Balbino
- Mirko
- Oliver Hummel
- Padraig
- Paulo Silveira
- Rafael Lucena
- Ricardo Cavalcanti
- Robson Ribeiro
- Thiago Fernandes
- Unknown
- Vinicius Garcia
- Wylliams
- Yguaratã C. Cavalcanti
- ivonei
Labels
- rise research (41)
- education (30)
- software reuse (25)
- reuse conferences (20)
- conferences (19)
- rise (19)
- research (15)
- spl (15)
- discussion (13)
- software engineering (13)
- product lines (12)
- architecture (11)
- RiSE Labs (8)
- computer science (8)
- interviews (8)
- RiSE papers (7)
- design (7)
- information retrieval (7)
- scientific problems (7)
- papers (6)
- bug (5)
- riss (5)
- software reuse models (5)
- David L. Parnas (4)
- dissertation (4)
- component (3)
- cruise (3)
- innovation (3)
- measurement (3)
- metrics (3)
- open source software (3)
- requirements (3)
- reuse books (3)
- search and retrieval (3)
- wire (3)
- Automotive systems (2)
- Software Engineering for Automotive Systems (2)
- Testing (2)
- cooperation (2)
- data mining (2)
- icsr (2)
- investments (2)
- post graduation (2)
- repository (2)
- researchers (2)
- reuse code (2)
- rise day (2)
- service-oriented architecture (2)
- software component quality (2)
- AOP (1)
- IEEE EUROMICRO (1)
- IEEE standards (1)
- In vitro (1)
- In vivo (1)
- Ontologies (1)
- Randy Pausch (1)
- Semantic Web (1)
- Software Evolution (1)
- Software Maintenance (1)
- awards (1)
- begin (1)
- bug report (1)
- business (1)
- characterization study (1)
- code (1)
- code inspection (1)
- component markets (1)
- cost models (1)
- definitions (1)
- eclipse (1)
- events (1)
- gmf (1)
- history (1)
- information technology (1)
- jobs (1)
- mobile (1)
- mobile games (1)
- model-driven development (1)
- modelware (1)
- pla (1)
- podcasts (1)
- poll (1)
- product derivation (1)
- product instantiation (1)
- programming languages (1)
- recommendation system (1)
- reuse project (1)
- scoping (1)
- soa (1)
- software architecture recovery (1)
- software engineering conferences (1)
- software reuse collection open source (1)
- sour code (1)
- sple (1)
- start (1)
- suggestions (1)
- thesis (1)
- traceability (1)
- virginia tech (1)
- visualization (1)
- workshop (1)
License
This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.
Subscribe in a reader
2 comments:
It should be big enough to do what it was intended to do. Not bigger and not too short than that. :P
In my point of view, this question involves to much things. Programming language, for example, to be practical. Or the capacity of developers to write compact algorithms, to be subjective.
In addition, how do you define a component? It must be self contained? If so, it will be bigger then one not self contained.
Hum.. this is a difficult question. I think that the size of the component is not the main feature or should be the main question. The size is relative... size in LOC, size in KB/MB, size in set of elements?
I agree with Yguaratã, and I believe that others questions are: what is needed to be reusable component? which metrics can help in answer this question?
Post a Comment