Compare and contrast problem domain and solution domain. What ...

[fnuegbu]

Compare and contrast problem domain and solution domain.
 
  What will be an ideal response?

Question 2

There was a time when software development was coding and nothing but coding, but as software and expectations from software grew more complex ________.
 
  A) the cost of development increased
  B) this narrow approach started to result in unreliable products
  C) the cost of development decreased
  D) more people became interested in software development

[fffftttt]

Answer to Question 1

The problem that is to be solved does not exist in a vacuum, but in a context called the problem domain. Medicine provides a ready example. To a patient, a headache is a problem, but the doctor must treat it as a symptom of the real problem. The doctor would be very negligent to prescribe aspirin for every headache, regardless of whether the root cause is listening to loud music or something less benign or even life-threatening. In building a solution, we also create a new and distinct context called the solution domain. This context contains elements that can be unrelated to the problem but are needed to support the purpose and the functionality of the solution: most cars have fans to cool down the engine, even though the heat produced by the engine has no connection to the transportation for which the car is built. (Similarly, the fans in computers are not related to computing.)

Answer to Question 2

B