Tag Archives: UML Modeling

Flashback: This Week in the Past on Tyner Blain [Mar 22]

A look back at the best from this week in the past.

Read the rest of the article …

How To Draw an Asynchronous Process

Documenting processes is something most business analysts have to do. The goal of documenting the process is to communicate requirements. By establishing a shared understanding of the process, you can establish the context for the requirements. Easy processes are easy to draw and understand. When documenting a more complex process, you need to provide the same clarity and consistency. In this article we show how to document asynchronous process steps to maximize the clarity of the documentation.

Read the rest of the article …

APR: Domain Model – UML Class Diagram

Along with design sketches and requirements, as part of the concurrent design and requirements development for our agile project, we have created a UML class diagram representing the domain. This iterative process allows us to incorporate the benefits of each perspective rapidly with the others in our race to prototype a working site.

This article reviews the domain model.

Read the rest of the article …

Use Case vs. UML Statechart – Business Rules

What is the better requirements management model for capturing business rules? The use case, or the UML statechart? In this article, we explore how customer orders are submitted and processed, and contrast how use cases and statecharts expose and document business requirements and business rules.

Foundation Series: Data Dictionary Definition

What is a data dictionary and how is it used when communicating and managing requirements?

Use case series: UML 2.0 use case diagrams

The UML way to organize and manage use cases. Pros Provides a high level view of the use cases in a system, solution, or application. Clearly shows which actors perform which use cases, and how use cases combine to form business processes Cons Presents an “inside-out” view of the sytem. This description reflects “what it […]