Unit Operations: Software Architecture

Separations Uniform Decomposition Abstraction All of the mentioned Separations Uniform Decomposition Abstraction All of the mentioned Modifiability and portability Modifiability and Scalability Portability and Scalability None of the mentioned Decomposition is the operation which places distinct piece of functionality into distinct component Decomposition is the operation of separating a large system component into two or more smaller ones Decomposition is the operation of creating virtual machine None of the mentioned It is the operation which places distinct piece of functionality into distinct component It is the operation of separating a large system component into two or more smaller ones It is the operation of creating virtual machine None of the mentioned Every component in the system can be built only from these sub component Each of the sub component represents a specialization of its parent functionality All of the mentioned None of the mentioned Reliability Performance All of the mentioned None of the mentioned To improve performance To circumvent layering when it does not provide needed services To speed system development All of the mentioned It is an operation that encapsulates either data or services and shares them among multiple independent consumers It is the operation which places distinct piece of functionality into distinct component It is the operation of separating a large system component into two or more smaller ones None of the mentioned Develop Scenarios Describe Candidate Architecture Classify Scenarios All of the mentioned Scenarios illustrate the kinds of activities that the system must support Scenarios illustrate the kinds of changes that it is anticipated will be made to the system All of the mentioned None of the mentioned Description should be done in architectural notation that is well understood by the parties involved in the analysis Description can be done in any notations that are well understood by the parties involved Description may or may not be described in notations that are used for analysis None of the mentioned Direct Scenario Indirect Scenario Forward Scenario Direct & Indirect Scenario For indirect scenario, the changes to the architecture that are necessary for it to support the scenario must be listed Cost of performing the change must be estimated There should be summary table that lists all scenarios (direct and indirect) All of the mentioned It exposes the allocation of functionality to the product’s design It follows a communication path which leads to systems stability It achieves main goal of modifiability None of the mentioned