Inception/Business Modeling/Requirements Engineering: The KAOS approach (Goal-oriented)

https://en.m.wikipedia.org/wiki/KAOS_(software_development)

Quoting:
"KAOS, is a goal-oriented software requirements capturing approach in requirements engineering.
It is a specific Goal modeling method (as the  i* or I Star is).
It allows for requirements to be calculated from goal diagrams.

KAOS stands for Knowledge Acquisition in automated specification or Keep All Objectives Satisfied.

The University of Oregon and the University of Louvain (Belgium) designed the KAOS methodology in 1990 by Axel van Lamsweerde and others (...) for capturing software requirements."

A tutorial can be found here:
http://www.objectiver.com/fileadmin/download/documents/KaosTutorial.pdf

Inception/Business Modeling/Requirements Engineering: i star framework?

A framework that could be especially suited for an inception phase of a system is i star:
https://en.m.wikipedia.org/wiki/I*

Quoting:
"i* (pronounced "i star") or i* framework is a modeling language suitable for an early phase of system modeling in order to understand the problem domain.

i* modeling language allows to model both as-is and to-be situations.

The name i* refers to the notion of distributed intentionality which underlines the framework. It is an approach originally developed for modelling and reasoning about organizational environments and their information systems composed of heterogeneous actors with different, often competing, goals that depend on each other to undertake their tasks and achieve these goals.

It covers both actor-oriented and Goal modeling.

i* models answer the question WHO and WHY, not what.

In contrast, the UML Use case approach covers only functional goals, with actors directly involved in operations (typically with software) [the what part, including functional requirements].

The KAOS approach covers goals of all types but is less concerned with the intentionality of actors.'"