The role of UML diagrams in planning an information system project on the example of a hiking tourist routes system.

Keywords: UML; modeling; diagram; information system; defect; planning.

Abstract

Any process requires preliminary analysis and planning. Modern information systems are getting more and more complex, and, accordingly, the planning stage requires additional time and attention. One of the tools actively used by specialists in the development of IT products is UML – a modeling language that allows you to describe and display the logic of the system. This article outlines the use of UML diagrams at the planning stage and its impact on the overall result of the developed solution. This study is based on the example of a hiking tourist routes system and the development of a separate real solution. The importance of using such an approach in requirements engineering is substantiated, which will enable tracking the dependence between models’ availability and the quality of the system. This paper analyzes not only the advantages of modeling but also the challenges and difficulties that may arise during the analysis of non-functional requirements for the system. This research made it possible to summarize the role of UML diagrams and outline the basic principles that will significantly improve the experience of using this approach at various stages of the information systems life cycle. This work lays the foundation for further research and will enable scaling the already obtained results to reveal additional features and details of the modeling application. It is worth emphasizing that such studies can pertain to different areas and aspects of UML, such as a tool for identifying the flaws or improving communication in a team of engineers in general. The obtained results can be applied in the field of testing, business analysis, and during the development of the architecture of software solutions.

References

1. Booch, G., Rumbaugh, J.E., & Jacobson, I. (2005). The Unified Modeling Language User Guide. Addison-Wesley.
2. Fowler, M. (2004). UML distilled: A brief guide to the standard object modeling language. Addison-Wesley.
3. Hutchinson, J., Whittle, J., Rouncefield, M., & Kristoffersen, S. (2011). Empirical assessment of MDE in industry. In Proceedings of the 33rd International Converence on Software Engineering (pp. 471-480). New York, NY; ACM.
4. Lange, C., Chaudron, M.R.V., Muskens, J., Somers, L.J., & Dortmans, H.M. (2003). An empirical investigation in quantifying inconsistency and incompleteness of UML designs. In Proceedings of the Workshop on Consistency Problems in UML-based Software Development (pp. 26-34). San Francisco, CA; Blekinge Institute of Technology.
5. McConnell, S. (2004). Code Complete: A practical handbook of software construction (2nd ed.). Microsoft Press.

Abstract views: 41
PDF Downloads: 35
Published
2024-06-16
How to Cite
Deineko , L., & Kunanets , N. (2024). The role of UML diagrams in planning an information system project on the example of a hiking tourist routes system . COMPUTER-INTEGRATED TECHNOLOGIES: EDUCATION, SCIENCE, PRODUCTION, (55), 293-300. https://doi.org/10.36910/6775-2524-0560-2024-55-37