Functional paleontology: System evolution as the user sees it

Proceedings - International Conference on Software Engineering

Volumn 2001-May, Issue , 2001, Pages 421-430

  Antón, Annie I ^a   Potts, Colin ^b  

^a North Carolina State University   (United States)

^b Georgia Institute of Technology   (United States)

Author keywords

Empirical methods; Human computer interaction (HCI); Measurement; Metrics; Requirements engineering; Reverse engineering; Sofiware evolution

Indexed keywords

HUMAN COMPUTER INTERACTION; REQUIREMENTS ENGINEERING; PERSONAL COMMUNICATION SYSTEMS; REVERSE ENGINEERING;

DESIGN AND IMPLEMENTATIONS; EMPIRICAL METHOD; HUMAN-COMPUTER INTERACTION; METRIC; PALAEONTOLOGY; REQUIREMENT ANALYSIS; REQUIREMENT ENGINEERING; SOFIWARE EVOLUTION; SOFTWARE EVOLUTION; SYSTEM EVOLUTION; INTERPERSONAL COMMUNICATION SERVICES; TELEPHONY SERVICES;

REVERSE ENGINEERING; SOFTWARE ENGINEERING;

EID: 0035024116     PISSN: 02705257     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ICSE.2001.919115     Document Type: Conference Paper

References (30)

1. Allen, R. and D. Garlan. “A formal basis for architectural connection” ACM Transactions on Software Engineering and Methodology, Volume 6, No. 3, pp. 213 - 249, July 1997.
2. Antbn, A.I. “Goal-Based Requirements Analysis, ” International Conference on Requirements Engineering IICRE '96). Colorado Springs, Colorado, USA, pp. 136-144, April 1996.
3. Antbn, A.I. & C. Potts. “The Use of Goals to Surface Requirements for Evolving Systems, ” Int'l Canference on So/hore Engineering (ICSE '98). Kyoto, Japan, pp. 157-166, 19-25 April 1998.
4. Basala, G. The Evolution qf Technologv. New York, Cambridge University Press. 1988.
5. Boehm. B. P. Bose, E. Horowitz & M.J. Lee. “Software requirements negotiation and renegotiation aids”, 17th Intl. Conf on Software Engineering, Seattle, WA, pp. 243-253, 24 - 28 April 1995.
6. Brand, S. How Buildings Learn: What Happens after They're Built. New York, Viking. 1994.
7. Curtis, B., H. Krasner, et al. “A field study of the software design process for large teams.” Communications of the ACM 3111): 1268-1287, 1988.
8. Dahlbom, B.and L. Mathiassen. Computers in Context: The Philosophy and Practice of' Systems Design. Blackwell, Oxford. 1993.
9. DeBaud, Jean-Marc and Klaus Schmid. A systematic approach to derive the scope of software product lines; Proc. Int. Conf. Software Eng. Los Angeles, CA: 1999, pp. 34 - 43.
10. Emmerson, Andrew. “Strowger and the Invention of the Automatic Telephone Exchange: 1879-1912, ” 1989.
11. E. Gamma, R. Helm, R. Johnson, J. Vlissides. Design Patterns: Elements of' Reusable Object-Oriented Software, Addison-Wesley, Reading, MA 1994.
12. Grudin, J. Computer-supported cooperative work: History and, focus.IEEE Computer: 19-26, 1994.
13. Hsi, I. & C. Potts (in press) “Studying the Evolution and Enhancement of Software Features”. Intl. Con/: Software Maintenance, San Jose, CA, 11-14 October 2000.
14. Jacobson, I. et. al. Object-Oriented Software Engineering: A Use CaseDrivenApproach, Addison-Wesley, 1992.
15. Michael Jackson. Software Requirements and Specifications. Addison-Wesley, 1995.
16. Karlsson. J. & K. Ryan. “A Cost-Value Approach for Prioritizing Requirements”. IEEE Software, pp. 67-74, 1997.
17. Kuhn, T.S. The Structure of Scientific Revolutions, 3rd edition Univ of ChicagoPress, 1996.
18. Lehman, M.M. and L.A. Belady. Program Evolution - Processes of Software Change, Academic Press, London, 1985.
19. Lehman, M.M. “Programs, Life Cycles and the Laws of Software Evolution, “Proc. IEEE Special Issue on Software Evolution, IEEE, Piscataway, NJ, Vol. 68, No. 9, September 1980, pp. 1060-1076.
20. MacDonell, S.G., Comparat!ve Review of Functional Complexity Assessment Methods, for Effort Estimation. Br. Computer Soc./Inst. Electrical Eng. J., 1994.9(3): p. 107-117.
21. Nardi, B.A., ed. Context and Consciousness: Activity Theoryand Human-Computer Interaction.. 1996, MIT Press: Cambridge, Mass.
22. Petroski, H. The Evolution of Usefil Things. New York, Vintage Books. 1992.
23. Potts, C. “Invented Requirements and Imagined Customers: Requirements Engineering for Off-the-shelf Software.” Second IEEE Int'l Symposition Requirements Engineering. 1995. York, UK: IEEE Computer Society Press.
24. Potts, C. “A ScenIC: A Strategy for Inquiry-Driven Requirements Determination, ” lEEE 4th International Symposium on Requirements Engineering, Limerick, Ireland, 7-I I June 1999.
25. Rogers, E. M. Diffusion of Innovations. New York, Free Press, 1995.
26. Sober, E. The Nature of Selection: Evolutionary Theory in Philosophical Focus. Chicago, IL, Chicago University Press, 1993.
27. Sullivan, K.J., “Software Design: The Options Approach, ” 2nd Intl. Software Architecture Workshop, Joint Proceedings of the SIGSOFT '96 Workshops, San Francisco, CA, pp. 15-18, Oct. 1996.
28. Tenner, E. Why Things Bite Back: Technology and the Revenge of Unintended Consequences. Knopf, 1996.
29. van Lamsweerde, A. and Darimont, R. and Massonet, P. “Goal-Directed Elaboration of Requirements for a Meeting Scheduler: Problems and Lessons Learnt, ” Proceedings 2nd Intemational Symposium on Requirements Engineering RE.99, York, UK. pp. 194-203, March 1995.
30. Zuboff, S. In the Age of the Smart Machine: The Future of Work and Power, Basic Books, 1988