The Object-Oriented Design Knowledge

Garzás, Javier; Piattini, Mario

doi:10.4018/9781591408963.ch001

Cited by 3 publications

(7 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Refactoring is an important aspect of software evolution since it aims to increase the quality of software [56]. It is defined as "a change made to the internal structure of a program to make it easy to understand and cheap to modify without changing its observable behavior" [15].…”

Section: Refactoringmentioning

confidence: 99%

“…The second is ensuring that restructuring the program does not change its functional behaviour. There are two types of refactoring [56]: code refactoring, and design refactoring.…”

Section: Refactoringmentioning

confidence: 99%

“…Refactoring is an important aspect of software evolution since it aims to increase the quality of software [56]. However, its impact on software security was hardly mentioned or studied until recently [35].…”

Section: A Refactoring and Securitymentioning

confidence: 99%

“…The second is ensuring that restructuring the program does not change its functional behaviour. There are two types of refactoring [56]: code refactoring, and design refactoring.Since refactoring steps may change a program or design's quality, including its security quality, refactoring is highly relevant to security metrics and can provide a way of validating their correctness. "Good" refactoring steps should be detectable by our security metrics.…”

mentioning

confidence: 99%

See 3 more Smart Citations

Developing Secure Systems: A Comparative Study of Existing Methodologies

Alshammari¹,

Fidge²,

Corney³

2016

LNSE

View full text Add to dashboard Cite

Abstract-With the increasing demand for developing high-quality and more reliable systems, the process of developing trustworthy computer software is a challenging one. In this paper, we review various approaches to producing more secure systems. This includes established general principles for designing secure systems. It also provides an introduction to general software quality measurements including existing software security metrics. This paper also includes a comparison of the various security metrics for developing secure systems (i.e., architectural, design, and code-level metrics). Lastly, the paper examines the approach of refactoring, illustrates its objectives, and shows how refactoring is generally used for enhancing the quality of existing programs from the perspective of information security. At the end of this paper, we provide a discussion of these three approaches and how they can be used to provide guidance for future secure software development processes.Index Terms-Security design principles, object-orientation, security metrics, secure refactoring. I. INTRODUCTIONMuch existing software is designed with poor consideration of information security which makes it vulnerable to many threats including malicious attacks [1]. Software patches are one of the suggested solutions for many of the security attacks facing software [1] but they are expensive to develop and deploy and do not solve basic design weaknesses in the program code. Another solution to achieve a secure product is by following a trustworthy security process [2]. Security processes, in general, consider many aspects of system design, coding, testing, and auditing [2] (e.g., international security standards such as the Common Criteria [3] or the Trusted Computer Criteria [4]).Another common approach for achieving a secure computer program is by following certain coding guidelines which focus on the level of individual program statements (e.g., to avoid/detect buffer overflows [5]). However, these solutions do not always work effectively and may, in general, even introduce new vulnerabilities to existing software [1]. Adding security features to systems after they have been developed and deployed has been a major cause of many system vulnerabilities [6]. Therefore, applying security principles from the early stages of the software development life cycle (SDLC) would be a better solution [1] and allow a Manuscript received October 10, 2014; revised January 5, 2015. Bandar M. Alshammari is with Aljouf University, Saudi Arabia (e-mail: bmshammeri@ju.edu.sa).Colin J. Fidge is with Queensland University of Technology, Australia (e-mail: c.fidge@qut.edu.au).Diane Corney is with Oracle, Australia (e-mail: diane.corney@oracle.com).more coherent system to be produced [6].Developing a secure system requires a good overall design which takes security into account from the beginning. A suggested methodology by Fernandez [1] incorporates security principles into each stage of the SDLC. It makes sure that each stage complies with these principles th...

show abstract

Section: Refactoringmentioning

confidence: 99%

“…The second is ensuring that restructuring the program does not change its functional behaviour. There are two types of refactoring [56]: code refactoring, and design refactoring.…”

Section: Refactoringmentioning

confidence: 99%

Section: A Refactoring and Securitymentioning

confidence: 99%

mentioning

confidence: 99%

See 2 more Smart Citations

Developing Secure Systems: A Comparative Study of Existing Methodologies

Alshammari¹,

Fidge²,

Corney³

2016

LNSE

View full text Add to dashboard Cite

show abstract

“…We developed a component based solution to satisfy the requirements as well as the general software engineering demands of reusability, maintainability and extensibility (Garzas and Piattini, 2006). The basic components of PaDU are shown in Figure 1.…”

Section: Its Purpose Requirements and Designmentioning

confidence: 99%

Fostering Continuous User Participation by Embedding a Communication Support Tool in User Interfaces

Yetim¹,

Draxler²,

Stevens³

et al. 2012

THCI

View full text Add to dashboard Cite

This paper critically reviews previous IS literature on user participation and argues that the literature is mainly empirically or normatively oriented and lacks design research on developing system prototypes in order to foster continuous user participation. It then contributes to the current research by introducing a system prototype, a communication tool that enables users to participate while using their application systems in their work contexts. The prototype provides different communication channels for supporting user-designer communications and knowledge sharing among users with respect to application usage. When integrated in the interface of an application system, the tool can help to adapt and redesign the application. The initial evaluation of the communication tool within the context of an application system indicates its usefulness and usability.

show abstract

An Adaptive Translation of Class Diagram to Relational Database

Kuskorn

Lekcharoen

2009

2009 International Conference on Information and Multimedia Technology

View full text Add to dashboard Cite

The purpose of this research is to propose an algorithm for translating class diagram into relational database. At first, class diagram is converter into Java source code. The algorithm analyses it by using the keywords of "class", "attribute", and "relation" and then generates relational database. It shows that this algorithm could reduce error, cost and time of translation. It is still needed for further study in case of many-to-many relationships of class diagram.

show abstract

The Object-Oriented Design Knowledge

Cited by 3 publications

References 0 publications

Developing Secure Systems: A Comparative Study of Existing Methodologies

Developing Secure Systems: A Comparative Study of Existing Methodologies

Fostering Continuous User Participation by Embedding a Communication Support Tool in User Interfaces

An Adaptive Translation of Class Diagram to Relational Database

Contact Info

Product

Resources

About