| Abstract [eng] |
Rapidly expanding organizational development and IT improvement in the field of IT projects are increasing the scope of projects within companies. Projects are becoming larger and requiring greater team involvement. With a growing abundance of job opportunities in the project field, more young specialists are choosing this IT direction. Currently, there are many methodologies that indicate how projects should be executed and how project scope should be evaluated. However, there is no methodology that specifies the steps to be taken to obtain a more accurate project scope estimation and how to gather as many requirements as possible from the client when facing time constraints.The research problem is the frequent occurrence of failures in IT projects due to inadequate project planning and scope estimation when companies initiate new projects. As a result, deviations from the project plan occur, the project scope changes, and the predetermined budget and timelines are not met.The research objective is to create conditions for more precise project planning and scope evaluation by proposing a methodology for collecting domain-specific information and requirements using models. In this master's research work, a methodology is developed to guide the novice project manager or other team members in systematically detailing the project and obtaining the project scope, including contingency resources for unforeseen circumstances. This methodology is also beneficial for experienced project planning members who want to introduce a work structure, clarity, and efficiency into the project planning phase to ensure that project requirements are fully collected and scope is evaluated considering project uncertainty and constantly changing client needs. The methodology includes requirements gathering from different UML models and identification criteria for overlap. Model creation can also improve communication with the client since visual representation of requirements is clearer than a conventional list of functions. The methodology describes rules for scanning selected models and their elements, based on which the models are scanned and requirements are automatically generated. The user can review, organize, and identify overlaps in the generated requirements using recommended metrics and manual assessment of their scope. It is recommended that the scope assessment be performed by the team responsible for task execution to obtain the most accurate estimation. After completing the assessment and inputting additional parameters, the scope result is obtained using a formulated formula. The obtained scope estimation is often higher than the traditionally calculated scope because it takes into account risks and the level of clarity for specific requirements. This ensures that unforeseen situations requiring additional time and resources to resolve and manage are accounted for. |
