The DOI matches its Crossref record; 15 of the 15 references it cites were found in a registry or an index.
The Future of Software Performance Engineering
Abstract
Performance is a pervasive quality of software systems; everything affects it, from the software itself to all underlying layers, such as operating system, middleware, hardware, communication networks, etc. Software Performance Engineering encompasses efforts to describe and improve performance, with two distinct approaches: an early-cycle predictive model-based approach, and a late-cycle measurement-based approach. Current progress and future trends within these two approaches are described, with a tendency (and a need) for them to converge, in order to cover the entire development cycle.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Component software beyond object oriented programming
Szyperski, C., Gruntz, D., & Murer, S. 1. (2002) · Cited by 4,633
On Non-Functional Requirements in Software Engineering
Chung, L., & do Prado Leite, J. C. S. (2009) · Lecture Notes in Computer Science · doi:10.1007/978-3-642-02463-4_19 · Cited by 2,247
Non-Functional Requirements in Software Engineering
Chung, L., Nixon, B. A., Yu, E., & Mylopoulos, J. (2000) · Springer eBooks · doi:10.1007/978-1-4615-5269-7 · Cited by 1,690
Model-driven Development of Complex Software: A Research Roadmap
France, R., & Rumpe, B. (2007) · Future of Software Engineering (FOSE '07) · doi:10.1109/fose.2007.14 · Cited by 1,123
Self-Managed Systems: an Architectural Challenge
Kramer, J., & Magee, J. (2007) · Future of Software Engineering (FOSE '07) · doi:10.1109/fose.2007.19 · Cited by 829
Model-based performance prediction in software development: a survey
Balsamo, S., Di Marco, A., Inverardi, P., & Simeoni, M. (2004) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2004.9 · Cited by 770
An empirical study of FORTRAN programs
Knuth, D. E. (1971) · Software: Practice and Experience · doi:10.1002/spe.4380010203 · Cited by 680
Experience with performance testing of software systems: issues, an approach, and case study
Weyuker, E. J., & Vokolos, F. I. (2000) · IEEE Transactions on Software Engineering · doi:10.1109/32.888628 · Cited by 255
Characterizing the scalability of a large web-based shopping system
Arlitt, M., Krishnamurthy, D., & Rolia, J. (2001) · ACM Transactions on Internet Technology · doi:10.1145/383034.383036 · Cited by 163
A Synthetic Workload Generation Technique for Stress Testing Session-Based Systems
Krishnamurthy, D., Rolia, J., & Majumdar, S. (2006) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2006.106 · Cited by 102
Cited by
A Survey of Performance Optimization for Mobile Applications
Hort, M., Kechagia, M., Sarro, F., & Harman, M. (2022) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2021.3071193 · Cited by 91
Rafi, M. N., Kim, D. J., Chen, T.-H., & Wang, S. (2024) · arXiv · doi:10.48550/arxiv.2412.18750
Metadata
- Authors
- Woodside, M., Franks, G., & Petriu, D. C.
- Venue
- Future of Software Engineering (FOSE '07)
- Publisher
- IEEE
- Published
- 2007-05
- Pages
- 171-187
- OpenAlex
- W2121589816
- Cited by
- 346
- References
- 15
- FWCI
- 14.39
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: The Future of Software Performance Engineering. https://app.cochat.ai/papers/10.1109/fose.2007.32
- The paper
- Woodside, M., Franks, G., & Petriu, D. C. (2007). The Future of Software Performance Engineering. Future of Software Engineering (FOSE '07). https://doi.org/10.1109/fose.2007.32
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.
