Gregory Fox

dblp:17/6166 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 1989
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Software maintenance and evolution · 100%

Topics — the 1 heaviest of 2, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Software maintenance and evolution
software performance engineering
0.011989
Performance Engineering as a Part of the Development Life Cycle for Large-Scale Software Systems · ICSE 1989
YearPublicationVenuePosition
1989 Performance Engineering as a Part of the Development Life Cycle for Large-Scale Software Systems
abstract
The development of a large-scale software system occurs in a structured manner, proceeding through a number of distinct development phases.An effort is needed throughout the three to five year development of these systems to avoid last minute discovery that the system fails to meet specified levels of performance.The role of performance engineering during the early (modeling) portions of development is well known.This paper addresses the role of performance engineering throughout the entire software development life cycle.The paper draws upon experiences from successful performance engineering efforts applied to large transaction-based software projects in which multiple hundreds of thousands of lines of code were developed .The nature of the performance engineering support required by such projects changes dramatically during the middle of the development period; failure to recognize the need for this change can result in discovery of performance shortfalls too late to correct them before the system must become operational.
Gregory Fox
ICSE1