An Event-driven Approach for the Separation of Concerns

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.

Download Full-text

JAVASCRIPT ASYNCHRONOUS PROGRAMMING

HUE UNIVERSITY JOURNAL OF SCIENCE TECHNIQUES AND TECHNOLOGY ◽

10.26459/hueuni-jtt.v128i2b.5104 ◽

2019 ◽

Vol 128 (2B) ◽

pp. 5-16

Author(s):

Tran Thanh Luong ◽

Le My Canh

Keyword(s):

Design Patterns ◽

Source Code ◽

Object Oriented ◽

Exception Handling ◽

Code Smells ◽

Asynchronous Programming ◽

Event Driven ◽

Programming Patterns ◽

The Impact

JavaScript has become more and more popular in recent years because its wealthy features as being dynamic, interpreted and object-oriented with first-class functions. Furthermore, JavaScript is designed with event-driven and I/O non-blocking model that boosts the performance of overall application especially in the case of Node.js. To take advantage of these characteristics, many design patterns that implement asynchronous programming for JavaScript were proposed. However, choosing a right pattern and implementing a good asynchronous source code is a challenge and thus easily lead into less robust application and low quality source code. Extended from our previous works on exception handling code smells in JavaScript and exception handling code smells in JavaScript asynchronous programming with promise, this research aims at studying the impact of three JavaScript asynchronous programming patterns on quality of source code and application.

Download Full-text