Domain-oriented architecture design for production control software

this paper, we present domain-oriented architectural design heuristics for production control software. Our approach is based upon the following premisses. First, software design, like all other forms of design, consists of the reduction of uncertainty about a final product by making design decisions. These decisions should as much as possible be based upon information that is certain, either because they represent laws of nature or because they represent previously made design decisions. An import class of information concerns the domain of the software. The domain of control software is the part of the world monitored and controlled by the software; it is the larger system into which the software is embedded. The software engineer should exploit system-level domain knowledge in order to make software design decisions. Second, in the case of production control software, using system-level knowledge is not only justified, it is also imposed on the software engineer by the necessity to cooperate with hardware engineers. These represent their designs by means of Process and Instrumentation Diagrams (PIDs) and Input-Output (IO) lists. They do not want to spend time, nor do they see the need, to duplicate the information represented by these diagrams by means of diagrams from software engineering methods. Such a duplication would be an occasion to introduce errors of omission (information lost during the translation process) or commission (misinterpretation, misguided but invisible design decisions made during the translation) anyway. We think it is up to the software engineer to adapt his or her notations to those of the system engineers he or she must work with. Third, work in patterns and software architectures started from the programminglanguage level and is now moving..

Assessing architectural evolution: A case study

This is the post-print version of the Article. The official published can be accessed from the link below - Copyright @ 2011 SpringerThis paper proposes to use a historical perspective on generic laws, principles, and guidelines, like Lehman’s software evolution laws and Martin’s design principles, in order to achieve a multi-faceted process and structural assessment of a system’s architectural evolution. We present a simple structural model with associated historical metrics and visualizations that could form part of an architect’s dashboard. We perform such an assessment for the Eclipse SDK, as a case study of a large, complex, and long-lived system for which sustained effective architectural evolution is paramount. The twofold aim of checking generic principles on a well-know system is, on the one hand, to see whether there are certain lessons that could be learned for best practice of architectural evolution, and on the other hand to get more insights about the applicability of such principles. We find that while the Eclipse SDK does follow several of the laws and principles, there are some deviations, and we discuss areas of architectural improvement and limitations of the assessment approach

Enforcing IPR through Informal Institutions: The possible role of religion in fighting software piracy

The existence of formal IPR laws can be considered a prerequisite for having efficient law enforcement but does not imply efficient enforcement in itself. A simple model is constructed to explain the interplay between the IPR law and human behavior within counterfeiting countries. It shows how a politically monitored IPR enforcement strategy is able to alter formal IPR laws or institutions but might not affect informal institutions, or human morals and behavior, to the same extent, hence barely affecting piracy situation. The model shows the essential role of informal institutions and its sanction mechanisms in the enforcement process. The main obstacle of IPR enforcement is that people are still not convinced that IPR violations are unethical. Religion can be considered an informal institution that might support or hinder formal laws issued with regards to IPR and hence influence de facto enforcement of laws, especially in countries with high piracy rate if a high adherence to religion is found. As the Religion-Loyalty Index (RLI) developed by this study shows, Muslim countries have the highest religiosity level among different religions. Consequently, an investigation of how Islamic jurisprudence views IPR piracy is conducted. As Islam generally prohibits IPR piracy, a set of policy recommendations based on new institutional perspective is presented that can effectively help in minimizing IPR piracy in developing countries in general and Muslim ones in specific.Intellectual Property Rights (IPR), Formal vs. Informal Institutions, New Institutional Economics (NIE), Software Piracy, Religion, Enforcement

System dynamics modelling for the management of long term software evolution processes

An approach and basic concepts for the study of the system dynamics of long-term software evolution processes is presented. The approach provides a generic context and framework that supports at least three crucial process areas requiring management decision, resource allocation, release planning, and process performance monitoring. The report exemplifies the approach with an executable model. The latter reflects the global software process at a high level of abstraction and includes phenomenological observations derived from the laws of software evolution and the behaviours thereby implied. It incorporates concepts such as progressive (e.g., functional enhancement) and anti-regressive (e.g., complexity control) activities and enables the study of policies of human resource allocation to classes of activities. The example shows how the model permits assessment of the impact of alternative policies on various evolutionary attributes. It is part of and exemplifies the methods for software process modelling being developed and applied in the FEAST projects

Analysis of the practical reform of engineering thermal physics teaching based on FLUENT

Engineering thermophysics is a technical science which studies the law of energy transformation in the form of heat and its application.It studies the internal laws of various thermal phenomena and thermal processes, and can be used to guide engineering practice. FLUENT is a tool course that plays a great role in assisting with the simulation of some devices in engineering thermophysics and fluids. However, in the process of learning simulation, students have had difficulty in mastering the FLUENT software and this paper proposes some constructive suggestions for measures to increase students\u27 mastery of this software