Solutions: Chapter 1: Software and Software Engineering 1.1) Classic examples include the use of "digital automobile dashboards" to impart a high tech, high quality images. Appliances that "think;" the broad array of consumer electronics; personal computers (today, differentiated more by their software function than the hardware), industrial instrumentation and machines. All e-commerce applications are differentiated by software. 1.2) This is a good problem for classroom discussion (time permitting). Rather than focusing on cliché' ridden (albeit important) issues of privacy, quality of life, etc., you might want to discuss "techno fright" and how software can help to exacerbate or remedy it. Another interesting possibility is to use Neumann's "Risks" column in SEN to key discussion. You might also consider new attempts at software-based ‘cash’ economies, new modes of interactive entertainment, virtual reality, ecommerce, etc. 1.3) It takes software so long to be finished, because of following reasons a) Facilities are not available on line. b) Development tools do not work as expected. c) Customer insists on the new requirements, requiring redesign and rework. d) Product depends on the government regulations that change unexpectedly. e) Strict requirements for compatibility with existing system require more testing, design, and implementation then expected. f) Requirements to operate under multiple operating systems take longer to satisfy than expected. g) Software project risk management takes more time then expected. h) Dependency on a technology that is still under development lengthens the schedule. Development costs are high: a) Unacceptably low quality requires more testing, design and implementation work to correct then expected. b) Development of the wrong software functions requires redesign and implementation. c) Development of the wrong user interface results in redesign and implementation. d) Development of extra software functions that are not require