For the Smart Home system what are the “hazards?” That is, make a list of what this system shall not do based on these regulations and any other information you have.

==2.1. Why is it important to have a mission statement?
==2.2. What is the relationship of a system mission statement to the enterprise’s mission statement?
==2.3. When should a domain vocabulary be established?

==2.4. Under what circumstances might the customer’s needs and desires be considered secondary?
==2.5. Think of a system or product you use often and try to guess what the mission statement is for that product, or the company that makes it.
==2.6. Search the Internet for the actual mission statement and compare it to your guess. Does such a mission statement exist? If it does exist, how does the actual mission statement compare to your guess?
==2.7. At what stage of the requirements development are additions to the requirements considered scope creep?

==3.1. What are some difficulties that may be encountered in attempting to elicit requirements without face-to-face interaction?
==3.2. Does the Heisenberg uncertainty principle apply to techniques other than ethnographic observation? What are some of the ways to alleviate the Heisenberg uncertainty principle?
==3.3. During ethnographic observation what is the purpose of recording the time and day of the observation made?
==3.4. Should requirements account for future scalability and enhancements?
==3.5. Which subset of the techniques described in this chapter would be appropriate for a setting where the customers are geographically distributed?
==3.6. Investigate the concept of “active listening.” How would this technique assist in requirements elicitation?
==3.7. If you are working on a class project, what selection of the techniques described in this chapter would you use to elicit system requirements from your customer(s)?