THE CALCULATION METHOD FOR INDICATORS PROJECT ESTIMATION IN THE IMPLEMENTATION OF SOFTWARE SYSTEMS RE-ENGINEERING
Keywords:software system, project, re-engineering, method of design points, indicator, estimation, use case, factor, weighting value, bounding constant.
Essentials. Today’s software systems have become so tightly integrated into our lives that it is virtually impossible to imagine the existence and development of mankind without them. But this progress also means that software systems currently in use have
quickly become outdated and obsolete due to the pace technical evolution. It is here that end to end process review comes down with the inheritance of the positive qualities of the software system and the phasing out of the negative one, that is, re-engineering. All
similar processes that begin with re-design, require a mandatory analytical assessment of the project’s key indicators since there are cases where re-engineering might be unprofitable for a particular software system. In the article below, the author takes a look at the
complex tool of evaluating the software project redesign, which could predict labor costs for reprogramming of the objects in conjunction with other indicators of the projects that determines the complexity of software system under review.
Objective. The object of this paper is to outline the method by which one can estimate and evaluate key aspects for software system reengineering with the help of complex tools for appraisal of the project under review.
Method. The technology described in the article is based on use of the Karner’s Point method with the introduction of significant additions and extensions. The establishment of coefficients and the selection of the constants are based on the Jacobson’s method and
tested on numerous statistics of the most similar projects.
Outcome. After analyzing the completed project and examining the report of crucial factors, it’s possible to provide quite accurate estimation for the actual man-hours of re-engineering for the particular project, given its key factors can be accurately adjusted.
Subsequently, you can use this data as the base line for the project life cycle. Evaluation factors used for project cost calculation will be combined in a report that will be included in the source design documentation, which is part of the organizational support of the
systems for the automation design of software systems.
Conclusions. The method of calculating Karner’s project points with the introduction of significant extensions to the process of software system re-engineering has been further developed. Each variable is determined and calculated separately, using measurements,
weighting factors and constrains. Measurements are performed by a team of experienced QA-analysts based on their ideas about the technical complexity of the project and the capabilities of the software developers. The coefficients and constants are based on data collected from 3–5 projects already completed by analysts with a big degree of similarity.
Velykodniy S. S. Problema reinzhiniringa vidov obespechenija
sistem avtomatizirovannogo proektirovanija,
Mezhdun. nauch. zhurn. «Upravljajushhie sistemy i
mashiny», 2014, No. 1, pp. 57–61, 76.
Velykodniy S. S. Reinzhyniryng system monitoryngu ta
dystancijnogo upravlinnja sudnovymy energetychnymy
ustanovkamy, Mater. XXII mizhn. konf. z avtom. upravl.
“Avtomatyka 2015”, Odesa, 10–11 veres. 2015. Odesa,
, pp. 133–134.
Velykodniy S. S. Metodologicheskie osnovy reinzhiniringa
sistem avtomatizirovannogo proektirovanija, Mezhdun.
nauch. zhurn. “Upravljajushhie sistemy i mashiny”, 2014,
No. 2, pp. 39–43.
Resource Estimation for Objectory Projects : project report,
Objective Systems, SF AB, 1993, 9 p.
Anda B. Effort Estimation of Use Cases for Incremental
Large-Scale Software Development, 27-th International
Conference on Software Engineering, St. Louis, MO, 15–21
May 2005, pp. 303–311.
Carroll E. R. Estimating Software Based on Use Case Point,
OOPSLA ‘05: Companion to the 20th annual ACM
SIGPLAN conference on Object-oriented programming, systems,
languages, and applications, San Diego, CA, 2005, pp.
–265. DOI: 10.1145/1094855.1094960
Clemmons R. Project Estimation with Use Case Points,
Cross Talk, 2006, No. 2, February, pp. 18–22.
Didkovs’ka M. V. Testuvannja: Kryterii’ ta metody. Kyi’v,
NTUU “KPI”, 2010, 96 p.
Cohn M. Agile Estimating and Planning. Prentice Hall,
, 368 p.
Orlov S. A. Programmnaja inzhenerija: uch. dlja vuzov. 5-e
izd. obnovl. i dop. SPb, Piter, 2016, 640 p.
How to Cite
Copyright (c) 2019 S. S. Velykodniy, O. S. Tymofieieva, S. S. Zaitseva-Velykodna
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Creative Commons Licensing Notifications in the Copyright Notices
The journal allows the authors to hold the copyright without restrictions and to retain publishing rights without restrictions.
The journal allows readers to read, download, copy, distribute, print, search, or link to the full texts of its articles.
The journal allows to reuse and remixing of its content, in accordance with a Creative Commons license СС BY -SA.
Authors who publish with this journal agree to the following terms:
Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution License CC BY-SA that allows others to share the work with an acknowledgement of the work's authorship and initial publication in this journal.
Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgement of its initial publication in this journal.
Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work.