• English
  • Project Info · MVC Design Pattern

    Project info is the basic building block of the platform — each project is a software system. The main requirements of a project are functional descriptions and non-functional descriptions, which can be decomposed into the three parts of the classic MVC (Model-View-Controller) design pattern.

    Three Main Components

    Data Model (Model)

    Corresponds to database structure

    The data model is the database structure of the project, including data tables and data fields:

    • Table Definitions: Database tables corresponding to each functional module
    • Field Definitions: Field names, types, constraints, etc.
    • Relationships: Primary keys, foreign keys, table relationships

    Data models can be created automatically by AI or connected to existing data sources.

    Interface Model (View)

    Corresponds to functional menus and pages

    The interface model includes the functional menu tree and the interface design implementation for each menu:

    • Menu Tree: The navigation structure of the system
    • Page Design: Layout and interaction for each page
    • Component Configuration: Settings for forms, lists, detail views, and other components

    Users can modify and design the system based on functional menus.

    Project Code (Controller)

    Corresponds to backend logic control

    Project code is the backend logic control service of the project:

    • API Routes: Definition and implementation of RESTful APIs
    • Business Logic: Data processing, validation, transformation, etc.
    • Tech Stack Engineering: Compilable and runnable, with log viewing

    MVC Collaboration

    ┌──────────────┐      ┌──────────────┐
    │   View       │ ←──→ │   Model      │
    │  (Interface) │      │  (Data)      │
    └──────┬───────┘      └──────┬───────┘
           │                     │
           │    ┌──────────────┐ │
           └───→│  Controller  │←┘
                │  (Code)      │
                └──────────────┘
    • The view presents data and receives user operations
    • The controller handles business logic and coordinates data read/write
    • The model stores business data and supports system operation
    Tip

    Understanding MVC layering helps you precisely locate issues during modification iterations: interface issues → adjust the view, data issues → modify the model, logic issues → fix in the controller.