Reusable and generic design decisions for developing UML-based domain-specific languages

Hoisl, Bernhard; Sobernig, Stefan; Strembeck, Mark

doi:10.1016/j.infsof.2017.07.008

Cited by 11 publications

(2 citation statements)

References 53 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…3 list down the security issues that are usually faced during the coding phase while best practices of secure coding are listed in Column 3 of Tab. 3 [28,33,[62][63][64][65][66][67][68][69][70]…”

Section: Coding Phasementioning

confidence: 99%

Security Threat and Vulnerability Assessment and Measurement in Secure Software Development

Humayun¹,

Jhanjhi²,

Almufareh³

et al. 2022

Computers, Materials &Amp; Continua

View full text Add to dashboard Cite

Security is critical to the success of software, particularly in today's fast-paced, technology-driven environment. It ensures that data, code, and services maintain their CIA (Confidentiality, Integrity, and Availability). This is only possible if security is taken into account at all stages of the SDLC (Software Development Life Cycle). Various approaches to software quality have been developed, such as CMMI (Capability maturity model integration). However, there exists no explicit solution for incorporating security into all phases of SDLC. One of the major causes of pervasive vulnerabilities is a failure to prioritize security. Even the most proactive companies use the "patch and penetrate" strategy, in which security is accessed once the job is completed. Increased cost, time overrun, not integrating testing and input in SDLC, usage of third-party tools and components, and lack of knowledge are all reasons for not paying attention to the security angle during the SDLC, despite the fact that secure software development is essential for business continuity and survival in today's ICT world. There is a need to implement best practices in SDLC to address security at all levels. To fill this gap, we have provided a detailed overview of secure software development practices while taking care of project costs and deadlines. We proposed a secure SDLC framework based on the identified practices, which integrates the best security practices in various SDLC phases. A mathematical model is used to validate the proposed framework. A case study and findings show that the proposed system aids in the integration of security best practices into the overall SDLC, resulting in more secure applications.

show abstract

Section: Coding Phasementioning

confidence: 99%

Security Threat and Vulnerability Assessment and Measurement in Secure Software Development

Humayun¹,

Jhanjhi²,

Almufareh³

et al. 2022

Computers, Materials &Amp; Continua

View full text Add to dashboard Cite

show abstract

“…Eclipse is an open-source tool that provides an approachable environment, a GUI, friendly editors [ 82 ], and a drag-and-drop facility. This tool supports the design and the reusability [ 83 ] of all the UML diagrams.…”

Section: Uml Profilingmentioning

confidence: 99%

Modeling and verification of authentication threats mitigation in aspect-oriented mal sequence woven model

2022

View full text Add to dashboard Cite

The modeling of security threats is equally important as the modeling of functional requirements at the design stage of software engineering. However, unlike functional requirements modeling, the modeling of security threats is neglected, which consequently introduces software defects during the early stages of software engineering. Hence, there is a need to mitigate these threats at the design stage. Security threats, specifically authentication threats, crosscut other functional and non-functional requirements when modeled using the object-oriented paradigm. This not only makes the design complex but also results in tangling and scattering problems. We therefore model authentication threats using the aspect-oriented modeling (AOM) technique since it separates crosscutting concerns and localizes them as separate units called aspects. Our main research aim is to remove scattering and tangling in security threats modeling using all the core features of the aspect-oriented technique. In this paper, we propose a research approach to model security threats and their mitigation in mal sequence diagram. Using this approach, our contribution makes a clear difference from previous work. Our first contribution is the modeling of authentication threats in the mal sequence diagram using the security profile and AOM profile. Our second contribution is the mathematical verification of the aspect-oriented mal sequence woven model in terms of correctness and completeness. Using the proposed approach, the scattering and tangling from the resultant woven model are successfully removed at the design stage. Thus, the complexity of models and the time and effort required for future modifications of design models are reduced.

show abstract

DSL as Variable Software

Sobernig

2020

Variable Domain-Specific Software Languages With DjDSL

View full text Add to dashboard Cite

Reusable and generic design decisions for developing UML-based domain-specific languages

Cited by 11 publications

References 53 publications

Security Threat and Vulnerability Assessment and Measurement in Secure Software Development

Security Threat and Vulnerability Assessment and Measurement in Secure Software Development

Modeling and verification of authentication threats mitigation in aspect-oriented mal sequence woven model

DSL as Variable Software

Contact Info

Product

Resources

About