ACRE (Acquisition of REquirements)

ACRE was bounded using a definition which separates acquisition from other
requirements engineering activities. ACRE provides methods for acquiring
requirements from stakeholders, rather than for mining requirements out of
documents (e.g. Goldin & Berry 1994). This is not intended to diminish the
importance of documentation. Indeed, knowledge acquired through communication
will often be interpreted using existing documents or documented rationale, for
political or other reasons. Each acquisition method in ACRE aims to improve
communication between stakeholders. One of the stakeholders must be a
requirements engineer who has been trained in use of that method. However,
ACRE also recognises that requirements acquisition, negotiation and agreement
are often interleaved, so although it provides methods for acquisition,
improvements in requirements negotiation and agreement are unplanned but
welcome. Specific methods and techniques which aim to improve negotiation are
discussed elsewhere (e.g. Boehm et al. 1994).
ACRE proposes methods to acquire both requirements for the software system and
knowledge about that system’s domain and environment. The environment is
described by diverse phenomena in the problem domain such as behaviour,
events, structure and states. This version of ACRE also does not include
participative design (e.g. Clement & Van den Besselar 1993) which necessitates
wider organisational and cultural changes. Rather, it proposes methods which can
be used by practitioners with little training within the existing organisational and
cultural context.
BOEHM B., BOSE P., HOROWITZ E. & LEE M-J., 1994, ‘Software Requirements as Negotiated Win Conditions’,
Proceedings of IEEE Conference on Requirements Engineering, IEEE Computer Society Press, 74-83.
CLEMENT A. & VAN DEN BESSELAR P., 1993, ‘A Retrospective Look at PD Projects’, Communications of the ACM 36(4),
GOLDIN L. & BERRY D., 1994, ‘AbstFinder, A Prototype Abstraction Finder for Natural Language Text for Use in
Requirements Elicitation: Design, Methodology and Evaluation’, Proceedings Ist International Conference on Requirements
Engineering, IEEE Computer Society Press, 84-93.

Reference: Reference: Neil Maiden (2011) Requirements Engineering Lecture Notes

This entry was posted in Acquiring Requirements and tagged , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s