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.

D. J. Karkaria

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

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

Computer networks · 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
Empirical software engineering · 61% Software maintenance and evolution · 30% Software testing · 9%

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

TopicWeightPapersLastEvidence papers
Empirical software engineering › software metrics
measurement validation
0.011994
Software product assessment · IEEE J. Sel. Areas Commun. 1994
Empirical software engineering
software metrics
0.011994
Software product assessment · IEEE J. Sel. Areas Commun. 1994
Software testing
software reliability
0.011994
Software product assessment · IEEE J. Sel. Areas Commun. 1994

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

source code measurement · 0.0COSMOS tool · 0.0
YearPublicationVenuePosition
1994 Software product assessment
abstract
Every year, British Telecom's (BT's) level of investment in software is growing. Not only is the level of investment high, but there is a great deal of reliance on this software to retain BT's competitive edge against stiff competition. The software is, therefore, likely to be working in a commercially critical environment where the cost of failure is high both in terms of lost revenue and good will. Techniques are available, at various levels of maturity, which can help to provide added assurance against software failure. The first part of the paper relates specifically to the ESPRIT COSMOS project and work within BT on validating measures gathered using the COSMOS tool at the source code level. The second part of the paper describes how the results of this project fit within the wider context of software assessment, and outlines some of the techniques that are currently being used within BT or are being developed. The paper concludes with a brief description of what may be viable in the next few years.>
D. J. Karkaria, Mark T. Norris, A. D. Pengelly
IEEE J. Sel. Areas Commun.1