How does the Rup methodology work in practice?

Question

Project management

Hello
I read the theory about the Rup methodology, I would like to understand how this technique works in practice.
As I understand it, in practice:
0. Analysts prepare a concept, identify requirements, fix it in documents
1. Analysts create models (defined) on uml at the stage of concept, analysis
2. Analysts create tasks for implementation by programmers (in the Jira system (or similar) with reference to models and uscases)
3. Programmers perform the specified tasks, write code, create a program.
4. After creating the program, testers test the system based on the scenarios described by analysts in the use case
. The project manager manages all participants and the process.
Bottom line: all points from 0 to 4 are performed (iteration) until we prepare the final version of the product.
So, can you briefly present the work on the RUP methodology? are my guesses correct?

Answer 1

RUP is quite a voluminous framework and is very well documented: all roles, stages, steps and microsteps, artifacts, etc. are described. (e.g. RUP Homepage , so simplifying to 5 points and asking if my guess is correct seems a little odd.
For a small project/team, RUP will seem redundant and heavy. I would recommend starting with its "lightweight" alternative to OpenUP

Answer 2

In general, you understand correctly, but I will add a few clarifying points from myself:
1) There is still a division into releases. But unlike Agile methodologies, the release usually lasts from 2-3 months to six months
2) The specifics of using RUP for many managers is often the connection of a Gantt chart to visualize the sequence of tasks. That is, it tracks how the tasks go in sequence
3) A new release starts in parallel with the previous one. That is, business analysts set tasks. While these tasks are in development and testing and the first release is not completed, business analysts simultaneously describe new requirements and tasks for the second release.
4) And finally, unfortunately, RUP rarely works perfectly in any company, as intended. It is characterized by displacement and lengthening of releases