Towards Mapping Control Theory and Software Engineering Properties using Specification Patterns

The eighteenth annual International Workshop on Principles of Diagnosis was held in Nashville, Tennessee, May 29–31, 2007. Papers presented at the workshop covered a variety of theories, principles, and computational techniques for diagnosis, monitoring, testing, reconfiguration, fault-adaptive control, and repair of complex systems. This year’s workshop emphasized inter-actions and exchange of ideas and experiences between researchers and practitioners whose backgrounds included AI, control theory, systems engineering, software engineering, and related areas.

Repository-based development of software systems has gained more attention recently by addressing new challenges such as security and dependability. However, there are still gaps in existing modeling languages and/or formalisms dedicated to define model repositories and the way how to reuse them in the automation of software development. Thus, there is a strong requirement for defining a model repository description language not only as a modeling approach, but also as a suitable instrument to support system and software engineers in the activity of search and retrieval of appropriate models beyond keyword-based search. Moreover, modeling approaches allow using tools for the specification and the exploitation of the designed artifacts e.g. analysis and evaluation. The goal of this paper is to advance the state of the art in model repository description for software and systems engineering. In particular, we have designed a flexible and extensible modeling language, by means of an OMG style metamodel, to specify model repositories for modeling artifacts, and we have defined an operational architecture for development tools. In particular, we show the feasibility of our own approach by reporting some preliminary prototype providing a model-based repository of security and dependability S&D pattern models.

Inverted pendulum remained as the most popular topic for control theory researches because of its characteristic of being non-linear, unstable and under-actuated system. It is ideal for verification, validation and enhancement of control theory by stabilizing the inverted pendulum in an upright position using various controller and stabilizer mechanism. For this project, Proportional-Integral-Derivative (PID) controller is used to stabilize the inverted pendulum by tuning the respective gains (kP, kI, and kD) to control the parameters of inverted pendulum which includes the rise time, settling time, overshoot and steady-state error in cooperation with of Arduino microcontroller. The objective of this project is to design and build a stabilizer mechanism with the integration of mechanical and electrical components to stabilize two Directional (2D) inverted pendulum similar to 3D printer mechanism. Besides that, PID controller will be tuned in Arduino microcontroller and control the output of stabilizer mechanism. The stabilizer mechanism is designed in SolidWorks software and built using various manufacturing techniques, raw materials and 3D printing, while the electronics components such as gyroscope and Direct Current (DC) motors are controlled using Arduino Due in C++ language. The gyroscope determines the tilting angle of the pendulum as a feedback in the control loop, and the gains of PID are used to control the speed and direction of DC motor to provide sufficient force/torque to keep the inverted pendulum in an upright position. The stabilizer mechanism with inverted pendulum has been built and the gains of PID have been tuned using “trial and error” method as friction is now taken into consideration. The inverted pendulum is successfully stabilized in an upright position (0o measure at z-axis) using control theory.

As that of coordination and ISO 15288, discipline system engineering and software engineering processes, methods have a lot in common, and concerns. In most of the system software interest, now offers an important function, more and more is the most significant factors determine the non-functional attributes. In the implementation of the system collection and failure are often attributed to the system and/or software engineering recovery. Need to use systems engineering software design and development, and need to incorporate software engineering concepts into system engineering, suggests that the decision of the two disciplines the close relationship between is appropriate. This article describes a definite theory integrating the two disciplines, defines a framework on establishing a vocabulary integration, and gives the use of this framework preliminary results to describe the system and software integration of defense plans.

Almost all of today's man‐made mechanical and electronic systems are actually cyberphysical systems (CPSs). Formerly physical systems, from rockets to hair dryers and faucets, gain capabilities from software sensing, calculating, and control. Although some software will remain mostly divorced from physical items (e.g., cloud systems), much complex software will control, sense, and communicate with physical systems, which are then called CPSs. Although many systems engineers did not come to the discipline from a software background, CPSs still need systems engineering. Additionally, software engineers must step out of their “subsystem” box and work with systems engineers to build tomorrow's systems. To enable that, systems engineers should continue to apply systems engineering principles, including continuous learning (especially about software) and coordinating (including teaching software engineers about systems engineering). The time is now to take on new behaviors to meet the challenges of CPSs. Systems engineers must work alongside software engineers to reach the joint goal of system success.

Simultaneous and collaborative development of satellites and Information Systems to support their lifecycle processes

The Rockwell International-Collins Avionics Divisions are developing an avionics systems engineering graduate program with Iowa State University. The author discusses the proposed curriculum and the four avionics systems engineering courses that will be offered. The four courses are: Systems Engineering and Analysis, Avionics Systems Engineering, System Project Management, and Software Systems Engineering. The Systems Engineering and Analysis course introduces system engineering concepts and principles. The second course applies the system engineering techniques presented in the first course to avionics. Current avionics functions are presented and then used to discuss avionics systems. The third course discusses avionics systems engineering from the project management viewpoint. The Software Systems Engineering course examines the systems aspect of software. >

With the affordable advanced computerized equipments and tools, systems engineering and software systems engi- neering become closely related. Software engineering to the low level computer software and systems is not suffi- cient enough for systems engineers' needs to build com- plex computerized systems. Every engineering system has its own systems engineering's theory and technology. Are there general principles, theories, and technology for two or a collection of systems? In this article a new inte- grated field called Systems Software Engineering (SSE) is proposed. SSE research is to study the common paradigms, theories, technology of the systems among all or simply a collection of engineering fields, applied science fields, com- puter science, software engineering, and mathematical sci- ences. According to the author's opinion, none except few like Lofti Zadeh's soft computing and granular computing are towards this trend that they have integrated fuzzy set the- ory and granular computing as an example. An integrated "Systems Software Engineering" theory based on Boolean logic, Hilbert logic and set theory is introduced. Based on Boolean logic and Hilbert logic as the foundation for the de- cision systems and control systems for information systems, we can develop integrated foundations, theories, principles, and tools for information science. We adopt bioinformat- ics, bioengineering and medical information systems as a special case to describe our integrated "Software Systems Engineering". As a matter of fact, we can choose any other integrated modern related fields as our special case to study in this paper.

Systems engineering is a transdisciplinary scientific and applied direction that combines the principles of a systems approach, methods, tools and standards that provide an integrated methodology and relevant technologies for the design and development of complex systems, their comprehensive analysis and verification, efficient and safe use. The modern approach to systems engineering is characterized by an accentuated modeling of systems throughout their life cycle with the ultimate goal of creating their digital twins. It is called model-based systems engineering (MBSE). Consistent integration of MBSE with software engineering leads to the formation of the MBSSE (Model-Based Systems and Software Engineering) direction. This textbook is devoted to this area, the main objective of which is to study the conceptual and scientific-methodological foundations of MBSE and MBSSE, models and methods of life cycle management of systems and software, basic standards of systems engineering, study and mastery of the UML and SysML systems modeling languages and the corresponding modeling tools, study of requirements engineering methods and development of a description of the system architecture, familiarization with the concept of digital twins and their role in MBSE, study of the MBSSE reference model and its relationship with the process standards of systems engineering, study of the methodological aspects of the system and software integration process. The final chapter of the textbook is devoted to the study of the mathematical foundations of systems engineering. The main aspects of the mathematical theory of systems by A. Wayne Wymore, which became an important stimulus for the development of the model-oriented approach in systems engineering, and modern research, including the apparatus of finite automata by David Harel, the formalism of modeling of discrete systems DEVS, research into category theory as a formal mathematical basis for model-based system design are considered. The authors recommend this course as a basic course for training IT professionals.

As illustrated in the harmonization of ISO 15288 and ISO 12207, the disciplines of systems engineering and software engineering share many processes, methods, and concerns. In most systems of interest, software now provides a significant majority of functionality and increasingly is a significant component in determining non‐functional attributes. Failures in system acquisition and implementation are often attributed to systems and/or software engineering shortfalls. The need to apply systems engineering to software design and development, as well as the need to incorporate software engineering concepts into systems engineering decisions, implies that a closer relationship between the two disciplines is appropriate. This paper states a clear rationale for integrating the two disciplines, defines a framework that establishes a vocabulary for discussing integration, and presents initial findings in using that framework to describe systems and software integration in ongoing defence programs.

This Appendix summarises what is perhaps the most widely used systems engineering Standard in the world: ISO/IEC 15288:2015 Systems and software engineering - System Life Cycle Processes [1]. The Appendix presents information on ISO15288:2015 using the “seven views”approach to Process modelling that is discussed in Chapter 7, five out of the seven possible Views are presented; no Information Views or Process Behaviour Views are given as the Standard is written at a level which does not allow these Views to be abstracted and modelled. The Views are given without commentary and are intended to be used as a reference in conjunction with a reading of the Standard. As an aid to understanding the content of ISO15288:2015, the reader is also directed to the INCOSE Systems Engineering Handbook [2].

The C* Conference on Computer Science and Software Engineering (C3S2E) was established in 2008. C3S2E 2010 is the third annual meeting in the C3S2E conference series and is held in Montréal, Québec, Canada, during May 19-20, 2010. The conference aims to address the need of the academic community in computer science and software engineering. It brings together academics, government and industry professionals to discuss recent progress and challenges in a broad range of areas in the field of computer science and software engineering such as algorithms and theory, artificial intelligence, bioinformatics, computer architecture, computer graphics, computer security, computer vision, data mining, databases, image processing, information retrieval, machine learning, as well as software engineering. C3S2E 2010 also serves as a platform for theoreticians and practitioners to exchange their original research ideas on academic or application aspects of computing and engineering of software systems, present their new findings on theoretical or practical aspects of computer science and software engineering, share their experiences on integrating new technologies into products and applications, discuss their work on applying computing and software engineering to real-life situations, describe their development and operations of challenging computing related systems, and identify unsolved challenges. Although it is the third time C3S2E is held, this comprehensive conference has grown from a Canadian conference into an international conference. For C3S2E 2010, we continue to keep our tradition for inviting international experts in various areas of computer science and software engineering to join our team of international program committee. As a result, our Program Committee consists of professionals from different parts of the world including Australia, Canada, Germany, Hong Kong, Italy, Japan, Portugal, South Korea, Turkey, UAE, and UK. This committee has done an excellent job in finishing the single-blind review and on-line double-blind debate processes in record time. On average, about 90% of reviews were submitted by the due date and about 3.67 reviews were received for each paper. In terms of submissions, we have attracted many high-quality papers submitted by authors globally. The paper selection process was thorough and competitive. On average, each paper was refereed by at least three reviewers, and about 18% of submissions were accepted as full research papers. This year, we have an intensive program that spans over two days. In addition to research papers and student posters, we also include position papers, which allow authors to give their opinions and vision on exploring new concepts and research directions.

Introduction The computing sciences are complex fields that combine both theoretical and practical components. Students successfully completing an undergraduate computer science program should have instruction in both the mathematical and theoretical foundations of computing as well as the more practical aspects of how to effectively use computers to solve problems. Software engineering, as its name implies, is more directed toward the practical aspects of how to successfully develop complex systems that meet user requirements and are reliable, usable, and maintainable. Computing Curricula 2005 recognizes the need for more extensive education to produce professional engineers than what can be reasonably provided in a typical computer science program (ACM, 2005). As such, they propose engineering be treated as a totally separate discipline within computer science education. However, while there has been some debate about the exact role engineering should have in a computer science program (Curran, 2003), the ACM Curricula has maintained the importance of engineering to all computer science students and has kept it as a core element in computer science education (ACM, 2008). For purposes of this paper, we will focus on the teaching of engineering within the computer science discipline. Unlike other topics in the computer science major, the techniques and principles taught in engineering are often first developed and refined in industry before arriving in the classroom. As commercial development techniques and tools evolve, so pedagogical methodologies change. Computer science educators have taken different approaches to teaching engineering over the years, both as a result of changing methodologies as well as individual beliefs about what teaching methods work best in a particular academic environment. This paper is a case study in applying current productivity tools (specifically Redmine) in a engineering course at our institution. The objectives of the study are to investigate how to integrate the tools into the existing structure and evaluate their impact. We describe our experience in recently changing our approach to teaching engineering to be more aligned with current tools and how to effectively use them in an academic environment. The paper begins with an overview of engineering teaching methods, then describes our traditional approach and motivation for changing, how the new approach was integrated into the course, our experience with the change, and, finally, our plans for the future Software Engineering Education Background Software Engineering is defined as the application of a systematic, disciplined, quantifiable approach to the development, operation and maintenance of software (Petkovic, Thompson, & Todtenhoefer, 2006, p. 294). The need to teach engineering in colleges has been identified for decades. Stiller & LeBlanc (2002) point out as far back as the early 1990's, ACM Computing Curricula suggested that the at least one engineering course should be required in accredited computer science programs. They point out that the number of large projects in industry demand this and suggest that the proof of the success of these accredited computer science programs should be seen in the reduction of failure in the design and operation of large computer programs. Software engineering programs can be thought of as a replacement for the old apprenticeship programs which taught the trades to workman (Stroulia, Bauer, Craig, Reid, & Wilson, 2011). The issue, however, is how to bring this effect into the classroom. Many educators feel that current practices of teaching engineering are not adequately preparing students for the real world of development. Nurkkala & Brandle (2011) summarize the problems with current teaching approaches: * No product--students are creating projects, not commercial grade products * Short duration--single semester, or two-semester, courses impose an artificial time constraint * High turnover--new students each semester means the talent pool remains shallow and student skills are not developing based on previous experience * Low complexity--by necessity given time constraints and skill sets * No maintenance--as a result of short duration, students do not experience a key aspect of development, the maintenance phase * No customer--most engineering projects do not interface with a real customer To address these shortcomings, different approaches to teaching engineering have emerged and been proposed in the literature. …

In this paper, solvability conditions for disturbance accommodating control (DAC) have been discussed and applied on wind turbine controller design in above-rated wind speed to regulate rotor speed and to mitigate turbine structural loads. An asymptotically stabilizing DAC controller with disturbance impact on the wind turbine being totally canceled out can be found if certain conditions are fulfilled. Designing a rotor speed regulation controller without steady-state error is important for applying linear control methodology such as DAC on wind turbines. Therefore, solvability conditions of DAC without steady-state error are attractive and can be taken as examples when designing a multitask turbine controller. DAC controllers solved via Moore–Penrose Pseudoinverse and the Kronecker product are discussed, and solvability conditions of using them are given. Additionally, a new solvability condition based on inverting the feed-through D term is proposed for the sake of reducing computational burden in the Kronecker product. Applications of designing collective pitch and independent pitch controllers based on DAC are presented. Recommendations of designing a DAC-based wind turbine controller are given. A DAC controller motivated by the proposed solvability condition that utilizes the inverse of feed-through D term is developed to mitigate the blade flapwise once-per-revolution bending moment together with a standard proportional integral controller in the control loop to assist rotor speed regulation. Simulation studies verify the discussed solvability conditions of DAC and show the effectiveness of the proposed DAC control design methodology.

Switching-type fuzzy controller design by genetic algorithms