Computer Aided Software Engineering(CASE)for CAD Systems Production

In the paper the basic elements of CAD systems from software point of view are dis-cussed.The creation and next the modification of CAD systems needs specialized software tools.In thepaper the idea computer Aided Software Engineering(CASE)for CAD systems production and practi-cal software realization of such a software tool is considered.The main element of this tool is specialprogram provided for convenient storage and modification of CAD source program.In the paper thesimple examples are presented and discussed.     

Knowledge Based Software Engineering for Software Development

Information revolution means that the software such as MIS developed by software engineers must be capable of rapid adaptation to constantly changing circumstances and demands in order to remain capable of effectively fulfilling their missions. The key to achieve these goals is to maintain an update understanding of the workers＇ requirements, how well thcse are currently met, and how well current and future needs might be met by conceivable solution options. This paper proposes an engineering approach of knowledge based software systems for the development and evolution of software systems. This approach captures the changing requirements of the works, together with the details of the solutions that are intended to meet them, in a repository.     

Development of Software Engineering: A Research Perspective

In the past 40 years, software engineering has emerged as an important sub-field of computer science and has made significant contribution to the software industry. Now it is gradually becoming a new independent discipline. This paper presents a survey of software engineering development from a research perspective. Firstly, the history of software engineering is reviewed with focus on the driving forces of software technology, the software engineering framework and the milestones of software engineering development. Secondly, after reviewing the past academic efforts, the current research activities are surveyed and new challenges brought by Internet are analyzed. Software engineering researches and activities in China are also reviewed. The work in Peking University is described as a representative.     

Empirical Software Engineering Models: Can They Become the Equivalent of Physical Laws in Traditional Engineering?

Traditional engineering disciplines such as mechanical and electrical engineering are guided by physical laws. They provide the constraints for acceptable engineering solutions by enforcing regularity and thereby limiting complexity. Violations of physical laws can be experienced instantly in the lab. Software engineering is not constrained by physical laws. Consequently, we often create software artifacts which are too complex to be understood,tested or maintained. As too complex software solutions may even work initially, we are tempted to believe that no laws apply. We only learn about the violation of some form of "cognitive laws" late during development or during maintenance, when too high complexity inflicts follow-up defects or increases maintenance costs. Initial work by Barry Boehm (e.g., CoCoMo) aimed at predicting and controlling software project costs based on estimated software size. Through innovative life cycle process models (e.g., Spiral model) Barry Boehm also provided the basis for incremental risk evaluation and adjustment of such predictions. The proposal in this paper is to work towards a scientific basis for software engineering by capturing more such time-lagging dependencies among software artifacts in the form of empirical models and thereby making developers aware of so-called "cognitive laws" that must be adhered to. This paper attempts to answer the questions why we need software engineering laws and how they could look like, how we have to organize our discipline in order to build up software engineering laws, what such laws already exist and how we could develop further laws, how such laws could contribute to the maturing of science and engineering of software in the future, and what the remaining challenges are for teaching, research, and practice in the future.     

Secure—I*: Engineering Secure Software Systems through Social Analysis

Engineering secure software systems requires a thorough understanding of the social setting within which the system-to-be will eventually operate. To obtain such an understanding, one needs to identify the players involved in the system's operation, and to recognize their personal preferences, agendas and powers in relation to other players. The analysis also needs to identify assets that need to be protected, as well as vulnerabilities leads to system failures when attacked. Equally important, the analyst needs to take rational steps to predict most likely attackers, knowing their possible motivations, and capabilities enabled by latest technologies and available resources. Only an integrated social analysis of both sides (attackers/protectors) can reveal the full space of tradeoffs among which the analyst must choose. Unfortunately, current system development practices treat design decisions on security in an ad-hoc way, often as an afterthought. This paper introduces a methodological framework based on i^*, for dealing with security and privacy requirements, namely, Secure-i^*. The framework supports a set of analysis techniques. In particular, attacker analysis helps identify potential system abusers and their malicious intents. Dependency vulnerability analysis helps detect vulnerabilities in terms of organizational relationships among stakeholders. Countermeasure analysis supports the dynamic decision-making process of defensive system players in addressing vulnerabilities and threats. Finally, access control analysis bridges the gap between security requirement models and security implementation models. The framework is illustrated with an example involving security and privacy concerns in the design of electronic health information systems.In addition, we discuss model evaluation techniques, including qualitative goal model analysis and property verification techniques based on model checking.     

The 14th Asia-Pacific Software Engineering Conference

Theme： Software Engineering Innovation Everywhere.Tbe fourteenth Asia-Pacific Software Engineering Conference （APSEC） will be held in Nagoya, Japan. APSEC is the leading international conference in software engineering and technology in the Asia-Pacific region. APSEC 2007 will bring together researchers and practitioners from industry, academia, and government to share the state of the art techno- logy in soRwar~ ~ngine, ering and seek to explore emerging challenges in soRware engineering innovation.As the rapid pervading of embedded and ubiquitous software, our lives are increasingly dependent on the software. Software engineering is facing challenges of safety, dependability, sustainability, and other various aspects in the development of such software or the provision of services using the software. Over the next several years, all kinds of embedded, personal, and enterprise application software will be connected together with each other, and will cover the globe. This is expected to bring about a sea change in software engineering.     

Software: Hero or Zero?

People might love to support underdogs, but they also love to kick them when they're down. And, at this point in time at least, software is the world's technological underdog!     

Redesign of a Systems Engineering Language: Formalisation of χ

This paper describes the redesign of a systems engineering language called . This is an engineering language designed to specify and analyse industrial systems. The main objective of this redesign was to enable mathematical reasoning about specifications. We discuss the original language, the requirements and design decisions, and the resulting syntax and semantics of the new version of , called . In particular, we elaborate on semantical aspects of s time model.     

Empirical Research in Software Engineering — A Literature Survey

Empirical research is playing a significant role in software engineering (SE), and it has been applied to evaluate software artifacts and technologies. There have been a great number of empirical research articles published recently. There is also a large research community in empirical software engineering (ESE). In this paper, we identify both the overall landscape and detailed implementations of ESE, and investigate frequently applied empirical methods, targeted research purposes, used data sources, and applied data processing approaches and tools in ESE. The aim is to identify new trends and obtain interesting observations of empirical software engineering across different sub-fields of software engineering. We conduct a mapping study on 538 selected articles from January 2013 to November 2017, with four research questions. We observe that the trend of applying empirical methods in software engineering is continuously increasing and the most commonly applied methods are experiment, case study and survey. Moreover, open source projects are the most frequently used data sources. We also observe that most of researchers have paid attention to the validity and the possibility to replicate their studies. These observations are carefully analyzed and presented as carefully designed diagrams. We also reveal shortcomings and demanded knowledge/strategies in ESE and propose recommendations for researchers.     

The 2008 International Conference on Embedded Software and Systems

July 29-31, 2008, Chengdu, Sichuan, China The goal of ICESS'08 is to provide a forum for scientists, engineers, and researchers to discuss and exchange their new ideas, novel results, work in progress and experiences on all aspects of embedded software and systems. Topics of particular interest include, but are not limited to     

Evaluating Anti-Virus Software: Which Is Best?

Abstract

A few years ago, computer securitymeant protecting yourself fromviruses and changing passwords.Today, computer security is much morecomplex and viruses have fallen to the back-ground. So how does one chose the bestvirus product today? What does one lookfor? This article provides some insight andsuggestions.     

Requirements Engineering f��r Product Service Systems

In recent years, manufacturing companies and service providers have moved towards offering customer-specific problem solutions. These integrated bundles usually consist of hardware, software, and service components and are called product service systems (PSS) or hybrid products. Since the success of the resulting solution depends on the understanding of all requirements, requirements engineering (RE) has become a key factor. The article analyzes the state of the art of RE for PSS based on an extensive literature review in the domains of product-, software-, and service engineering. For this, criteria are derived from the characteristics of PSS and from the task area of RE in the life cycle of PSS. Based on these criteria we analyze the most established RE approaches for their suitability for PSS. An important finding is that integrated/interdisciplinary approaches for RE are missing. Moreover, the maturity of RE approaches in the three domains varies significantly. All analyzed approaches heavily rely on concepts and solution characteristics of their own domain so that a transfer to other domains is hardly possible. This literature review lays the foundation for successful RE for PSS and especially for future research aiming at combining and integrating RE approaches and models of product-, software-, and service engineering. Such requirement models could connect concepts of single domains and enable an integrated and seamless RE for PSS.     

Development and Experience of“Software Project Practice”Course for the Master of Software Engineering

Practice is an important phase in the teaching of software engineering.How to improve students' practical ability is a common problem for many software colleges.The course of Software Project Practice is proposed to enhance students' practical skills.In this course,the students participate in the whole process of software development practice and take the exercise of entrepreneurial project development in their learning stage.     

A Software Tool for Constructing Traditional Chinese Medical Expert Systems

It is an urgent task to hnplemeut a lot of expert systems to capture the valuable expertise ofexperienced doctors of traditional Chinese medicine.In order to meet the needs,a software tool isdeveloped.It features a unified diagnosis model,a specially designed knowledge representationlanguage and an efficient but effective inference engine.To implement an expert system,it isonly necessary to input the expert's knowledge expressed in knowledge representation languagewithout the design of any additional software.The time and effort required for implementing anexpert system are thus greatly saved.The software is very compact and can run onmicrocomputers e.g.IBM-PC/XT.Two traditional Chinese medical expert systems have beensuccessfully implemented with the tool.     

Software development: science,craft or racket?

In the past, software development has been variously described as a science, art, craft, trade, racket, etc. Even today opinions vary considerably about how software should he developed and what qualifications are most appropriate for software developers.In the article the problematic state of affairs in the field of software development today is illustrated. The spectrum of possible software worlds of the future is characterized by its three extremes: an audacious (reckless), a backward (reactionary) and a celestial radical) software future.It is argued that the detailed specification, design and development of computer software is by nature an engineering field. In practice, however, software development is too often treated today as patchwork, conducted by underqualified personnel instead of by professionally educated engineers. This is the major cause of many problems and disappointments that we have been and still are experiencing in applying computer systems.