1 / 11

i* with Aspects: Evaluating Understandability

i* with Aspects: Evaluating Understandability. Ricardo A. Ramos - rar2@cin.ufpe.br Fernanda Alencar - fmra@ufpe.br João Araújo - ja@di.fct.unl.pt Ana Moreira - amm@di.fct.unl.pt Jaelson Castro - jbc@cin.ufpe.br Rosangela Penteado - roangel@dc.ufscar.br. www.cin.ufpe.br/~ler. Motivation.

teigra
Download Presentation

i* with Aspects: Evaluating Understandability

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. i* with Aspects: Evaluating Understandability Ricardo A. Ramos - rar2@cin.ufpe.br Fernanda Alencar - fmra@ufpe.br João Araújo - ja@di.fct.unl.pt Ana Moreira - amm@di.fct.unl.pt Jaelson Castro - jbc@cin.ufpe.br Rosangela Penteado - roangel@dc.ufscar.br www.cin.ufpe.br/~ler

  2. Motivation • When new approaches or methods are proposed, it is necessary to evaluate them, and this evaluation can focus different quality attributes, such as understandability, modularization, and etc. This evaluation will encourage the software engineers to use them with some support about its quality [Kitchenham et al, 1995]. Kitchenham, B., Pickard, L., Pfleeger, A. L. Case Studies for Method and Tool Evaluation. In: IEEE Software, Vol. 12 Nr. 45 (1995).

  3. Objective To evaluate the understandability of i* models. How? • Five concerns of two excerpts of requirements documents are selected. • The first requirements document was modeled by the original i* approach and the other one by i* with aspects. • A set of metrics are applied in both

  4. The Meeting Schedule System In original i* version Response Time Concern

  5. The Meeting Schedule System In i* with aspectsversion Response Time Concern

  6. The Abstract Approach to Measure Requirement Documents Guidelines assist to select measurable artefacts Abstract metrics are instantiates using templates

  7. Instantiated metrics to the Response Time concern

  8. Data Analysis

  9. Data Analysis – Vocabulary Size

  10. Conclusions • This evaluation helps us to infer that the aspect-oriented i* approach could improve the modularity and decrease the total number of requirements structures. • Is important to note that the internal structures and the compositions rules are not evaluated.New evaluations will be performed in this direction.

  11. i* with Aspects: Evaluating Understandability Ricardo A. Ramos - rar2@cin.ufpe.br Fernanda Alencar - fmra@ufpe.br João Araújo - ja@di.fct.unl.pt Ana Moreira - amm@di.fct.unl.pt Jaelson Castro - jbc@cin.ufpe.br Rosangela Penteado - roangel@dc.ufscar.br www.cin.ufpe.br/~ler

More Related