![]() |
subject > process > analysis > domain analysis |
![]() ![]() | ||||
domain analysis | ||||
subject | fact |
domain analysis | allows a software engineer to focus on the most important issues, to make fewer mistakes, and to follow accepted procedures and standards | ![]() |
has definition The process by which a software engineer learns enough background information so that he or she can understand the problem and make good decisions during requirements analysis and other stages of the software engineering process | ![]() | |
enables a software engineer to communicate with the stakeholders more effectively, so he will be able to establish requirements more quickly | ![]() | |
has benefits
| ![]() | |
has risk software developers may make invalid assumptions and hence create poor requirements or design | ![]() | |
indicates opportunities for future development | ![]() | |
is a subtopic of 4.1 - Domain Analysis | ![]() | |
is part of requirements and specification | ![]() | |
is performed before requirements analysis | ![]() | |
is a kind of analysis | ![]() | |
shows software engineer the subtleties of the domain, ensuring that the solutions adopted will more effectively solve the customer's problem | ![]() | |
process | see also process^2 | ![]() |