How history justifies system architecture (or not)

International Workshop on Principles of Software Evolution (IWPSE)

Volumn 2003-January, Issue , 2003, Pages 73-83

  Zimmermann, T ^a   Diehl, S ^a   Zeller, A ^a  

^a SAARLAND UNIVERSITY   (Germany)

Author keywords

Computer architecture; Computer science; History; Program processors; Prototypes; Software design; Software prototyping; Software systems; Visual databases; Visualization

Indexed keywords

COMPUTER ARCHITECTURE; COMPUTER SCIENCE; COMPUTER SOFTWARE; FLOW VISUALIZATION; HISTORY; PROGRAM PROCESSORS; SOFTWARE DESIGN;

DATABASE SCHEMAS; FINE GRAINED; PROTOTYPES; SOFTWARE ENTITIES; SOFTWARE SYSTEMS; SYSTEM ARCHITECTURES; VISUAL DATABASE;

SOFTWARE PROTOTYPING;

EID: 84943196231     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/IWPSE.2003.1231213     Document Type: Conference Paper

References (6)

1. J. M. Bieman, A. A. Andrews, and H. J. Yang. Understanding change-proneness in OO software through visualization. In Proc. 11th International Workshop on Program Comprehension, pages 44-53, Portland, Oregon, May 2003.
2. K. Fogel and M. O'Neill. cvs2cl.pl: CVS-log-message-to-ChangeLog conversion script, Sept. 2002. http://www.redbean.com/cvs2cl/.
3. H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In Proc. International Conference on Software Maintenance (ICSM '98), Washington D.C., USA, Nov. 1998. IEEE.
4. IEEE Architecture Working Group. IEEE recommended practice for architectural description of software-intensive systems. IEEE Standard 1471-2000, 2000.
5. G. Snelting. Reengineering of configurations based on mathematical concept analysis. ACM Transactions on Software Engineering and Methodology (TOSEM), 5(2):146-189, 1996.
6. D.Čubranić and G. C. Murphy. Hipikat: Recommending pertinent software development artifacts. InProc. 25th International Conference on Software Engineering (ICSE), pages 408-418, Portland, Oregon, May 2003.