Business modeling with the Unified Modeling Language (UML) provides an approach to modeling business processes using the same language (the UML) software teams use to model systems. By using the same notation across business and system domains, communication between business analysts and software teams is improved, and business considerations are more likely to be included in the system requirements, eventually leading to a better system. The course introduces UML as a business notation and ties business models to system models. Students gain experience in business modeling through a series of group exercises that require the students to model the business processes of a small Real Estate franchise.

back to top

To benefit from this course, it is desirable that students have completed the following courses or equivalents:-

• Essentials of Visual Modelling with UML

back to top

To benefit from this course, students should have the following experience:-

Students should be familiar with the software development lifecycle and the requirements elicitation process

back to top

This course teaches tasks that are part of the jobs for the following team members: Business-Process Analyst, Requirements Specifier and System Analyst.

back to top

This course covers the following topics:-

• Understand the value of business modeling to software teams
• Understand where business modeling applies
• Describe business processes using UML
• Relate business models to system requirements

back to top

This course teaches the following skills:-

• Business Modelling

back to top

This course teaches techniques and skills supported by following tools:-

• IBM Rational Rose
• IBM Rational XDE

back to top

This course consists of the following modules:-

1. Introduction to business modeling
2. Setting the business modeling activity goals
3. Finding business actors and use cases
4. Detailing business use cases
5. Concepts of object orientation
6. Finding business workers and entities
7. Detailing business workers and business entities
8. Defining automation requirements

back to top