As a fundamental component to identifying requirements for a new system, business analysts must be able to illustrate how "actors", such as end users, stakeholders, or related systems, will be affected once the new system is implemented. This process, also known as Use Case Modeling, provides business analysts with a powerful tool for documenting functional requirements-and the interactions between these requirements-in a manner that can be easily communicated to designers, programmers, project manager, and other project stakeholders.

This course provides business analysts with the required competencies for creating use case diagrams and use case scenarios, which serve as a vehicle for eliciting, analyzing, documenting and communicating functional requirements. You will practice creating use cases in the Unified Modeling Language (UML) to graphically represent the interactions between use cases and actors. To fully gain the benefits of UML, you will create use case diagrams through an object-oriented approach, which enables business analysts to sift through the complexity of a system by breaking it down into smaller units.

Take this course and you'll gain more than just the lexicon required for use case and object oriented modeling. Through interactive exercises, you will practice writing the alternate/exception flows, arranging objects into properly named classes, and reading class diagrams. Most importantly, you'll gain the ability to integrate use case modeling within the software development life cycle to ensure that project requirements are accurate, complete, and map to the objectives of the business.

Reminder: Prior to taking this course, you should have acquired the background as taught in How to Gather and Document User Requirements and Process Modeling Management.