Identifying Architectural Problems through Prioritization of Code Smells

Vidal, Santiago; Guimarães, Everton; Oizumi, Willian; Garcia, Alessandro; Pace, Andrés Díaz; Marcos, Claudia

doi:10.1109/sbcars.2016.11

Cited by 21 publications

(39 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Finally, recent studies provide empirical evidence that certain smell types often co-occur in the software system. Consequently, the co-occurrence of di erent code smells may increase the negative e ects on each code smell the code structural quality (57,86,90). For instance, Oizumi et al (2016) observe that the co-occurrence of code smells manifest in di erent ways, such as the so-called code smell agglomerations, and may involve multiple code elements together, from di erent parts of the source code.…”

Section: Studies On Code Smellsmentioning

confidence: 99%

“…Consequently, the co-occurrence of di erent code smells may increase the negative e ects on each code smell the code structural quality (57,86,90). For instance, Oizumi et al (2016) observe that the co-occurrence of code smells manifest in di erent ways, such as the so-called code smell agglomerations, and may involve multiple code elements together, from di erent parts of the source code. Consequently, the co-occurrence of code smells makes it di cult to identify and eliminate code smells, aimed at improving the code structural quality.…”

Section: Studies On Code Smellsmentioning

confidence: 99%

See 1 more Smart Citation

To Collaborate or Not to Collaborate?: Improving the Identification of Code Smells

OLIVEIRA¹

View full text Add to dashboard Cite

Section: Studies On Code Smellsmentioning

confidence: 99%

Section: Studies On Code Smellsmentioning

confidence: 99%

To Collaborate or Not to Collaborate?: Improving the Identification of Code Smells

OLIVEIRA¹

View full text Add to dashboard Cite

“…Several studies have presented techniques based on code smells to help developers to identify design problems (28,38,39,41,47,46). Code smells have been explored by these studies due to their co-occurence with design problems (47,53,54).…”

Section: Problem Statementmentioning

confidence: 99%

“…Code smells have been explored by these studies due to their co-occurence with design problems (47,53,54). Some studies found that elements a ected by design problems tend to have code smells, i.e., code smells and design problems co-occur in these elements (38,41,46,47). Thus, they used such co-occurrence to state that code smells are consistent indicators of design problems.…”

Section: Problem Statementmentioning

confidence: 99%

“…We do not know if developers will actually consider one or multiple code smells to identify design problems, let alone if they can identify design problems using code smells. Even though some studies have showed how code smells are consistent indicators of design problems (38,41,46,47), we still have to investigate if: (i) code smells are key symptoms to identify design problems in practice, and (ii) developers are able to use them. These investigations aim to understand whether code smells su ce in helping developers to identify design problems.…”

Section: Problem Statementmentioning

confidence: 99%

See 1 more Smart Citation

Understanding How Developers Identify Design Problems in Practice

SOUSA¹

View full text Add to dashboard Cite

A critical assessment of the design issues in e‐commerce systems development

Ehikioya

Guillemot

2020

Engineering Reports

View full text Add to dashboard Cite

Designers of electronic commerce (e-commerce) transaction system applications face many challenges; some are old while others are emerging because of the emerging nature of the e-commerce domain itself. This article examines the critical design challenges at different stages of the design process of e-commerce applications. The high-level designs have a large number of new issues specific to Web applications. Among them, the security and networking problems are the most determinant for the success of the applications. At the detailed design level, the languages and the user interface are major concerns. The user interface, specific to the Web, forces designers to redefine the traditional concept of the end user for the more appropriate customer-centric concept. This is necessary to address the needs of consumers and for the survival of e-commerce businesses.In addition, we also examine issues bothering the development team and the e-commerce environment. Designers experienced in non-Web applications can be more successful at developing e-commerce applications if they address the issues we identified in this article in a creative way. K E Y W O R D Sdesign issues, e-commerce, e-commerce systems/application INTRODUCTIONThe concept of electronic commerce (e-commerce) has crystallized into a fairly well understood concept 1-7 ; its popularity and fast paced acceptance as an alternative to the brick and mortar market economic model 3,8 tend to undermine a clear understanding, and clear exposition of the characteristics, of e-commerce. Most adherents of e-commerce often focus only on the exchange of value end product 6,7 without paying close attention to, or knowing the intricacies of, the underlying transaction itself. 1,4,[9][10][11][12][13] Therefore, a proper characterization of e-commerce applications is fundamental. We focus on the design challenges in e-commerce transactions in a typical business-to-consumer (B2C) e-commerce domain, which is more popular, more widely patronized by users, and attracts a higher volume of e-commerce transactions. The B2C e-commerce includes retail transactions of products or services from businesses to individual shoppers (ie, businesses sell products or services to individual consumers). Thus, the seller is a business organization whereas the buyer is a consumer.

show abstract

Identifying Architectural Problems through Prioritization of Code Smells

Cited by 21 publications

References 15 publications

To Collaborate or Not to Collaborate?: Improving the Identification of Code Smells

To Collaborate or Not to Collaborate?: Improving the Identification of Code Smells

Understanding How Developers Identify Design Problems in Practice

A critical assessment of the design issues in e‐commerce systems development

Contact Info

Product

Resources

About