The concept of concern is used in Enterprise Architecture (EA) to express a stakeholder's area of interest in a system whose architecture is to be described. Many EA-related problems are rooted in weak stakeholder orientation. We propose an approach to explicitly model stakeholders' concerns as part of an architecture description. Our contribution is a modeling notation for concern elicitation and a method for concern identification. Our approach is based on goal-oriented requirements engineering and is compatible to the conceptual framework of the ISO 42010 international standard. We claim that our approach allows for a more thorough understanding of stakeholders' concerns and facilitates a stronger stakeholder orientation in EA.    «

The concept of concern is used in Enterprise Architecture (EA) to express a stakeholder's area of interest in a system whose architecture is to be described. Many EA-related problems are rooted in weak stakeholder orientation. We propose an approach to explicitly model stakeholders' concerns as part of an architecture description. Our contribution is a modeling notation for concern elicitation and a method for concern identification. Our approach is based on goal-oriented requirements engineerin...    »