François Coallier

System acquisition based on software product assessment

The procurement of complex software product involves many risks. To properly assess and manage those risks, Bell Canada has developed methods and tools that combine process capability assessment with a static analysis based software product assessment. This paper describes the software product assessment process that is part of our risk management approach. The process and the tools used to conduct a product assessment are described. The assessment is in part based on static source code metrics and inspections. A summary of the lessons learned since the initial implementation in 1993 is provided. Over 20 products totalling more than 100 million lines of code have gone through this process.

Verifying, validating, and measuring the performance of expert systems

Abstract The use of expert systems has increased rapidly during the last few years. There is a growing need for systematic and reliable techniques for evaluating both expert system shells and complete expert systems. In this paper, we discuss evaluation strategies from several points of view: classification, validation, verification, and performance analysis. We note that ther are several respects in which expert system evaluation is similar to software evaluation in general and, consequently, that it may be possible to apply established software engineering techniques to expert system evaluation. In particular, formal analysis is replacing (or enhancing) traditional testing of conventional software. We believe that increasing formalization is an important trend and we indicate ways in which it could be carried further.

How ISO 9001 fits into the software world

ISO 9001, together with its companion guide, ISO 9000-3, is a key standard for many suppliers, but its focus is on the control of manufacturing processes. The author considers how this fits into software development and how ISO 9001 stacks up to the US National Institute of Standards and Technologys Malcolm Baldridge Quality Award and the Software Engineering Institutess Capability Maturity Model.<<ETX>>

Profiling software through the use of metrics

This paper presents an approach to software assessment using a new software tool that integrates most of the known static metrics. A six‐step method shows how to use metrics to obtain a picture of the software project. The method is visual and each step provides graphical representations of the data. Successive integration of data results in normality profiles. Examples illustrate each step. The method is adaptable to various environments and specific applications.

A roadmap for enterprise integration

The ability to provide integration between business functions that may be supported across multiple applications is a critical need for modern organizations. However, problems often emerge from overly ambitious or imprecise requirements resulting from inadequate plans for integrating different systems (legacy or otherwise). This paper analyzes the field of enterprise integration and provides an analysis of the extent of the problem and current trends that address the problem. It identifies gaps in the field, outstanding research issues, and provides an initial roadmap toward a solution.

Thirteen Knights and the Seven-headed Dragon: an interdisciplinary software engineering framework

This paper summarizes the findings of the STEP2002 workshop on Interdisciplinary Software Engineering, which took place on the 6th and 7th of October 2002 in Montreal, Canada. The workshop considered the future of software engineering as an interdisciplinary activity by identifying ideas, models and techniques which are already used in cognate disciplines, and are deemed applicable to software engineering, with the aim of breaking down rigid barriers between disciplines, representations and processes.

A Holistic Approach for the Architecture and Design of an Ontology-Based Data Integration Capability in Product Master Data Management

In the context of a broadened product lifecycle management envi- ronment, a traditional product information management, also referred to as product master data management (P-MDM) needs to be complemented by other MDM domains. Such MDM domains may include Customers, Financials, Sup- pliers, Human Resources, Events and other domains. To satisfy such a transver- sal set of requirements requires a true cross-enterprise semantic integration capability. This capability cannot be met by current off-the-shelf technologies. This paper proposes a research approach that would elicit the definition of a reference architecture and a multi-domain ontology, from research and devel- opment work performed notably in ontology engineering, in both academic and industry domains.

Interdisciplinary influences in software engineering practices

In consideration of the future of software engineering as an interdisciplinary activity, this paper explores the existing coverage of interdisciplinary software engineering areas in established or emerging software engineering frameworks. In particular we investigate the Software Engineering Body of Knowledge (SWEBOK), the Capability Maturity Model (CMM) and related Capability Maturity Model Integration (CMMI), and the Rational Unified Process (RUP). Following the investigation of the interdisciplinary elements of these frameworks we explore potential areas of advancement and opportunities, that is, where and how future body of knowledge, process, and framework revisions might benefit from the interdisciplinary approach.

A product line engineering practices model

This paper describes work in progress towards the elaboration of a Product Line practices model that combines concepts proposed by various authors. The strengths of existing Product Line flameworks and models are summarized and a new model is proposed in the form of 31 Product Line practice areas, grouped in five categories. An important objeclive of this Product Line practices model is that it should be easily incorporated into existing development methodologies, while remaining aligned with existing systems engineering standards.

A strategy for CASE tool standard

The approach of the IEEE Computer Society Task Force on Professional Tools to developing a standard for CASE (computer-aided-software-engineering) tool information exchange is described. This standardization effort has been the main objective of the task force up to now. The two other efforts have been the creation of a CASE tool standard body and a CASE tool database.<<ETX>>