Initial software quality requirements tend to be imprecise, subjective, idealistic, and context-specific. An extended characterization of the common Softgoal concept is proposed for representing and reasoning about such requirements during the early stages of the requirements engineering process. The types of information often implicitly contained in a Softgoal instance are highlighted to allow richer requirements to be obtained. On the basis of the revisited conceptual foundations, guidelines are suggested as to the techniques that need to be present in requirements modeling approaches that aim to employ the given Softgoal conceptualization. (Accepted for presentation at the 25th Int. Conf. on Conceptual Modeling, Tucson, Arizona, Nov. 2006; and for publication in the conference proceedings.) 1 Dealing with Software Quality Requirements Ensuring the quality of software has become a major issue in software engineering research and practice since the 1970s [5]. As increasingly complex s...