Short answers (300 words)

Software architecture We began last week by talking about definitions of quality, and now we are going to begin discussing design and how design affects quality. Software Architecture is a popular topic in software design, and having the right architecture for the problem at hand can make a huge difference in product quality. This week we will begin with an overview of software architecture, which will frame a few design case studies we will examine this semester.

To read • [required] David Garlan and Mary Shaw. Sections 1-3. An

Introduction to Software Architecture, Carnegie Mellon University, Tech Report CMU-CS-94-166, 1994, pp. 1-15.

• [required] Nenad Medvidovic and Richard N. Taylor. Separating fact

from fiction in software architecture. In Proceedings of the Third

International Workshop on Software Architecture, ACM Press, 1998, pp.

105-108.

• [optional] George H. Fairbanks. Chapter 1. Just Enough Software Architecture [textbook]. Marshall & Brainerd, 2010, pp. 1-11.

To turn in Prepare a brief (no more than one page) written answer to the following two questions. Write up your answer using MS Word or LaTex. One well- presented paragraph for each question is sufficient.

1. What are the important similarities and differences between an "architectural style" and a "programming paradigm" (like functional programming, logic programming, dataflow, etc.)?

2. How do you think "architectural style" affects software quality?