%0 Conference Paper %1 ernst07icsm %A Ernst, Neil A. %A Mylopoulos, John %B International Workshop on Software Evolvability at ICSM %C Paris, France %D 2007 %I IEEE Computer Society %K design goals history personal requirements software %T Tracing software evolution history with design goals %U http://www.neilernst.net/blog/wp-content/uploads/2007/08/swhist.pdf %X When designing software for evolvability, it is important to understand which particular designs have worked in the past – and which have not. This paper argues that understanding the history of a software innovation is valuable in setting the context for future innovations. There is no formal discipline of software history. While there is an active body of research in information technology (IT) and innovation management, which seeks to understand how to maximize value from IT spending, this research often ignores the meaningful technological underpinnings of such tools. We suggest that the study of design history should be extended to software artifacts. The paper introduces notions like requirements analysis, technology context, and social context to explain how, and why, certain technologies evolved as they did. We apply these concepts to the history of distributed computing protocols. We conclude with observations drawn from this history that suggest designing software for evolvability must consider the history of similar applications in the requirements analysis.

@inproceedings{ernst07icsm, abstract = {When designing software for evolvability, it is important to understand which particular designs have worked in the past – and which have not. This paper argues that understanding the history of a software innovation is valuable in setting the context for future innovations. There is no formal discipline of software history. While there is an active body of research in information technology (IT) and innovation management, which seeks to understand how to maximize value from IT spending, this research often ignores the meaningful technological underpinnings of such tools. We suggest that the study of design history should be extended to software artifacts. The paper introduces notions like requirements analysis, technology context, and social context to explain how, and why, certain technologies evolved as they did. We apply these concepts to the history of distributed computing protocols. We conclude with observations drawn from this history that suggest designing software for evolvability must consider the history of similar applications in the requirements analysis.}, added-at = {2008-05-22T21:18:39.000+0200}, address = {Paris, France}, author = {Ernst, Neil A. and Mylopoulos, John}, biburl = {https://www.bibsonomy.org/bibtex/23b8ed0b0f57e2af912a9bb84518d0d6c/neilernst}, booktitle = {International Workshop on Software Evolvability at ICSM}, interhash = {ae5caf28de83851781abea6783962cdf}, intrahash = {3b8ed0b0f57e2af912a9bb84518d0d6c}, keywords = {design goals history personal requirements software}, month = {October}, publisher = {IEEE Computer Society}, timestamp = {2008-05-22T21:18:39.000+0200}, title = {Tracing software evolution history with design goals}, url = {http://www.neilernst.net/blog/wp-content/uploads/2007/08/swhist.pdf}, year = 2007 }