Traditionally system development starts with the specification of system requirements. The focus of such an approach is on the system under construction, which is considered as of primary importance to the development success. The major problem with such an approach, however, is the neglect of concerns held by the various system stakeholders, whose opinions, loyalties and fears may impact considerably the perception and the reception of the implemented system, its functions and its features. Typically, stakeholder concerns are not collected or identified, and are viewed as of little significance in the system development process. In this paper, however, we present the case for recognising the value of stakeholder concerns, and their use in aligning business needs with system requirements. We describe a method of gathering and analysing stakeholder concerns across an application domain, and then packaging the development experience in dealing with these concerns into patterns. Experience patterns can subsequently be used to guide systems analysts in selecting the most appropriate requirements for the target stakeholder community.<br /
