domain analysis document | can help educate other software engineers who join the team later |  |
has part - Introduction, including the name of the domain and the motivation for performing the analysis
- Glossary which gives the meanings of all terms used in the domain that are either not part of everyday language or else have special meanings
- General knowledge about the domain - important facts or rules that are widely known by the domain experts and which would normally be learned as part of their education
- Customers and users - who will or might buy the software, and in what industrial sectors they operate. Also, describe the other people who work in the domain, even peripherally.
- The environment - equipment and systems used
- Tasks and procedures currently performed - what the various people do as they go about their work
- Competing software, including advantages and disadvantages
- Similarities across domains and organizations - what distinguishes the customer's organization from others, as well as what they have in common
|  |
is a subtopic of 4.1 - Domain Analysis |  |
is a kind of document |  |
should contain a brief summary of the information you have found, along with references that will enable others to find that information |  |
should not contain an excessive amount of detailed information |  |
summarizes information found during domain analysis |  |
document | should be written for a particular audience |  |