Visual Modeling uses universally recognizable graphic notations to capture business processes. Visual Modeling helps in the analysis and design of new systems. Visual Modeling can explain complex systems parts by breaking them up into smaller parts called objects. These objects can be combined to build component based reusable systems and architecture.

UML stands for Unified Modeling Language; a visual modeling notation. UML has become the industry standard for capturing systems since 1997 and was developed as a collaborative effort from IBM, Oracle, Microsoft and HP. UML is the standard language for visualizing, specifying, constructing, and documenting life cycle.

UML can be used for:

  • Data Modeling concepts (Entity Relationship Diagrams)
  • Business Modeling (work flow)
  • Object Modeling
  • Component Modeling
Return
UML uses Actors and Use Case to represent a process:
  • Actors are someone or some thing that must interact with the system under development
  • Use Cases are patterns of behavior the system exhibits.
A Use Case is a sequence of related transactions performed by an actor and the system in a dialogue. Actors are examined to determine their needs. A flow of events document is created for each use cases, written from an actors point of view.

Details what the system must provide to the actor when the use cases is executed

  • How the use case starts and ends
  • Normal flow of events
  • Alternate flow of events
  • Exceptional flow of events