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

Milton Silva

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

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution
software process improvement
0.011986
Introducing Software Quality Engineering into a Telecommunications Development Environment · IEEE J. Sel. Areas Commun. 1986
Empirical software engineering › practitioner studies
industrial experience report
0.011986
Introducing Software Quality Engineering into a Telecommunications Development Environment · IEEE J. Sel. Areas Commun. 1986
YearPublicationVenuePosition
1986 Introducing Software Quality Engineering into a Telecommunications Development Environment
abstract
This paper summarizes the author's experience in introducing software quality engineering methodology into a telecomm system design organization. The discussion covers: how software quality was marketed and managed as a profit maker and time saver, the multiphase introduction timetable for diverse quality concepts, criteria for hiring and training staff, and the operating guidelines for the Quality Group. In less than two years, a quality-oriented development culture has been established. Substantially shorter development times, and lower design costs per line of code are being routinely attained while guaranteeing a high level of operational reliability at product introduction.
Milton Silva
IEEE J. Sel. Areas Commun.1