The Design of Software (CLOSED)

A public forum for discussing the design of software, from the user interface to the code architecture. Now closed.

The "Design of Software" discussion group has been merged with the main Joel on Software discussion group.

The archives will remain online indefinitely.

Definitions of "implementation domain" & "problem domain" ?

I see many articles use the word of "implementation domain" and "problem domain". It sounds like some concept in software design. But I don't know where these word come from and what're their differences?
Fei Xu Send private email
Monday, April 10, 2006
Implementation domain = the world of software / computers.
Problem domain = the world of the user of the application.

You must try and use terms from the problem domain in the user interface / docs.

eg. if you are developing an application to manage forests the word "TreeControl" means something very different to you and the user!

Some people argue that you should use terms from the problem domain even inside the code in function / var names since this gets you closer to the user and better able to understand the problem.
Martin Send private email
Monday, April 10, 2006

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
Powered by FogBugz