Work with UML's nine diagrams in order to become familiar with how their architecture fits into the development process. Most of your 24 hours will be taken up with this orientation. You will gain the rudiments of the object to orientation relationships, how to work with aggregate and composite information, as well as how to interface information with team members graphically. Choose a case study to apply this information.
Learn how to perform a domain analysis and gather system requirements for your selected case study. The "world" where your case comes from is your domain. If your case comes from a company's quality department, you'd do a quality departmental analysis. The analysis and gathering of system requirements would glean information to pull into a UML diagram. This study takes about seven hours to understand the basics.
Choose a design for your UML diagram depending on the information gleaned from the analysis and system requirements. The last couple of hours learn about embedded systems and the future of UML.