How does RUP describe software architecture? What is the relationship between RUP and software architecture?

Question

I am looking for articles or documents that describe the software architecture in terms of RUP.

Do you know any document?

Answer 1

The Rational Unified Process describes "component-based architecture" as one of seven core "best practices." I don’t quite understand what this means. On the Internet, a better description is similar to this, from the Rational Unified Process: Guidelines for Software Developers white paper:

Using component-based architectures. The process focuses on the early development and basic installation of a robust executable architecture before transferring resources for full-blown development. It describes how to create a flexible, flexible architecture, adapt changes, is intuitive, and promotes more efficient software reuse. Rational Unified Process supports component-based software development. Components are non-trivial modules, subsystems that perform a clear function. The Rational Unified Process provides a systematic approach to defining architecture using new and existing components. They are built in a well-defined architecture, both ad hoc, and in component infrastructure such as the Internet, CORBA and COM, for which the industry of reusable components is emerging.

The source link for this is p. 140 of the book Component Software Engineering: Selected Documents from the Institute for Software Development .

The developerWorks IBM article, “ What is software architecture? ” Looks more helpful and accessible to me. Although it is not specific to RUP, it tries to define the “component” and the key elements that the software architecture should describe. Alternatively, any process book should include something about a recommended software architecture. At the end of the Wikipedia article there is an additional reading list that would be a good starting point.

Answer 2

The concept of software architecture is central to RUP and is well supported throughout the process.

First, RUP describes several roles, one of which is a software architect :

This usually includes the identification and documentation of architecturally significant aspects of the system, including the requirements, design, implementation, and deployment of system “views”.

Then RUP has an artifact called an SOF ( ) architecture document :

A software architecture document provides a comprehensive architectural overview of the system, using a number of different architectural portray different aspects of the system.

The system is "sliced" and documents various views. Philip Kruchten , director of the development process, popularized the 4 + 1 architectural model . Representation:

• use case / scenario
• logical view
• type of development
• view process
• physical / deflective performance

IMO, this is a really good structure. However, you do not need to follow this structure in SAD. The purpose of the SAD is to describe information that complements the code, especially how non-functional requirements will be met. Here are some interesting guidelines on what such a document should contain.

You can see the RUP samples: a course registration system and a collegiate sports paging system .