6. Conclusion

Conceptual modeling remains relevant for specifying "what the system must do" in precise terms that enable its implementation. However, it is insufficient for reasoning about "what the system should be used for" and helping IS project stakeholders understand their wishes, desires, and needs, as well as the implications of these for the requirements imposed on the IS.

The article introduced a goal-driven requirements engineering approach that allows the "why" question to be explored in a systematic and participatory manner, resulting in a consensus-based requirements document validated by all stakeholders, which serves as the starting point for IS conceptualization.

The approach was illustrated by a case involving hotel room reservations.

The goal-based approach presented in the article can be applied in contexts...