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

Mikhail Perepletchikov

dblp:86/5497 · DBLP profile ↗
← Back
2ranked-venue papers
2as first author
0since 2021 · last 2011
0000-0002-4029-7908ORCID · verified

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

Software engineering, systems software and programming languages · 2 · 2 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
2 papers
Empirical software engineering · 50% Services computing and microservices · 22% Software maintenance and evolution · 22%

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

TopicWeightPapersLastEvidence papers
Empirical software engineering
controlled experiment
0.112011
A Controlled Experiment for Evaluating the Impact of Coupling on the Maintainability of Service-Oriented Software · IEEE Trans. Software Eng. 2011
Empirical software engineering › software metrics
coupling metrics
0.112011
A Controlled Experiment for Evaluating the Impact of Coupling on the Maintainability of Service-Oriented Software · IEEE Trans. Software Eng. 2011
Services computing and microservices › service-oriented architecture
service-oriented application
0.112010
The Impact of Service Cohesion on the Analyzability of Service-Oriented Software · IEEE Trans. Serv. Comput. 2010
Requirements engineering and software design › distributed system design
service-oriented design
0.012011
A Controlled Experiment for Evaluating the Impact of Coupling on the Maintainability of Service-Oriented Software · IEEE Trans. Software Eng. 2011

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

controlled experiment · 0.2coupling metrics · 0.1software metrics · 0.1
YearPublicationVenuePosition
2011 A Controlled Experiment for Evaluating the Impact of Coupling on the Maintainability of Service-Oriented Software
abstract
One of the goals of Service-Oriented Computing (SOC) is to improve software maintainability as businesses become more agile, and thus underlying processes and rules change more frequently. This paper presents a controlled experiment examining the relationship between coupling in service-oriented designs, as measured using a recently proposed suite of SOC-specific coupling metrics and software maintainability in terms of the specific subcharacteristics of analyzability, changeability, and stability. The results indicate a statistically significant causal relationship between the investigated coupling metrics and the maintainability of service-oriented software. As such, the investigated metrics can facilitate coupling related design decisions with the aim of producing more maintainable service-oriented software products.
Mikhail Perepletchikov, Caspar Ryan
IEEE Trans. Software Eng.1
2010 The Impact of Service Cohesion on the Analyzability of Service-Oriented Software
abstract
Service-Oriented Computing (SOC) is intended to improve software maintainability as businesses become more agile and underlying processes and rules change more frequently. However, to date, the impact of service cohesion on the analyzability subcharacteristic of maintainability has not been rigorously studied. Consequently, this paper extends existing notions of cohesion in the Procedural and OO paradigms in order to account for the unique characteristics of SOC, thereby supporting the derivation of design-level software metrics for objectively quantifying the degree of service cohesion. The metrics are theoretically validated, and an initial empirical evaluation using a small-scale controlled study suggests that the proposed metrics could help predict analyzability early in the Software Development Life Cycle. If future industrial studies confirm these findings, the practical applicability of such metrics is to support the development of service-oriented systems that can be analyzed, and thus maintained, more easily. In addition, such metrics could help identify design problems in existing systems.
Mikhail Perepletchikov, Caspar Ryan, Zahir Tari
IEEE Trans. Serv. Comput.1