Despite the fact that many of the people working on the UML Profile for Systems Engineering talked about using models to discover system requirements, most of the methodologies and tutorials talk about interfacing with textual requirement management tools like DOORS and importing and exporting requirements to and from models captured in modeling tools. While some think this is a deficiency in UML or SysML, the language is not the problem. The way the language is being used – i.e. the methodology is the problem. You could no more craft good textual requirements if I just offered you an English language dictionary than you could create good model-based requirements if I handed you a UML specification. In this tutorial we will explore not only a modeling language but a method for using it to document and manage requirements. Requirements that consist of only written statements can be confusing. Visualizations that can be referenced by text greatly improve understanding and help to solve communications problems with stakeholders.