Model Driven Architecture as an Approach for Modeling and Generating Graphical User Interface

2016 ◽  
pp. 651-656
Author(s):  
Sarra Roubi ◽  
Mohammed Erramdani ◽  
Samir Mbarki
Keyword(s):  
User Interface ◽  
Graphical User Interface ◽  
Model Driven Architecture ◽  
Model Driven

scholarly journals Geração automática de testes em um processo de Model Driven Development: um exemplo de utilização da ferramenta Sikuli

2017 ◽  
Vol 9 (4) ◽  
pp. 90
Author(s):  
Romulo De Almeida Neves ◽  
Willian Massami Watanabe
Keyword(s):  
User Interface ◽  
Graphical User Interface ◽  
Model Driven Development ◽  
Code Coverage ◽  
Model Driven ◽  
Model Driven Testing

Contexto: Model Driven Development (MDD) eleva a importância de modelos dentro do ciclo de vida do software, incorporando-os como parte integrante do produto final por meio de técnicas de modelagem e geração de código, com isso, parte da complexidade do software fica escondida dentro de geradores. Problema: Mesmo com a utilização do processo MDD, o custo associado à elaboração de casos de teste ainda é alto. Objetivo: Automatizar a geração de casos de teste incorporando o Model Driven Testing (MDT) em um processo MDD já existente a fim de gerar automaticamente casos de teste de aceitação para um sistema legado. Justificativa: Garantir a qualidade do software gerado através de um processo de geração de código e reduzir o tempo geral do ciclo de vida do software. Método: Foi realizado uma prova de conceito como forma de validar o objetivo deste trabalho e avaliar a efetividade da abordagem de teste utilizando a métrica de Code Coverage dos casos de testes gerados automaticamente. Resultados: Para este estudo foram selecionados cinco Graphical User Interface (GUIs), na qual a GUI Seguradoras obteve 98% de cobertura de código pelos casos de teste, Moeda obteve 94,39%, Fornecedor com 95,04%, Tipo do item com 95,95% e por fim a GUI Classificação Contábil obteve 95,91% de cobertura dos casos de teste.

Use of Business Models within Model Driven Architecture

2009 ◽  
Vol 38 (38) ◽  
pp. 119-130
Author(s):  
Erika Asnina
Keyword(s):  
Business Models ◽  
Business Processes ◽  
Use Cases ◽  
Separation Of Concerns ◽  
Model Driven Architecture ◽  
Model Driven ◽  
Development Processes ◽  
Business Requirements ◽  
Complex Computer ◽  
Independent Model

Use of Business Models within Model Driven Architecture Model Driven Architecture is a framework dedicated for development of large and complex computer systems. It states and implements the principle of architectural separation of concerns. This means that a system can be modeled from three different but related to each other viewpoints. The viewpoint discussed in this paper is a Computation Independent one. MDA specification states that a model that shows a system from this viewpoint is a business model. Taking into account transformations foreseen by MDA, it should be useful for automation of software development processes. This paper discusses an essence of the Computation Independent Model (CIM) and the place of business models in the computation independent modeling. This paper considers four types of business models, namely, SBVR, BPMN, use cases and Topological Functioning Model (TFM). Business persons use SBVR to define business vocabularies and business rules of the existing and planned domains, BPMN to define business processes of both existing and planned domains, and use cases to define business requirements to the planned domain. The TFM is used to define functionality of both existing and planned domains. This paper discusses their capabilities to be used as complete CIMs with formally defined conformity between planned and existing domains.

Sign in / Sign up

Export Citation Format

Share Document