(300 words, less than one page)
Defining software quality To begin this course, this reading introduces you to the broader ideas behind the topic of software quality and provides some initial perspectives on why quality is hard to measure, and how software engineers have approached this tough measurement problem. You will also learn that there is no single, universal definition of software quality, and the concept is used with varying meanings in different situations.

To read Each week of the semester, you will have a reading assignment to complete that includes a brief written response to two questions based on the reading.

• [required] Robert Glass. The link between software quality and software maintenance

. Software Conflict: Essays on the Art and Science of Software Engineering, Prentice-Hall, 1991, pp. 49-51.

• [required] Robert Glass. Can you MANAGE quality into a software product?

Software Conflict: Essays on the Art and Science of Software Engineering, Prentice-Hall, 1991, pp. 147-149.

• [required] Roger S. Pressman. Chapter 14: Quality Concepts

. Software Engineering: A Practitioner’s Approach, 7th ed., McGraw-Hill, 2010, pp. 398-415 [can also use 8th edition].

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. Robert Glass does not include all of the quality attributes that are in McCall’s list of quality factors. Do you believe the extra attributes in McCall’s list are necessary for “quality” software, or is Glass’ definition sufficient? Justify your answer.

2. In Glass’ definition, which single attribute do you believe is most important, and why?

Defining software quality
To read
To turn in