Variability Expression within the Context of UML

2011 ◽  
pp. 322-349 ◽  
Author(s):  
Patrick Tessier ◽  
Sébastien Gerard ◽  
François Terrier ◽  
Jean-Marc Geib
Keyword(s):  
Product Line ◽  
Effective Solution ◽  
Time To Market ◽  
Uml Profiles ◽  
Software Engineers ◽  
Parameterized Model ◽  
Model Variability ◽  
Uml Models ◽  
The Way

Time-to-market is one of the most severe constraints imposed on today’s software engineers. The increasing complexity of systems has also shortened the time available for designing them. Several solutions have therefore been proposed to decrease the time and cost of producing applications. This chapter presents the product line paradigm as an effective solution for managing both the variability of products and their evolutions. The product line approach calls for designing a generic and parameterized model that specifies a family of products. It is then possible to instantiate a member of that family by specializing the “parent” model or “framework.” In describing the latter, designers need to explicitly model variability and commonality points among applications. The following discussion explains in detail how UML models express these different requirements. We then describe specific extensions of UML profiles and the way they are used in various product line methodologies.

scholarly journals A universal CAR-NK cell approach for HIV eradication

2021 ◽  
Vol 5 (3) ◽  
pp. 192-194
Author(s):  
Arosh S. Perera Molligoda Arachchige ◽  
Keyword(s):  
Drug Development ◽  
Hiv Infection ◽  
Nk Cells ◽  
Cancer Immunotherapy ◽  
Nk Cell ◽  
Therapeutic Drug ◽  
Effective Solution ◽  
Hiv Eradication ◽  
Novel Approaches ◽  
The Way

<abstract> <p>No therapeutic drug has been able to completely eradicate HIV-infection so far, even after decades of research. A major challenge in HIV drug development is its immense diversity. NK cells are well-known for their anti-viral and anti-tumor functions. Since recently, NK cells have gained interest of researchers as they have paved the way for novel approaches in controlling HIV-infection supported by promising results observed in cancer immunotherapy trials. Here we report an anti-DNP CAR-NK cell approach introduced by Lim et al. capable of recognizing 2,4-dinitrophenyl tagged to anti-gp160 antibodies, which seemingly provides an effective solution to counteract HIV variability.</p> </abstract>

scholarly journals Adapting the unified software development process for user interface development

2006 ◽  
Vol 3 (1) ◽  
pp. 33-52 ◽  
Author(s):  
Zeljko Obrenovic ◽  
Dusan Starcevic
Keyword(s):  
User Interface ◽  
Human Computer Interaction ◽  
User Interfaces ◽  
Multimodal Interfaces ◽  
Software Developers ◽  
Software Engineers ◽  
Unified Process ◽  
Uml Models ◽  
Computer Interaction

In this paper we describe how existing software developing processes, such as Rational Unified Process, can be adapted in order to allow disciplined and more efficient development of user interfaces. The main objective of this paper is to demonstrate that standard modeling environments, based on the UML, can be adapted and efficiently used for user interfaces development. We have integrated the HCI knowledge into developing processes by semantically enriching the models created in each of the process activities of the process. By using UML, we can make easier use of HCI knowledge for ordinary software engineers who, usually, are not familiar with results of HCI researches, so these results can have broader and more practical effects. By providing a standard means for representing human computer interaction, we can seamlessly transfer UML models of multimodal interfaces between design and specialized analysis tools. Standardization provides a significant driving force for further progress because it codifies best practices enables and encourages reuse, and facilitates inter working between complementary tools. Proposed solutions can be valuable for software developers, who can improve quality of user interfaces and their communication with user interface designers, as well as for human computer interaction researchers, who can use standard methods to include their results into software developing processes.

Evolution and Maintenance of Web Sites

2011 ◽  
pp. 255-271
Author(s):  
Rafael Capilla ◽  
Juan C. Duenas
Keyword(s):  
Web Sites ◽  
Systems Development ◽  
Product Line ◽  
Software Systems ◽  
Software Products ◽  
Software Companies ◽  
Software Engineers ◽  
The Common ◽  
Common Architecture ◽  
The Web

In this chapter we describe the product line models, and show how to apply them for developing and evolving Web products. A product line captures the common and variable aspects of software systems as key assets under a common architecture. Software companies are increasingly adopting this approach in order to accelerate the development of families of similar software products. In certain domains, such as the Web systems, development and maintenance operations are required more often. New techniques to engineer Web sites are needed in order to reduce the time to market for the Web products and to maintain the systems afterward. The authors believe that understanding the notion of lightweight product line and the role that the architecture plays will help software engineers in the construction of software products, and they will be able to manage the evolution effectively against future changes.

Adding More Agility to Software Product Line Methods

2014 ◽  
Vol 5 (4) ◽  
pp. 17-34 ◽  
Author(s):  
Kun Tian
Keyword(s):  
Cost Effective ◽  
Software Product Line ◽  
Product Line ◽  
Time To Market ◽  
Engineering Software ◽  
Software Product ◽  
Agile Practices ◽  
Market Needs ◽  
Development Methods ◽  
Development Application

Software Product Line Methods (SPLMs) have been continuously gaining attention, especially in practice, for on one hand, they address diverse market needs while controlling costs by planned systematic reuse in core assets development (domain engineering), and on another hand, they reduce products' time-to-market, achieving a certain level of agility in product development (application engineering). More cost-effective and agile as they are than traditional development methods for producing families of similar products, SPLMs still seem to be heavy weight in nature. In SPLMs, significant up-front commitments are involved in development of a flexible product platform, which will be modified into a range of products sharing common features. Agile Methods (AMs) share similar goals with SPLMs, e.g., on rapidly delivering high quality software that meets the changing needs of stakeholders. However, they appear to differ significantly practices. The purpose of this work is to compare Agile and Software Product line approaches from fundamental goals/principles, engineering, software quality assurance, sand project management perspectives, etc. The results of the study can be used to determine the feasibility of tailoring a software product line approach with Agile practices, resulting in a lighter-weight approach that provides mass customization, reduced time-to-market, and improved customer satisfaction.

An Industrial Case Study on Managing Variability with Traceability in Software Product Lines

2015 ◽  
Vol 3 (1) ◽  
pp. 1-15 ◽  
Author(s):  
Taeho Kim ◽  
Sungwon Kang
Keyword(s):  
Product Line ◽  
Washing Machine ◽  
Product Lines ◽  
Industrial Case Study ◽  
Rapid Product Development ◽  
Software Product ◽  
Software Engineers ◽  
Requirement Changes ◽  
Line Engineering

In order to successfully carry out software product line engineering, it is important to manage variability and explicit traceability management of variabilities with development artifacts. Trace links of variability with development artifacts allows software engineers to have rapid product development and reduces maintenance efforts resulting from requirement changes or defect corrections as trace links improve the understandability of their side effects. In this study, the authors present a Variability Tracing Approach (VTA), which consists of variability analysis, variability classification, and variability implementation. The proposed approach is applied to developing the development of a washing machine software platform. This paper describes the results of how a member product can be configured under the proposed VTA.

scholarly journals Towards UML representation for BPMN and DMN models

2019 ◽  
Vol 252 ◽  
pp. 02007 ◽  
Author(s):  
Anna Suchenia ◽  
Paweł Łopata ◽  
Piotr Wiśniewski ◽  
Bernadetta Stachura-Terlecka
Keyword(s):  
Process Model ◽  
Business Models ◽  
Unified Modeling Language ◽  
Consistency Checking ◽  
Functional Requirements ◽  
Unified Modeling ◽  
Management Group ◽  
Design Alternatives ◽  
Software Engineers ◽  
Uml Models

Unified Modeling Language (UML) is a standardised Object Management Group (OMG) notation among software engineers. There have been many attempts to design alternatives to UML. Recently, new notations such as Business Process Model and Notation (BPMN) and Decision Model and Notation (DMN) have been proposed for modelling processes and decisions. These dedicated notations provide a simpler way of capturing functional requirements in a designer-friendly fashion. Moreover, some concepts as rules cannot be directly modelled in UML. Our research considers a method of translating business models such as BPMN and DMN into a set of consistent UML models, which can be later used by business analysts and developers to understand and implement the system. As a single notation design, it allows the user to take advantage of software supporting UML modelling and consistency checking, in addition using such translation can provide additional insights into OMG business models. Furthermore, the design provided in a single notation can be easier to follow and develop. This approach supports also visualisation of rules. It is important to mention that the proposed solution does not extend any custom UML artifacts and can be used with standard UML tools.

Online Examination System for Microsoft Office Software Operations

2013 ◽  
Vol 756-759 ◽  
pp. 911-915
Author(s):  
Lin Lin Li ◽  
Liang Xu Sun
Keyword(s):  
Effective Solution ◽  
Work Efficiency ◽  
Examination System ◽  
Computer Lab ◽  
Online Examination ◽  
Actual Operation ◽  
Evaluation Problem ◽  
Microsoft Office ◽  
Office Software ◽  
The Way

online examination is an effective solution to the level evaluation problem for computer basic operations. This paper proposed an online examination system for computer basic operations, especially, Microsoft Office software operations. The system mainly achieved functions including making exams intelligently, collecting and marking documents submitted automatically in the exam by the database, socket, ado and VBA program methods. This system supported some kinds of Microsoft Office software including Word, Excel, PowerPoint and Access. The actual running result showed the system could help teachers to improve work efficiency and students to improve software operations by the way of online actual operation in computers. The system has been running in the USTL university computer lab center for some times which has already proved that it was very valid to solve level evaluation problem for Microsoft Office software operations.

scholarly journals DevOps-Driven Approach to Development in Cloud

2021 ◽  
Author(s):  
Anita Nair
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Service Oriented Architecture ◽  
Architectural Style ◽  
Time To Market ◽  
Development Life Cycle ◽  
Service Oriented ◽  
Software Development Life Cycle ◽  
Waterfall Model ◽  
The Way

<div> <p>DevOps, a prevalent terminology in organizations today, has evolved as a paradigm that once was SDLC. From the mammoth concept of the “WaterFall Model” to the more recent Agile Framework and the emerging DevOps methodology, the Software Development Life Cycle saw a huge business win in “Time to market”, over several other advantages like risk aversion, flexibility, requirement readjustments, collaboration etc. to name a few. This whitepaper elaborates on the various salient features of DevOps that shapes the way software releases are made today. DevOps is most suited to Cloud and this paper explains the way the two technologies synergize. Service Oriented Architecture is an architectural style that is essential in simplifying the business and this paper explains how DevOps facilitates creation of granular services that ultimately helps in attaining flexibility and agility of development and operations in Cloud.</p> </div>

scholarly journals Organizational Culture and Organizational Commitment in Software Product Line Institutionalization: the Perspective of Organizational Change

2019 ◽  
Vol 8 (12) ◽  
pp. 2603-2607
Keyword(s):  
Organizational Culture ◽  
Organizational Commitment ◽  
Software Product Line ◽  
Product Line ◽  
Equation Modeling ◽  
Survey Method ◽  
Software Product ◽  
Software Engineers ◽  
Cultural Types ◽  
The Relationship

This study aims to investigate what factors of organizational culture are associated with successful institutionalization of software product line and to explore if organizational commitment has a mediation effect on the relationship between these factors of organizational culture and software product line performance. To do this, this study collected data from 352 employees of a Korean company by survey method. Also, a structural equation modeling has been taken. As a result, as a result of the three organizational cultural types first proposed to take into account the features of the software engineer, result-oriented culture, open system culture, and employee-centered culture increase their commitment to the organization. Second, software engineers' emotional commitment to organizations improves SPL performance. Finally, software engineers' emotional, organizational commitments mediate the relationship between employee-centric culture and SPL performance. This study is the first one to show the organizational culture types associated with psychological contracts and to understand how these organizational cultural types affect software product line performance through organizational commitment. The results of this study provide conceptual insight to administrators who want to find organizational culture types without sacrificing software product line performance.

Adding More Agility to Software Product Line Methods

2018 ◽  
pp. 1294-1311
Author(s):  
Kun Tian
Keyword(s):  
Cost Effective ◽  
Software Product Line ◽  
Product Line ◽  
Time To Market ◽  
Engineering Software ◽  
Software Product ◽  
Agile Practices ◽  
Application Engineering ◽  
Market Needs ◽  
Development Methods

Software Product Line Methods (SPLMs) have been continuously gaining attention, especially in practice, for on one hand, they address diverse market needs while controlling costs by planned systematic reuse in core assets development (domain engineering), and on another hand, they reduce products' time-to-market, achieving a certain level of agility in product development (application engineering). More cost-effective and agile as they are than traditional development methods for producing families of similar products, SPLMs still seem to be heavy weight in nature. In SPLMs, significant up-front commitments are involved in development of a flexible product platform, which will be modified into a range of products sharing common features. Agile Methods (AMs) share similar goals with SPLMs, e.g., on rapidly delivering high quality software that meets the changing needs of stakeholders. However, they appear to differ significantly practices. The purpose of this work is to compare Agile and Software Product line approaches from fundamental goals/principles, engineering, software quality assurance, sand project management perspectives, etc. The results of the study can be used to determine the feasibility of tailoring a software product line approach with Agile practices, resulting in a lighter-weight approach that provides mass customization, reduced time-to-market, and improved customer satisfaction.

Sign in / Sign up

Export Citation Format

Share Document