Abstract
Globalization urges the necessity of having world class leaders, and very frequently in its formation, is required to teach them computational tools to mainly improve their project management facilities. In order to give project management a greater quality, a very important point is to control and follow up all users’ diverse requirements, from the beginning to the end of each or any type of project: administrative, academic, engineering, software, video games, virtual and mixed reality, etc. This research shows a project requirements manager’s approach which allows knowing the specific requirements in each of its phases and give an advanced description of its various types and their traceability. This prototype promotes project requirement management best practices, and link them to the various areas of engineering, administration, planning and also with society, industry, commerce and academic sectors.
Highlights
Over the past decades, different types of projects failure are widely known
RE is based on Software Engineering Management, which can be adapted to any different type of project
The proposed requirements organizer prototype is based on the RE and project management methodological model under standards guidance [13], [15], [18], [19], [20], [21], among others
Summary
Different types of projects failure are widely known. For example, not meeting deadlines, overflowing budgets, not corresponding functionalities with customer’s specifications, and as a consequence, a negative impact has been obtained within entrepreneurs and investors. It is common knowledge that when a project ends the deliverables are given to the client, assuming that all the needs and requirements requested have been met in accordance with signed contracts, but it turns out that the resulting products are not those that the users expected, so the final results are not satisfactory [1], [2], [3], [4]. There are common errors, such as not specifying agreements due to the informality with which the client's requests are treated. This has to do with the lack of correct detection, definition and formalization of client or usersrequirements. Objectives: These must be defined at the project beginning in order to formalize the results of each request submitted by clients or users and the holistically system to which they will be connected
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: Proceedings of the Institute for System Programming of the RAS
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
