Depending on how technically inclined the audience is, you might want to leave some parts out, and add others. If you show them class models, will they understand? Will they care?
Most of the people that I work with who would count as "upper management" do not care very much about implementation details (it sounds like this is what your presentation focuses on), they mostly will care about:
- introduction and general overview (what is the point of this system?)
- high-level architecture (how is it built - at a high level?)
- user stories (what can a user do with this system?)
- data model (sometimes these are useful/necessary, but it depends on the project)
(I would run the presentation in that order as well)
Some members of the audience might care about the other types of diagrams (probably the use-case diagrams more than the others), and the diagrams can be useful in explaining other parts of the presentation, but I'm not sure I'd launch into them straightaway or make them the focus of the presentation.
Of course, if your audience is highly technical and want to see this kind of info, then go for it! But I'd still start off the presentation with some kind of general overview, just to give some context for the rest of the presentation.