Scott Ambler lists 35 modeling artifact types with examples. He indicates if the technique is simple enough for stakeholders to learn, whether it is usually a paper-based artifact, whether he suggests creating it on a whiteboard, and what type of software he would consider using to create and maintain it.
Don’t jump to conclusions reading the simple looking indicators Scott Ambler added.
For example, creating artifacts on whiteboards might suggest a brainstorming type of meeting where the drawings are created in front of stakeholders. In that context I have strong reservations on the marking of all the UML2 artifacts for creating on a whiteboard. When you examine the markings set by Scott Ambler closely however, you’ll see that he marks all UML2 artifacts as NOT simple enough for stakeholders. So it’s OK for team members to explain to each other concepts on the whiteboard, but it’s NOT OK to use them in brainstorming sessions with stakeholders. That’s what Scott Ambler says, when you read carefully!