Introduction to RUP (The Rational Unified Process. An Introduction) (Category Management)

This is a book by Philip Cracchten. (Philippe Kruchten) It is dedicated to the development process, which in the late nineties and early two thousandth claimed to become the de facto standard in software development. It was no longer waterfall, which everyone interprets simplistically and prefers to stigmatize talking about the lack of iterations and feedback. (broadly). In this book 2001 The author gives the following tips on the organization of production processes (which are relevant now) 1. Develop iteratively The author kicks waterfall, then recalls the spiral model of Barry Boym, and then proposes an iterative process, as a result of each iteration of which a release version is created. Inside the standard iteration are planning, requirements management, analysis and design, implementation, distribution, testing and evaluation. 2. Manage requirements Requirement refers to a condition or characteristic that the system must meet. The author proposes to work actively with functional and non-functional requirements, as well as system limitations. We need to be able to document requirements and track their impact on the system and on decisions and trade-offs. 3. Use modular architectures The author recommends the use of a modular architecture that promotes elasticity, distribution of responsibility, the use of standardized components and visual modeling. 4. Use visual modeling Here the author talks about the importance of modeling and recalls UML. (unified model language) It is a unified modeling language, which had many hopes in those days. Now many people also want to model visually, but they already use other notations and approaches for this. (C4 Model, ArchiMate, SysML, 4+1, ...). Exactly, by the way. model4+1" It was recommended inside RUP as an architecture-based process. The point is, we had 5 logical, process, development, physical, scenarios. Moreover, the scenario presentation is based on user scenarios and combines other views. 5. Do not forget to check the quality The importance of automated testing and finding bugs in the early stages of software development. This is called shift-left testing:) 6. Watch the changes. Here the author speaks about the repetition of the process of software changes. We are now doing this through a built-in CI/CD process. (continuous integration / continuous delivery). Interestingly, the recommendations have not become outdated over the past time and have even become much clearer + a cool instrumentalization has appeared:)

Next, the author talks about the four functions of software development and shows that all these functions are implemented inside the RUP and are based on software development. 6 advice given above

1. Ensure leadership is consistent with team actions
2. Determine which artifacts should be created and when
3. Explain what individual developers and teams should do.
4. Provide criteria for monitoring and measuring products and activities.

And then in the book, the author analyzes in detail how RUP works and how to use it to build the development process.

P.S. Philippe Cracten, the author of the book, is a very cool specialist in both process and software architecture. He was Director of RUP Process Development at Rational before 2003 The year Rational was acquired by IBM. In 2020 Received the Software Architecture Award from Carnegie Mellon University | Software Engineering Institute (here speech About the state of software architecture, which was timed to the award)

P.P.S. I remember years. 17 Back then, I got to know this process through training and training at Luxoft. I was impressed with the approach where you could build a custom cube process that RUP provided. At the time, I thought it was a rather complicated design:)

#SoftwareArchitecture #Architecture #Software #Management #Leadership