The Object-Oriented Design Knowledge

Author(s):  
Javier Garzas ◽  
Mario Piattini

In order to establish itself as a branch of engineering, a profession must understand its accumulated knowledge. In this regard, software engineering has advanced greatly in recent years, but it still suffers from the lack of a structured classification of its knowledge. In this sense, in the field of object-oriented micro-architectural design designers have accumulated a large body of knowledge and it is still have not organized or unified. Therefore, items such as design patterns are the most popular example of accumulated knowledge, but other elements of knowledge exist such as principles, heuristics, best practices, bad smells, refactorings, and so on, which are not clearly differentiated; indeed, many are synonymous and others are just vague concepts.

Author(s):  
JAVIER GARZÁS ◽  
MARIO PIATTINI

After years of experience in object-oriented design, software engineers have accumulated a great deal of knowledge in the design and construction of object-oriented systems: important contributions to this field including principles, heuristics, lessons learned, bad smells, refactorings, and so on, with the resultant major improvements in software development. However, this large body of knowledge is still not well organized, its terminology is ambiguous, and it is very difficult to make practical use of the contributions made. In this regard, we believe it is important to define an ontology in order to structure and unify design knowledge, since a good understanding of the experience derived from practical work is critical for software engineers. This ontology could be used to improve communication between software engineers, inter-operability among designs, design re-usability, design knowledge searching and specification, software maintenance, knowledge acquisition, etc. In the ontology we incorporate knowledge specific to both domain and technology. Such an organized body of knowledge could also be used for registering and documenting design rationale issues.


Proceedings ◽  
2021 ◽  
Vol 74 (1) ◽  
pp. 13
Author(s):  
Hatice Koç ◽  
Ali Mert Erdoğan ◽  
Yousef Barjakly ◽  
Serhat Peker

Software engineering is a discipline utilizing Unified Modelling Language (UML) diagrams, which are accepted as a standard to depict object-oriented design models. UML diagrams make it easier to identify the requirements and scopes of systems and applications by providing visual models. In this manner, this study aims to systematically review the literature on UML diagram utilization in software engineering research. A comprehensive review was conducted over the last two decades, spanning from 2000 to 2019. Among several papers, 128 were selected and examined. The main findings showed that UML diagrams were mostly used for the purpose of design and modeling, and class diagrams were the most commonly used ones.


2014 ◽  
Vol 556-562 ◽  
pp. 5267-5270
Author(s):  
Tai Fa Zhang ◽  
Ya Jiang Zhang ◽  
Jun Yao

Nowadays, object-oriented design is the trend of software design patterns, and the database connection pool is one of the important research topics. The paper firstly describes the basic principle of connection pool under traditional, tomcat and hibernate modes. Based on that, a new connection pool method is proposed, and these four methods are experimentally simulated in java language at last. The comparative analysis has verified that the presented connection pool owns the optimum access time and it can greatly improve the access efficiency of database.


Author(s):  
K. Sridhar Patnaik ◽  
Itu Snigdh

Despite the rapid growth in IoT research, a general principled software engineering approach for the systematic development of IoT systems and applications is still missing. Software engineering as a discipline provides the necessary platform to carry on the underlying design, coding, implementation, as well as maintenance of such systems. UML diagrams present a visually comprehensible outlay of the construction of IoT systems. The chapter covers the modelling of IoT systems using UML diagrams. Starting with the architectural design of any IoT system to behavioral aspects is covered in this chapter using a case study of IoT-based remote patient health monitoring system. The diagrams shown in this chapter are the sample diagrams for understanding IoT-based complex systems. The chapter focuses on the work carried out by Franco Zambonelli in context of developing abstract model of an IoT system using software engineering concepts. The chapter also focus on the pioneer work carried by J. F. Peters in intelligent system design patterns for robotic devices using pattern classification.


Author(s):  
Sherri S. Frizell ◽  
Roland Hübscher

Design patterns have received considerable attention for their potential as a means of capturing and sharing design knowledge. This chapter provides a review of design pattern research and usage within education and other disciplines, summarizes the reported benefits of the approach, and examines design patterns in relation to other approaches to supporting design. Building upon this work, it argues that design patterns can capture learning design knowledge from theories and best practices to support novices in effective e-learning design. This chapter describes the authors’ work on the development of designs patterns for e-learning. It concludes with a discussion of future research for educational uses of design patterns.


2001 ◽  
Vol 59 (2) ◽  
pp. 181-196 ◽  
Author(s):  
G. Antoniol ◽  
G. Casazza ◽  
M. Di Penta ◽  
R. Fiutem

Sign in / Sign up

Export Citation Format

Share Document