Search

Writing formal specifications can help developers understand users' requirements, and build a solid foundation for implementation. But like other activities in software development, it is error-prone, especially for large-scale systems. In practice, effective detection of specification errors still remains a challenge. In this paper, we put forward a rigorous, systematic method for the inspection of model-based formal specifications. The method makes good use of the well-defined consistency properties of a specification to provide precise rules and guidelines for inspection. The inspection process utilizes both well-defined expressions derived from the specification and human inspectors' judgments to find errors. We present a case study of the method by describing how it is applied to inspect an Automated Teller Machine (ATM) software specification to investigate the method's feasibility, and explore potential challenges in using it. We also describe a prototype software tool including its functions and distinct features to demonstrate the tool supportability of the method. [ABSTRACT FROM PUBLISHER]

Experience in all aspects of software engineering has confirmed the pivotal role of focusing on architectural concerns in the development of complex software-intensive systems. Consequently, the past 20 years has seen significant investments in the theory and practice of software architecture. However, architectural deficiencies are frequently cited as a key factor in the shortcomings and failures that lead to unpredictable delivery of complex operational systems. Here, we consider the art and science of software architecture: we explore the current state of software architecture, identify key architectural trends, and directions in academia and industry, and highlight some of the architectural research challenges which need to be addressed. The paper proposes a detailed agenda of research activities to be carried out by a partnership between academia and industry. While challenges exist in many domains, for this paper we draw examples from one area of particular concern: safety-critical systems. [ABSTRACT FROM AUTHOR]

Presents summaries of the uses of formal methods in software development organized by the Association for Information Technologies (AIT). Basis of the paper on the premise ethat formal methods are valuable to industry; Significance of their introduction in representing a significant step in the evolution of software development towards a true engineering discipline.

The UK has long been in the grip of a supposed IT skills shortage. But is there really a shortage of people, or is there instead a lack of good management, professional discipline and productivity? John McDermid takes a fresh look at the issue [ABSTRACT FROM PUBLISHER]