Model-based testing uses a test model which defines in general an infinite set of correct system runs. The task for the test case generator is to select an ”interesting” subset of all the traces. The way this subset is chosen is defined by the test case specification. Two types are widely used: structural or functional test case specifications. The first is given in terms over the model elements, the later is derived from the underlying system requirements. Whereas structural criteria are easily applicable to any model and support fully automation, functional specifications need more manual definition but are closer to the users' requirements. In this paper we propose a method which combines advantages of both: structural criteria and functional test case specification. Especially it supports automation in large parts but focuses on the users' requirements as well. Furthermore the method provides an easy and flexible adjustment to project-specific needs. By setting up parameters the tester is able to influence the functional focus of the generated tests.