You have one practice area called Requirements Engineering and another called Understanding Relevant Domains. Whats the difference between requirements analysis and domain analysis?
Remember that a domain is a specialized body of knowledge or area of expertise. Hence, domain analysis explores and captures the knowledge areas key to a product line and therefore tends to be broader in scope than requirements analysis. Requirements analysis usually focuses on specific applications. For example, domain analysis for a product line might identify areas of general commonality and variation across a body of relevant functionality (perhaps by examining and comparing legacy systems that have that functionality). Requirements analysis would identify a specific set of commonalities and variations for the family of products to be built.
Related Questions
- You have one practice area called Requirements Engineering and another called Understanding Relevant Domains. Whats the difference between requirements analysis and domain analysis?
- Are there any special environment requirements for the area where practice will happen?
- Whats the difference between domain analysis and requirements analysis?"
