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. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Michael Daskalantonakis

dblp:73/5986 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 1992
—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
Empirical software engineering · 50% Software maintenance and evolution · 50%

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

TopicWeightPapersLastEvidence papers
Empirical software engineering
software metrics
0.011992
A Practical View of Software Measurement and Implementation Experiences Within Motorola · IEEE Trans. Software Eng. 1992
Software maintenance and evolution
software process improvement
0.011992
A Practical View of Software Measurement and Implementation Experiences Within Motorola · IEEE Trans. Software Eng. 1992

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

goal/question/metric approach · 0.0
YearPublicationVenuePosition
1992 A Practical View of Software Measurement and Implementation Experiences Within Motorola
abstract
A practical view of software measurement that formed the basis for a companywide software metrics initiative within Motorola is described. A multidimensional view of measurement is provided by identifying different dimensions (e.g., metric usefulness/utility, metric types or categories, metric audiences, etc.) that were considered in this companywide metrics implementation process. The definitions of the common set of Motorola software metrics, as well as the charts used for presenting these metrics, are included. The metrics were derived using the goal/question metric approach to measurement. A distinction is made between the use of metrics for process improvement over time across projects and the use of metrics for in-process project control. Important experiences in implementing the software metrics initiative within Motorola are also included.>
Michael Daskalantonakis
IEEE Trans. Software Eng.1