There are multiple ways in which one can gather requirements for the task of understanding and supervising the evolution of a sytem from the 10'000ft perspective as eric sais it.
distill requirements from informal interviews with individual experts
-- erik donnenburg
-- adi groza
-- reinout heeck
-- contact mihu and see if i can talk with anybody at siemens
find requirements in the literature
- i don't remember seing requirements for this level...
find requirements on discussions on the net
-- Tips for reading code on the c2 wiki Library calls, Search, ...
-- Discussion on slashdot on how do you reverse engineer half a million lines of c/c++ code.
a formal survey
- survey separately[ the researchers and ask what do they thing is useful. then survey the potential users and see what *they* think it is helfpul.
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 :)
Friday, March 14, 2008
how to gather requirements
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)