Addressing requirements issues within a conceptual modeling environment

The paper takes the position that research on how to formalize informal requirements information is not enough. One must actually identify what tasks the requirements analyst is undertaking, identify the types of knowledge that are being interrelated, and work out the desired relationships, or correspondences, between the various views. To do this, a conceptual modeling environment (ACME) is needed to define the various modeling viewpoints. An example is the definition of functional and architectural requirements and the assertion/retraction of design decisions that assign functions to components.<
>