The Rational Unified Process emphasizes addressing high-risk areas very early, by rapidly developing an initial version of the system, which defines its architecture. It does not assume a fixed set of firm requirements at the inception of the project, but allows you to refine the requirements as the project evolves. It expects and accommodates changes. The process does not put either a strong focus on documents or ‘ceremonies’, and it lends itself to the automation of many of the tedious tasks associated with software development. The main focus remains the software product itself and its quality, as measured by the degree to which it satisfies its end-users and meets its return on investment objective altogether. It is generic enough to be tailored to a wide variety of software products and projects, both in size and application domain and it is centered around three areas: people, process, and tools or methods.