An Industrial System Engineering Process Integrating Model Driven Architecture and Model Based Design

2012 ◽  
pp. 810-826 ◽  
Author(s):  
Andrea Sindico ◽  
Marco Di Natale ◽  
Alberto Sangiovanni-Vincentelli
Keyword(s):  
System Engineering ◽  
Industrial System ◽  
Engineering Process ◽  
Model Driven Architecture ◽  
Model Driven ◽  
Model Based

Modellbasierte Entwicklung von Web 2.0-Anwendungen mit MDA™ (Model-Based Development of Web 2.0 Applications with MDA)

i-com ◽  
2007 ◽  
Vol 6 (1) ◽  
pp. 28-32
Author(s):  
Roland Petrasch
Keyword(s):  
Web 2.0 ◽  
Model Driven Architecture ◽  
Model Driven ◽  
Model Based

Modellbasierte Software-Entwicklung wie die Model Driven Architecture der OMG eignet sich für Anwendungssysteme, bei denen die fachliche Essenz von den technischen Details zu trennen und dabei ein hoher Grad an Automatisierung erwünscht ist, denn die Vermischung von fachlichen Aspekten (Anwendersicht) mit den implementationsspezifischen Details (Entwicklersicht) erschwert (nicht nur) bei Web 2.0 die Wartbarkeit, Wiederverwendbarkeit und Portabilität der Software. Modellbasierte Software-Entwicklung ermöglicht den Austausch von Technologien bzw. Plattformen – unter Beibehaltung der fachlichen Modelle. Dieser Beitrag zeigt an einem einfachen Beispiel, wie aus einer „alten” Web-Anwendung eine Software unter Verwendung von AJAX für das Web 2.0 entstehen kann, ohne dass eine komplette Neuentwicklung stattfindet.

Designing the database for a reliability aware Model-Based System Engineering process

2013 ◽  
Vol 111 ◽  
pp. 171-182 ◽  
Author(s):  
Robin Cressent ◽  
Pierre David ◽  
Vincent Idasiak ◽  
Frederic Kratz
Keyword(s):  
System Engineering ◽  
Engineering Process ◽  
Model Based

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