Download:
by Annie I. Ant—n Colin Potts
In Proceedings of the 23rd International Conference on Software Engineering
http://www.csc.ncsu.edu/faculty/anton/pubs/icse2001.pdf
Add To MetaCart
Abstract:
It has long been accepted that requirements analysis should precede architectural design and implementation, but in software evolution and reverse engineering this concern with black-box analysis of function has necessarily been de-emphasized in favor of code-based analysis and designer-oriented interpretation. In this paper, we redress this balance by describing "functional paleontology", an approach to analyzing the evolution of user-visible features or services independent of architecture and design intent. We classify the benefits and burdens of interpersonal communication services into core and peripheral categories and investigate the telephony services available to domestic subscribers over a fifty-year period. We report that services were introduced in discrete bursts, each of which emphasized different benefits and burdens. We discuss the general patterns of functional evolution that this "fossil record " illustrates and conclude by discussing their implications for forward engineering of software products.
Citations
|
482
|
A Formal Basis for Architectural Connection
– Allen, Garlan
- 1997
|
|
329
|
Diffusion of innovations
– Rogers
- 1995
|
|
203
|
Context and consciousness: Activity theory and human–computer interaction
– Nardi
- 1996
|
|
103
|
Computer-Supported Cooperative Work: History and focus
– Grudin
- 1994
|
|
101
|
Program life cycles and laws of software evolution
– Lehman
|
|
90
|
Goal-Directed Elaboration of Requirements for a Meeting Scheduler
– Lamsweerde, Darimont, et al.
- 1995
|
|
86
|
Software Requirements & Specifications
– JACKSON
- 1995
|
|
76
|
The use of goals to surface requirements for evolving systems
– Antón, Potts
- 1998
|
|
61
|
Goal-Based Requirements Analysis
– Antón
- 1996
|
|
60
|
A Cost-Value Approach for Prioritizing Requirements
– Karlsson, Ryan
- 1997
|
|
58
|
How Buildings Learn: What Happens After They’re Built, Viking
– Brand
- 1994
|
|
46
|
Software Requirements Negotiation and Renegotiation Aids: A Theory-W Based Spiral Approach
– Boehm, Bose, et al.
- 1995
|
|
36
|
Computers in Context: The Philosophy and Practice of Systems Design
– Dahlbom, Mathiassen
- 1995
|
|
33
|
ScenIC: A strategy for inquiry-driven requirements determination
– Potts
- 1999
|
|
27
|
A systematic approach to derive the scope of software product lines
– DeBaud, Schmid
- 1999
|
|
26
|
Invented requirements and imagined customers: requirements engineering for off-the-shelf software
– Potts
- 1995
|
|
21
|
Object-Oriented Software Engineering (A Use Case Driven Approach
– al
- 1992
|
|
17
|
Why things bite back: Technology and the revenge of unintended consequences
– Tenner
- 1996
|
|
15
|
The evolution of useful things
– Petroski
- 1992
|
|
14
|
The Structure of Scientific Revolutions, 3rd edition
– KUHN
- 1996
|
|
7
|
Comparative Review of Functional Complexity Assessment Methods for Effort Estimation
– MacDonell
- 1994
|
|
7
|
The Nature of Selection: Evolutionary Theory in Philosophical Focus
– Sober
- 1984
|
|
4
|
Software design: the options approach," presented at
– Sullivan
- 1996
|
|
2
|
et al. "A field study of the software design process for large teams
– Curtis, Krasner
- 1988
|
|
2
|
Strowger and the Invention of the Automatic Telephone Exchange
– Emmerson
- 1989
|
|
1
|
The Evolution of Technology
– Basala
- 1988
|
|
1
|
in press) “Studying the Evolution and Enhancement
– Hsi
- 2000
|
