In the modern software development lifecycle, the transition from unstructured requirements to structured design is often a bottleneck. Architects and developers spend countless hours analyzing requirement documents to extract nouns, verbs, and relationships to build Unified Modeling Language (UML) diagrams. Visual Paradigm has revolutionized this process with its AI-Powered Textual Analysis tool. This intelligent feature automates the creation of Class Diagrams by parsing natural language descriptions and converting them into visual models.
This comprehensive guide explores how to leverage this tool to bootstrap object-oriented design projects, refine domain models, and accelerate the documentation phase of software engineering.
Key Concepts
Before diving into the workflow, it is essential to understand the core terminology used within Visual Paradigm’s ecosystem and object-oriented design.
- Textual Analysis: A technique used in requirement engineering to parse written descriptions (problem statements) to identify potential software artifacts.
- Candidate Classes: Nouns or noun phrases identified in the text that represent entities, objects, or concepts within the system (e.g., “Customer”, “Order”).
- Class Details: The specific characteristics of a class, subdivided into Attributes (data fields derived from adjectives or possessive nouns) and Operations (behaviors or methods derived from verbs).
- Problem Statement: A high-level description of the application domain that serves as the input for the AI engine.
Comprehensive Guidelines: Generating Your First Diagram
Follow this step-by-step workflow to transform a basic idea into a fully realized UML Class Diagram using Visual Paradigm.

Phase 1: Initialization and Domain Definition
To begin, you must access the tool and define the scope of your software project.

- Launch the Tool: Open the Visual Paradigm desktop application or the online edition. Navigate to Tools > Apps.
- Select the Category: Choose the Software Development category and locate Textual Analysis (usually on page 2). Click Start Now.
- Input the Domain: Enter a specific name or brief description of your system (e.g., “Hospital Management System” or “e-Commerce Platform”).
- Generate Problem Description: Click the generation button. The AI engine will expand your brief input into a coherent, detailed paragraph describing the system’s actors, use cases, and functionality. Tip: Review this text carefully. The accuracy of the diagram depends on the clarity of this description.
Phase 2: AI-Driven Analysis
Once the description is set, the AI performs three layers of extraction.

- Identify Candidate Classes: Click Identify Candidate Classes. The AI scans the text for key nouns. It provides a list of proposed classes along with the reasoning for their selection. Review this list to ensure no non-entity nouns (like “System” or “Database”) are incorrectly classified as domain objects.

- Extract Details (Attributes & Operations): Click Identify Class Details. The tool associates verbs with specific classes to create methods and identifies properties. For example, if the text says “The user enters a password,” the AI adds a
password attribute to the User class.

- Detect Relationships: Click Identify Class Relationships. This step determines how classes interact, identifying associations, aggregations, compositions, and inheritance hierarchies. It also attempts to define multiplicity (e.g., One-to-Many).

Phase 3: Visualization and Refinement
The final phase involves rendering the visual model and integrating it into your workflow.
- Generate Diagram: Click Generate Diagram. The tool places the identified classes and relationships onto a canvas, applying standard UML notation.
- Iterate: If the diagram is missing a feature (e.g., a “Payment Gateway”), edit the problem description to include it and re-run the identification steps. The AI will merge the new requirements into the existing model.

- Export and Edit: For advanced layout changes, open the diagram in Visual Paradigm Online or import it back into the desktop version via Team > Import from Web Diagram.

Practical Example: Library Management System
To illustrate the power of this tool, consider a scenario where we need to model a library system.
Input Description
“A library system allows members to borrow books. The librarian manages the inventory. Each book has a specific ISBN and title. Members must pay a fine if a book is returned late.”
AI Analysis Breakdown
The following table demonstrates how the AI maps textual elements to UML components:
| Text Segment |
Identified Element |
UML Type |
Reasoning |
| “Members”, “Librarian”, “Book” |
Member, Librarian, Book |
Class |
Nouns representing core entities. |
| “borrow” |
borrow() |
Operation |
Action performed by the Member class. |
| “ISBN”, “title” |
isbn, title |
Attribute |
Properties belonging to the Book class. |
| “Members… borrow books” |
Association |
Relationship |
Interaction between Member and Book. |
Resulting Diagram
The tool generates a diagram where Member is associated with Book via a ‘borrow’ relationship, and Book contains attributes for string ISBN and string title.
Checklist for Success
Use this checklist to ensure you are getting the most out of Visual Paradigm’s AI textual analysis.
- [ ] Preparation: Is your initial topic or domain clearly defined?
- [ ] Description Audit: Did you review the AI-generated problem statement for logical flow before starting the analysis?
- [ ] Class Verification: Have you filtered out abstract concepts that should not be classes (e.g., “Information”, “Success”)?
- [ ] Relationship Check: Did you verify the directionality and multiplicity of relationships (e.g., Is a book borrowed by one member or many)?
- [ ] Iteration: Have you re-run the analysis after making manual edits to the text?
- [ ] Integration: Is the final diagram saved to your workspace for team collaboration or code generation?
Why Choose AI-Powered Modeling?
Visual Paradigm’s approach serves as a bridge between abstract requirements and concrete engineering. It significantly reduces the time required to produce initial drafts of architecture. By automating the rote task of identifying nouns and verbs, architects can focus on high-level design patterns and logic. Whether you are a student learning UML or a professional bootstrapping a microservices architecture, this tool provides a robust foundation for object-oriented design.