Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data.

L. David Balk

dblp:44/3666 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 2000
—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 · 77% Requirements engineering and software design · 23%

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution › software integration
COTS integration
0.012000
PPT: a COTS integration case study · ICSE 2000
Requirements engineering and software design
software process
0.012000
PPT: a COTS integration case study · ICSE 2000

Methods — techniques the papers use, named apart from their topics

case study · 0.0
YearPublicationVenuePosition
2000 PPT: a COTS integration case study
abstract
T. Rowe Price Investment Technologies built The Product and Project Tracking System (PPT) to reduce the human resources needed to track and forecast Information Technology projects. Instead of developing or purchasing a new system, the need was met by integrating Commercial-off-the-Shelf (COTS) products already used and licensed by the company. The conclusion can be made that this approach reduces development costs while providing more flexibility than a single vendor solution. This paper described the process used and issues encountered in building a system from software products generally intended for stand-alone applications. It discusses the rationale behind the system, the choice of products, the software engineering process used, the handling of changes, and modifications made in business practice. A discussion will be made of the initial Return on Investment and ongoing support requirements.
L. David Balk, Ann Kedia
ICSE1