We offer editions tailored to the scale and purpose of your development.
The Professional Edition supports distributed development across multiple teams, while the Enterprise Edition supports product line development and ultra-large-scale development.
In addition, each edition is available in two types: Architect, which allows you to customize the design tool, and Designer, which allows you to design within a customized design tool. Architect is intended for senior designers and process definers, while Designer is intended for design team members on the ground.
* Click here for the differences between the Enterprise Edition and Professional Edition
-
Professional Edition
An edition that supports development across multiple teams.
Equipped with Subversion integration and design file split/merge functions, it provides features to support development by multiple teams across companies and departments.
-
Enterprise Edition
This edition supports variation development for multiple products, ultra-large-scale project development, and organizational operations.
In addition to the features of the Professional Edition, it includes the following capabilities:
- Product line development features supporting variability definition via feature models and product-specific variability switching
- Partial loading feature to improve work efficiency when multiple teams collaboratively develop ultra-large-scale projects
- Organizational profile operation features, such as profile combination, on-site customization, and tracking profile revisions
- 3-way merge feature that allows you to resolve conflicts by reviewing changes when merging during distributed development
Feature List
This is a feature list by edition for the latest version of Next Design.
| Category | Features | Description | Pro | Ent |
|---|---|---|---|---|
| Meta-model definition *1 | Add and remove entities | Allows you to add and remove entities. | ◯ | ◯ |
| Add and remove elements from entities | Allows you to add and remove fields from entities. | ◯ | ◯ | |
| Define relationships between entities | Allows you to define relationships (such as traceability links) between entities. | ◯ | ◯ | |
| View definition *1 | Document | Provides document-style representation similar to Word. | ◯ | ◯ |
| Tree Grid | Provides tabular representation similar to Excel, allowing you to view design information hierarchically. | ◯ | ◯ | |
| ER Diagram | Provides a high-level overview of relationships between design information using diagrams. | ◯ | ◯ | |
| Tree Diagram | Allows you to selectively collapse tree-structured design information, helping you focus on the specific areas you want to review. | ◯ | ◯ | |
| Sequence Diagram | Displays interactions between design information in a chronological format. | ◯ | ◯ | |
| Custom shapes and icons | Allows you to customize the visual appearance of design information using custom images. | ◯ | ◯ | |
| Profile Usage *1 | Modularizing Profiles | You can export and package profiles. | ◯ | ◯ |
| Importing Profiles | You can import copies of modularized profiles into projects for reuse. | ◯ | ◯ | |
| Profile Reuse (Reference, Customization, and Updates) | You can customize modularized profiles by referencing them and track profile updates. | – | ◯ | |
| Standard diagram support | UML/SysML | Supports UML/SysML-compliant representations such as requirement diagrams, structural diagrams, and behavioral diagrams. | ◯ | ◯ |
| Mind Map | Supports mind maps as a structured way to organize thoughts. | ◯ | ◯ | |
| GSN (Goal Structuring Notation) | GSN can be expressed that can be used to describe a dependability case. | ◯ | ◯ | |
| Flowchart | Represents sequential processes and workflows using flowcharts. | ◯ | ◯ | |
| PFD (Process Flow Diagram) | The diagrammatic method for process design, PFD, can be expressed. | ◯ | ◯ | |
| Model Editing | Unlimited undo and redo | There is no limit to the number of input operations, and you can undo and redo your work. | ◯ | ◯ |
| Model editing via drag and drop | Shapes can be placed and moved using mouse operations. | ◯ | ◯ | |
| Editing support such as quick styles, search, and replace | Edit models and their visual appearance intuitively and efficiently. | ◯ | ◯ | |
| Traceability view between editors | Display traceability for design information between main and sub-windows. | ◯ | ◯ | |
| Batch editing of models | Edit information for selected models in bulk. | ◯ | ◯ | |
| Traceability | Traceability Tree | Display cross-model trace information in a tree format for a comprehensive overview. | ◯ | ◯ |
| Filtering of trace information | Filter the displayed items to check traceability with high visibility. | ◯ | ◯ | |
| Traceability matrix | Display trace information between models in a matrix format to verify coverage. | ◯ | ◯ | |
| Traceability report | Export traceability data to an Excel file in a tabular format. | ◯ | ◯ | |
| Excluding items from tracing | When trace information is not linked, you can enter the reason for exclusion. | ◯ | ◯ | |
| Document export | Word export | Export design information as a Word document. | ◯ | ◯ |
| HTML output | Design information can be documented as HTML files. | ◯ | ◯ | |
| PDF output | Design information can be documented as a PDF file. | ◯ | ◯ | |
| Image export | Export design information as an image file. | ◯ | ◯ | |
| Team development | Splitting into multiple files | Design files can be split into arbitrary units (e.g., per design assignment). | ◯ | ◯ |
| Merging Split Files | Split design files can be merged. | ◯ | ◯ | |
| Partial Loading of Model Files | Only the model files specified when opening a project can be loaded. | – | ◯ | |
| Configuration Management Tool Integration | Integrates with configuration management tools to handle lock control directly within NextDesign. | ◯ | ◯ | |
| Model Difference Display | Displays differences between project files before and after changes, or between arbitrary revisions. | ◯ | ◯ | |
| Extensions | Extension Development | Extensions can be developed using languages such as C# and JavaScript. | ◯ | ◯ |
| Extension Execution | Extensions can be loaded and executed within NextDesign. | ◯ | ◯ | |
| Extension execution via CLI | Extensions can be executed using command-line tools. | ◯ | ◯ | |
| Distribution via Packages | Extensions and profiles distributed via the cloud can be downloaded. | ◯ | ◯ | |
| Product Line Development | Feature Model Definition | The relationships between features across products can be modeled using tree-structured diagrams. | – | ◯ |
| Registration and Derivation of Multiple Products | Product lines can be defined, and features to be used can be assigned to each product. | – | ◯ | |
| Variant Assignment to Design Data | Features can be linked to design information using drag and drop. | – | ◯ | |
| Design Data Export | You can export the design information of the fixed products. | – | ◯ | |
| Git Integration | File Format Switching | You can choose between binary and human-readable file formats. | ◯ | ◯ |
| Logical Model Merging *2 | You can merge models while maintaining logical consistency using a dedicated merge tool. | ◯ | ◯ | |
| Git Operations in Next Design *2 | Basic Git commands such as commit and push can be executed directly from Next Design. | ◯ | ◯ | |
| Conflict Resolution via 3-way Merge *2 | Even if conflicts occur, you can resolve them using a 3-way merge within Next Design. | – | ◯ |
*1 Architect only
*2 Requires extension features or provided tools