Transforming an enterprise model into a use case model using existing heuristics

Siqueira, Fábio Levy; Silva, Paulo Sérgio Muniz

doi:10.1109/modre.2011.6045363

Cited by 5 publications

(2 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…According to Bezivin (2006), a metamodel outlines the organization, relationships, and limitations of the different components in a model. By doing so, metamodels enable model transformation tools to apply transformation operations to models more efficiently (Siqueira and Silva, 2011). Model is an instance of a metamodel.…”

Section: Metamodelsmentioning

confidence: 99%

Untitled

2023

UsaConf

View full text Add to dashboard Cite

АННОТАЦИЯВ данной статье расмотрена культурная и историческая роль героя Советского Союза -Маншук Маметовы. Рассмотрены культурные 14 произведения посвященные прославленной юной девушке Казахстана, а также людям войны и труда.

show abstract

Section: Metamodelsmentioning

confidence: 99%

Untitled

2023

UsaConf

View full text Add to dashboard Cite

show abstract

“…Other works have focused on facilitating the derivation of system requirements from business processes. In Dijkman and Joosten (2002), Stolfa and Vondrak (2006), and Siqueira and Silva (2011), the authors define mappings that use business processes modeled with Activity Diagrams or BPMN as the basis to identify actors, use cases, and some of the relationships between use cases. Likewise, in de la Vara and Sánchez (2009), functional requirements, represented as Task Descriptions, are derived from business processes modeled with BPMN.…”

Section: Related Workmentioning

confidence: 99%

Modeling Business and Requirements Relationships to Facilitate the Identification of Architecturally Significant Requirements

Berrocal

García-Alonso

Murillo

2014

International Journal of Software Innovation

View full text Add to dashboard Cite

In architectural decision making, the architects have to acquire a complete picture of the system. This picture is obtained analysing the business information and the system requirements. The relationships between business elements or between requirements are particularly important to know the impact of each quality requirement on the system. However, due to the focus of each artefact and notation on documenting specific elements, the relationships between elements of different kind are kept implicit. This requires an in-depth analysis of the models generated on the part of the architect in order to make them explicit. Misunderstandings that take place during this stage can lead to an incorrect design. Here, a set of BPMN and UML profiles to explicitly represent these relationships is presented, together with a model for documenting how each non-functional requirement impacts on the system views. Thus, more information is provided to the architect, thereby decreasing the risk of misinterpretation.

show abstract