Milestones in Software Engineering and Knowledge Engineering History: A Comparative Review

Abstract

We present a review of the historical evolution of software engineering, intertwining it with the history of knowledge engineering because “those who cannot remember the past are condemned to repeat it.” This retrospective represents a further step forward to understanding the current state of both types of engineerings; history has also positive experiences; some of them we would like to remember and to repeat. Two types of engineerings had parallel and divergent evolutions but following a similar pattern. We also define a set of milestones that represent a convergence or divergence of the software development methodologies. These milestones do not appear at the same time in software engineering and knowledge engineering, so lessons learned in one discipline can help in the evolution of the other one.

A Review on Ontology Development Methodologies for Developing Ontological Knowledge Representation Systems for various Domains

“…Similarly, [95] claimed that Methontology is the best among others with detailed activities for development process. Nonetheless, the methodology is not without some notable shortcomings.…”

Presenting an Approach for Conducting Knowledge Architecture within Large-Scale Organizations

“…A common engineering methodology in the scope of KM is CommonKADS [ 26 ]. CommonKADS is a comprehensive methodology which addresses all KM processes within an integrated and comprehensive structure [ 27 ]. From the viewpoint of CommonKADS, knowledge engineering is a process during which different models are created and each aspect of an individual’s knowledge can be recounted.…”

Requirements for Diagraming in the Design of Mental Health Delivery Services

“…Similarly, the use of formal drawings in engineering and science has a long history. However, a more rigorous use of diagrams in the design of business processes and complex engineering systems may be traced back to the beginning of the last century (del Aguila et al, 2014). Significant research has since been conducted into the nature, uses and the role of diagrams in the design of systems and processes in several fields including engineering design (Purcell and Gero, 1998), industrial engineering (Graham, 2008), systems engineering (Object Management Group, 2011), software engineering (Störrle and Fish, 2013;Yusuf et al, 2007) and computer science (Blackwell, 2019).…”

“…A considerable part of these efforts appears to have been devoted to the development of effective diagrammatic representational methods that facilitate a systematic approach to the design of complex systems. For instance, in software engineering, the search for an effective diagrammatic method took several decades before the development of the Unified Modelling Language (UML) in 1995 (del Aguila et al, 2014). In recent decades, several researchers have become interested in the value of diagrams and the need to understand the ways in which they are perceived and used in the design of systems and processes.…”