There are some practical problems with UML complexity
and lack of unified method or framework for requirements
engineering [9]. Practitioners and scientists propose
different approaches for eliciting and analyzing software
requirements. The most popular tools that are used in
modern requirements analysis is use cases. It was adopted
by numerous companies, and described in requirements
engineering textbooks [10, 11]. UML provides Use Case
diagram for visualizing use case analysis artifacts.
However, requirements analysis is not limited to use cases.
In fact, they capture only end user-level functional
requirements. A lot of research is also made in specifying
business goals and processes, performing domain analysis.
Although it was shown that UML might be extended and
used for business modelling, the business modellers’ community was not satisfied by UML, and created a new
Business Process Modelling Notation (BPMN), which has
become OMG standard as well. In many cases, they also
apply Integration Definition for Function Modeling
(IDEF) notations [12, 13]. In domain analysis, analysts
continue to apply old-style Entity Relationship (ER)
notation, which was popular in database design since 70s
[141]. A significant attention is paid to business goals,
business rules, business object lifecycles, business roles
and processes in organization, which also can be done
using UML [15, 16].