• Aucun résultat trouvé

A Change Management Approach in Product Lines for Use Case-Driven Development and Testing VVS

N/A
N/A
Protected

Academic year: 2021

Partager "A Change Management Approach in Product Lines for Use Case-Driven Development and Testing VVS"

Copied!
1
0
0

Texte intégral

(1)

A Change Management Approach in Product Lines for Use Case-Driven

Development and Testing

Context & Problem Statement

Automotive domain: software development driven by standards

Product line Use case modeling Method: PUM

software verification & validation

V V

.lu

S

Ines Hajri, Arda Goknil, and Lionel C. Briand Interdisciplinary Centre for Security, Reliability and Trust (SnT)

University of Luxembourg

Evolution of requirements and test cases in a family of products

Ad-hoc change management in the context of product lines Use case centric development and requirements-driven testing

Current & Future Activities

Selected Publications

Requirement Configuration Approach: PUMConf

I. Hajri, A. Goknil, L. C. Briand, and T. Stephany. Applying product line use case modeling in an industrial automotive embedded system: Lessons learned and a refined approach. In ACM/IEEE MODELS’15, pages 338–347, 2015.

I. Hajri, A. Goknil, L. C. Briand, and T. Stephany. A requirements configuration approach and tool for use case-driven development. In Software and Systems Modeling Journal (SoSyM), Springer, 2016.

A modeling method for capturing variability information in product line use case and domain models

A change impact analysis approach for product line use case and domain models

An automated regression test selection approach for product line use case and domain models

An automated configuration approach for product specific use case and domain models

Project Goals

1) Context

2) Problem Statement

Elicit Product Line

Use Cases 1

Product Line Use Case Specifications Product Line Use Case

Diagram

Check Conformance for

Diagram and Specifications Update the

Diagram and Specifications

List of Inconsistencies

Model the Domain

Product Line Domain Model 4

3 2 <<s>>

<<p>>

<<p>>

<<m>>

Modeling variability in product line use case and domain

models

Relying on Natural Language Processing (NLP) to automatically report inconsistencies between product line use case diagrams and specifications

PUMConf guides stakeholders in making configuration

decisions in product line models and automatically generates product-specific use case and domain models

Product Line Use Case and Domain Models

Use Case and

Domain Models Use Case and

Domain Models Use Case and

Domain Models

Customer A

for Product X Customer B

for Product X

Customer C for Product X Identify

Commonalities and Variabilities

Configure

Configurator

Reconfigure Reconfigure

evolves

to evolves

to

Reconfigure evolves

evolves evolves

evolves

Change impact analysis for evolving configuration decisions

Change impact analysis for evolving product line use case and domain models

Automated regression test selection for test cases derived from use case models

I. Hajri, A. Goknil, L. C. Briand, and T. Stephany. Incremental Reconfiguration of Product Specific Use Case Models for Evolving Configuration Decisions. In REFSQ’17, pages 1-19, 2017.

Références

Documents relatifs

As part of the approach, we provided (i) a product line modeling methodology centered around use case modeling for document- ing variability in PL use case diagrams and

To accomplish this goal, our proposal is divided into four pillars: (1) a modeling method in which variability infor- mation is explicitly represented in Product Line (PL) use

Our configuration approach builds on our previous work (i.e., Product line Use case Modeling method) and is supported by a tool relying on natural language pro- cessing and

The key charac- teristics of our tool are (1) the consistency checking of PL artifacts by relying on Natual Language Processing, (2) the automated and interactive configuration

Chapter 6 presents an automated classification and prioritization approach, based on our use case- driven modeling and configuration techniques, to support product line testing

This change has the following consequences: (i) the variation point Method of Clearing Error Status should now be considered in subsequent decisions; (ii) the variant use case

However, the applicability of these approaches in the context of security and privacy requirements modeling for mobile apps shows limitations with respect to (1) their support

How- ever, the applicability of these approaches in the context of security and privacy requirements modeling for multi-device software ecosystems shows limitations with respect to