Program evolution: processes of software change
Program evolution: processes of software change
An experimental evaluation of the assumption of independence in multiversion programming
IEEE Transactions on Software Engineering
Grasping reality through illusion—interactive graphics serving science
CHI '88 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Software Process Evolution at the SEL
IEEE Software
Proceedings of the Conference on The Future of Software Engineering
A static analyzer for finding dynamic programming errors
Software—Practice & Experience
The structure and value of modularity in software design
Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering
Software Engineering Economics
Software Engineering Economics
The Mythical Man-Month: Essays on Softw
The Mythical Man-Month: Essays on Softw
Automatic generation of program specifications
ISSTA '02 Proceedings of the 2002 ACM SIGSOFT international symposium on Software testing and analysis
An Ethnographic Study of Copy and Paste Programming Practices in OOPL
ISESE '04 Proceedings of the 2004 International Symposium on Empirical Software Engineering
The Standish report: does it really describe a software crisis?
Communications of the ACM - Music information retrieval
Chapter I: Notes on structured programming
Structured programming
Formal Software Analysis Emerging Trends in Software Model Checking
FOSE '07 2007 Future of Software Engineering
Software debugging, testing, and verification
IBM Systems Journal
How large are software cost overruns? A review of the 1994 CHAOS report
Information and Software Technology
Bayesian reasoning for software testing
Proceedings of the FSE/SDP workshop on Future of software engineering research
On the relationship of concern metrics and requirements maintainability
Information and Software Technology
Hi-index | 0.00 |
Software engineering is broadly discussed as falling far short of expectations. Data and examples are used to justify how software itself is often poor, how the engineering of software leaves much to be desired, and how research in software engineering has not made enough progress to help overcome these weaknesses. However, these data and examples are presented and interpreted in ways that are arguably imbalanced. This imbalance, usually taken at face value, may be distracting the field from making significant progress towards improving the effective engineering of software, a goal the entire community shares. Research dichotomies, which tend to pit one approach against another, often subtly hint that there is a best way to engineer software or a best way to perform research on software. This, too, may be distracting the field from important classes of progress.