A text-based visual notation for the unit testing of model-driven tools

2017 ◽  
Vol 49 ◽  
pp. 196-215
Author(s):  
Daniel Strüber ◽  
Felix Rieger ◽  
Gabriele Taentzer
Keyword(s):  
Unit Testing ◽  
Model Driven ◽  
Visual Notation

scholarly journals Towards Model-Driven Unit Testing

2007 ◽  
pp. 182-192 ◽  
Author(s):  
Gregor Engels ◽  
Baris Güldali ◽  
Marc Lohmann
Keyword(s):  
Unit Testing ◽  
Model Driven

Approach to constructing software unit testing tools

1995 ◽  
Vol 10 (6) ◽  
pp. 245 ◽  
Author(s):  
Gang Luo ◽  
Robert L. Probert ◽  
Hasan Ural
Keyword(s):  
Unit Testing ◽  
Testing Tools

Developing a Web-based Application for Energy Supply Systems

2019 ◽  
Vol 2 (3) ◽  
pp. 164-169
Author(s):  
Mohammed Faza ◽  
Maulahikmah Galinium ◽  
Matthias Guenther
Keyword(s):  
Energy Supply ◽  
Power Plants ◽  
Acceptance Testing ◽  
Design Activity ◽  
Unit Testing ◽  
Validity Testing ◽  
Energy Supply System ◽  
Time Series Modelling ◽  
Supply Systems ◽  
Energy Supply Systems

An energy supply system consists of a system of power plants and transmission anddistribution systems that supply electrical energy. The present project is limited to the modellingof the generation system. Its objective is the design and implementation of a web-basedapplication for simulating energy supply systems using the Laravel framework. The projectfocuses on six modules representing geothermal energy, solar energy, biopower, hydropower,storage, and fossil-based energy that are allocated to satisfy a given power demand. It isexecuted as a time series modelling for an exemplary year with hourly resolution. Thedevelopment of the software is divided into four steps, which are the definition of the userrequirements, the system design (activity, use case, system architecture, and ERD), the softwaredevelopment, and the software testing (unit testing, functionality testing, validity testing, anduser acceptance testing). The software is successfully implemented. All the features of thesoftware work as intended. Also, the software goes through validity testing using three differentinput data, to make sure the software is accurate. The result of the testing is 100% accuracy withrespect to the underlying model that was implemented in an excel calculation.

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