Introduction - If you have any usage issues, please Google them yourself
Requirements analysis determined how users will interact with system-to-be (external behavior)
Domain modeling determines how elements of system-to-be interact (internal behavior) to produce the external behavior
Knowledge of how system-to-be is supposed to behave ( requirements analysis, e.g., use cases)
Studying the work domain (or, problem domain)
Knowledge base of software designs
Developer’s past experience with software design