scholarly journals A Novel Clone-Based Reuse Method to Maintain Proficiency in Software Engineering Practice

The source code of an application paves way for a quality software product. Quality software in-turn helps in imposing software reuse. In this paper, pieces of similar codes also known as code clones or code duplications are considered as reusable software components. In general code clones are considered harmful in software engineering practice. They are considered to degrade the quality of software. Code clones are detected and removed without further processing. In this paper, a token- based CodeClone reuse method is proposed to detect type1 and type-4 clones. Positive effects of clones are analyzed and beneficial clones are extracted from the cluster of clones detected. The proposed method aids in the art of developing software thereby enforcing the concept of software reuse. The working principle of the proposed method is implemented using open source software as inputs. Beneficial clones are further stored in a database for future use. Clone report is generated as it assists in knowing about the clone details within a software system.

2012 ◽  
Vol 241-244 ◽  
pp. 2709-2713
Author(s):  
Gang Xiang ◽  
Hua Wang ◽  
Hui Wang ◽  
Guiyuan Zhang ◽  
Bo Jiang

Based upon the summary of software engineering, this paper sets forth the engineering practice content of application software of information system, and puts forward the work emphases, such as promoting the capability of software demonstration, improving the quality of software design, emphasizing the application of software reuse, enhancing the capability of software test and intensifying technical configuration management. Thenceforth a primary prospect is presented.


2014 ◽  
Vol 687-691 ◽  
pp. 1921-1924
Author(s):  
Xi Jun Song ◽  
Zhi Lian Zeng

With the development of information society, the size and number of computer software increases sharply. This demands the quality of software higher and higher. Thus does software engineering management come into being, and is enriched, developed and perfected in engineering practice continually. In this paper, the author analyses the new theory's research background, meaning, and the applicant region. This paper sums up the experience of software engineering implementation in project developing, and points out the problems of software in software explore. From the character and existing problem in software, the author compares the usability of a lot of soft engineer process models in developing organization, points out the importance of the implantation in these organizations. In the end, this paper also gives its suggestions on implant principle, organization development, system building, staff training, and environment construction.


Author(s):  
Anas AL-Badareen

    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.


Author(s):  
Jihane Lakhrouit ◽  
Karim Baïna

<p><span lang="EN-US">Measurements play an important role in many scientific fields in general and in</span><span lang="EN-US">the</span><span lang="EN-US">analysis</span><span lang="EN-US">of</span><span lang="EN-US">enterprise</span><span lang="EN-US">architecture</span><span lang="EN-US">in</span><span lang="EN-US">particular.</span><span lang="EN-US">In software engineering, the measures are used to control the quality of the software product and better manage development projects to control the cost of production.</span><span lang="EN-US">In this article we proposed firstly models and measures to evaluate and analyze the complexity of the enterprise architecture and especially the heterogeneity of components and relationships, and secondely we developed a model to automatically detect the change of measures and their impact on enterprise architecture.</span></p>


2020 ◽  
Vol 12 (11) ◽  
pp. 4663 ◽  
Author(s):  
Mehwish Naseer ◽  
Wu Zhang ◽  
Wenhao Zhu

Software engineering is a competitive field in education and practice. Software projects are key elements of software engineering courses. Software projects feature a fusion of process and product. The process reflects the methodology of performing the overall software engineering practice. The software product is the final product produced by applying the process. Like any other academic domain, an early evaluation of the software product being developed is vital to identify the at-risk teams for sustainable education in software engineering. Guidance and instructor attention can help overcome the confusion and difficulties of low performing teams. This study proposed a hybrid approach of information gain feature selection with a J48 decision tree to predict the earliest possible phase for final performance prediction. The proposed technique was compared with the state-of-the-art machine learning (ML) classifiers, naïve Bayes (NB), artificial neural network (ANN), logistic regression (LR), simple logistic regression (SLR), repeated incremental pruning to produce error reduction (RIPPER), and sequential minimal optimization (SMO). The goal of this process is to predict the teams expected to obtain a below-average grade in software product development. The proposed technique outperforms others in the prediction of low performing teams at an early assessment stage. The proposed J48-based technique outperforms others by making 89% correct predictions.


Software metrics have a direct link with measurement in software engineering. Correct measurement is the prior condition in any engineering fields, and software engineering may be not an exemption, as those size and complicated nature of software increases, manual examination of software becomes a harder assignment. Most Software Engineers worry about the quality of software, how to measure and enhance its quality. The overall objective of this study was to asses and analysis software metrics used to measure the software product and process. In this Study, the researcher used a collection of literatures from various electronic databases, available since 2008 to understand and know the software metrics. Finally, in this study, the researcher has been identified software quality will be a method for measuring how software is designed and how well the software conforms to that configuration. A percentage of the variables that we would be searching for software superiority and Correctness, item quality, Scalability, completeness and absence of bugs of those quality standard that might have been utilized from you quit offering on that one association will be unique in relation to others for this reason it may be better to apply the software measurements to measure the quality of software and the current is most common software metrics tools to decrease the partiality of faults during the valuation of software quality. The central influence of this study is an indicationaround software metrics to illustrate for development in this field by critical investigation about key metrics initiated onboth developer and user interactiona unified definition of software quality management on User and Developer (SQMUD) is proposed


2021 ◽  
pp. 115-128
Author(s):  
G. Mirskikh ◽  
◽  
V. Vasyuk ◽  
T. Knizhka ◽  
I. Krisak ◽  
...  

The paper is devoted to the analysis of the software life cycle of engineering objects. To implement the processes and relevant procedures aimed at ensuring, as well as maintaining proper management of the level of software quality at the stages of the life cycle, it is proposed to use the life cycle model as a methodological basis for achieving the goal - achieving the proper level of consumer quality of the final product, taking into account the conditions and circumstances. exploitation.. The considered model of the life cycle in the framework of software engineering is a structure that determines the sequence of implementation and relationships of processes and procedures of a different nature that may arise when performing any actions in relation to software, from the emergence of a need for this software and ending with its final withdrawal from use. If necessary, the life cycle model has a relationship with the content, scale and complexity of the corresponding project, on the characteristics of the conditions and circumstances under which a particular software is created and operated. At the same time, the existence of a life cycle model, carefully developed at the same time, adequate to the existing conditions and circumstances, is the basis for the implementation of general quality management within the framework of a program project, which at this point in time is stipulated as a methodological basis for obtaining a project at the output of an object that meets the presented requirements and modern quality standards. The main reasons for the need to pay special attention to modeling the life cycle of the software being developed and the component of the environment surrounding the software at different stages of its life cycle, taking into account the life cycle of material engineering objects, are presented. Taking into account the presented concept of the life cycle implementation in some virtual enterprise, the software sequentially performs the transition from one state to the next, from consumer properties specified by the customer to an already finished software product and quite real consumer properties supported by the corresponding characteristics, this software is in operation to moral aging, and also goes into a state characterized by the modernization or removal of this software from use. Key words: software, engineering object, software life cycle model, software development, engineering activities


Sign in / Sign up

Export Citation Format

Share Document