(wolf-lessons)
finished reading wolfmaier's paper. pretty cool stuff. the guys talk from experience.
- effort of analyzing a system is abour 10-12 man days.
- high level analysis is applied. critical metrics are detected. expected metrics values.
- good source of heuristics that can be mapped on top of the softwarenaut view.
- absolutely necesary to involve the architects
- sotograph - seems to have been useful for them.
- generated code has to be treated differently
19.07 - 19.28
Mircea writing things related to his thesis, so he won't forget them. One has many things floating through his head in the year of the thesis :)
Sunday, March 16, 2008
wolfmaier's lessons
Labels:
paper
Blog Archive
-
▼
2008
(33)
-
▼
March
(27)
- Top-Down Software Exploration
- Related Work on Module Depdendencies
- inherit and reuse...
- [micro-survey] metamodels of hierarchical explorat...
- ...
- programming in the large vs. programming in the small
- todos
- ...
- wolfmaier's lessons
- [micro-survey] Clustered Decomposition Evolution
- ...
- harel - on visual formalisms
- fast-read
- ...
- supervising vs. understanding
- how to gather requirements
- Links
- Survey Bricolage
- ...
- Survey on Architectural-Level Evolution
- ...
- archjava
- ...
- mining software compilations
- why not architecture
- lens
- masters
-
▼
March
(27)