Your what is my how: Why requirements and architectural design should be iterative.
Michael W. WhalenAnitha MurugesanMats Per Erik HeimdahlPublished in: TwinPeaks@RE (2012)
Keyphrases
- architectural design
- detailed design
- design decisions
- software architecture
- functional requirements
- high level
- information retrieval
- real time systems
- user requirements
- information systems
- expert systems
- data driven
- digital libraries
- back end
- database systems
- e learning
- decision making
- artificial intelligence
- iterative optimization
- data mining