Guidance for Requirements Engineering Processes

International audienceGuidance plays a crucial role in requirements engineering as this task is both ill defined and highly intellectual. Guidance can be provided once the goal to be achieved has been identified. Two kinds of guidance are proposed, point and flow guidance. The former supports the fulfillment of goals whereas the latter helps in goal identification. Guidance is driven by guidelines which we have modelled as processes instantiated from a process meta-model just as any other, normal process is. Finally, guidelines are modular. This makes possible the rapid modification of guidelines. The paper presents the two types of guidance, the corresponding guidelines and the tool environment which supports the enactment of guidelines

La variabilité due à la sensibilité au contexte dans les processus téléologiques

National audienceVariability has proved to be a central concept in different engineering domains, manufacturing, software development etc. in order to develop solutions that can be easily adapted to different organizational settings and different sets of customer at a low price. Teleological processes have, by nature, a high level of variability. Our position is that the integration of "context-awareness" in that kind of processes increases their intrinsic variability with specific criteria. We propose an indicator typology with an usage process and illustrate it with the MAP intentional process model

Modeling the role variability in the MAP process model

International audienceBusiness process modeling is a valuable technique helping organizations to specify their processes, to analyze their structure and to improve their performance. Conventional process modeling techniques are proven to be inefficient while dealing with non-repetitive, knowledge-intensive processes such as Case Management processes. In this work we use the MAP notation to model a Mortgage Approval Process as defined in Banking. To increase the navigability and practical value of map models, we extend the MAP notation with the concepts of Roles, Relations between roles, and Role Configuration Rules

Processus téléologique et variabilité: Utilisation de la sensibilité au contexte

International audienceVariability has proved to be a central concept in different engineering domains, manufacturing, software development etc. in order to develop solutions that can be easily adapted to different organizational settings and different sets of customer at a low price. Teleological processes have, by nature, a high level of variability. Our position is that the integration of "context-awareness" in that kind of processes increases their intrinsic variability with specific criteria. We propose an indicator typology with an usage process and illustrate it with the MAP intentional process model

A Multi-Model View of Process Modelling

International audienceSituatedness of development processes is a key issue in both the software engineering and the method engineering communities, as there is a strong felt need for process prescriptions to be adapted to the situation at hand. The assumption of the process modelling approach presented in this paper is that process prescriptions shall be selected according to the actual situation at hand i.e. dynamically in the course of the process. The paper focuses on a multi-model view of process modelling which supports this dynamicity. The approach builds on the notion of a labelled graph of intentions and strategies called a map as well as its associated guidelines. The map is a navigational structure which supports the dynamic selection of the intention to be achieved next and the appropriate strategy to achieve it whereas guidelines help in the operationalization of the selected intention. The paper presents the map and guidelines and exemplifies the approach with the CREWS-L'Ecritoire method for requirements engineering

A model‐based solution for process modeling in practice environments: PLM4BS

Today's world economic situation is ruled by issues such as reducing cost, improving quality, maximizing profit, and improving and optimizing processes at organizations. In this context, business process management can be an essential strategy, but it is not usually consolidated at software organizations because software process properties involve a complex business process management application on software lifecycle. Consequently, software organizations often focus on Software Process Modeling (SPM), and each involved role performs process execution and orchestration independently and manually. This fact makes software processes maintenance, monitoring, and measurement become difficult tasks. This paper proposes a model‐based approach for SPM taking into account concepts related to process execution, orchestration, and monitoring. It is framed into a model‐driven engineering‐based and toolbased framework: Process Lifecycle Management for Business Software (PLM4BS). We present a SPM metamodel and its concrete syntax (through Unified Modeling Language profiles) that lays the foundation for extending PLM4BS. Its underlying metamodel allows managing processes automatically. Furthermore, PLM4BS improves current state‐of‐the‐art proposals in 6 dimensions: expressiveness, understandability, granularity, measurability, orchestrability, and business variables and rules. Also, PLM4BS has been evaluated in a multiple‐case study, in which the 6 mentioned dimensions were already validated.Ministerio de Economía y Competitividad TIN2016‐76956‐C3‐2‐RMinisterio de Economía y Competitividad TIN2015‐71938‐RED