scholarly journals Reuse Alternatives based on the Sources of Software Assets

2021 ◽  
Vol 10 (1) ◽  
Author(s):  
Anas AL-Badareen
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Software Reuse ◽  
Development Process ◽  
Software Systems ◽  
Software Development Process ◽  
Software Products ◽  
Engineering Discipline

    Abstract— Since the idea of software reuse appeared in 1968, software reuse has become a software engineering discipline. Software reuse is one of the main techniques used to enhance the productivity of software development, which it helps reducing the time, effort, and cost of developing software systems, and enhances the quality of software products. However, software reuse requires understanding, modifying, adapting and testing processes in order to be performed correctly and efficiently. This study aims to analyze and discuss the process of software reuse, identify its elements, sources and usages. The alternatives of acquiring and using software assets either normal or reusable assets are discussed. As a result of this study, four main methods are proposed in order to use the concept of reuse in the software development process. These methods are proposed based on the source of software assets regardless the types of software assets and their usages.

scholarly journals Measuring the Quality Of the Development Process Academic System with E-GQM Method

2021 ◽  
Vol 5 (1) ◽  
Author(s):  
Sarwosri Sarwosri ◽  
Umi Laili Yuhana ◽  
Siti Rochimah ◽  
Rizky Januar Akbar ◽  
Maidina Choirun Nisa
Keyword(s):  
Software Development ◽  
Development Process ◽  
Software Process ◽  
Development Project ◽  
Average Score ◽  
Software Development Process ◽  
Software Development Project ◽  
Software Products ◽  
Academic System

In a software development project, aspects of software quality are very important. All stakeholders expect high quality of software. To ensure the quality of software products, it is also necessary to ensure that the process that is carried out have a quality. Research that is mostly done is in terms of assessing the quality of software products. But the software process is also very important to be assessed from their quality too. In every software development process, the developer needs guidance in carrying out every aspect of it. In each of these aspects, it must be determined what goals are to be achieved and how to measure whether those goals have been achieved or not. One method that can be used for this is the Extended Goal Question Metric method. In this method, for each development process in software, will be determined what aspects must be achieved, from each aspect there are defined a number of goals to measure these aspects. For each goal, one or more goal will be determined one or more questions that are relevant to that. For each Question an appropriate metric will be determined. The next step is mapping between G to Q and Q to M. The measurement is done by calculating the goal value obtained from the metric calculation. From this metric, the value of each Goal will be obtained, whether it was achieved or not. Tests were carried out on the software process for the development of academic system features at DPTSI ITS. The value of each goal has exceeded 0.51 (for a scale of 0-1) so that it achieved the quality of the Software development process. The total average score was 0.889. 

Trust Elements in Open Source

2010 ◽  
pp. 334-342
Author(s):  
Barbara Russo ◽  
Marco Scotto ◽  
Alberto Sillitti ◽  
Giancarlo Succi
Keyword(s):  
Software Development ◽  
Development Process ◽  
Automatic Measurement ◽  
Automatic Process ◽  
Software Development Process ◽  
Software Products ◽  
Development Tools ◽  
On Line ◽  
Measurement Approach

The quality of a software development process is based on a large spectrum of various elements that must be identified and assessed. The majority of elements can be measured quantitatively and possibly using an automatic process. Some elements, however, are rather subjective and depend strongly on different opinions of people using or evaluating the software development process. An automatic measurement approach is difficult to achieve (for example by on-line questionnaires or surveys inserted inside software products or software development tools). The foundation for all assessments is a set of elements that will be at a certain point of development or use measured and evaluated.

METHODS OF SELECTING ACCEPTABLE STRATEGIES OF SOFTWARE DEVELOPMENT

2018 ◽  
pp. 33-39
Author(s):  
V. A. Fedorova ◽  
T. A. Moiseeva ◽  
E. V. Poddubnaya
Keyword(s):  
Software Development ◽  
Development Process ◽  
Software Systems ◽  
Software Development Process ◽  
Software Product ◽  
Collective Development ◽  
The Moment ◽  
The Cost ◽  
Development And Management

Currently, software is used in many areas of human activity. But the developers of software systems often have problems that leads to exceeding the time and budget of development, as well as reduces the quality and security of software. The paper proposes a methodology developed by the authors, which allows you to standardize the process of creating software. The proposed approach greatly facilitates the organization of the process of collective development and management of software development, improves the quality of the developed software, reduces the risks of the developer and the customer and also reduces the time spent on the creation of software and the cost of its development. The developed technique fully standardizes the software development process, from the moment of creation of specification and ending with the introduction and support of the software product.

Formalization Process in Software Development

2011 ◽  
pp. 1559-1565
Author(s):  
Aristides Dasso ◽  
Ana Funes
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Development Process ◽  
System Development ◽  
General Rule ◽  
Software Development Process ◽  
Mathematical Basis ◽  
Engineering Discipline ◽  
Formal Basis ◽  
Pros And Cons

Nowadays, software engineering (SE) is considered more frequently an engineering discipline. Several definitions have been proposed by different authors, and many of them agree in affirming that SE is the application of principles and systematic practices for the development of software. That is—as it was established by the IEEE (1990)—SE is the application of engineering to the software. As a general rule all engineering applications use mathematics or mathematical tools as a basis for their development. However, software engineering is an exception to this rule. Not all the techniques and software development methods have a formal basis. Formal methods1 (FM) rely on mathematical foundations. FM are a collection of methodologies and related tools, geared to the production of software employing a mathematical basis. There are a number of different formal methods each having its own methodology and tools, specially a specification language. As it is expressed in Wikipedia (2006) and Foldoc (2006), we can say that FM are “mathematically based techniques for the specification, development and verification of software and hardware systems.” FM are based on the production of formal specifications— for which they have a formal language to express it. Sometimes there is also a method to use the language in the software development process. The aims of FM can vary according to the different methodologies, but they all shared a common goal: the production of software with the utmost quality mainly based on the production of software that is error free. To achieve this, the different FM have developed not only a theory, but also different tools to support the formal process. FM can cover all the steps of the life cycle of a software system development from requirement specification to deployment and maintenance. However, not all FM have that capacity, and not always it is convenient to apply them. It is necessary to make an evaluation between pros and cons before applying FM in the software development process.

scholarly journals AN EMPIRICAL STUDY ON PREDICTORS OF GREEN SUSTAINABLE SOFTWARE PRACTICES IN MALAYSIAN ELECTRONIC INDUSTRIES

2018 ◽  
Author(s):  
Bokolo Anthony Jnr ◽  
Mazlina Abdul Majid ◽  
Awanis Romli
Keyword(s):  
Software Development ◽  
Survey Data ◽  
Development Process ◽  
Software Systems ◽  
Software Development Process ◽  
Software Developers ◽  
Software Products ◽  
Environmental Friendly ◽  
Life Cycle Process ◽  
Social And Environmental Impacts

Currently, sustainability is a pertinent issue that should be considered in the software development process; hence it is imperative to recognize how environmental-friendly practices can be applied in the electronic industries that develop and deploy software products. However, sustainability is not fully considered when electronic industries implement modern software systems. Additionally, software developers in electronic industries believe that software is environmental friendly mainly because it is virtual. Conversely, the life cycle process and approaches applied to implement, deploy and maintain software do possess social and environmental impacts that are usually not accounted for by electronic industries. Therefore this study identified the predictors that determine sustainable software practice applications in electronics industries by presenting a model to facilitate sustainable software products development. The identified predictors influence sustainable software practices applications which correlate to environmental, technical, economic, social and individual dimensions of sustainability in electronics industries. Based on the identified predicators, this research developed a set of indicators for survey questions and collected data from 133 respondents from Information Technology (IT), software, environmental and electronic- based industries. The survey data aimed to verify each of the identified predictors that influence sustainable software practice applications. Descriptive and inferential statistical results from the survey data show that each of the predictors is significant and do influence sustainable software development. The finding from this study provides insights to electronic industries in implementing sustainable software practice applications.

scholarly journals Are UX Evaluation Methods Providing the Same Big Picture?

Sensors ◽  
2021 ◽  
Vol 21 (10) ◽  
pp. 3480
Author(s):  
Walter Takashi Nakamura ◽  
Iftekhar Ahmed ◽  
David Redmiles ◽  
Edson Oliveira ◽  
David Fernandes ◽  
...  
Keyword(s):  
Software Development ◽  
Decision Process ◽  
Development Process ◽  
Evaluation Methods ◽  
Sentence Completion ◽  
Software Development Process ◽  
Software Application ◽  
Software Products ◽  
Big Picture ◽  
The Impact

The success of a software application is related to users’ willingness to keep using it. In this sense, evaluating User eXperience (UX) became an important part of the software development process. Researchers have been carrying out studies by employing various methods to evaluate the UX of software products. Some studies reported varied and even contradictory results when applying different UX evaluation methods, making it difficult for practitioners to identify which results to rely upon. However, these works did not evaluate the developers’ perspectives and their impacts on the decision process. Moreover, such studies focused on one-shot evaluations, which cannot assess whether the methods provide the same big picture of the experience (i.e., deteriorating, improving, or stable). This paper presents a longitudinal study in which 68 students evaluated the UX of an online judge system by employing AttrakDiff, UEQ, and Sentence Completion methods at three moments along a semester. This study reveals contrasting results between the methods, which affected developers’ decisions and interpretations. With this work, we intend to draw the HCI community’s attention to the contrast between different UX evaluation methods and the impact of their outcomes in the software development process.

Practical Experience in Customization for a Software Development Process for Small Companies Based on RUP Process and MSF

2011 ◽  
pp. 71-93 ◽  
Author(s):  
Valerio Fernandes del Maschi ◽  
Luciano S. Souza ◽  
Mauro de Mesquita Spínola ◽  
Wilson Vendramel ◽  
Ivanir Costa ◽  
...  
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Development Process ◽  
Practical Experience ◽  
Software Development Process ◽  
Small Companies ◽  
Engineering Process ◽  
Software Projects ◽  
Software Engineering Process ◽  
Unified Process

The quality in software projects is related the deliveries that are adjusted to the use, and that they take care of to the objectives. In this way, Brazilian organizations of software development, especially the small and medium ones, need to demonstrate to future customers whom an initial understand of the business problem has enough. This chapter has as objective to demonstrate methodology, strategy, main phases and procedures adopted beyond the gotten ones of a small organization of development of software in the implantation of a Customized Software Engineering Process and of a Tool of Support to the Process in the period of 2004 to 2006 on the basis of rational unified process (RUP) and in the Microsoft solutions framework (MSF).

Sign in / Sign up

Export Citation Format

Share Document