Pierre Bourque

• PhD by Published Work
• Professor at École de Technologie Supérieure

Performance is seen as multidimensional parameter by an organization, which can be managed in both a graphical and a transparent manner. Because managing performance targets in software engineering is so critically important, the historical data, analysis models, and tools that take into account the specifics of software development and maintenance...

The Guide to the Software Engineering Body of Knowledge (the SWEBOK Guide) provides generally accepted knowledge for the software engineering profession. The content of the SWEBOK Guide is derived from academic sources and the best practices of the profession. The SWEBOK Guide is a reference document for many academic and industrial curricula, cert...

In the Guide to the Software Engineering Body of Knowledge (SWEBOK® Guide), the IEEE Computer Society establishes a baseline for the body of knowledge for the field of software engineering, and the work supports the Society’s responsibility to promote the advancement of both theory and practice in this field. It should be noted that the Guide does...

The importance and complexity of software systems require software engineers who possess the appropriate skills, knowledge, and experience to develop, maintain, and acquire such systems. Graduate education is key in advancing professional software engineering. The "Graduate Software Engineering 2009 (GSwE2009): Curriculum Guidelines for Graduate De...

The Software Engineering Body of Knowledge (SWEBOK), published in 2004, and now under revision, has influenced many software engineering graduate programs worldwide. In 2009, guidelines were published for graduate programs in software engineering (GSWE2009). GSWE2009, now sponsored by both the IEEE Computer Society and the Association for Computing...

There is a need to collect, measure, and present progress information in all projects, and Agile, Lean and DevOps projects are no exception. In this article, the authors show how the line of balance, a relatively obscure indicator, can be used to gain insights into the progress of projects not provided by burn down charts or cumulative flow diagram...

Agile estimation approaches usually start by sizing the user stories to be developed by comparing them to one another. Various techniques, with varying degrees of formality, are used to perform the comparisons – plain contrasts, triangulation, planning poker, and voting. This article proposes the use of a modified paired comparison method in which...

In this paper, we present the application of a set of software engineering roles. Role definitions were developed using internationally recognized software engineering reference documents for a major railway development organization: Bombardier Transportation. The description of the Software Architect role is explained. This paper will also illustr...

Based on the empirical analysis of data contained in the International Software Benchmarking Standards Group (ISBSG) repository, this paper presents software engineering project duration models based on project effort. Duration models are built for the entire dataset and for subsets of projects developed for personal computer, mid-range and mainfra...

For the past 30 years, various estimation models and tools have been developed to help managers perform estimation tasks. Some of these estimation tools date from the late 1970s, and have been progressively modernized by their vendors in terms of tools' user interfaces and new functions to facilitate not only project estimation but also detailed pr...

Publié dans Génie logiciel Dans le présent article, les auteurs font un tour d'horizon du développement des ontologies. Les ontologies sont d'une grande utilité spécialement pour la communication entre humains, entre humains et agents artificiels et entre systèmes informatiques. En effet, les ontologies mettent à la disposition d'une telle communi...

A major difficulty with current organizational performance models in software engineering management is to represent many possible viewpoints quantitatively and in a consolidated manner, while at the same time keeping track of the values of the individual dimensions of performance. The models currently proposed do not meet the analytical requiremen...

Traceability analysis is a technique that enables the verification of software requirements within the software life cycle. Within a context where there is a lack of common understanding of what must be traced, a number of methods have been proposed to implement software requirements traceability analysis, many of these methods dealing with softwar...

This paper investigates image vector attributes weights in order to detect a scene change in a video. Another objective is the development of an MPEG-7 library for annotating and presenting MPEG-7 documents. The contributions of this paper are: an exploration of the limits of scene identification technique, using the Oracle 10 g database, describin...

A major difficulty with current organizational performance models in software engineering management is to represent many possible viewpoints quantitatively and in a consolidated manner, while at the same time keeping track of the values of the individual dimensions of performance. The models currently proposed do not meet the analytical requiremen...

This position paper addresses the fourth issue submitted to the panel members: the identification of roles for national and international bodies and what actions should they undertake to advance "best practices" in software engineering. In the fifty-odd-year history of software, various methods and techniques, methodologies and tools have been prop...

Software engineering is a new discipline and a new profession. This thesis shows how the author’s published works have contributed to the maturation of software engineering as a discipline and as a recognised profession through research conducted within three themes: the fundamental principles of software engineering, the Guide to the Software Engi...

Publié dans Génie Logiciel On présente ici l’analyse et l’amélioration des définitions de rôles et également l’identification des responsabilités appropriées, des connaissances, et des habilités requises pour chaque rôle d’une équipe de développement de logiciels. Le concept de rôle renvoie à un ensemble de responsabilités définies qui pourraient...

In this paper, we present the results of a project conducted to analyze the coverage of the roles within the Bombardier Engineering System (BES) Software Engineering (SWE) process definition and subsequently improve the role definitions. This is the common software engineering process definition of Bombardier's Transportation division. Role definit...

Currently, components technology represents a major step in the evolution of software technology as a whole. Although it has been undergoing continuous enhancement, this technology suffers from a number of limitations: in particular, components' unused functionalities. For instance, a software component incorporates a set of functions of which a si...

Even though measurement is considered an essential concept in recognized engineering disciplines, measures in software engineering are still far from being widely used. To figure out why software measurement has not yet gained enough peer recognition, this paper presents a set of issues that still have to be addressed adequately by the software mea...

A list of fundamental principles of software engineering is viewed as needed to solidify the foundations of the field, thereby enabling and hastening the maturation of the discipline. Most of the authors who have investigated software engineering principles note that the discipline has a foundation. Some talk about principles, others about concepts...

Software measurement programs are now widely recommended in software engineering, more specifically in support of larger continuous process improvement programs. However, software measurement programs exhibit some of the undesirable characteristics of software development projects in the sense that they are very risky undertakings in themselves. Me...

audiences and plan audiences and plan Research issues 9 Project Objectives Project Objectives Promote a consistent view of software engineering worldwide Clarify the place of, and set the boundary of, software engineering with respect to other disciplines Characterize the contents of the Software Engineering Body of Knowledge - SWEBOK Provide a top...

These guidelines are written to provide assistance to anyone involved in the accreditation of Canadian university programs in computer studies and software engineering. They specify the objectives of accreditation, the various steps in the process, and the essential and highly desirable qualities of accreditable programs. Questions and suggestions...

The SWEBOK guide is a project of the IEEE Computer Society and is designed to characterize the discipline of software engineering and to provide a topical guide to the literature describing the generally accepted knowledge within the discipline. The trial version of the SWEBOK guide has been published in December 2001. The paper reviews a selection...

This paper is the product of a workshop held in Amsterdam during the Software Technology and Practice Conference (STEP 2003). The purpose of the paper is to propose Bloom’s taxonomy levels for the Guide to the Software Engineering Body of Knowledge (SWEBOK) topics for three software engineer profiles: a new graduate, a graduate with four years of e...

This paper presents an experience report on an open and independent assessment of a pilot e-learning course on Microsoft FrontPage. The e-learners in the pilot course were Canadian knowledge workers from various industry sectors. The specifically adapted to e-learning, course evaluation criteria and the fully transparent independent assessment proc...

Articulating a body of knowledge is an essential step toward developing a profession because it represents a broad consensus regarding the contents of the discipline. The IEEE Computer Society, with the support of a consortium of industrial sponsors, has recently published the Guide to the Software Engineering Body of Knowledge (SWEBOK). Throughout...

This paper presents a combined, high-level quality view of TL9000 handbook and ISO/IEC 9126 in the process of defining, measuring, evaluating and finally achieving appropriate quality of user-centered software products. In its practices-related part this paper discusses the benefits, which the use of TL9000 product operational (in-the-field) qualit...

In May 2001, trial version of the guide to the Software Engineering Body of Knowledge (SWEBOK) was released in a Web format and, in December 2001, in book format with the intent to collect comments and possible improvements. Up to now, feedback received confirmed the usefulness of the guide for all documented knowledge areas, with the exception of...

Not Available

This paper is the result of a workshop held in Montreal in October 2002 during the Software Technology and Practice Conference (STEP 2002). The purpose of the paper is to present a preliminary mapping of two related but distinct software engineering body of knowledge initiatives, and also a list of proposals to improve them: the guide to the Softwa...

In May 2001, of the Guide to the Software Engineering Body of Knowledge (SWEBOK) was released in a Web format and, in December 2001, in book format with the intent to collect comments and possible improvements. Up to now, feedback received confirmed the usefulness of the guide for all documented knowledge areas, with the exception of the software c...

The goal of this paper is to highlight differences identified between three Knowledge Areas or chapters of the Guide to the Software Engineering Body of Knowledge and the Rational Unified Process. The differences identified are of two types: terminology differences and topics that can only be found in one or other of the compared documents. The pap...

A set of fundamental principles can act as an enabler in the establishment of a discipline; however, software engineering still lacks a set of universally recognized fundamental principles. This article presents a progress report on an attempt to identify and develop a consensus on a set of candidate fundamental principles. A fundamental principle...

Identifying an agreed body of knowledge is an essential step in moving software engineering from an ideal to a recognized profession. Sponsored by the IEEE Computer Society and managed by the Universite du Quebec a Montreal, the Software Engineering Body of Knowledge (SWEBOK) project is developing a guide to the body of knowledge of software engine...

The IEEE Computer Society and the Association for Computing Machinery are working on a joint project to develop a guide to the Software Engineering Body of Knowledge (SWEBOK). Articulating a body of knowledge is an essential step toward developing a profession because it represents a broad consensus regarding the contents of the discipline. Without...

This paper presents a confirmatory analysis of empirical models that predict software engineering project duration based on project effort, based on a more recent and much larger sample. The models are based on the analysis of project data provided by release 4 of the International Software Benchmarking Standards Group (ISBSG) repository. Duration...

The IEEE Computer Society and the Association for Computing Machinery are working on a joint project to develop a guide to the Software Engineering Body of Knowledge (SWEBOK). Articulating a body of knowledge is an essential step toward developing a profession because it represents a broad consensus regarding the contents of the discipline. Without...

The Guide to the SWEBOK project is ending the Stone Man phase and a first operational version of the Guide will be published in the Spring of 2000. The project team is currently planning the subsequent Iron Man phase which will focus heavily on promoting and experimenting the Guide in various contexts. In order to evaluate the usability and adequac...

This paper proposes a high-level and field tested experimental approach or framework for software engineering. This four-phase experimental framework begins in the definition phase by developing our intuitive understanding of the problem that we wish to solve into a precise specification of an experiment. The sampling design and the appropriate mea...

Not Available

Reporting on the SWEBOK project, the authors-who represent the project's editorial team-discuss the three-phase plan to characterize a body of knowledge, a vital step toward developing software engineering as a profession

Not Available

Not Available

Publié dans Génie Logiciel Les auteurs, membres de l’équipe directrice du projet SWEBOK, décrivent les trois phases de leur projet, qui vise à caractériser un corpus de connaissances, ce qui est une étape essentielle pour amener le génie logiciel au stade de véritable profession.

A requirement for software productivity analysis and estimation is the ability to measure the size of a software product from the user's viewpoint, that is, from a functional perspective rather than from a technical perspective. One example of such a measurement method is Function Point Analysis (FPA). FPA is now widely used in the Management Infor...

IT projects continue to be canceled, delivered late and over budget, fail to deliver what was expected or deliver error-prone results. This state of affairs prevails today despite more than 30 years of evolution in the methods, techniques and tools of information technology, software engineering and project management. It is clear that software pro...

In the 50-year history of software development, various methodologies and techniques have been proposed to facilitate the development of software responsive to needs. Most have proved to be more specific to the then-current state of technology than has been understood at the time. At this time, enough examples have accumulated that we can begin to...

Le génie logiciel ne dispose toujours pas d'un ensemble de principes fondamentaux reconnus par tous. Cet article décrit une démarche qui vise le développement d'un tel ensemble. Un premier atelier de travail tenu à Montréal en 1996 a permis la formulation de critères que devraient rencontrer de tels principes. Suite à cet atelier, une étude Delphi...

This report describes work done by the Software Engineering Management Research Laboratory at the Universit du Qubec Montral and its industrial research partner SELAM to adapt FPA to real-time software. In section 2, we present a short description of FPA as defined by the International Function Point Users Group (IFPUG) version 4.0 (1994). Next, in...