Article

Received 01.11.2023

Revised 30.01.2023

Accepted 30.03.2023

Retrieved from Vol. 27, No. 1, 2023

Pages 24 -30

Bezverkhiy, O., Serhienko, I., & Shkabura, O. (2023). Designing an application to manage software product development processes. The National Transport University Bulletin, 27(1), 24-30. https://doi.org/10.33744/2308-6645-2023-1-55-024-030

Designing an application to manage software product development processes

Oleksandr Bezverkhiy Ihor Serhienko Oleksandr Shkabura

This article examines the features of the process of planning and developing software products that require the developer to interact with a large number of them, which significantly affects work productivity and reduces the speed of creating the final product. In this case, the possibility of optimizing the programmer's work process by centralizing all work aspects in one application is considered, which will allow more efficient use of work time and build more qualitative and meaningful communications related to the work process. The object of research is the process of developing an application for managing software product development processes. The purpose of the work: designing the development of an application for managing the development processes of software products, which will represent a complete system for software development, minimizing the complexity of communications and information perception, and will significantly speed up the main processes of work on the developed software. Having analyzed the most popular tools for development, the main advantages and disadvantages of these systems have been established. The concept of project databases was determined, namely: data was divided into dynamic and static, the structure of the database was created and schematically illustrated, the number of fields and the types of information that these fields will store were determined. A connection to a static MongoDb database cluster and a client link connection to a dynamic Firebase database have been implemented

software product; responsibility management; scrum; asynchronous communication
  1. Orlyk, S., Buluy, Yu. Introduction to software engineering and software life cycle management. Software engineering. Program requirements [Electronic resource]. Mode of access: http://www.sorlik.ru/swebok/3software_engineering_requirements.pdf.
  2. Cockburn, A. (2015). Writing Effective Use Cases. Addison-Wesley, 270 p.
  3. Standard Glossary of Terms Used in Software Testing. Version 1.2. ISTQB, 2006 [Electronic resource]. Access mode: www.istqb.org/downloads/glossary.
  4. IEEE Standard 1061-1998. IEEE Standard for Software Quality Metrics Methodology (Industry Standard).
  5. Cockburn, A. (1999). Methodology per Project. Humans and Technology Technical Report, TR 99.04. Salt Lake City, USA [Electronic resource]. Access mode: http://alistair.cockburn.us/Methodology+per+project.
  6. Vygers, K. (2004). Development of Requirements for Software (translated from English). Moscow, 576 p.
  7. Electron JS – Official Documentation [Electronic resource]. Access mode: https://www.electronjs.org/docs.
  8. Simpson, K. (2017). You Don’t Know JS: This & Object Prototypes, 173 p.
  9. MongoDB Official Documentation [Electronic resource]. Access mode: https://docs.mongodb.com/.

https://doi.org/10.33744/2308-6645-2023-1-55-024-030