One of the most significant impediments to the long-term maintainability of software applications is code smells. Keeping up with the best coding practices can be difficult for software developers, which might lead to performance throttling or code maintenance concerns. As a result, it is imperative that large applications be regularly monitored for performance issues and code smells, so that these issues can be corrected promptly. Resolving code smells in software systems can be done in a variety of ways, but doing so all at once would be prohibitively expensive and can be out of budget. Prioritizing these solutions are therefore critical. The majority of current research prioritizes code smells according to the type of smell they cause. This method, however, is not sufficient because of a lack of knowledge regarding the frequency of code usage and code changeability behavior. Even the most complex programs have some components that are more important than others. Maintaining the functionality of certain parts is essential since they are often used. Identifying and correcting code smells in places that are frequently utilized and subject to rapid change should take precedence over other code smells. A novel strategy is proposed for finding frequently used and change-prone areas in a codebase by combining business logic, heat map information, and commit history analysis in this study. It examines the codebase, commits, and log files of Java applications to identify business processes, heat map graphs, and severity levels of various types of code smells and their commit history. This is done in order to present a comprehensive, efficient, and resource-friendly technique for identifying and prioritizing performance throttling with also handling code maintenance concerns.

/pdf/code-smell-prioritization-with-business-process-mining-and-2hsr175r.pdf

Code Smell Prioritization with Business Process Mining and Static Code Analysis: A Case Study

Data science continues to provide state-of-the-art disruptive breakthroughs to the cybersecurity research business in order to preserve cyberspace for seamless possibilities. While various systematic literature reviews attempt to document these innovative techniques and approaches in order to inspire future research directions, semantic relation extraction’s promises have not been utilized in cybersecurity data science reviews, narrowing existing reviews to the bother-line of research questions. However, in this study, a network of mention approach is used to evaluate semantic relationships in data science studies for cybersecurity using the degree of centrality as a metric. To generate edges linking research nodes with existing unanimity in their research method, a 6-number semantic relation threshold is used. The experimental outcome returned a book publishing as research after analyzing 38 original studies.

Semantic relation evaluation of data science articles using network of mention

Organizations use Role-Based Access Control (RBAC) to protect computer-based resources from unauthorized access. There has been considerable work on formally specifying RBAC policies but there is still a need for RBAC policy specification techniques that can be integrated into software design methods. This paper describes a method for incorporating specifications of RBAC policies into UML design models. Reusable RBAC policies are specified as patterns and are expressed using UML template diagrams. Incorporating RBAC policies into an application specific model involves instantiating the patterns and composing the instantiations with the model. The method also includes a technique for specifying patterns of RBAC violations. Developers can use the patterns to identify policy violations in their models. The method is illustrated using a small banking application.

Modeling Role-Based Access Control using parameterized UML models

: UMLsec is an extended UML-based secure modelling profile. It has been applied at the phase of the software design and architecture. Although it appeared over two decades ago and been integrated into some tools, how extensively it has been adopted or used by the software security community is questionable. This paper employs social science methodologies to fill this gap. The contribution of this study is to find the reasons affecting the UMLsec adoption by software practitioners and researchers and their proposals to increase this adoption. As a result, only 13% of the sample uses UMLsec. In addition, four problems preventing the use of UMLsec, (1) using a pattern-driven security methodology rather than UMLsec (2) agile supportability; agile process reduces the design and architecture documentation including UML diagram (3) UMLsec standardization and tooling is still questionable (4) the awareness and training on use UMLsec are weak. The study also presented proposals for UMLsec improvement, in particular (1) simplifying the notations to apply UMLsec in many fields (2) raising awareness (e.g., demonstrating practical examples to the interested people). The paper discussed the threats to the validity of the study and suggested open issues for future research.

An Exploratory Study of Why UMLsec Is Not Adopted

Information system drives every aspect of human endeavor, and it is a major stakeholder in human existence. Systems with poor modeling suffer a lot from poor implementation down to poor performance due to lack of critical subjection and testing. Software modeling is, therefore, of paramount importance in order to achieve a reliable system. There has been a lot of works done in software modeling, and eventually, the Universal Modeling Language was formulated to create a standard for software modeling. Although there have been some development or modeling tools that can be used to model a software system and the design then converted to software codes that can then be perfected, none of these tools has considered security and integrated as a single tool. Therefore, this paper focuses on building an integrated system (all-encompassing system) for building UMLsec-based modeled systems that will convert UML diagrams to code. The system integrates Eclipse Mars incorporated with Papyrus modeling plug-ins and Eclipse Kepler with Java EE incorporated with CARiSMA plug-ins. These four tools were integrated together by an executable application built with NetBeans. The system was tested by modeling an e-government system from the class diagram to analysis and code generation.

Olutimi Onilede

Papers

From Modeling to Code Generation: An Enhanced and Integrated Approach