Ing. de software

Annals of Software Engineering Volume 10 Comparative Studies of Engineering Approaches for Software Engineering

Guest Editors Dilip Patel, PhD and Yingxu Wang, PhD

1

Table of Contents
Comparative Software Engineering: Review and Perspectives …….…………………………..….. 0 Y. Wang and D. Patel Pinnacles of Software Engineering Technologies Pinnacles of Software Engineering: 25 Years of FormalMethods ……………………….……………… 1 D. Bjorner Object Modelling Languages: An Evaluation and Some Key Expectations for the Future ……..…….. 2 F. Barbier and B. Henderson-Sellers A Comparative Analysis of Hardware and Software Fault Tolerance: Impact on Software Reliability Engineering …………………………………………………..….…………. 3 A. Mili, H. Ammar, B. Cukic and C. Fuhrman From Conceptual Modeling to Requirement Engineering:An Engineering Approach ….…..…………. 4 C. Rolland Software Development Cost Estimation Approaches – A Survey …………………………....………..… 5 B. Boehm, C. Abts and S. Chulani A Comparative Study of Formal Analysis Techniques for Software Architecture Specifications ….…. 6 J. Tsai and K. Xu Three Empirical Studies of a Software Reuse Reference Model …………………………..………….…. 7 D.C. Rine and N. Nada Approaches toSoftware Engineering Software – A Performing Science? …………………………..…………………………………………..…. 8 W. Humphrey Metaphor, Myth and Mimicry: The Bases of Software Engineering ….………………………….…….... 9 A. Bryant Software is Different 10 B. Beizer …………………………………………………………………………………..….…..

Are Software Engineers True Engineers? ……………………………………………………..………..… 11 C. Lewerentz and H. Rust An Approach for Pattern OrientedSoftware Development Based on a Design Handbook ……...….. 12 D. J. Ram, K.N. Anantharaman, K.N. Guruprasad, M. Sreekanth, S.V.G.K. Raju and A. A. Rao Quality Technique Transfer: Manufacturing and Software …………………………………………….... 13 G. A. King Mapping Software: Are We Nearing Standardisation? ………………… …………………………..…… 14 B. Banerjee

2

Comparative Software Engineering: Review and Perspectives – GuestEditors’ Introduction
Yingxu Wang* and Dilip Patel** * Centre for Software Engineering, IVF Argongatan 30, S-431 53, Molndal, Gothenburg, Sweden Tel: +46 31 706 6174, Fax: +46 31 27 6130 Yingxu.Wang@acm.org ** School of Computing, IS, and Mathematics South Bank University 103 Borough Road, London SE1 0AA,UK dilip@sbu.ac.uk

Abstract: Engineering is a set of disciplines seeking solutions forcomplicated problems and systems that could not be done by individuals. The aim of engineering is to repetitively produce complicated artefacts in an efficient way. This paper describes a set of generic engineering principles and an engineering maturity model. With the engineering principles and model, the nature and status of software engineering are analysed. Interesting findings on what softwareengineering can learn from generic engineering principles are presented. This paper intends to show the nature, status and problems of software engineering, as well as its future trends, based on the comparative studies between the generic engineering principles and software engineering practices.
Keywords: Engineering, software engineering, engineering principles, engineering maturity model,nature of software engineering, cross fertilisation

1. “To Be or Not To Be?”
To many professionals engineering means systematic planing, teamwork, rigorous process, repeatability, efficiency. Software professionals have been arguing the term “software engineering” and its implication for three decades since Frits Bauer invented it in 1968 [1-2]. Yet, still some fundamental questions remain, suchas: a. Is software development an engineering discipline? b. Are software developers engineers or craftsmen? There were completely different assertions and opinions on the above issues of “to be or not to be” that is still confusing the academics, practitioners, and students [3 - 7] in software engineering and in the software industry. In investigating these fundamental problems, the authors...