Creating use cases of project components enables representation of the different use contexts of the system. From a use case, you can describe how a functionality or set of functionalities is implemented within an application or service.

By means of use cases, HOPEX System Blueprint enables addition to description of an application architecture of the detailed specifications of its different sub-systems.

To simplify the identification of an application system use case, you can base your approach on the definition of requirements. Requirements are constraints to be respected within the framework of an application evolution project.