Lifecycles

2019 ◽  
pp. 1-32
Keyword(s):  
Large Scale ◽  
Software Systems ◽  
Software Products ◽  
Product Success ◽  
Product Features ◽  
Lifecycle Model ◽  
Software Product ◽  
Project Risks ◽  
Mission Critical ◽  
Common Understanding

This chapter discusses lifecycle model application for software development. It compares the benefits and shortcomings of different models. The authors argue that there is no universal lifecycle model. For agility, this chapter recommends combining prototyping with the other models. The authors suggest this to achieve a common understanding of the key product features and to reduce project risks. The lifecycle model choice determines project economics and time to market. The model also influences product quality and overall project success. However, product success essentially depends on human factors. The authors analyze the applicability of the lifecycle models to large-scale, mission-critical software systems. Finally, this chapter introduces a methodology. It includes a spiral-like lifecycle and a set of formal models and visual tools for software product development. This methodology helps to optimize the software product lifecycle. It fits large-scale, complex heterogeneous software products.

scholarly journals Fragment-oriented programming: a framework to design and implement software product line domain components

DYNA ◽  
2018 ◽  
Vol 85 (207) ◽  
pp. 74-83 ◽  
Author(s):  
Daniel Correa ◽  
Raúl Mazo ◽  
Gloria Lucia Giraldo Goméz
Keyword(s):  
Software Product Line ◽  
Preliminary Evidence ◽  
Product Line ◽  
Software Systems ◽  
Software Components ◽  
Product Lines ◽  
Reusable Software ◽  
Software Products ◽  
Manual Intervention ◽  
Software Product

Software product lines facilitate the industrialization of software development. The main goal is to create a set of reusable software components for the rapid production of a software systems family. Many authors have proposed different approaches to design and implement the components of a product line. However, the construction and integration of these components continue to be a complex and time-consuming process. This paper introduces Fragment-oriented programming (FragOP), a framework to design and implement software product line domain components, and derive software products. FragOP is based on: (i) domain components, (ii) fragmentations points and (iii)fragments. FragOP was implemented in the VariaMos tool and using it we created a clothing stores software product line. We derivedfive different products, integrating automatically thousands of lines of code. On average, only three lines of code were manually modified;which provided preliminary evidence that using FragOP reduces manual intervention when integrating domain components.

Architecture-Centered Integrated Verification

2012 ◽  
pp. 201-222
Author(s):  
Yujian Fu ◽  
Zhijang Dong ◽  
Xudong He
Keyword(s):  
Petri Nets ◽  
Software Architecture ◽  
Large Scale ◽  
Future Research ◽  
Software Systems ◽  
Compositional Verification ◽  
Software Product ◽  
Implementation Level ◽  
High Level ◽  
Florida International University

The approach aims at solving the above problems by including the analysis and verification of two different levels of software development process–design level and implementation level-and bridging the gap between software architecture analysis and verification and the software product. In the architecture design level, to make sure the design correctness and attack the large scale of complex systems, the compositional verification is used by dividing and verifying each component individually and synthesizing them based on the driving theory. Then for those properties that cannot be verified on the design level, the design model is translated to implementation and runtime verification technique is adapted to the program. This approach can highly reduce the work on the design verification and avoid the state-explosion problem using model checking. Moreover, this approach can ensure both design and implementation correctness, and can further provide a high confident final software product. This approach is based on Software Architecture Model (SAM) that was proposed by Florida International University in 1999. SAM is a formal specification and built on the pair of component-connector with two formalisms – Petri nets and temporal logic. The ACV approach places strong demands on an organization to articulate those quality attributes of primary importance. It also requires a selection of benchmark combination points with which to verify integrated properties. The purpose of the ACV is not to commend particular architectures, but to provide a method for verification and analysis of large scale software systems in architecture level. The future research works fall in two directions. In the compositional verification of SAM model, it is possible that there is circular waiting of certain data among different component and connectors. This problem was not discussed in the current work. The translation of SAM to implementation is based on the restricted Petri nets due to the undecidable issue of high level Petri nets. In the runtime analysis of implementation, extraction of the execution trace of the program is still needed to get a white box view, and further analysis of execution can provide more information of the product correctness.

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.

Obstacles for the Integration of HCI Practices into Software Engineering Development Processes

2006 ◽  
pp. 422-428 ◽  
Author(s):  
Xavier Ferre ◽  
Natalia Juristo ◽  
Ana M. Moreno
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Computer Literacy ◽  
Software Process ◽  
Software Systems ◽  
Software Products ◽  
Software Market ◽  
Visible Part ◽  
Software Product ◽  
Development Processes

Usability has become a critical quality factor in software systems, and it has been receiving increasing attention over the last few years in the SE (software engineering) field. HCI techniques aim to increase the usability level of the final software product, but they are applied sparingly in mainstream software development, because there is very little knowledge about their existence and about how they can contribute to the activities already performed in the development process. There is a perception in the software development community that these usability-related techniques are to be applied only for the development of the visible part of the UI (user interface) after the most important part of the software system (the internals) has been designed and implemented. Nevertheless, the different paths taken by HCI and SE regarding software development have recently started to converge. First, we have noted that HCI methods are being described more formally in the direction of SE software process descriptions. Second, usability is becoming an important issue on the SE agenda, since the software products user base is ever increasing and the degree of user computer literacy is decreasing, leading to a greater demand for usability improvements in the software market. However, the convergence of HCI and SE has uncovered the need for an integration of the practices of both disciplines. This integration is a must for the development of highly usable systems. In the next two sections, we will look at how the SE field has viewed usability. Following upon this, we address the existing approaches to integration. We will then detail the pending issues that stand in the way of successful integration efforts, concluding with the presentation of an approach that might be successful in the integration endeavor.

Architecture-Centered Integrated Verification

2011 ◽  
pp. 104-124
Author(s):  
Yujian Fu ◽  
Zhijang Dong ◽  
Xudong He
Keyword(s):  
Petri Nets ◽  
Software Architecture ◽  
Large Scale ◽  
Future Research ◽  
Software Systems ◽  
Compositional Verification ◽  
Software Product ◽  
Implementation Level ◽  
High Level ◽  
Florida International University

The approach aims at solving the above problems by including the analysis and verification of two different levels of software development process–design level and implementation level-and bridging the gap between software architecture analysis and verification and the software product. In the architecture design level, to make sure the design correctness and attack the large scale of complex systems, the compositional verification is used by dividing and verifying each component individually and synthesizing them based on the driving theory. Then for those properties that cannot be verified on the design level, the design model is translated to implementation and runtime verification technique is adapted to the program. This approach can highly reduce the work on the design verification and avoid the state-explosion problem using model checking. Moreover, this approach can ensure both design and implementation correctness, and can further provide a high confident final software product. This approach is based on Software Architecture Model (SAM) that was proposed by Florida International University in 1999. SAM is a formal specification and built on the pair of component-connector with two formalisms – Petri nets and temporal logic. The ACV approach places strong demands on an organization to articulate those quality attributes of primary importance. It also requires a selection of benchmark combination points with which to verify integrated properties. The purpose of the ACV is not to commend particular architectures, but to provide a method for verification and analysis of large scale software systems in architecture level. The future research works fall in two directions. In the compositional verification of SAM model, it is possible that there is circular waiting of certain data among different component and connectors. This problem was not discussed in the current work. The translation of SAM to implementation is based on the restricted Petri nets due to the undecidable issue of high level Petri nets. In the runtime analysis of implementation, extraction of the execution trace of the program is still needed to get a white box view, and further analysis of execution can provide more information of the product correctness.

Digital education: Using electronic resources in psychological support of the educational process

2020 ◽  
pp. 55-61
Author(s):  
Ju. A. Tikhonova
Keyword(s):  
Preschool Education ◽  
Educational Process ◽  
Psychological Support ◽  
Diagnostic Methods ◽  
Practical Application ◽  
Software Products ◽  
School Year ◽  
Psychological Service ◽  
Software Product ◽  
The City

The article discusses the development trends of the modern preschool education system in the aspect of the activity of the teacherpsychologist of the preschool educational organization. The experience of using 1C software products in the practical work of the psychological service of kindergarten 318 of the city of Perm in the aspects of psychological monitoring of children’s readiness to study at school and correctional and developmental work with preschool children is presented. The components of the child’s psychological readiness for school are described. On practical examples, diagnostic methods for determining the level of readiness of children for schooling are analyzed. The data of testing kindergarten pupils at the beginning of the 2019/2020 school year on the parameters allowing to identify urgent problems and determine the direction of the necessary correctional development work are presented. Features of the practical application of the software product 1C:Preschool Psychodiagnostics in the process of psychological support of preparing children for school are considered. Methods are described, the scope of which is aimed not only at the study of personality traits, but also at its development. The possibilities of using games of the 1C:Educational Collection in the correctional and developmental work are disclosed. The description of game collections is given, options for their use are presented.

A Literature Review Study of Software Defect Prediction using Machine Learning Techniques

2018 ◽  
Vol 6 (6) ◽  
pp. 300 ◽  
Author(s):  
Feidu Akmel ◽  
Ermiyas Birihanu ◽  
Bahir Siraj
Keyword(s):  
Machine Learning ◽  
Software Metrics ◽  
Quality Standard ◽  
Machine Learning Techniques ◽  
Software Systems ◽  
Health Care Insurance ◽  
Software Defect ◽  
Learning Techniques ◽  
Software Product

Software systems are any software product or applications that support business domains such as Manufacturing,Aviation, Health care, insurance and so on.Software quality is a means of measuring how software is designed and how well the software conforms to that design. Some of the variables that we are looking for software quality are Correctness, Product quality, Scalability, Completeness and Absence of bugs, However the quality standard that was used from one organization is different from other for this reason it is better to apply the software metrics to measure the quality of software. Attributes that we gathered from source code through software metrics can be an input for software defect predictor. Software defect are an error that are introduced by software developer and stakeholders. Finally, in this study we discovered the application of machine learning on software defect that we gathered from the previous research works.

Sign in / Sign up

Export Citation Format

Share Document