Safety-critical systems manufacturers have the duty of care, i.e., they should take correct steps while performing acts that could foreseeably harm others. Commonly, industry standards prescribe reasonable steps in their process requirements, which regulatory bodies trust. Manufacturers perform careful documentation of compliance with each requirement to show that they act under acceptable criteria. To facilitate this task, a safety-centered planning-time framework, called ACCEPT, has been proposed. Based on compliance-by-design, ACCEPT capabilities permit to design Compliance-aware Engineering Process Plans, (...) which are able to show the planning-time allocation of standard demands, i.e., if the elements set down by the standard requirements are present at given points in the engineering process plan. In this paper, we perform a case study to understand if the ACCEPT produced models could support the planning of space software engineering processes. Space software is safety and mission-critical, and it is often the result of industrial cooperation. Such cooperation is coordinated through compliance with relevant standards. In the European context, ECSS-E-ST-40C is the de-facto standard for space software production. The planning of processes in compliance with project-specific ECSS-E-ST-40C applicable requirements is mandatory during contractual agreements. Our analysis is based on qualitative criteria targeting the effort dictated by task demands required to create a CaEPP for software development with ACCEPT. Initial observations show that the effort required to model compliance and processes artifacts is significant. However, such an effort pays off in the long term since models are, to some extend, reusable and flexible. The coverage level of the models is also analyzed based on design decisions. In our opinion, such a level is adequate since it responds to the information needs required by the ECSS-E-ST-40C framework. (shrink)

Unlike in most professions, a license is not required to work as a software engineer. This essay argues software engineers, because they now render an essential service to society, should be licensed in a process that resembles licensing for doctors, lawyers and teachers.

The purpose of this article is to propose an ethical framework for software engineers that connects software developers’ ethical responsibilities directly to their professional standards. The implementation of such an ethical framework can overcome the traditional dichotomy between professional skills and ethical skills, which plagues the engineering professions, by proposing an approach to the fundamental tasks of the practitioner, i.e., software development, in which the professional standards are intrinsically connected to the ethical responsibilities. In so doing, (...) the ethical framework improves the practitioner’s professionalism and ethics. We call this approach Ethical-Driven Software Development, as an approach to software development. EDSD manifests the advantages of an ethical framework as an alternative to the all too familiar approach in professional ethics that advocates “stand-alone codes of ethics”. We believe that one outcome of this synergy between professional and ethical skills is simply better engineers. Moreover, since there are often different software solutions, which the engineer can provide to an issue at stake, the ethical framework provides a guiding principle, within the process of software development, that helps the engineer evaluate the advantages and disadvantages of different software solutions. It does not and cannot affect the end-product in and of-itself. However, it can and should, make the software engineer more conscious and aware of the ethical ramifications of certain engineering decisions within the process. (shrink)

Experiments in computing share many characteristics with the traditional experimental method, but also present significant differences from a practical perspective, due to their aim at producing software artifacts and the central role played by human actors and organizations involved in the software development process. By analyzing some of the most significant experiments in the subfield of software engineering, we aim at showing how the conceptual framework that supports experimental methodology in this context needs an extension (...) in a socio-technical perspective. (shrink)

Over the past four decades, software engineering has emerged as a discipline in its own right, though it has roots both in computer science and in classical engineering. Its philosophical foundations and premises are not yet well understood. In recent times, members of the software engineering community have started to search for such foundations. In particular, the philosophies of Kuhn and Popper have been used by philosophically-minded software engineers in search of a deeper understanding (...) of their discipline. It seems, however, that professional philosophers of science are not yet aware of this new discourse within the field of software engineering. Therefore, this article aims to reflect critically upon recent software engineers’ attempts towards a philosophy of software engineering and to introduce our own philosophical thoughts in this context. Finally, we invite the professional philosophers of science to participate in this interesting new discourse. (shrink)

Online user feedback is principally used as an information source for evaluating customers’ satisfaction for a given goods, service or software application. The increasing attitude of people towards sharing comments through the social media is making online user feedback a resource containing different types of valuable information. The huge amount of available user feedback has drawn the attention of researchers from different fields. For instance, data mining techniques have been developed to enable information extraction for different purposes, or the (...) use of social techniques for involving users in the innovation of services and processes. Specifically, current research and technological efforts are put into the definition of platforms to gather and/or analyze multi-modal feedback. But we believe that the understanding of the type of concepts instantiated as information contained in user feedback would be beneficial to define new methods for its better exploitation. In our research, we focus on online explicit user feedback that can be considered as a powerful means for user-driven evolution of software services and applications. Up to our knowledge, a conceptualization of user feedback is still missing. With the purpose of contributing to fill up this gap we propose an ontology, for explicit online user feedback that is founded on a foundational ontology and has been proposed to describe artifacts and processes in software engineering. Our contribution in this paper concerns a novel user feedback ontology founded on a Unified Foundational Ontology (UFO) that supports the description of analysis processes of user feedback in software engineering. We describe the ontology together with an evaluation of its quality, and discuss some application scenarios. (shrink)

Conceptual modeling of a portion of the world is a necessary prerequisite to set the stage and define software system boundaries. In this context, one of the challenges is to provide a unified framework to create a comprehensive representation of the targeted domain. According to many researchers, conceptual model (CM) development is a hard task, and system requirements are difficult to collect, causing many miscommunication problems. Accordingly, CMs require more than modeling ability alone: they first require an understanding of (...) the targeted domain that the model attempts to represent. Accordingly, a preconceptual modeling (pre-CM) stage is intended to address ontological issues before typical CM development is initiated. It involves defining a portion of reality when entities and processes are differentiated and integrated as unified wholes. This pre-CM phase forms the focus of research in this paper. The purpose is not show how to model; rather, it is to demonstrate how to establish a metaphysical basis of the involved portion of reality. To demonstrate such a venture, we employ the so-called thinging machine (TM) modeling that has been proposed as a high-level CM. A TM model integrates staticity and dynamism grounded in a fundamental construct called a thimac (things/machine). It involves two modes of reality, existence (events) and subsistence (regions: roughly, specifications of things and processes). Currently, the dominant approach in CM has evolved to limit its scope of application to develop ontological categorization (types of things). In contrast, advocates of TM modeling have pursued a broader metaphysical study of the nature of the domain’s things and processes beyond categorization. In the TM approach, pre-CM metaphysics is viewed as a part and parcel of CM itself. The general research problem is how to map TM constructs to what is out there in the targeted domain. Discussions involve the nature of thimacs (things and processes) and subsistence and existence as they are superimposed over each other in reality. Specifically, we make two claims, (i) the perceptibility of regions as a phenomenon and (ii) the distinctiveness of existence as a construct for events. The results contribute to further the understanding of TM modeling in addition to introducing some metaphysical insights. (shrink)

Software systems play an ever more important role in our lives and software engineers and their companies find themselves in a position where they are held responsible for ethical issues that may arise. In this paper, we try to disentangle ethical considerations that can be performed at the level of the software engineer from those that belong in the wider domain of business ethics. The handling of ethical problems that fall into the responsibility of the engineer has (...) traditionally been addressed by the publication of Codes of Ethics and Conduct. We argue that these Codes are barely able to provide normative orientation in software development. The main contribution of this paper is, thus, to analyze the normative features of Codes of Ethics in software engineering and to explicate how their value-based approach might prevent their usefulness from a normative perspective. Codes of Conduct cannot replace ethical deliberation because they do not and cannot offer guidance because of their underdetermined nature. This lack of orientation, we argue, triggers reactive behavior such as “cherry-picking,” “risk of indifference,” “ex-post orientation,” and the “desire to rely on gut feeling.” In the light of this, we propose to implement ethical deliberation within software development teams as a way out. (shrink)

Program comprehension is an essential part of software engineering. The paper describes the constructivist theory of comprehension, a process based on assimilation and accommodation of knowledge. Assimilation means that the new facts are either added to the existing knowledge or rejected. Accommodation means that the existing knowledge is reorganized in order to absorb new facts. These processes are illustrated by case studies of knowledge-level reengineering of a legacy program and of incremental change. In both cases, we constructed (...) preliminary knowledge from the program documentation, and then adjusted it by comprehending the actual code. The case studies supported constructivism as a suitable theory of program comprehension. (shrink)

Modern software is infested with flaws having information security aspects. Pervasive computing has made us and our society vulnerable. However, software developers do not fully comprehend what is at stake when faulty software is produced and flaws causing security vulnerabilites are discovered. To address this problem, the main actors involved with software vulnerability processes and the relevant roles inside these groups are identified. This categorisation is illustrated through a fictional case study, which is scrutinised in the (...) light of ethical codes of professional software engineers and common principles of responsibility attribution. The focus of our analysis is on the acute handling of discovered vulnerabilities in software, including reporting, correcting and disclosing these vulnerabilities. We recognise a need for guidelines and mechanisms to facilitate further improvement in resolving processes leading to and in handling software vulnerabilities. In the spirit of disclosive ethics we call for further studies of the complex issues involved. (shrink)

Digital artifacts often fail to perform as expected. It has recently been argued that this should not be analyzed as software malfunctioning. Rather, every case that is not the result of hardware failures would be due to design errors. This claim, which hinges on the notion of ‘implementation’, highlights a potential fundamental difference between software and other technical artifacts. It also implies that software engineers have more extensive responsibilities than creators of other artifacts. After reconstructing the argument, (...) we show that it rests on two presuppositions regarding the nature of software and the activities of its creators, which we call ‘complete control’ and ‘self-containedness’. Software is taken to be a self-contained unit through which the software engineer exerts complete control over a machine’s behavior. These two presuppositions as well as the usage of implementation and strong claims regarding responsibility can be found throughout the literature on software engineering. Still, we argue that the presuppositions are untenable in light of current practices. For one thing, software engineers cannot exert complete control because software has become too complex for any technique to reliably locate every fault in it. For another, the creation and running of software are nowadays heavily mediated processes involving many agential activities. As a result, the performance of digital artifacts may vary, often in undesirable ways, without either hardware failures or design errors. This undermines the conclusion that software cannot malfunction, while also revealing the complications in developing a metaphysical account of software that fits contemporary practices. (shrink)

The distinction between the modeling of information and the modeling of data in the creation of automated systems has historically been important because the development tools available to programmers have been wedded to machine oriented data types and processes. However, advances in software engineering, particularly the move toward data abstraction in software design, allow activities reasonably described as information modeling to be performed in the software creation process. An examination of the evolution of programming languages (...) and development of general programming paradigms, including object-oriented design and implementation, suggests that while data modeling will necessarily continue to be a programmer's concern, more and more of the programming process itself is coming to be characterized by information modeling activities. (shrink)

Some of the fundamental activities of the software development process are related to the discipline of Requirements Engineering. Their objectives are to discover, analyze, document, and verify the system’s requirements. The requirements are the conditions or capabilities that software needs to have or fulfill to meet its users’ needs, and problems in its identification can mean the failure of a software project. This study is part of the research that is being developed to propose a (...) model based on Know­ledge Organization Systems to be used in the Requirements engineering process. This article aims to present the results of an analysis on a set of Know­ledge Organization Systems to identify whether they are likely to be applied in the Requirements engineering process and identify at which stage of this process each one of them can be implemented. The Know­ledge Organization Systems analyzed were the authority files, gazetteers, glossaries, subject headings, classification systems, thesauri, semantic networks, and ontologies. Based on the results obtained, it was possible to conclude that the Know­ledge Organization Systems analyzed can be used in the Requirements engineering process and, consequently, contribute to increasing the software requirements’ quality. (shrink)

This paper presents an experience in developing professional ethics by an approach that integrates knowledge, teaching methodologies and assessment coherently. It has been implemented for students in both the Software Engineering and Computer Engineering degree programs of the Technical University of Madrid, in which professional ethics is studied as a part of a required course. Our contribution of this paper is a model for formative assessment that clarifies the learning goals, enhances the results, simplifies the scoring and (...) can be replicated in other contexts. A quasi-experimental study that involves many of the students of the required course has been developed. To test the effectiveness of the teaching process, the analysis of ethical dilemmas and the use of deontological codes have been integrated, and a scoring rubric has been designed. Currently, this model is also being used to develop skills related to social responsibility and sustainability for undergraduate and postgraduate students of diverse academic context. (shrink)

Simulation software used for modeling has become as ubiquitous as computers themselves. Despite growing reliance on simulation in educational and workplace settings, users encounter frustration in using simulation software programs. The authors conducted a study with 26 engineering students and interviewed them about their experience learning the simulation software Arena for optimization modeling. These students experienced frustration with the process of learning to “think” like the simulation software. Students explained their difficulty with learning the (...) software in a way that implied human dialogue with a machine and negotiation with Arena in an attempt to overcome this frustration. Rather than being gender specific, frustrations were experienced by most male and female students equally, specifically those who held a perception of difference between human and machine “thinking.” The authors contend that communication difficulty with the embedded assumptions of the software is the source of frustration rather than deficiencies of users. (shrink)

This paper has a dual character, combining a philosophical ontological exploration with a conceptual modeling approach in systems and software engineering. Such duality is already practiced in software engineering, in which the current dominant modeling thesis is object orientation. This work embraces an anti-thesis that centers solely on the process rather than emphasizing the object. The approach is called occurrence-only modeling, in which an occurrence means an event or process where a process is (...) defined as an orchestrated net of events that form a semantical whole. In contrast to object orientation, in this occurrence-only modeling objects are nothing more than long events. We apply this paradigm to (1) a UML/BPMN inventory system in simulation engineering and (2) an event-based system that represents medical occurrences that occur on a timeline. The aim of such a venture is to enhance the field of conceptual modeling by adding yet a new alternative methodology and clarifying differences among approaches. Conceptual modeling’s importance has been recognized in many research areas. An active research community in simulation engineering demonstrates the growing interest in conceptual modeling. In the clinical domains, temporal information elucidates the occurrence of medical events (e.g., visits, laboratory tests). These applications give an opportunity to propose a new approach that includes (a) a Stoic ontology that has two types of being, existence and subsistence; (b) Thinging machines that limit activities to five generic actions; and (c) Lupascian logic, which handles negative events. With such a study, we aim to substantiate the assertion that the “occurrence only” approach is a genuine philosophical base for conceptual modeling. The results in this paper seem to support such a claim. (shrink)

Reverse engineering is such common engineering technique that many of us have contact it daily, even if we are not aware of it. When we use an aftermarket product, it is likely to be a reverse engineered version of the manufacturer’s original. When we click to accept the conditions governing their use of a piece of software, we agree not to reverse engineer it. The process of reverse engineering starts with an artefact for which the (...) relevant functions are known. Reverse engineering then creates a different artefact - not a copy - that has the relevant functions of the original. An engineer designing an aftermarket mobile phone charger would identify the physical and electrical properties of the charger made by the original equipment manufacturer and create a new charger using different components that will plug into the phone and charge it in the same way as the original. In earlier chapters we saw how when Thomas Edison set to work on a new invention, he often started with functions it should achieve and worked to create an invention that fulfilled those functions. Reverse engineering reverses this process, starting with a finished artefact and creating another that fulfils the same functions. This chapter will apply concepts developed in earlier chapters to reverse engineering and to the use of the term reverse engineering in the biological sciences. (shrink)

Over the past 50 years, Nelson algebras have been extensively studied by distinguished scholars as the algebraic counterpart of Nelson's constructive logic with strong negation. Despite these studies, a comprehensive survey of the topic is currently lacking, and the theory of Nelson algebras remains largely unknown to most logicians. This paper aims to fill this gap by focussing on the essential developments in the field over the past two decades. Additionally, we explore generalisations of Nelson algebras, such as N4-lattices which (...) correspond to the paraconsistent version of Nelson's logic, as well as their applications to other areas of interest to logicians, such as duality and rough set theory. A general representation theorem states that each Nelson algebra is isomorphic to a subalgebra of a rough set-based Nelson algebra induced by a quasiorder. Furthermore, a formula is a theorem of Nelson logic if and only if it is valid in every finite Nelson algebra induced by a quasiorder. (shrink)

In the context of technology development and systems engineering, knowledge is typically treated as a complex information structure. In this view, knowledge can be stored in highly sophisticated data systems and processed by explicitly intelligent, software-based technologies. This paper argues that the current emphasis upon knowledge as information (or even data) is based upon a form of rationalism which is inappropriate for any comprehensive treatment of knowledge in the context of human-centred systems thinking. A human-centred perspective requires us (...) to treat knowledge in human terms. The paper sets out the particular importance of tacit knowledge in this regard. It sets out two case studies which reveal the critical importance of a careful treatment of tacit knowledge for success in two complex, technology-driven projects. (shrink)

While the issue of standards has received attention from analysts in science and technology studies, this attention has tended to focus on either units of measurement or compatibility standards. Much less attention has been devoted to equally important standards of practice. These are the procedural or process standards which govern how technologists go about designing and constructing artifacts. Such standards have a substantial documented history in the form of engineering codes of practice. As the embodiment of judgments rendered (...) by a particular community of technological practi tioners, these standards both reflect and shape the exercise of practitioner judgment. This article explores both these functions through examples drawn from structural and software engineering. These examples yield insights regarding both the role of formal procedural standards in technological practice and the unusual nature of software technology. (shrink)

Automated software engineering has attracted a large amount of research efforts. The use of object-oriented methods for software systems development has made it necessary to develop approaches that automate the construction of different Unified Modeling Language models in a semiautomated approach from textual user requirements. UML use case models represent an essential artifact that provides a perspective of the system under analysis or development. The development of such use case models is very crucial in an object-oriented development (...) method. The main principles used in obtaining these models are described. A natural language processing tool is used to parse different statements of the user requirements written in Arabic to obtain lists of nouns, noun phrases, verbs, verb phrases, etc., that aid in finding potential actors and use cases. A set of steps that represent our approach for constructing a use case model are presented. Finally, the proposed approach is validated using an experiment involving a group of graduate students who are familiar with use case modeling. (shrink)

Sabdabrahma Siddhanta, popularized by Patanjali and Bhartruhari will be scientifically analyzed. Sphota Vada, proposed and nurtured by the Sanskrit grammarians will be interpreted from modern physics and communication engineering points of view. Insight about the theory of language and modes of language acquisition and communication available in the Brahma Kanda of Vakyapadeeyam will be translated into modern computational terms. A flowchart of language processing in humans will be given. A gross model of human language acquisition, comprehension and communication (...) class='Hi'>process forming the basis to develop software for relevant mind-machine modeling will be presented. The implications of such a model to artificial intelligence and cognitive sciences will be discussed. The essentiality and necessity of a physics, communication engineering , biophysical and biochemical insight as both complementary and supplementary to using mathematical and computational methods in delineating the theory of Sanskrit language is put forward. Natural language comprehension as distinct and different from natural language processing is pointed out. (shrink)

One might poetically muse that computers have the essence both of logic and machines. Through the case of the history of Separation Logic, we explore how this assertion is more than idle poetry. Separation Logic works because it merges the software engineer’s conceptual model of a program’s manipulation of computer memory with the logical model that interprets what sentences in the logic are true, and because it has a proof theory which aids in the crucial problem of scaling the (...) reasoning task. Scalability is a central problem, and some would even say the central problem, in appli- cations of logic in computer science. Separation Logic is an interesting case because of its widespread success in verification tools. For these two senses of model—the engineering/conceptual and the logical—to merge in a genuine sense, each must maintain their norms of use from their home disciplines. When this occurs, both the logic and engineering benefit greatly. Seeking this intersection of two different senses of model provides a strategy for how computer scientists and logicians may be successful. Furthermore, the history of Separation Logic for analysing programs provides a novel case for philosophers of science of how software engineers and computer scientists develop models and the components of such models. We provide three contributions: an exploration of the extent of models merging that is necessary for success in computer science; an introduction to the technical details of Separation Logic, which can be used for reasoning about other exhaustible resources; and an introduction to the problems, process, and results of computer scientists for those outside the field. (shrink)

This letter contains suggestions for editors and software providers to help avoid affiliation bias in the initial and concluding stages of the peer review process. Submission management systems have a responsibility to ensure protection against affiliation bias. This can be achieved by automatically withholding the author’s identity and affiliation information from all editors, including the Editor-in-Chief, until a decision about publication has been made. Journals relying on email-based submissions are in a more difficult situation. Not having external support (...) in confirming the submitting author’s identity, this dilemma can be resolved through the implementation of strict instructions and guidelines concerning manuscript submission and handling. In this case the “human factor” cannot be fully eliminated, while automated processes can only be changed intentionally and with a certain delay. Therefore, with the suggested steps, submission management systems could become a strong guard against unconscious bias while also making conscious bias more difficult to impact the peer review process. (shrink)

Design is a conceptive activity which is usually presented as a sensible, sequential process and action. This book claims that design cannot be reduced to the rational, effective planning and organization that most models (such as design thinking) present. The author suggests another type of rationality which is based on what the humanities call aesthetics, writing, composition, and style: a rationality based in imaginary elaboration and coherence. The chapters, therefore, demonstrate that design practice is about creating not only functional (...) tools, but planes of reflections that challenge norms. To support this claim, this book analyzes research programs, art works, and design projects that produced new information and communication technologies (ICT). This is detailed using examples in each chapter. From these examples, two types of conclusions are derived: a first level considers the lessons that we can draw from these examples in terms of design practice while the second level starts a theoretical discussion based on these analyses of use cases. The goal is to develop an understanding of conception in its different forms. This book brings the use of these neglected methods to the foreground as a way to explicate the design process. Taking into consideration the humanities within design contributes to the discussion on pluridisciplinarity. The book posits that design as a historical and situated activity is a truly multidisciplinary endeavor that bridges the gap between engineering sciences and the humanities. (shrink)

Supplementary to matter and energy, information is the third essence for modeling the natural world. An emerging discipline known as cognitive informatics is developed recently that forms a profound interdisciplinary study of cognitive and information sciences, and tackles the common root problems sharing by informatics, computing, software engineering, artificial intelligence, cognitive science, neuropsychology, philosophy, linguistics, and life science. CI focuses on internal information processing mechanisms and the natural intelligence of the brain. This paper describes the historical development of (...) informatics from the classical information theory and contemporary informatics, to CI. The domain of CI, and its interdisciplinary nature are explored. Foundations of CI, particularly the brain versus the mind, the acquired life functions versus the inherited ones, and generic relationships between information, matter, and energy are investigated. The potential engineering applications of CI and perspectives on future research are discussed. It is expected that the investigation into CI will result in fundamental findings towards the development of next generation IT and software technologies, and new architectures of computing systems. (shrink)

Requirement specifications in software engineering involve developing a conceptual model of a target domain. The model is based on ontological exploration of things in reality. Many things in such a process closely tie to problems in metaphysics, the field of inquiry of what reality fundamentally is. According to some researchers, metaphysicians are trying to develop an account of the world that properly conceptualizes the way it is, and software design is similar. Notions such as classes, object (...) orientation, properties, instantiation, algorithms, etc. are metaphysical concepts developed many years ago. Exploring the metaphysics of such notions aims to establish quality assurance though some objective foundation not subject to misapprehensions and conventions. Much metaphysical work might best be understood as a model-building process. Here, a model is viewed as a hypothetical structure that we describe and investigate to understand more complex, real-world systems. The purpose of this paper is to enhance understanding of the metaphysical origins of conceptual modeling as exemplified by a specific proposed high-level model called thinging machines (TMs). The focus is on thimacs (things/machine) as a single category of TM modeling in the context of a two-phase world of staticity and dynamics. The general idea of this reality has been inspired by Deleuze’s ‘the virtual’ and related to the classical notions of Leibniz’s monads and Avicenna’s essence. The analysis of TMs leads to several interesting results about a thimac’s nature at the static and existence levels. (shrink)

Basic abstraction principles are reached through ontology, which was traditionally conceived as a depiction of the world itself. Ontology is also described using conceptual modeling (CM) that defines fundamental concepts of reality. CM is one of the central activities in computer science, especially as it is mainly used in software engineering as an intermediate artifact for system construction. To achieve such a goal, we propose Stoic CM (SCM) as a description of what a system must do functionally with (...) minimal ambiguity. As a case study, we apply SCM to investigate the ontology of BPMN (business process modeling notation). Such an undertaking would demonstrate SCM notions and simultaneously may offer a viable ontological foundation for BPMN. SCM defines the being of things and actions in reality based on Stoic notions of existence and subsistence. It has two levels of specification: (1) a subsistence static model where things and actions subsist and (2) an existence dynamic model where things and actions exist in time. From the Stoic ontological point of view, while a thing existing has a clear denotation, subsistence indicates the thing is “being there,” but it is inactive (does not participate in an event). We apply SCM to BPMN processes that involve buying a new car with many notions, such as activity, task, event, and message. The result indicates that SCM produces a tighter representation of reality, thus providing the necessary description of the part in the application world to be used as requirements for developing the software system. (shrink)

What we have learnt in the last six or seven decades about virtual machinery, as a result of a great deal of science and technology, enables us to offer Darwin a new defence against critics who argued that only physical form, not mental capabilities and consciousness could be products of evolution by natural selection. The defence compares the mental phenomena mentioned by Darwin’s opponents with contents of virtual machinery in computing systems. Objects, states, events, and processes in virtual machinery which (...) we have only recently learnt how to design and build, and could not even have been thought about in Darwin’s time, can interact with the physical machinery in which they are implemented, without being identical with their physical implementation, nor mere aggregates of physical structures and processes. The existence of various kinds of virtual machinery (including both “platform” virtual machines that can host other virtual machines, e.g. operating systems, and “application” virtual machines, e.g. spelling checkers, and computer games) depends on complex webs of causal connections involving hardware and software structures, events and processes, where the specification of such causal webs requires concepts that cannot be defined in terms of concepts of the physical sciences. That indefinability, plus the possibility of various kinds of self-monitoring within virtual machinery, seems to explain some of the allegedly mysterious and irreducible features of consciousness that motivated Darwin’s critics and also more recent philosophers criticising AI. There are consequences for philosophy, psychology, neuroscience and robotics. (shrink)

The aim of this study is to analyze the use of the Automation and networking among the faculty members and the students of engineering college libraries in Sri Venkateswara University Area. A well structured questionnaire was distributed among the 1314 faculty members and the students under study. The present study demonstrates and elaborates the various aspects of the Automation status, Categories of software used, Areas of Computerization, Source finance for their library automation work, automated services, topology of computer (...) networking is used, to know the types of networks used, satisfaction with digital library services. It was found that the Automation and Networking has become a vital instrument for teaching, research and learning process for these respondents. Some suggestions are set forth to make the services more beneficial for the academic community of the engineering colleges under study. Key words: Automation, Network, Topology. (shrink)

James Tizard, Tim Rietz, and Kelly BlincoeTo create inclusive software, development teams need to consider how they identify inclusive requirements for a software product. Requirements elicitation is the first stage in the process of developing the requirements of a software system. Elicitation is about describing the functionality, reliability, efficiency, and usability of the system to be developed, so that it suits the end users’ needs [12].Recent research has found that both traditional elicitation techniques (e.g., user interviews) (...) and newer online crowd-based approaches may have challenges in gathering the views of a diverse set of users. In particular, there are significant challenges in eliciting requirements from users with cognitive disabilities, as well as ensuring that the full demographic spectrum (e.g., by gender, age, ethnicity) of a user base is adequately represented.This chapter discusses the motivations for more inclusive requirements elicitation and the challenges that need to be overcome and finally makes recommendations for both requirements engineering practitioners and researchers. (shrink)

The notion of specification plays a key role in the developing science of computing. It is typically considered to be the keystone in the software development process. However, there is no single, generally agreed meaning of specification that bears close scrutiny. Instead there is a variety of different, although partially interlocking and overlapping interpretations of the term.We catalogue this varietal profusion and attempt to lay bare both the sources and consequences of each major alternative. We attempt to present (...) the full range of possibilities, and the biases inherent in each style of interpretation. (shrink)

Domain-Driven Design (DDD) has become one of the most influential approaches to modeling complex software systems. It proposes that software architectures should be structured around domain models and bounded contexts that represent conceptual areas of a business. -/- This paper critically examines that assumption by analyzing the structural organization of real business operations. It argues that enterprises are not naturally decomposed into domains but operate through end-to-end processes that span multiple organizational units. These processes depend on a relatively (...) small set of shared organizational entities — such as customers, products, contracts, financial transactions, documents, and employees — which participate in multiple processes simultaneously. -/- Such entities function as shared invariants of enterprise systems. Because they are inherently cross-cutting, they cannot be cleanly partitioned across independent domain boundaries without producing duplication of information, model divergence, and loss of organizational consistency. -/- The paper introduces a simple formal model relating business processes and organizational entities and shows that shared invariants arise naturally from the structure of enterprise processes. On this basis, it proposes the concept of Domain Zero: a foundational architectural domain responsible for maintaining the shared informational core of the organization. -/- The paper concludes that while domain-oriented decomposition may be useful as a software engineering technique, enterprise systems are structurally organized around shared invariants rather than domains. (shrink)

This project was undertaken to develop a telelearning knowledge base aimed at making specialized telelearning knowledge accessible to non-specialized practitioners in the field. The challenge stems from a rationale related to a user-centered approach for the software design process, which is focused on learning in the context of professional practice, the bridge to be built between expert and practitioner knowledge, as well as the knowledge valorization of the latter. In order to take into account users and their situated (...) actions, a usage study was integrated in the analysis phase. This study allows the creation of procedural and contextual telelearning models, and also lists of needs. These results serve as a basis for formulating guidelines for the development of ontologies, for the design of the telelearning knowledge base user interface and telelearning knowledge base environmental description. This paper presents the guidelines and orientations derived from these models. (shrink)

The Software Engineering Code of Ethics and Professional Practice, intended as a standard for teaching and practicing software engineering, documents the ethical and professional obligations of software engineers. The code should instruct practitioners about the standards society expects them to meet, about what their peers strive for, and about what to expect of one another. In addition, the code should also inform the public about the responsibilities that are important to the profession. Adopted in 2000 (...) by the IEEE Computer Society and the ACM--two leading international computing societies--the code of ethics is intended as a guide for members of the evolving software engineering profession. The code was developed by a multinational task force with additional input from other professionals from industry, government posts, military installations, and educational professions. (shrink)

An engineer who becomes an educator in a school of software engineering has the mission to teach how to design and construct software systems, therein applying his or her knowledge and expertise. However, due to their engineering background, engineers may forget that educating a person is not the same as designing a machine, since a machine has a well-defined goal, whilst a person is capable to self-propose his or her own objectives. The ethical implications are clear: (...) educating a free person must leave space for creativity and self-determination in his or her own discovery of the way towards personal and professional fulfillment, which cannot consist only in achieving goals selected by others. We present here an argument that is applicable to most fields of engineering. However, the dis-analogy between educating students and programming robots may have a particular appeal to software engineers and computer scientists. We think the consideration of three different stages in the educational process may be useful to engineers when they act as educators. We claim that the three stages are essential to engineering education. In particular, education is incomplete if the third stage is not reached. Moreover, mentoring is incompatible with an educational assessment framework that considers the goals of the engineer are always given by others. In our view, then, an integral education is not only beyond programming the behavior of students, but also beyond having them reach those given goals. (shrink)

Over the past 30 years, computer engineering has developed a lot. Currently, computer and software applications have a central role in business, medicine, security, communications, industry, education, and everyday life. Software developers, peoples who manage computer networks, data security analysts can do well, but they also have the potential to cause suffering and harm to the clients or ordinary peoples, willingly or not. For this reason, IT activities must be regulated by specific laws. From the beginning, we (...) argue that the law is not the same thing as ethics, even if both promote the good. Certain ethical principles can be strengthened by law. In the field of computer science and technology, can exists theft, privacy violations, violence and harassment. To combat and punish such actions and behaviors, law is needed. But is software engineering a profession? If so, are there codes of professional ethics whereby specialists in the field can regulate their professional activity, as is the case, for example, in areas such as justice or medicine? In relation with that, Gibbs and Ford have identified 8 components of a professional infrastructure. Some of that is: initial vocational training, professional accreditation, licensing, continuous vocational training, the existence of code of ethics.. With the fact that software engineering is a profession, in this article we present the main principles of behavior. The principles are not legally binding. This are grouped by interest categories depending on who or what is involved in the interaction with software engineering. (shrink)

This chapter discusses ethical software engineering and we discuss notable failures such as the space shuttle disaster and the defective Therac-25 radiotherapy machine. We discuss the extraordinary Volkswagen emissions scandal, where engineers designed a “defeat device” that would allow Volkswagen cars to pass emission tests in the United States.

Theories related to cognitive sciences, Human-in-the-loop Cyber-physical systems, data analysis for decision-making, and computational ethics make clear the need to create transdisciplinary learning, research, and application strategies to bring coherence to the paradigm of a truly human-oriented technology. Autonomous objects assume more responsibilities for individual and collective phenomena, they have gradually filtered into routines and require the incorporation of ethical practice into the professions related to the development, modeling, and design of algorithms. To make this possible, it is pertinent and (...) urgent to bring them closer to the problems and approaches of the humanities. Increasingly transdisciplinary research must be part of the construction of systems that provide developers and scientists with the necessary bases to understand the ethical debate and therefore their commitment to society. This article considers two theories as articulating axes: Blumenberg’s, coming from the field of philosophy, for whom the process of technification and especially the implementation of mathematical models in their algorithmic form leads to an emptying of meaning and therefore makes programmers who implement their functions to be alien to the concerns that gave them origin; Daston’s, belonging to the field of the history of science and according to which the division of labor in the processes of technification of the calculation implies a kind of subordination in which those who implement the inventions of a small group of privileged mathematicians ignore the procedures that put them into operation. Given these two theories, the black box models prevalent in AI development, and the urgency of establishing explanatory frameworks for the development of computational ethics, this article exposes the need to give a voice to the cultural history of consciousness for promoting the discussions around the implementation of mathematical algorithms. The paper takes as a reference the different points of view that have emerged around the study of technological ethics, its applicability, management, and design. It criticizes the current state of studies from a humanistic perspective and explains how the historical perspective allows promoting the training of software engineers, developers and creators so that they assume intuitions and moral values in the development of their work. Specifically, it aims to expose how cultural history, applied to the study of consciousness and its phenomena, makes those involved in this technological revolution aware of the effect that they, through their algorithms, have on society in general and on human beings in particular. (shrink)

There are many tangled normative and technical questions involved in evaluating the quality of software used in epidemiological simulations. In this paper we answer some of these questions and offer practical guidance to practitioners, funders, scientific journals, and consumers of epidemiological research. The heart of our paper is a case study of the Imperial College London covid-19 simulator, set in the context of recent work in epistemology of simulation and philosophy of epidemiology.

Explorations in Systems Phenomenology in Relation to Ontology, Hermeneutics and the Meta-dialectics of Design -/- SYNOPSIS A Phenomenological Analysis of Emergent Design is performed based on the foundations of General Schemas Theory. The concept of Sign Engineering is explored in terms of Hermeneutics, Dialectics, and Ontology in order to define Emergent Systems and Metasystems Engineering based on the concept of Meta-dialectics. -/- ABSTRACT Phenomenology, Ontology, Hermeneutics, and Dialectics will dominate our inquiry into the nature of the Emergent Design (...) of the System and its inverse dual, the Meta-system. This is an speculative dissertation that attempts to produce a philosophical, mathematical, and theoretical view of the nature of Systems Engineering Design. Emergent System Design, i.e., the design of yet unheard of and/or hitherto non-existent Systems and Metasystems is the focus. This study is a frontal assault on the hard problem of explaining how Engineering produces new things, rather than a repetition or reordering of concepts that already exist. In this work the philosophies of E. Husserl, A. Gurwitsch, M. Heidegger, J. Derrida, G. Deleuze, A. Badiou, G. Hegel, I. Kant and other Continental Philosophers are brought to bear on different aspects of how new technological systems come into existence through the midwifery of Systems Engineering. Sign Engineering is singled out as the most important aspect of Systems Engineering. We will build on the work of Pieter Wisse and extend his theory of Sign Engineering to define Meta-dialectics in the form of Quadralectics and then Pentalectics. Along the way the various ontological levels of Being are explored in conjunction with the discovery that the Quadralectic is related to the possibility of design primarily at the Third Meta-level of Being, called Hyper Being. Design Process is dependent upon the emergent possibilities that appear in Hyper Being. Hyper Being, termed by Heidegger as Being (Being crossed-out) and termed by Derrida as Differance, also appears as the widest space within the Design Field at the third meta-level of Being and therefore provides the most leverage that is needed to produce emergent effects. Hyper Being is where possibilities appear within our worldview. Possibility is necessary for emergent events to occur. Hyper Being possibilities are extended by Wild Being propensities to allow the embodiment of new things. We discuss how this philosophical background relates to meta-methods such as the Gurevich Abstract State Machine and the Wisse Metapattern methods, as well as real-time architectural design methods as described in the Integral Software Engineering Methodology. One aim of this research is to find the foundation for extending the ISEM methodology to become a general purpose Systems Design Methodology. Our purpose is also to bring these philosophical considerations into the practical realm by examining P. Bourdieu’s ideas on the relationship between theoretical and practical reason and M. de Certeau’s ideas on practice. The relationship between design and implementation is seen in terms of the Set/Mass conceptual opposition. General Schemas Theory is used as a way of critiquing the dependence of Set based mathematics as a basis for Design. The dissertation delineates a new foundation for Systems Engineering as Emergent Engineering based on General Schemas Theory, and provides an advanced theory of Design based on the understanding of the meta-levels of Being, particularly focusing upon the relationship between Hyper Being and Wild Being in the context of Pure and Process Being. (shrink)

In conceptual modeling (CM) as a subdiscipline of software engineering, current proposed ontologies (categorical analysis of entities) are typically established through whole adoption of philosophical theories (e.g. Bunge’s). In this paper, we pursue an interdisciplinary research approach to develop a diagrammatic-based ontological foundation for CM using philosophical ontology as a secondary source. It is an endeavor to escape an offshore procurement of ontology from philosophy and implant it in CM. In such an effort, the CM diagrammatic language plays (...) an important role in contrast to dogmatic philosophical languages’ obsession with abstract entities. Specifically, this paper is about developing a descriptive (in contrast to formal) ontology that a modeler accepts as a supplementary account of reality when using thinging machines (TMs; i.e. a reality that uncovers the ontology of things that TM modeling discusses or “talks about,” akin to the ontology of natural language). Although existence is a well-established notion, we defend subsistence (Stoic term) as a supplementary mode of reality (e.g. reflection of event). The aim here is aligned toward developing CM notions and processes that are firm enough. Classical analysis of being per se (e.g. identity, substance, classes, objects) is de-emphasized in this work; nevertheless, philosophical concepts form an acknowledged authority to compare to. As a case study, such a methodology is applied to the notion of information that provides a common-sense understanding of the world. This application would enhance understanding of the TM methodology and clarify some of the issues that shed light on the question of the nature of information as an important concept in software engineering. Information is defined as about events; that is, it is about existing things. It is viewed as having a subsisting nature that exists only through being “carried on” by other things. The results seem to indicate a promising approach to define information and understand its nature. (shrink)

The massive redeployment hypothesis (MRH) is a theory about the functional topography of the human brain, offering a middle course between strict localization on the one hand, and holism on the other. Central to MRH is the claim that cognitive evolution proceeded in a way analogous to component reuse in software engineering, whereby existing components-originally developed to serve some specific purpose-were used for new purposes and combined to support new capacities, without disrupting their participation in existing programs. If (...) the evolution of cognition was indeed driven by such exaptation, then we should be able to make some specific empirical predictions regarding the resulting functional topography of the brain. This essay discusses three such predictions, and some of the evidence supporting them. Then, using this account as a background, the essay considers the implications of these findings for an account of the functional integration of cognitive operations. For instance, MRH suggests that in order to determine the functional role of a given brain area it is necessary to consider its participation across multiple task categories, and not just focus on one, as has been the typical practice in cognitive neuroscience. This change of methodology will motivate (even perhaps necessitate) the development of a new, domain-neutral vocabulary for characterizing the contribution of individual brain areas to larger functional complexes, and direct particular attention to the question of how these various area roles are integrated and coordinated to result in the observed cognitive effect. Finally, the details of the mix of cognitive functions a given area supports should tell us something interesting not just about the likely computational role of that area, but about the nature of and relations between the cognitive functions themselves. For instance, growing evidence of the role of “motor” areas like M1, SMA and PMC in language processing, and of “language” areas like Broca’s area in motor control, offers the possibility for significantly reconceptualizing the nature both of language and of motor control. (shrink)

We examine the philosophical disputes among computer scientists concerning methodological, ontological, and epistemological questions: Is computer science a branch of mathematics, an engineering discipline, or a natural science? Should knowledge about the behaviour of programs proceed deductively or empirically? Are computer programs on a par with mathematical objects, with mere data, or with mental processes? We conclude that distinct positions taken in regard to these questions emanate from distinct sets of received beliefs or paradigms within the discipline: – The (...) rationalist paradigm, which was common among theoretical computer scientists, defines computer science as a branch of mathematics, treats programs on a par with mathematical objects, and seeks certain, a priori knowledge about their ‘correctness’ by means of deductive reasoning. – The technocratic paradigm, promulgated mainly by software engineers and has come to dominate much of the discipline, defines computer science as an engineering discipline, treats programs as mere data, and seeks probable, a posteriori knowledge about their reliability empirically using testing suites. – The scientific paradigm, prevalent in the branches of artificial intelligence, defines computer science as a natural (empirical) science, takes programs to be entities on a par with mental processes, and seeks a priori and a posteriori knowledge about them by combining formal deduction and scientific experimentation. We demonstrate evidence corroborating the tenets of the scientific paradigm, in particular the claim that program-processes are on a par with mental processes. We conclude with a discussion in the influence that the technocratic paradigm has been having over computer science. (shrink)

In this paper, we examine the potential integration of artificial intelligence (AI) into capital punishment through lethal autonomous mechanisms (LAMs), an extension of developments in lethal autonomous weapons (LAWs). While most philosophical and ethical research on autonomous weapons systems focuses on warfare and policing, their potential role in capital executions remains unexplored. Through anticipatory analysis of LAMs’ integration into what we term the “death row network,” we show how retentionists might leverage these technologies to counter key abolitionist critiques. We analyze (...) how LAMs could undermine two abolitionist arguments: the harm to corrections personnel and the medicalization of execution protocols. However, we argue that while LAMs resolve these specific challenges, they simultaneously generate new ethical concerns. First, LAMs will not eliminate the moral and psychological burden on corrections personnel entirely but rather redistribute it to networks of AI developers, software engineers, and technology professionals who become implicated in state-sanctioned killings through their work. Similarly, LAMs address the medicalization concern, yet they merely shift ethical scrutiny from the medical sector to the technology corporations developing LAMs and their industrial partners. Second, LAMs’ elimination of human presence undermines the exercise of benevolence through sustained interpersonal engagement, from sharing final conversations to offering comfort during an inmate’s last moments. This human connection, which preserves dignity even within a dehumanizing process, cannot be replicated by automated systems and is a further argument against their adoption. (shrink)

This chapter highlights the crucial role organizational structures play in enabling ethical deliberation within software development. It emphasizes that ethical software engineering depends not only on deliberating about what is right but also on creating an organizational structure that actively supports ethical reflection and decision-making. Ethical deliberation cannot properly flourish in environments constrained by tight deadlines, inadequate resources, or conflicting incentives; therefore, organizations must intentionally cultivate both formal and informal structures that promote ethical awareness and deliberation. Furthermore, (...) this chapter argues that agile methodologies offer a particularly conducive environment for ethical deliberation through their iterative processes, team autonomy, and low hierarchies. Specifically, Sprint 0 and the role of the Product Owner are identified as a key point and role for integrating ethics early and continuously into the development process. Ultimately, the chapter calls for institutionalizing ethical practices within software-producing organizations, acknowledging the uniqueness of each organizational context, and underscoring the necessity of adapting these guidelines pragmatically to achieve sustainable ethical software development. (shrink)

This paper offers a review of Giuseppe Primero’s (2020) book “On the foundations of computing”_._ Mathematical, engineering, and experimental foundations of the science of computing are examined under the light of the notions of formal, physical, and experimental computational validity provided by the author. It is challenged the thesis that experimental computational validity can be defined only for the algorithmic method and not for the software development process. The notions of computational hypothesis and computational experiment provided by (...) Primiero (2020) are extended to the case of software development. Finally, it is highlighted how the hypothetical-deductive method is involved in the practice of using models to corroborate computational hypotheses in software testing. As a concluding remark, it is underlined how defining experimental computational validity in the context of software development offers a sound experimental foundation to the science of computing. (shrink)

Among the various contemporary schools of moral thinking, consequence-based ethics, as opposed to rule-based, seems to have a good acceptance among professionals such as software engineers. But naïve consequentialism is intellectually too weak to serve as a practical guide in the profession. Besides, the complexity of software systems makes it very hard to know in advance the consequences that will derive from professional activities in the production of software. Therefore, following the spirit of well-known codes of ethics (...) such as the ACM/IEEE’s, we advocate for a more solid position in the ethical education of software engineers, which we call ‘moderate deontologism’, that takes into account both rules and consequences to assess the goodness of actions, and at the same time pays an adequate consideration to the absolute values of human dignity. In order to educate responsible professionals, however, this position should be complemented with a pedagogical approach to virtue ethics. (shrink)

The rapid adoption of digital technologies has revolutionized business operations and introduced emerging concepts such as Digital Twin (DT) technology, which has the potential to predict system responses before they occur, making it an attractive option for smart and sustainable tourism. However, implementing DT software systems poses significant challenges, including compliance with regulations and effective communication among stakeholders, and concerns surrounding security, privacy, and trust with the use of big data. To address these challenges, this paper proposes a documentation (...) framework for architectural decisions (DFAD) that applies the concept of big data governance to the digital system. The framework aims to ensure accountability, transparency, and trustworthiness while adhering to rules and regulations. To demonstrate its applicability, a case study and three case scenarios on the potential use of Mobile Positioning Data (MPD) in Indonesia for DT technology in smart and sustainable tourism were examined. The paper highlights the benefits of DFAD in shaping stakeholder communication and human–machine interactions while leveraging the potential of MPD to measure tourism statistics by Statistics Indonesia since 2016. Not only the documentation framework promotes compliance with regulations, but it also facilitates effective communication among stakeholders and enhances trust and transparency in the use of big data in DT technology for smart and sustainable tourism. This paper emphasizes the importance of effective big data governance and its potential to promote sustainable tourism practices. The multidisciplinarity approach on political science, software engineering, tourism, and official statistics provides an opportunity for academic contribution and decision-making processes. (shrink)