Automated traceability analysis for UML model refinements

Briand, Lionel C.; Labiche, Yvan; Yue, Tao

doi:10.1016/j.infsof.2008.06.002

Cited by 34 publications

(27 citation statements)

References 28 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Some researchers have proposed model based regression approaches. Reference [17] proposed a test case generation technique for UML designs using the symbolic execution method. Reference [18] presented a safe regression technique that used various UML diagrams.…”

Section: Related Workmentioning

confidence: 99%

Extracting The Minimized Test Suite for Revised Simulink/Stateflow Model

Park¹,

Park²,

Chung³

et al. 2017

IJAIA

View full text Add to dashboard Cite

show abstract

Section: Related Workmentioning

confidence: 99%

Extracting The Minimized Test Suite for Revised Simulink/Stateflow Model

Park¹,

Park²,

Chung³

et al. 2017

IJAIA

View full text Add to dashboard Cite

show abstract

“…To further investigate the properties of interaction events, and their weighted influence on the relevance of entities in a collaboration space, we performed a study of CVS records associated with real development projects. 5 open source projects were analysed. Only artefact checkins with version repositories associated with more than one project member were considered.…”

Section: Modelling Traceability As Belief Networkmentioning

confidence: 99%

“…Briand et al [5] investigated the problem of traceability in model-driven development practices by monitoring users' modifications. Trace links are identified by first determining the intent of the designer that lay behind changes when models are refined.…”

Section: Review Of Related Workmentioning

confidence: 99%

Exploring a Bayesian and linear approach to requirements traceability

Omoronyia

Sindre

Stålhane

2011

Information and Software Technology

View full text Add to dashboard Cite

For large software projects it is important to have some traceability between artefacts from different phases (e.g., requirements, designs, code), and between artefacts and the involved developers. This is especially critical during maintenance, when people working on the software may be different from the original developers and therefore have a harder struggle to understand the artefacts and the consequences of changes. However, if the capturing of traceability information during the project is felt as laborious to the original developers, they will often be sloppy in registering the relevant traceability links so that the information is incomplete. This makes automated toolbased collection of traceability links a tempting alternative, but this has the opposite challenge of generating too many potential trace relationships, not all of which are equally relevant. A key issue is therefore how to rank such auto-generated trace relationships. This paper presents two approaches for such a ranking: a Bayesian technique and a linear inference technique. Both techniques depend on the interaction event trails left behind by collaborating developers while working within a development tool. The advantage of our approach is that it can be used to provide traceability insights that are contextual and would have been much more difficult to capture manually. The outcome of a preliminary study suggest the advantage of the linear approach, we also explore the challenges and potentials of the two techniques. Finally we present some key lessons learnt during this research.

show abstract

“…A modification tool of PIM to keep consistency with PSM is researched. 4 Also, there is no consistency if a developer edits the original model. A developer can keep consistency if a MDA tool generates models from the edited models again.…”

Section: Introductionmentioning

confidence: 99%

Development of a Tool to Keep Consistency between a Model and a Source Code in Software Development Using MDA

Katayama

Kikkawa

Kita

et al. 2017

JRNAL

View full text Add to dashboard Cite

This study improves efficiency of software development using MDA. This paper develops the tool that keeps consistency between a model and a source code in software development using MDA. The tool has two functions: (i) Generating a source code and (ii) Keeping consistency between a model and a source code. A simple ATM example is used in order to confirm effectiveness of the tool. The tool can reduce time and effort to keep consistency between models and a source code.

show abstract

Automated traceability analysis for UML model refinements

Cited by 34 publications

References 28 publications

Extracting The Minimized Test Suite for Revised Simulink/Stateflow Model

Extracting The Minimized Test Suite for Revised Simulink/Stateflow Model

Exploring a Bayesian and linear approach to requirements traceability

Development of a Tool to Keep Consistency between a Model and a Source Code in Software Development Using MDA

Contact Info

Product

Resources

About