How RUP describes software architecture? What is the relation between RUP and software architecture?

Question

I'm looking for articles or documents which describes software architecture from RUP point of view.

Do you know any document ?

Answer 1

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

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

This typically includes identifying and documenting the architecturally significant aspects of the system, including requirements, design, implementation, and deployment "views" of the system.

Then, RUP has an artifact called sofware architecture document (SAD):

The Software Architecture Document provides a comprehensive architectural overview of the system, using a number of different architectural views to depict different aspects of the system.

The system is "sliced" and document using different views. Philippe Kruchten, director of process development, popularized the 4+1 architectural view model. The views are:

• use case/scenario
• logical view
• development view
• process view
• physical/depoyment view

IMO, this is indeed a good structure. You don't need however to necessary follow this structure in the SAD. Purpose of the SAD is to describe information complementary to the code, especially how non-functional requirements will be met. Here are interesting guidelines about what such a document should contain.

You can have a look at the RUP samples: course registration system and collegiate sport paging system.