Software for Automated Design of Network Graphics of Software Systems Reengineering

Abstract

The subject of the work is the construction of a graphical network model of reengineering of the software system. Purpose of the paper is development of software for increasing the level of automation of designing network charts for the organization of production by reengineering software systems in the framework of project management. Network planning is one of the forms of graphical representation of the work content and the duration of implementation of strategic plans and long-term complexes of project, planning, organizational and other activities of the enterprise. Along with linear charts and table calculations, network planning methods are extensively used in the development of long-term plans and models for the creation of complex production systems and other objects of long-term use. The “Nodes-Activity” type of graphs is used in modern specialized packages of planning and operational management computer programs. The task before creating a software tool is the ability to work with all types of network charts with the possibilities of their comprehensive transformation. Methods. The article is based on methods of network planning for the PERT (Program Evaluation and Review Technique) methodology, the use of elements of graph theory and the Gantt chart method as an accounting method for project management. Simulation of the system software architecture is carried out within the UML (Unified Modeling Language) 2.5 methodology using the CASE toolkit Enterprise Architect 14. Project decisions proposed by the authors are the results of the article. The content of the design part is determined, firstly, by the specifics of the planning of software projects reengineering, and secondly, by the features of specific technical proposals for a project that is manageable. The architecture (project “Frame”) software for managing network planning of software project reengineering is designed in the article. Conclusions. The architecture is developed in the form of several structural and behavioral diagrams, namely: use case diagram, which provides an analyst with a detailed idea of the software field of application; sequence diagram that is designed to create a programmer's imagination on how to perform actions when working with a future program tool; statechart diagram that is required for a visual representation of those states in which the software can be at different times; class diagrams that are used to design the main form filling of the future software; component diagram that is designed to examine the composition of the components of the future software and indicate the sequence of compilation and assembly of individual modules. The numerical and temporal estimation of the planning parameters is based on the data obtained from the Gantt design charts.