Christophe Gnaho

Web-Based Information Systems Development - A User Centered Engineering Approach

Web-based Information System (WIS) engineering is more complex than traditional Information System (IS) engineering in that it raises many new issues such as presentation issues, user profiling, navigation support etc...This paper presents a method - a set of product models along with process models for the development of WIS.This method adds the dimension of user modeling and customization to Web engineering. By capturing the user profiles, the designer is able to define user categories and to tune the presentation of the WIS content according to the specificity of the user. Besides, by capturing the user goals, he is able to define guidelines for navigating in the Hyperspace in order to optimize the satisfaction of the user needs.Finally, the proposed approach considers, as it does in much traditional software approaches, three different levels of abstraction (conceptual, logical and physical). It also clearly separates the management of potential users data, content design, navigational design and interface design. Such separation of concerns facilitates many maintenance tasks and leads to a higher degree of independence and flexibility.

An electronic handbook for accessing domain specific generic patterns

This work addresses the issues of defining (a) the structure of a knowledge repository of good business practices for managing change in organisations and (b) a Web based tool for providing a simple means for accessing this knowledge. Following the proposal made within the ESPRIT project ELEKTRA*, the expression of best business practices is done in terms of generic patterns. The term ‘pattern’ refers to such knowledge that may be repeatable from one situation to another, and shareable by many different users. The knowledge encapsulated in patterns is expressed in terms of the concepts of the EKD methodology (Enterprise Knowledge Development) such as enterprise goals, enterprise processes etc.. This paper presents the framework for representing the patterns and a set of mechanisms for navigating within the repository of patterns in a WWW environment.

Modeling the Impact of Non-functional Requirements on Functional Requirements

To develop quality software and systems, both functional and non-functional requirements need to be taken into account at the same level of abstraction; and must be traced throughout the development cycle. The concept of goal has been widely used and adopted to represent functional and non-functional requirements. However the issue of the impact of non-functional requirements on functional requirements has been rarely addressed. The aim of this paper is to propose a first contribution to this issue.

Self-adaptive systems requirements modelling: Four related approaches comparison

When developing Self Adaptive Systems (SAS), their highly adaptiveness has to be taken into account as early as the requirements elicitation. Because such systems modify their behaviour at run-time in response to changing environmental conditions, Non Functional Requirements (NFRs) play an important role. One has to identify as early as possible the requirements that are adaptable. Because of the inherent uncertainty in these systems, goal based approaches can help in the development of their requirements. In order to cope with this purpose, we have defined a combined approach based on several requirements modelling techniques. In this paper we use a common case study and well defined comparison criteria to illustrate the way those techniques can benefit from each other. This submission is a synthesis and hence make some reference of more specific requirements models submissions.

Une extension SysML pour l'ingénierie des exigences non fonctionnelles orientée but

This paper describes a work-in-progress in the framework of a research project aiming at defining traceability links between requirements phase and specification phase. The main idea is to extend the SysML language with the most relevant concepts of commonly used requirements engineering approaches. In this paper, we first define a set of SysML extensions to represent basic concepts of KAOS goal model. Then, we present a software tool to support the proposed extensions.

Supporting variability in goal-based requirements

This paper addresses the problem of introducing variability in goal-based requirements. The proposed approach adopts and extends the KAOS goal oriented metamodel with variability concepts. The resulting metamodel is then used to model common and variable requirements at goal level. The application domain is the Cycab, a public vehicle with fully automated driving capability.

Poster: How to Handle Environmental Uncertainty in Goal-Based Requirements Engineering

The objective of this poster paper is to investigate on how to deal with environmental uncertainty in goal based requirements engineering. To do so, we explore the introduction of RELAX concepts into SysMLKaos. RELAX is a Requirements Engineering language for Dynamically Adaptive Systems while SysMLKaos is a Goal based Requirements Engineering approach. We use an extract of a Landing Gear System case study to illustrate the proposed approach.

An Electronic Ekd Method Guide over the Web

In this paper we propose a web based tool called “ The EKD Electronic Guide Book ” which forms the base line of the guidance component of the EKD method. The EKD method proposes a set of models for describing enterprise knowledge for the purpose of handling situations of change such as business process transformation or improvement, information system re-engineering, information system requirements elicitation, etc.. The core of the “ EKD Electronic Guide Book” is a set of process guidelines which constitute the expression of EKD method knowledge and heuristics. These guidelines help in both the understanding of the EKD models concepts and the use of these concepts in the construction of the different EKD models. Following the process modelling approach developed in the ESPRIT project NATURE(Novel Approaches to Theories Underlying Requirements Engineering), they are expressed as the contexts formed of a situation and a decision. The paper describes the structure of the process guidelines repository, the structure of the tool along with its main functionalities. All these are exemplified.