Summary of the article ‘From Conceptual Modelling to Requirements Engineering’
Wrote by the collaboration between Ms Colette Rolland (University of Paris 1 – Sorbonne) and Naveen Prakash (Delhi Institute of Technology Pappankala).

This paper explains methods and process of Requirement Engineering. Traditional Information System engineering is based on a schema which is used for a link between the Universe of Discourse (what the user expect) and the computer application. The schema catches from the real world certain characteristics which are useful.

Technological evolutions and economic pressure often change the. When IS is changing, requirements which is refer are also changing. Many investigations show that one of principals reasons of a project fail is a bad understanding of what we are waiting. Requirement Engineering will focus on the organizational purpose and on what the system must do and in which way. This new approach implies multiples research and analysis of scenarios and alternative where each activity should be justified by a requirement.

Requirement engineering source from the Universe of Discourse that match with what users expect and from constraints imposed by the environment where the system subject is. This both sources are separated in two worlds, Usage World which describe what the system must do (activity) and the Subject World which contains object from the real world. System World made the system concept which respond to requirements of the both discourses worlds. Relationship between Discourses Worlds and System are specialized. Indeed, between Usage World and System World it can differentiate Usage fit relationship and Intentional relationship. Usage fit relationship describe what system users expect. Intentional relationship describes the goal of the stakeholders. Domain genericity relationship is a relation which is often pre-defines and depends on the domain more than the application.

In the Usage World, system’s