Although related literature uses the term
Requirements Engineering to broadly describe the
requirements process this is not a term frequently
found in industry. As the requirements process is
just one aspect of software engineering it does not
in itself result in the delivery of a fully engineered
product. In this tutorial we therefore follow the
practice adopted in the Guide to SWEBOK
(Software Engineering Body of Knowledge), in
which the term Requirements Engineer is replaced
by the general term Software Engineer [5].
Additional terms such as elicitor, analyst, and
specifier that depict specific roles of the
requirements process are also used.