Modeling interactions using role-driven patterns

Dı́az, Isabel; Pastor, Óscar; Matteo, Alfredo

doi:10.1109/re.2005.42

Cited by 16 publications

(15 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…After eliminating duplicates, 361 papers remained to be further investigated. After filtering the results (361 papers) of the electronic search by applying the inclusion/exclusion criteria, we identified 11 papers [6,14,19,21,24,25,36,40,48,51,54] to include. The manual search of journals and conference proceedings yielded an additional six primary studies (i.e., [10,17,18,20,47,49]), and two of them (i.e., [18,49]) are more recent discussions and therefore replaced two of the 11 papers identified from the electronic search (i.e., [19,48]).…”

Section: Statistics From Included Primary Studiesmentioning

confidence: 99%

“…However, two intermediate models (three transformations) are required in this approach (Column 5). For the approach proposed in [14] (first approach in Configuration 4), the transformation from use cases to intermediate models (Step 2) is not described in the paper and therefore the automation of this step is unknown as indicated in the table. The approaches proposed in [45,49] and [17] have been implemented and therefore they are automated approaches.…”

Section: Transformation-automationmentioning

confidence: 99%

“…3.2.1.2). We do not know what requirements preprocessing techniques are applied in the approach proposed in [14], since it is not described in the paper. The approach proposed in [45,49] does not have any requirements preprocessing technique since the transformation from use cases plus a domain model to state machines relies on the template structure of the use cases and the domain model.…”

Section: Transformation-efficiencymentioning

confidence: 99%

“…A ''?'' for approach [14] indicates that the transformation is unknown since it is not discussed in the paper. Only one approach [47] applies pattern-based transformations (denoted as ''P'') and only one approach [6] applies identity transformation (denoted as ''I'').…”

Section: Transformation-efficiencymentioning

confidence: 99%

See 3 more Smart Citations

A systematic review of transformation approaches between user requirements and analysis models

2010

View full text Add to dashboard Cite

Model transformation is one of the basic principles of Model Driven Architecture. To build a software system, a sequence of transformations is performed, starting from requirements and ending with implementation. However, requirements are mostly in the form of text, but not a model that can be easily understood by computers; therefore, automated transformations from requirements to analysis models are not easy to achieve. The overall objective of this systematic review is to examine existing literature works that transform textual requirements into analysis models, highlight open issues, and provide suggestions on potential directions of future research. The systematic review led to the analysis of 20 primary studies (16 approaches) obtained after a carefully designed procedure for selecting papers published in journals and conferences from 1996 to 2008 and Software Engineering textbooks. A conceptual framework is designed to provide common concepts and terminology and to define a unified transformation process. This facilitates the comparison and evaluation of the reviewed papers.One of the basic principles of Model Driven Architecture (MDA) [29] is model transformation. To build a software system, a series of transformations is performed: transformation from requirements to Platform Independent Model (PIM) (the analysis model), transformation from PIM to Platform Specific Model (PSM) (the design model), and transformation from PSM to code. However, the transformation from requirements to an analysis model is not part of the MDA lifecycle, which starts from an analysis model and ends with deployed code [29]. The reason of this exclusion is perhaps that requirements are mostly in a textual form, which is not a model formal enough to be understood by computers. As a result, requirements are not suitable for automated transformations, and only manual heuristics, such as Abbott's heuristics [4], are in general followed [9,32]. However, if a (semi-) automated transformation technology from requirements to an analysis model were devised, it would help fill an important gap in the MDA software development lifecycle.If these transformations can be automated, full traceability from requirements (through PIM and PSM) to the ultimate software code can be obtained at the same time. Traceability is the ability to link requirements to corresponding analysis and design models, code, test cases, and other software artifacts. Traceability is important during software development because it enables engineers to understand the connections between various artifacts of a software system, and it is also used to determine whether

show abstract

Section: Statistics From Included Primary Studiesmentioning

confidence: 99%

Section: Transformation-automationmentioning

confidence: 99%

Section: Transformation-efficiencymentioning

confidence: 99%

Section: Transformation-efficiencymentioning

confidence: 99%

See 2 more Smart Citations

A systematic review of transformation approaches between user requirements and analysis models

2010

View full text Add to dashboard Cite

show abstract

“…Metamorfosis permite la deducción semi-automática del modelo de diagrama de secuencias a partir de la descripción de los casos de uso [110], [118].…”

Section: Diagramas De Secuenciaunclassified