scholarly journals Testing and Traceability Aspects in the Context of the Model Driven Architecture (MDA)

2010 ◽  
Vol 41 (1) ◽  
pp. 52-59 ◽  
Author(s):  
Andrejs Grave
Keyword(s):  
Software Development ◽  
Software Systems ◽  
Development Projects ◽  
Problem Domain ◽  
Model Driven Architecture ◽  
System Description ◽  
Model Driven ◽  
Definition Of ◽  
Description Technique

Testing and Traceability Aspects in the Context of the Model Driven Architecture (MDA) With the growth of complexity of the software systems it becomes more complicated to ensure and evaluate quality of the software being built. This paper discusses quality of the software in the context of the Model Driven Architecture. Paper analyses factors that affect quality of the software in the software development projects that are developed using MDA. As one of the important factor that affects quality of the software, is traceability. This paper provides description of the traceability property and importance of it within development of the software. Within context of this paper traceability is considered as a property of a system description technique that allows changes in one of the system descriptions to be traced to the corresponding portions of the other descriptions. This paper is focused on such aspects of the software development as testing and traceability in the context of MDA. Paper contains in review of traceability, MDA and traceability within MDA. Also paper contains description of the method for formal definition of the problem domain - called Topological functioning modeling for model driven architecture (TFMfMDA). This paper introduces method of the application of the TFM as the traceability tool. TFM as the traceability tool can be used to analyze impact of the changes and select most important tests.

A method for investigating the quality of evolving object-oriented software using defects in global software development projects

2016 ◽  
Vol 28 (8) ◽  
pp. 622-641 ◽  
Author(s):  
Ronald Jabangwe ◽  
Claes Wohlin ◽  
Kai Petersen ◽  
Darja Šmite ◽  
Jürgen Börstler
Keyword(s):  
Software Development ◽  
Object Oriented ◽  
Global Software Development ◽  
Development Projects

Transformation of Platform-Independent Model into Platform-Specific Model in Model-Driven Architecture

2013 ◽  
pp. 88-113
Author(s):  
Yashwant Singh ◽  
Manu Sood
Keyword(s):  
Software Development ◽  
Development Strategy ◽  
Specific Model ◽  
Relational Model ◽  
Model Transformations ◽  
Model Driven Architecture ◽  
Model Driven ◽  
Management Group ◽  
Enterprise Java Bean ◽  
Independent Model

The Model-Driven Architecture approach to software development uses transformation models for transforming Platform-Independent Models (PIM) into Platform-Specific Models (PSM) as its core software development strategy. The Model-Driven Architecture (MDA) approach and corresponding standards of the software development based on models have been initiated by the Object Management Group. In this chapter, the authors analyze the basic models of MDA (i.e., Computational Independent Model [CIM], PIM, and PSM) using a suitable example and formalize the model transformations for transforming PIM into PSM. These transformations have been illustrated through the generation of a Relational Model, an Enterprise Java Bean (EJB) Model, and a Web Model from PIM for the example under consideration, using UML profile, and keeping in mind the property of reusability of models in MDA transformations. The focus has been on the specification and formalization of rules needed to get the Relational PSM, EJB PSM, and Web PSM from PIM. A transformation tool, whose functionality of transformation of PIM into Relational PSM, EJB PSM, and Web PSM, is illustrated in this chapter.

Open Source Software Systems

2010 ◽  
pp. 439-459
Author(s):  
R. B. Lenin ◽  
S. Ramaswamy ◽  
Liguo Yu ◽  
R. B. Govindan
Keyword(s):  
Software Development ◽  
Software Systems ◽  
The Internet ◽  
Development Projects ◽  
Work Processes ◽  
High Quality ◽  
Software Products ◽  
Geographic Boundaries ◽  
Doing Business ◽  
Development Costs

Complex software systems and the huge amounts of data they produce are becoming an integral part of our organizations. We are also becoming increasingly dependent on high quality software products in our everyday lives. These systems ‘evolve’ as we identify and correct existing defects, provide new functionalities, or increase their nonfunctional qualities - such as security, maintainability, performance, etc. Simultaneously, more software development projects are distributed over multiple locations (often globally) and are often several millions of dollars in development costs. Consequently, as the Internet continually eliminates geographic boundaries, the concept of doing business within a single country has given way to companies focusing on competing in an international marketplace. The digitalization of work and the reorganization of work processes across many organizations have resulted in routine and/or commodity components being outsourced.

Pair Modeling

2010 ◽  
pp. 1171-1178 ◽  
Author(s):  
Pankaj Kamthan
Keyword(s):  
Software Development ◽  
Software Process ◽  
Software Systems ◽  
Model Driven ◽  
Model Driven Approach

We model software for a variety of reasons: to assess the viability of or plan software systems to be built, to optimize use of (minimize, or ideally, avoid waste of) resources in response to inevitable changes in business, social, or technological environments, or simply to understand existing software systems. Indeed, as indicated by the model-driven approach to software development (Beydeda, Book, & Gruhn, 2005), models are becoming first-class members of organizations and software process environments that embrace them. The examples of collaboration in implementation of software are well-known (Nosek, 1998; Williams & Kessler, 2003). As models get large and complex, the need for creating them collaboratively in a systematic manner arises, and we propose pair modeling as an approach.

Integrating Quality Criteria and Methods of Evaluation for Software Models

2009 ◽  
pp. 2728-2743
Author(s):  
Anna E. Bobkowska
Keyword(s):  
Software Development ◽  
Quality Criteria ◽  
Integrated Approach ◽  
Specific Situation ◽  
Modeling Languages ◽  
Model Driven ◽  
Software Models ◽  
Methods Of Evaluation ◽  
Model Driven Software Development

Successful realization of the model-driven software development visions in practice requires high quality models. This chapter focuses on the quality of models themselves. It discusses context-free and context-dependent quality criteria for models and then moves on to methods of evaluation which facilitate checking whether a model is good enough. We use linguistic theories to understand groups of criteria and their impact on other models, software product and the process of software development. We propose a strict distinction of the impacts of visual modeling languages, models of the system and tools for quality criteria. This distinction is helpful when designing the methods of evaluation and making decision about the point in time, scope and personnel responsible for quality assessment. As the quality criteria and several methods of evaluation has usually been considered separately we propose a methodology which integrates them. Such an integrated approach provides the following benefits. It allows for designing methods of evaluation based on quality criteria and elements of the model (or modeling language) in the context of specific needs. It can be applied for management of the scope of evaluation with quality criteria as well as configuration of the method to a specific situation. It allows for flexible and efficient conduct of the evaluation with selection of the methods of evaluation. Finally, this chapter presents case studies which illustrate the approach.

Research on Model Driven Architecture

2010 ◽  
Vol 40-41 ◽  
pp. 1012-1015
Author(s):  
Yuan Yuan Zhang ◽  
Qin Gao ◽  
Heng Liang Wu
Keyword(s):  
Software Development ◽  
Basic Concept ◽  
Development Process ◽  
Software Development Process ◽  
Model Driven Architecture ◽  
Model Driven ◽  
Design And Implementation ◽  
Level Of Abstraction ◽  
Core Technology ◽  
Architecture Specification

Model driven architecture (MDA) is an architecture specification of software development proposed by OMG in July 2001. MDA holds that the best way of software development is to enhance the level of abstraction of the system, isolate the design and implementation of the system, and separate the business conduct, so as to overcome the difficulties caused by the complexity of software. This paper presents the basic concept and core technology, and gives the software development process based on MDA.

Sign in / Sign up

Export Citation Format

Share Document