scholarly journals A study on dynamic aspects variability in the SOLAR educational software ecosystem

2020 ◽  
Vol 26 (1) ◽  
Author(s):  
Emanuel F. Coutinho ◽  
Carla I. M. Bezerra
Keyword(s):  
Educational Software ◽  
Software Evolution ◽  
Automatic Measurement ◽  
Virtual Learning Environment ◽  
Feature Model ◽  
Software Modeling ◽  
Software Ecosystem ◽  
Software Products ◽  
Feature Diagram ◽  
Software Evolution And Maintenance

Abstract A Software Ecosystem (SECO) refers to a collection of software products with some degree of symbiotic relationship. SOLAR is a Virtual Learning Environment (VLE) that enables the publication of courses and interaction with them among its various users. In this context, SOLAR SECO emerges, where diverse situations of software evolution and maintenance are part of its development process. The aim of this paper is to discuss the dynamic variability of SOLAR educational software ecosystem and software modeling. As an example, dynamic variability aspects of the feature model of SOLAR VLE discussion forum functionality were discussed, one of the most widely used services within SOLAR SECO. As a major conclusion of this work, we identified that the use of the contextual feature diagram allows the study of the dynamic aspects of a system, even more supported by tools to support automatic measurement collection.

scholarly journals Feature Model Configuration Based on Two-Layer Modelling in Software Product Lines

2019 ◽  
Vol 9 (4) ◽  
pp. 2648
Author(s):  
Elham Darmanaki Farahani ◽  
Jafar Habibi
Keyword(s):  
Product Line ◽  
Feature Model ◽  
Functional Requirements ◽  
Product Lines ◽  
Software Products ◽  
Model Configuration ◽  
Software Product ◽  
Software And Hardware ◽  
Application Requirements

The aim of the Software Product Line (SPL) approach is to improve the software development process by producing software products that match the stakeholders’ requirements. One of the important topics in SPLs is the feature model (FM) configuration process. The purpose of configuration here is to select and remove specific features from the FM in order to produce the required software product. At the same time, detection of differences between application’s requirements and the available capabilities of the implementation platform is a major concern of application requirements engineering. It is possible that the implementation of the selected features of FM needs certain software and hardware infrastructures such as database, operating system and hardware that cannot be made available by stakeholders. We address the FM configuration problem by proposing a method, which employs a two-layer FM comprising the application and infrastructure layers. We also show this method in the context of a case study in the SPL of a sample E-Shop website. The results demonstrate that this method can support both functional and non-functional requirements and can solve the problems arising from lack of attention to implementation requirements in SPL FM selection phase.

scholarly journals Design of Self-practice Listening and Supplementary Vocabulary Exercises for a TOEFL-ITP Preparation Course in Vietnam

2017 ◽  
Vol 5 (2) ◽  
pp. 102
Author(s):  
Duy Ngoc Pham ◽  
Thu Thi Xuan Nguyen
Keyword(s):  
Information And Communication Technology ◽  
Communication Technology ◽  
Learning Process ◽  
Educational Software ◽  
Virtual Learning Environment ◽  
Learning System ◽  
Learning And Teaching ◽  
University Of Technology ◽  
Information And Communication ◽  
E Learning

The amount of information to be accumulated at university has been increasing in recent years, so students nowadays are moving towards using computers in the learning process. Application of Information and Communication Technology (ICT), particularly educational software, to facilitate the learning and teaching process has become a more and more popular trend among teachers. In Thai Nguyen University of Technology (TNUT), Vietnam, a multi-disciplinary virtual learning environment (http://e-learning.tnut.edu.vn) has been established on the MOODLE platform. The aim of this paper is to introduce the design of self-practice listening and vocabulary exercises for the TOEFL-ITP preparation course by integrating the exercises designed with the Hot Potatoes and Quizlet into TNUT’s institutional e-learning system. First, the advantages of the e-learning system are discussed. Second, the tools and materials necessary for the design are described. Finally, a suggestion on integrating the listening and vocabulary exercises designed by the Hot Potatoes software and Quizlet into the available e-learning system is introduced.

Addressing Non-Functional Properties in Feature Models: A Goal-Oriented Approach

2014 ◽  
Vol 24 (10) ◽  
pp. 1439-1487 ◽  
Author(s):  
Mehdi Noorian ◽  
Mohsen Asadi ◽  
Ebrahim Bagheri ◽  
Weichang Du
Keyword(s):  
Functional Properties ◽  
Product Line ◽  
Feature Model ◽  
Software Systems ◽  
Feature Models ◽  
Target Domain ◽  
Product Lines ◽  
Software Products ◽  
Software Product ◽  
Goal Models

Software Product Line (SPL) engineering is a systematic reuse-based software development approach which is founded on the idea of building software products using a set of core assets rather than developing individual software systems from scratch. Feature models are among the widely used artefacts for SPL development that mostly capture functional and operational variability of a system. Researchers have argued that connecting intentional variability models such as goal models with feature variability models in a target domain can enrich feature models with valuable quality and non-functional information. Interrelating goal models and feature models has already been proposed in the literature for capturing non-functional properties in software product lines; however, this manual integration process is cumbersome and tedious. In this paper, we propose a (semi) automated approach that systematically integrates feature models and goal models through standard ontologies. Our proposed approach connects feature model and goal model elements through measuring the semantic similarity of their annotated ontological concepts. Our work not only provides the means to systematically interrelate feature models and goal models but also allows domain engineers to identify and model the role and significance of non-functional properties in the domain represented by the feature model.

scholarly journals Why and how to investigate interaction design of software development tools

2015 ◽  
Vol 6 (1) ◽  
pp. 1
Author(s):  
Juliana Jansen Ferreira ◽  
Clarisse Sieckenius de Souza ◽  
Renato Cerqueira
Keyword(s):  
Software Development ◽  
Interaction Design ◽  
Software Modeling ◽  
Modeling Tools ◽  
Inspection Method ◽  
Software Products ◽  
Development Tools ◽  
Long Run ◽  
Software Development Tools

The existence of some relationship between the usability of software development tools and the quality of end users’ interaction with the product these tools contribute to build would not be surprising. Should this be the case, a developer's problematic use experience with these tools would increase the workload of HCI experts, whose aim is to promote high quality user experience with software products. Yet, this connection has not deserved much attention from researchers, and it is unclear how investigations should be conducted to verify if it is true. Our contribution in this paper is a first step in this direction. We propose an inspection method to characterize communicability and usability aspects of software modeling tools. By combining both aspects and articulating our analysis around tool, notations and people, we provide valuable conceptual links that, we argue, may in the long run of subsequent research contribute significantly to verify the (extent of the) relation between HCI quality of development tools and developed products.

scholarly journals Phylogenetic analysis of software evolution, a case study: VE&MINT

2018 ◽  
Author(s):  
Alvaro Ortiz-Troncoso
Keyword(s):  
Phylogenetic Analysis ◽  
Life Cycle ◽  
Open Source ◽  
Software Evolution ◽  
Real Life ◽  
Traditional View ◽  
Software Ecosystem ◽  
Life Project ◽  
Project Governance

Open source projects may face a forking situation at some point during their life-cycle. The traditional view is that forks are a waste of project resources and should be avoided. However, in a wider technological and organisational context, forks can be a way to foster the creation of a software ecosystem. Either way, forking is explicitly allowed by open source licenses. Notwithstanding, methods for quantifying the evolution of forks are currently scarce. The present work attempts to answer the question whether a real-life project has forked. It does so by considering code and organisational characteristics of the project, and analysing these characteristics by applying methods ported from biological phylogenetics. After finding that the project is forked, implications for project governance are discussed.

scholarly journals How do Technical Factors Affect Developers in Mobile Software Ecosystems

2019 ◽  
Author(s):  
Caio Steglich ◽  
Sabrina Marczak ◽  
Rodrigo Santos ◽  
Luiz Pedro Guerra ◽  
Luiz Henrique Mosmann ◽  
...  
Keyword(s):  
Literature Review ◽  
Field Study ◽  
Mobile Devices ◽  
Software Evolution ◽  
Real Life ◽  
Mobile Technologies ◽  
Software Ecosystem ◽  
Software Ecosystems ◽  
Mobile Software ◽  
Technical Factors

The Software Evolution area brings applications to the Mobile era in which users want to use these applications on their mobile devices. A Mobile Software Ecosystem (MSECO) is the kind of ecosystems in which developers build applications to attend the needs of mobile technologies users (e.g., Android and iOS). Literature explains that the capability to attracting and retaining people (i.e., developers and users) is essencial to MSECO sustainability, i.e., to the MSECO survive along the years. In a previous work, we conducted a literature review that identified 6 factors that may influence developers to participate in an MSECO. In this study, we present a Field Study aiming to understand how these 6 identified factors may have influenced practitioners in real life projects.

Sign in / Sign up

Export Citation Format

Share Document