System behavior description using states faces problems like state explosion, lack of clear definition of state, state identification and coordination between multiple agents. The goals of this work are to ease design activity, to reduce engineering efforts, and to mitigate project risks. The proposed way is to improve information flow during design by adding definitions and some protocols or rules for communicating a specification or design description. This work presented an objective definition of system status (way of interaction with the rest of the world) along other concepts. This work focused in definitions as mind entities and their importance to rationalize work and mitigate project risks during design. This article presented some simple examples to illustrate the advantages of each aspect of proposed definition of system status and discussed limits and exceptions for such definition. The key finding was the proposed definition which was the simplest while keeping completeness at a given product breakdown level. Such definition of status enforced formal segregation of needs and solutions, and eased the inclusion of behavior definition in specifications.