adplus-dvertising
frame-decoration

Question

What is the definition of software architecture according to Bass et al., 2003?

a.

The architecture of a software system defines the system in terms of computational components and interactions among those components.

b.

The software architecture of a program or computing system is the structure or structures of the environment, which comprise software elements, the externally visible properties of those elements, and the relationships among them.

c.

The structure or structures of the system that comprise software elements, the externally visible properties of those elements, and the relationships among them.

d.

None of the above

Answer: (c).The structure or structures of the system that comprise software elements, the externally visible properties of those elements, and the relationships among them. Explanation:According to Bass et al., 2003, the definition of software architecture is the structure or structures of the system that comprise software elements, the externally visible properties of those elements, and the relationships among them.

Engage with the Community - Add Your Comment

Confused About the Answer? Ask for Details Here.

Know the Explanation? Add it Here.

Q. What is the definition of software architecture according to Bass et al., 2003?

Similar Questions

Discover Related MCQs

Q. What is the insight reflected in the definition of software architecture according to Bass et al., 2003?

Q. How does the software architecture observe the overall architecture?

Q. In the software architecture, how can the global structure of the system be observed?

Q. What is the purpose of the global structure of the system in software architecture?

Q. How can it be determined if a design decision is major or not?

Q. What is the purpose of separating the user interface from the processing part in a library system?

Q. What is the purpose of storing data about books in a flat file in a library system?

Q. What is the architectural design process about?

Q. What is the goal of the work in software architecture?

Q. What is the difference between the traditional design phase and a "proper" software architecture phase?

Q. What is the focus of the software architecture phase?

Q. What is the outcome of the iterative process between the requirements engineering and software architecture phases?

Q. What is the main difference between the design phase and the software architecture phase?

Q. What is the difference between the requirements engineering phase and the software architecture phase?

Q. What is the difference between the traditional process models and the process models that include a software architecture phase in terms of iteration?

Q. Who are the stakeholders involved in traditional models of software development?

Q. What is the difference between the traditional models of software development and the process models that include a software architecture phase in terms of balancing functional and quality requirements?

Q. In traditional process models, what happens once the functional requirements are agreed upon?

Q. Is there a balancing of functional and quality requirements in traditional process models?

Q. In process models that include a software architecture phase, when does development proceed?